Module 8 · Track B: The N+1 Document

8.1 · Add the next document

Prompt

Here's one new document. Figure out where it fits in the existing ontology, make a targeted edit to the right metric/entity/notes — not a rebuild — and open a focused change describing exactly what changed and why. Don't touch unrelated files.

You’ll see: the new document slot in via a small, reviewable change. The model evolves continuously; every change is diff-able and auditable.

8.2 · Consume & maintain

Prompt

Expose these metrics as a stable surface callable from BI or via API/MCP, and describe an agent that watches for new documents or schema changes and proposes an ontology update automatically.

You’ll see: the ontology become a reusable, self-maintaining layer other tools can build on.

Then close the loop: re-ask your Module 1 baseline with the ontology attached.

Prompt

[Your Module 1 baseline question, exactly as you asked it cold.] Note which definition you used and show the SQL.

✅ Checkpoint

Document N+1 produced a targeted edit, not a rebuild — and unrelated files were untouched
You know how the metrics get consumed downstream (BI, API/MCP) and watched for staleness

Track B: Validate & Govern Role-Based Access

​8.1 · Add the next document

​8.2 · Consume & maintain

​✅ Checkpoint

8.1 · Add the next document

8.2 · Consume & maintain

✅ Checkpoint