Agent Workflow Architecture, Rules, and Autonomy Grill Status

Branch Dashboard

Current Round

• Round: R1
• Current frontier: empty
• Shared-understanding confirmation: confirmed

Locked Direction

• Technical questions are integrated into the ordinary requirements design tree; there is no mandatory named architecture phase.
• Domain-modeling grills implementation and architecture consequences.
• Requirements-grill names architecture concerns lightly and generically.
• Every grill assesses technical consequences; deep technical closure activates only for code-bearing or architecture-bearing work.
• GLOSSARY.md stays glossary-only. Accepted architecture is persisted in the grill and compiled into SPEC.md.
• The target architecture is accepted before planning; planning derives tasks, waves, migration choreography, and validation from it.
• Project-specific guidance lives as granular Codebase Rules under .agents/rules/.
• A small Rule Authoring Skill joins writing-for-agents in the post-scaffold continuation.
• Scoped AGENTS.md files are concise indexes into the Rule Registry rather than rule dumps.
• They retain only the scope boundary, exact skill-routing table, and exhaustive Rule Registry pointer as inline routing content.
• The Rule Registry has one central index and scope-grouped granular rules with stable ids.
• Rule activation uses deterministic path/scope and task triggers; tags aid discovery.
• Every activated rule receives an evidence-backed individual verdict.
• Code Evidence or a durably linked accepted architecture decision may establish a rule.
• Rule files are project-owned and preserved. Harness owns their authoring contract.
• The Rule Authoring Skill runs only from scaffold and update post-command handoffs.
• Its migration inner reference moves current Harness guidance into the first proving Rule Registry.
• Full Delivery continues automatically through phase boundaries and review routing.
• A HITL Checkpoint exists only when explicitly requested by the user.
• Full Delivery has full permission for all operations required by its selected inner steps and no permission for unrelated work.
• Full Delivery permits three complete review passes. After review three and its repair, focused validation replaces review four.

Parked Branches

• None.

Glossary

Terms

• Technical Grill Branch: Codebase-grounded technical and architecture decisions reached inside the normal requirements design tree.
• Codebase Rule: One independently testable repository-specific pattern or invariant.
• Rule Registry: The .agents/rules/ surface that indexes and progressively discloses Codebase Rules.
• Rule Authoring Skill: The small post-command skill that derives and maintains the Rule Registry from accepted authority.
• Rule Evaluation Ledger: Per-rule pass | fail | not-applicable evidence for one task.
• Full Delivery: Uninterrupted delivery routing through closeout inside accepted goal bounds.
• HITL Checkpoint: A manual delivery stop explicitly requested by the user.

Relationships

• A Technical Grill Branch supplies accepted architecture decisions to create-spec; create-plan derives execution from them.
• A scoped AGENTS.md points to the Rule Registry.
• The Rule Authoring Skill creates or maintains Codebase Rules.
• Scaffold and update post-command handoffs invoke the Rule Authoring Skill.
• Every activated Codebase Rule has one entry in the Rule Evaluation Ledger.
• Full Delivery stops at a HITL Checkpoint only when the user explicitly requests it.

Axioms

• Requirements closure includes applicable technical design closure.
• Every grill assesses technical consequences; only code-bearing or architecture-bearing work requires deep technical closure.
• GLOSSARY.md remains the domain glossary; accepted architecture belongs to the grill and SPEC.md.
• Technical depth is integrated into the design tree, not forced into a named second phase.
• Prompt references stay concise; detailed project patterns are progressively disclosed.
• Tags help discovery but do not replace deterministic rule activation.
• Full delivery does not ask for permission between ordinary in-bounds steps.
• Full delivery permission is bounded by its selected inner steps, not by an action-class allowlist.
• Full review is capped at three passes; focused validation after the third repair is part of the same uninterrupted Full Delivery.

Flagged Ambiguities

• None.

Final Consistency

• Every branch is decision-complete.
• The current frontier is empty.
• No accepted term, relationship, or axiom conflicts with another.
• No branch is parked.
• The user confirmed the persisted shared understanding on 2026-08-14.