aibook console

publishing state admin HEAD · 57c3077 · projected 2026-10-26T14:53:46Z

What this page is

The operator's view of the books: the editions each one has, where each edition is published, and what is actually served. It is not the reading surface. The book a reader reads is the application at aibook[-stg].ocooee.com; this dashboard describes it and never renders a chapter.

Identity is the gate's, not this page's: the suite session in front of /book/ decides who may load this document, and a static page cannot read that credential — so it does not claim to. Every row below is a projection of config/books.yaml, the same row the builds read.

The shelf

BookStatusPublic editionPrivate edition Application host (prd / stg)Public projectConsole project
The DevOps Engineer's Guide to Effective AI Usage
guide
publishedpublished · 3 page(s) · base /not served · 4 page(s) built, no reader route yet (plan)aibook.ocooee.com
aibook-stg.ocooee.com
ocooee-aibook
ocooee-aibook-stg
ocooee-aibook-console-prd
ocooee-aibook-console-stg

How publishing works

EditionTriggerDestinationWhat proves it
publicmain push · v* tag the book's own Pages project, base / make validate · the deploy's audio + player-config assertions
privatenot published built to site-private/ only — no host, no project, no route make build-private · make check-edition-separation
this dashboardthe same deploy run ocooee-aibook-console-{stg,prd} at /book/ make console-dashboard · the anonymous 302 to the door

Why the console is not the book

The book was served here once: a MkDocs site mounted at /book, with the console's session as its only gate. That put a reader's navigation inside an operator console, made the book's own address a console path, and — because a Pages project's *.pages.dev origin is public — left the private edition readable by anyone who knew the project name. The decision record is console-is-not-a-book-host.md; the split follows mail's.