You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Add a generic, governed Autonomous Run Protocol that connects a tracker task to a delivery artifact, isolated agent workspace, evidence packet, and human handoff without making the template dependent on a specific tracker, agent, CI, or cloud provider.
Acceptance criteria
A single canonical document defines the end-to-end contract: tracker task → delivery artifact (FT-* or another flow owner) → isolated workspace → agent run → evidence → handoff/closure.
The protocol is integration-neutral: no Linear/GitHub/Codex/CI/cloud-specific assumptions; integrations are adapters and project configuration.
Dispatch gates require a selected flow, a link to its canonical owner, and all applicable upstream readiness gates (including Problem Ready and, where required, Solution Ready).
The protocol identifies work that must not be dispatched autonomously: Human Routing, incomplete intent/acceptance, required external approval, or uncontrolled security/production risk.
It specifies a deterministic isolated-workspace contract, lifecycle, reuse/cleanup rules, and prevention of concurrent runs for one delivery unit.
It specifies a minimal run-state contract with idempotent claim, bounded concurrency, retry/backoff, eligibility reconciliation, cancellation, and restart recovery.
It defines an evidence packet: change/PR reference, required-check results, acceptance evidence, manual-only gaps, residual risks, and handoff state. A successful process exit alone is not completion.
It specifies the least-privilege secret and external-action posture and delegates project decisions to autonomy boundaries.
Existing indexes and canonical documents link to the protocol without duplicating owned facts.
memory-bank-cli lint, memory-bank-cli doctor --profile template, and git diff --check pass; no downstream-specific terms leak into memory-bank-template/.
References
OpenAI Symphony SPEC.md
Existing Feature Flow, Validation Profiles, Autonomy Boundaries, and Session Handoff
Goal
Add a generic, governed Autonomous Run Protocol that connects a tracker task to a delivery artifact, isolated agent workspace, evidence packet, and human handoff without making the template dependent on a specific tracker, agent, CI, or cloud provider.
Acceptance criteria
FT-*or another flow owner) → isolated workspace → agent run → evidence → handoff/closure.Problem Readyand, where required,Solution Ready).memory-bank-cli lint,memory-bank-cli doctor --profile template, andgit diff --checkpass; no downstream-specific terms leak intomemory-bank-template/.References
SPEC.md