Canonical language for technical grilling, project rules, and uninterrupted full delivery

Agent Workflow Architecture, Rules, and Autonomy Glossary

This glossary defines the shared language for technical requirements closure, progressively disclosed project guidance, and uninterrupted delivery.

Terms

Codebase-grounded technical and architecture decisions reached inside the normal requirements design tree.

One independently testable repository-specific pattern or invariant.

The .agents/rules/ surface that indexes and progressively discloses Codebase Rules.

The small post-command skill that derives and maintains the Rule Registry from accepted authority.

Per-rule pass | fail | not-applicable evidence for one task.

Uninterrupted delivery routing through closeout inside accepted goal bounds.

A manual delivery stop explicitly requested by the user.

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 from post-scaffold and post-update handoffs.
Every activated Codebase Rule has one entry in the Rule Evaluation Ledger.
Full Delivery stops at a HITL Checkpoint only when the user explicitly asks for it.

Every grill assesses technical consequences. Code-bearing or architecture-bearing work closes applicable technical design before specification and planning.
GLOSSARY.md remains the domain glossary. Accepted architecture belongs to the grill and SPEC.md.
Technical depth stays inside the normal design tree rather than a mandatory named second phase.
Prompt references stay concise; detailed project patterns are progressively disclosed through the Rule Registry.
Tags aid discovery, while deterministic scope, path, and task triggers govern rule activation.
Full Delivery does not ask permission between ordinary in-bounds steps.
Full Delivery permission covers every operation required by its selected inner steps and excludes unrelated work.
Full review is capped at three passes. Focused validation follows the third repair without creating a HITL Checkpoint.