6f9427d613
Implements the process layer of the v1 feature-lock planner: capability proposals arrive uniform via issue form; the lock artifact (docs/architecture/v1-scope.md) is CODEOWNERS-gated; the shared CLAUDE.md/AGENTS.md guidelines gain the scope gate, additive-only API rules, and pre-push checklist for agent-driven contributions. Co-authored-by: Claude Fable 5 <noreply@anthropic.com>
1.0 KiB
1.0 KiB
Silo v1 Scope
Status: NOT LOCKED — proposal window open.
Propose capabilities with the v1 capability proposal issue template; triage happens on the Silo v1 project.
When the scope locks, this file becomes the source of truth and will contain:
- Locked capabilities — a table of capability epics (issue links) with one-line scope statements.
- API policy — additive-only within
/api/v1(no field renames/removals, no type changes, no status-code repurposing; removals only via the Deprecation/Sunset header flow; capability endpoints for feature detection). Contract tooling: #135. - Amendment rules — after lock, this file changes only via PR with code-owner review. An amendment PR is the exception process: it must say what changes, why it cannot wait for v1.1, and what it displaces.
Until lock: treat any capability not tracked as Proposed/Locked on the project as out of scope
for feature PRs (see the scope gate in CLAUDE.md).