docs: add build registry fit guide from Angus reel

[jhillbht]

Summary

• add a new source-grounded doc translating Angus The Tech Bro's "full system" reel into Organized Codebase terms
• compare the reel's durable registry + specialized agents + scope/plan/build/test loop against OC's current README, docs, and verification model
• update the README to make the registry-backed advanced mode discoverable without turning it into the default story

Source + ingest receipts

• Source reel: https://www.facebook.com/reel/1690425296055493
• Jockey knowledge store: Organized Codebase References (ks_01a00589-1fe8-7292-8719-5239c71e9da5)
• Asset: 6a8064a8c8c4dec35fbceac6
• Item: ksi_01a00589-4c33-7082-aeb7-d2f376ff9159
• Response: resp_01a0058a-4127-7f23-bd16-c38c2d130db4
• Local manifest: /Users/claw/.openclaw/workspace/memory/ingests/facebook/1690425296055493_2026-08-15_organized-codebase-references/manifest.json

Comparison highlights

The reel argues for:

• durable state instead of ad hoc prompting
• a registry of work objects (tools / workflows / skills / apps / issues)
• narrow agents/skills
• an explicit scope -> plan -> build -> test loop
• human oversight as a feature, not a failure mode

This PR documents that Organized Codebase already matches the loop / verification / human-in-the-loop parts well, but does not yet teach a crisp advanced-mode story for persistent shared state. The new guide frames that as an optional build-registry layer rather than a new default requirement.

Verification

• git diff --cached --check ✅
• npm install --package-lock=false ✅ (required to install deps locally because npm ci currently fails against lockfile drift)
• npm test ⚠️ fails on current branch with a pre-existing runtime issue in src/utils/booster-utils.js (TypeError [ERR_INVALID_ARG_TYPE]: The "original" argument must be of type function via promisify(...)), unrelated to this docs-only change

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 1c73d8b6c3

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

[chatgpt-codex-connector]

Point the agent-role reference at an existing document

This newly added guide cites DOCUMENTATION/GRAPH-ENGINEERING-ORGANIZED-CODEBASE-FIT.md as an existing example, but that file is absent from the commit and repository history; a repo-wide filename search found only DOCUMENTATION/GRAPH-ENGINEERING-VERIFICATION-PLAYBOOK.md. Readers following this reference therefore cannot inspect the supporting documentation, so the path should be corrected to the intended tracked file or removed.

Useful? React with 👍 / 👎.