How this harness ports the philosophy of nrslib/takt — an AI Agent Orchestration Framework — including Faceted Prompting, Output Contracts, Worktree Isolation, and the 8 design principles, onto Claude Code's skills + agents + handoff dir without using the takt CLI itself.
The post-rebuild directory layout under ~/.claude/, and the criticality-driven 3-tier delivery rule that splits how each facet reaches the agent, explained with real examples.
A dictionary-style walkthrough of the responsibilities and boundaries of every rules / skills / agents / hooks / output-contracts / knowledge facet file, with real-code excerpts.
An explanation of Faceted Prompting — an organizing axis that splits prompts into Persona / Policy / Instruction / Knowledge / Output Contract — covering each facet's responsibility and the routing rules between them.
The five disciplines (usage-driven addition / size cap / one-file-one-concern / reverse ratchet / hooks-after-evidence) that structurally prevent harness re-bloat, and the inverted-approval workflow that makes deletion the default.
Post-bootstrap iterations (silent drop / doubled worktrees / wording drift, and more) walked through as problem → analysis → fix → verification.
The top page of a series that walks chapter by chapter through a Claude Code harness running at dozens-of-files scale, with nrslib/takt-derived Faceted Prompting (5 concerns) and orchestrator (takt-inspired) at its core.
The final chapter of the series, organizing a 3-tier summary, the state of the 4 Quality metrics, and the road ahead.
A walkthrough of each phase (⓪'-⑤) of the autodev flow using autodev-smoke's anagram-check task, with real spec / plan / story / done / review excerpts.
A walkthrough of the four symptoms observed in the pre-rebuild Claude Code harness and the decision to rebuild from zero, along with the four design decisions that shaped the new setup.