Documentation mapping to schema
An operator's documents can have no path to a queryable record
An operator holds what they know in documents. The facts are on the page, in prose and tables and appendices, and nothing downstream can query a page. Someone re-keys them, or nobody does.
Source documents become schema-conforming records an operator can query, checked by an independent critic before a person reads them, and every correction the operator makes teaches the next render.
The scattered mark is the problem the run starts from. Every tool sits off the route it drives, glyph and name, and opens its own page. A diamond is a decision the work cannot pass without today, with no tool yet doing it. The accented mark near the end is the named solution, into Solutions; the line beneath it is the outcome the run closes on.
Source documents are profiled, rendered against the target schema, criticised, and corrected by the operator, whose corrections return as learning.
Each step in the order it runs, and where one stops before the next begins.
- 01RECORDSOURCE DOCUMENTS A record the run reads, writes or hands on.Nothing in this run reaches it. Hands on to SCRIBE.
- 02SUBSTRATE · toolMANIFOLD Model calls.Nothing in this run reaches it. Hands on to SCRIBE.
- 03RUN · toolSCRIBE The whole loop, profile, propose, critic, render.Reached from SOURCE DOCUMENTS, NOT MECHANISED YET, MANIFOLD. Hands on to SCHEMA-CONFORMING RECORDS.
- 04RECORDSCHEMA-CONFORMING RECORDS A record the run reads, writes or hands on.Reached from SCRIBE. Hands on to OPERATOR.
- 05RECORD · personOPERATOR The run passes through a person here, not around them.Reached from SCHEMA-CONFORMING RECORDS. Hands on to NOT MECHANISED YET.
- 06RECORDNOT MECHANISED YET A record the run reads, writes or hands on.Reached from OPERATOR. Hands on to SCRIBE.
- 01picked upSCRIBE SOURCE DOCUMENTS.Matter the run starts from. No member of the suite put it there.
- 02hands onSCRIBE → OPERATOR Profile → propose → critic/evalua….Profile → propose → critic/evaluate → render (P0 pipeline order).A step following the one before it.
- 03parks hereOPERATOR NOT MECHANISED YET.Correction (accept/edit/reject and rationale).Nothing later in this run reads it, so this is where that branch of the run stops.
- 04nothing crossesOPERATOR → SCRIBE Correction (accept/edit/reject an….Correction (accept/edit/reject and rationale).This hand-off is not mechanised yet. A person notices, or nobody does.
- 05hands onMANIFOLD → SCRIBE hands on.A step following the one before it.
Source docs → profile is internal to Scribe, not a cross-tool handoff; the operator correction loop is a signal append (accept/edit/reject + rationale + embedding, into the tenant-gated Postgres correction store); corpus learning is a contract read (retrieval reads the corpus's own declared state at the next render, nothing is sent).