Orchestrate Reflective Development
Repository continuity composition
For repository-scoped work, compose maintain-repository-continuity in
Resume mode before selecting work. After an authorized repository change
passes domain validation, compose Refresh and Verify immediately before
presenting the pull request, and include the reconciled root CONTINUITY.md in
the same change. A policy-permitted no-change or exemption result must be
documented instead of fabricating an edit.
- Contribute: Cycle objective, phase results, validation, human decisions, blockers, and next bounded action
- Never claim: An autonomous loop, human approval, or completed phase without evidence
Purpose
Execute the reusable procedure governed by reflector.
Primary question:
How should the current bounded development cycle proceed, pause, synchronize, or complete?
Required Inputs
Resolve:
- governing specification and version
- current source or repository state
- scope and constraints
- upstream architecture or evidence
- output location
- validation expectations
- unresolved decisions
Missing evidence must remain visible.
Workflow
- resolve current cycle state and human alignment anchor
- define scope, exclusions, mode, and recursion budget
- read source specifications, issues, architecture, and prior cycles
- plan and execute one bounded work unit
- validate produced artifacts
- perform or consume a reflective audit
- detect drift and unresolved decisions
- record state and safe resume point
- stop at the synchronization boundary
Output Contract
Primary output:
reflective cycle record
Also report assumptions, evidence gaps, validation status, unresolved
questions, and downstream actions requiring separate authorization.
Constraints
- Follow the governing specification.
- Preserve provenance and uncertainty.
- Do not invent authority, evidence, or current behavior.
- Do not silently expand scope.
- Do not claim completion when required validation is missing.
- Keep proposed downstream work separate from authorized execution.
Completion Criteria
1---2name: orchestrate-reflective-development3description: Orchestrates a bounded reflective development cycle by planning, executing, and auditing one unit of work. Use when a development cycle needs to proceed, pause, synchronize, or complete with human alignment.4license: MIT5---67# Orchestrate Reflective Development89<!-- aether-continuity-disposition: reader-writer -->1011## Repository continuity composition1213For repository-scoped work, compose `maintain-repository-continuity` in14**Resume** mode before selecting work. After an authorized repository change15passes domain validation, compose **Refresh** and **Verify** immediately before16presenting the pull request, and include the reconciled root `CONTINUITY.md` in17the same change. A policy-permitted no-change or exemption result must be18documented instead of fabricating an edit.1920- **Contribute:** Cycle objective, phase results, validation, human decisions, blockers, and next bounded action21- **Never claim:** An autonomous loop, human approval, or completed phase without evidence2223## Purpose2425Execute the reusable procedure governed by `reflector`.2627Primary question:2829> How should the current bounded development cycle proceed, pause, synchronize, or complete?3031## Required Inputs3233Resolve:3435- governing specification and version36- current source or repository state37- scope and constraints38- upstream architecture or evidence39- output location40- validation expectations41- unresolved decisions4243Missing evidence must remain visible.4445## Workflow46471. resolve current cycle state and human alignment anchor482. define scope, exclusions, mode, and recursion budget493. read source specifications, issues, architecture, and prior cycles504. plan and execute one bounded work unit515. validate produced artifacts526. perform or consume a reflective audit537. detect drift and unresolved decisions548. record state and safe resume point559. stop at the synchronization boundary5657## Output Contract5859Primary output:6061 reflective cycle record6263Also report assumptions, evidence gaps, validation status, unresolved64questions, and downstream actions requiring separate authorization.6566## Constraints6768- Follow the governing specification.69- Preserve provenance and uncertainty.70- Do not invent authority, evidence, or current behavior.71- Do not silently expand scope.72- Do not claim completion when required validation is missing.73- Keep proposed downstream work separate from authorized execution.7475## Completion Criteria7677- [ ] Governing specification is resolved.78- [ ] Scope and constraints are explicit.79- [ ] Required evidence was inspected.80- [ ] The primary output was created.81- [ ] Validation was executed or its absence documented.82- [ ] Open questions and authorization needs are visible.
egohygiene