This is the publication side of the GEO programme. An intervention identifies content that ought to exist — a gap in what the engines can cite, an outdated page they keep quoting — and the document written in response lands here.
Why a separate application
In the GEO console a published document is a row in a vector index: it exists to ground the next answer, and it is read by a retriever, not a person. That is the right shape for retrieval and the wrong shape for review. Nobody can browse a vector store, and the metadata table beside it holds titles without bodies.
So the library is its own application, with its own SQLite database. Documents are readable, searchable, editable and versioned, and each one keeps the intervention and the question it came from.
What the states mean
- Draft — written, not submitted. Visible only in the admin screen.
- In review — with a reviewer. Waiting is a normal state, not a fault.
- Approved — signed off, not yet released.
- Live — the only state the public pages render.
- Archived — withdrawn, and kept. Withdrawing a document does not destroy it, but it does stop it being served.
Provenance is not decoration
Content produced to move a specific answer can only be judged next to the question it was answering. Every publication therefore stores the originating intervention, question and run id, and the article page shows them. A document whose origin cannot be named is one nobody can audit.
What is not here yet
Automatic import from the GEO app. The seam exists at /api/sync and reports itself as unavailable with a reason rather than returning an empty success. Documents are created here in the meantime.