docs: Add Meta-Boundary guide to clarify Application vs Tooling domains

This commit is contained in:
2026-03-02 12:44:34 -05:00
parent 9eabebf9f4
commit 5b3c0d2296
3 changed files with 36 additions and 0 deletions

View File

@@ -6,6 +6,7 @@ To serve as an expert-level utility for personal developer use on small projects
## Architecture Reference
For deep implementation details when planning or implementing tracks, consult `docs/` (last updated: 08e003a):
- **[docs/guide_architecture.md](../docs/guide_architecture.md):** Threading model, event system, AI client, HITL mechanism
- **[docs/guide_meta_boundary.md](../docs/guide_meta_boundary.md):** The critical distinction between the Application's Strict-HITL environment and the Meta-Tooling environment used to build it.
- **[docs/guide_tools.md](../docs/guide_tools.md):** MCP Bridge, Hook API, ApiHookClient, shell runner
- **[docs/guide_mma.md](../docs/guide_mma.md):** 4-tier orchestration, DAG engine, worker lifecycle
- **[docs/guide_simulations.md](../docs/guide_simulations.md):** Test framework, mock provider, verification patterns