Was macht Rung?
Govern only the next decision; keep work light.
Scope gate
Before references, establish a positive codebase relationship for the accepted outcome:
- Codebase: the outcome concerns the codebase or an artifact coupled to it in correctness and maintenance. Continue.
- Outside: no relationship. Load no Rung reference or artifact; continue with the Host.
- Mixed: govern the qualifying codebase portion; leave the rest with its owner.
Repository, path/type, tool use, and incidental code are insufficient. Read Development scope only if materially ambiguous.
Core prompts
- Outcome: Desired observation?
- Context: Relevant facts, constraints, and user changes?
- Approach: Smallest coherent direction?
- Evidence: Proof for the claim?
- Handoff: Delivery ready?
Keep these internal unless useful.
Operating spine
One Primary Agent owns facts, decisions, integration, verification, review, and handoff; one session by default. Read Execution model for radius, persistence, recovery, delegation, or ownership.
Signal routing
Pass the gate. Use one current reference by default; do not preload future phases. Combine only interacting concerns.
- Direction, identity, or authority: Clarify
- Unknown project facts/user work: Inspect
- Behavior, UX, ownership, boundary, data, dependencies, or errors: Design
- Dependencies, migration, collaboration, or recovery: Plan
- Editing scope, overlap, integration, or fact sources: Implement
- Behavior, compatibility, build, artifact, or release proof: Verify
- Diff, structure, risk, or delivery judgment: Review
- Revision, artifact, version, note, or publication: Release
Structure: Engineering Structure. Architecture assessment: guide. Harness changes: Project Harness.
Interaction: Workflow. Depth: Risk signals. State: Artifacts.
Handoff
Preserve repository facts and user work. No default .rung/ workspace. External writes need authorization. Report result, checks, uncovered scope, risk, and release state.