012-remote-desired-state
A setup profile declares remote desired state and doctor compares it without writing
Lifecycle approvedImplementation pendingVerification unknownQualification unknown
Amends 002's setup-profile and remote-doctor contract. A profile renders a versioned desired remote-state document covering required checks, extra jobs, code-owner review, merge queue, the review-exception environment and its reviewers, workflow-token defaults, secret names, repository custom properties, and profile identity. doctor --remote compares every field independently and never writes remote state or reads a secret value.
Read the full pinned specification ↗Relationships
Claimed units
- extends
{ "nature": "additive", "spec": "001-boundaries-and-authority", "unit": { "kind": "file", "path": "docs/decisions/00-founding-decisions.md" } } - extends
{ "nature": "additive", "spec": "002-environment-lifecycle", "unit": { "kind": "directory", "path": "crates/statecraft-home/" } } - extends
{ "nature": "additive", "spec": "002-environment-lifecycle", "unit": { "kind": "directory", "path": "crates/statecraft-environment/" } } - extends
{ "nature": "additive", "spec": "006-command-surface", "unit": { "kind": "directory", "path": "crates/statecraft-cli/" } }
Source headings
- 012: Remote desired state
- 1. Purpose
- 2. Territory
- 3. Behavior
- 3.1 The desired-state document
- 3.2 Read-only comparison
- 3.3 Comparison rules
- 3.4 External application boundary
- 3.5 GitHub capability limits are input facts
- 3.6 Observable negative cases
- 4. Out of scope
- 5. Resolved decisions
- Verification
Frozen anchors
No frozen anchors declared.