-
Notifications
You must be signed in to change notification settings - Fork 0
Explanation
github-actions[bot] edited this page Jun 13, 2026
·
7 revisions
Background and rationale — why the harness works the way it does. These pages give the reasoning behind the design; the load-bearing calls themselves are recorded as Decisions, and the structural map is under Architecture.
- Product intent — what problem the harness solves and for whom.
-
Auto-detect + auto-configure — why first-session config proposes-then-approves, and why it lives in
project.json. - How the pieces fit — the narrative of how phases, adapters, templates, and scripts interact.
- GitHub Projects integration — why and how the harness writes to ProjectsV2.
- Auto-orchestration — why the memory skills became a push surface, and how the briefing + idle chain + phase dispatch never nag.
- Single-repo state mode — how the harness degrades gracefully to repo-local state when no vault is reachable.
Decisions · Architecture · Designs · Home