Skip to content

docs: DISCOVERY-MAP D-OGAR-DOC-LAYER entry (charter #191 follow-up) #193

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
AdaWorldAPI merged 2 commits into from
Jul 13, 2026
Merged

docs: DISCOVERY-MAP D-OGAR-DOC-LAYER entry (charter #191 follow-up) #193

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
123d67d
docs: DISCOVERY-MAP D-OGAR-DOC-LAYER entry (charter #191 follow-up)
claude Jul 12, 2026
6d0825a
Merge main into claude/happy-hamilton-0azlw4 — resolve DISCOVERY-MAP …
claude Jul 13, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
22 changes: 22 additions & 0 deletions docs/DISCOVERY-MAP.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -1276,3 +1276,25 @@ isolation. The map's job is to keep them visible.
(semantics unruled). This is an offline BAKE (BOOTSTRAP-OK, envelope
owner 0), not an online write. Cross-ref D-EXEC-ONE-ACTION,
D-KAUSAL-CONSUME-PIN-ODOO, OGAR-TRANSPILE-SUBSTRATE (pull-back contract).

- **D-OGAR-DOC-LAYER** (2026-07-12; [S] — spec, council-pending): `ogar-doc`
is the document persistence + reconstruction layer over `ogar-ocr` (the
shipped 14-cap `ocr_actions` table). It PERSISTS a `doc.v1`: the **raw bytes
as a KV reference** (the `document` node value = `{sha256, kv_key, mime,
counts}`, never the bytes — raw lives in the consumer's blob store) + the
**awareness as a GUID-keyed SoA subtree** (page / region / table-cell / field
nodes, each a facet on the 4+12 register the ClassView projects). It
RECONSTRUCTS via a `reconstruct_document` ActionDef — walk the awareness
subtree, bind a template (`ogar-render-askama` + the proven
`tesseract-ocr-pdf::render_searchable_pdf` brick), re-emit a PDF; mutate a
field node + re-fire ⇒ the document re-issues with updated knowledge (the
operator's Spire.Doc-style headline). This FIRES the v2-deferred `typed_field`
mint (0x080A reserved — the trigger recorded in the OCR-ACTIONS-V2 D-entry) + adds a
`document` mint (0x080B); three facts-only ActionDefs (`persist` / `read` /
`reconstruct_document`, External kausal). Consumers inherit it via the classid
Comment on lines +1293 to +1294

@chatgpt-codex-connector chatgpt-codex-connector Bot Jul 12, 2026

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 Badge Keep ActionDef names aligned with the charter

The charter this entry points to names the facts-only capabilities persist_document, read_document, and reconstruct_document in docs/OGAR-DOC-LAYER-PROPOSAL.md D4, so recording persist / read here as ActionDefs creates a conflicting canonical name for future implementers following the discovery map. Please use the charter’s exact names here to avoid minting or documenting the wrong predicates later.

Useful? React with 👍 / 👎.

membrane (`lance_graph_contract::ogar_codebook::canonical_concept_id`) — no
per-consumer `tesseract-ogar` dep, dodging the customer-binary dep-graph
landmine. OGAR-AS-IR §3 + SURREAL-AST-TRAP-PREFLIGHT answered in the charter.
Charter: `docs/OGAR-DOC-LAYER-PROPOSAL.md` (merged #191). Grade [S] until the
5+3 council + a probe promote it; the canon mints (0x080A/0x080B) land WITH
the council-verified build, never ahead of it.
Loading