Deny burndown by default for externally writable trackers #768
No reviewers
Labels
No labels
burndown-2026-06
autonomy
async-consult
autonomy
epic
autonomy
headless
autonomy
live-collab
coherence-core
priority
P0
priority
P1
priority
P2
priority
P3
priority
P4
qa-fixture
role/ai
role/creator
role/design
role/director
role/engineer
role/exec
role/human
role/ops
role/qa
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
coilyco-flight-deck/agentic-os!768
Loading…
Reference in a new issue
No description provided.
Delete branch "issue-766"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Deny Ward burndown by default for externally writable issue trackers, and keep only the private internal repos explicitly opted in until Ward can make actor-aware admission decisions.
This lands the temporary containment for #766 and records the current restoration trail in a dedicated rollout note. Public repos stay open for human triage, but they no longer inherit autonomous execution by default.
.ward/repos.kdltoburndown default=#falseand explicitly opted in the two private internal repos that still get autonomous burndown.docs/ward-burndown-policy.mdand linked it from the repo maps.Tests:
ward exec test -- tests/test_ward_specs_bundle.pyward exec pre-commit-documentation-layoutcloses #766