AGENTS.md: prohibit warded engineers from debugging live deployments #522
No reviewers
Labels
No labels
burndown-2026-06
coherence-core
consult
headless
interactive
P0
P1
P2
P3
P4
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!522
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "issue-466"
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?
This updates
AGENTS.mdwith the sealed-role prohibition against iterating on live deployments, and bumps the documentation-layout char cap so the always-loaded doctrine can carry the new rule.## Agent rules.agents_md_max_charsto17000so the base doctrine stays in context.Tests:
ward pre-commit-allpassed locally.closes #466
ward.workflow: pull-request-and-merge
WARDED_WORKFLOW: blocked 🛑
details
workflow: pull-request-and-merge; review summary: skipped - the in-container review gate was intentionally skipped by ~/.ward/config.yaml default.
The implementation itself was straightforward. The only surprise was the Forgejo Actions run for PR #522 staying in
runningfor minutes with no usable job detail exposed through the API, so the branch was left blocked on the forge runner rather than on repo-side changes.Confidence: medium. Follow-up: a human with Forgejo runner access needs to unblock or restart the PR check for
coilyco-flight-deck/agentic-os#522.