AGENTS.md: prohibit warded engineers from debugging live deployments #522

Merged

coilysiren merged 2 commits from issue-466 into main

2026-07-14 10:00:21 +00:00

coilyco-ops commented

2026-07-14 09:38:15 +00:00

Owner

This updates AGENTS.md with 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.

Added the engineer/QA live-deployment prohibition under ## Agent rules.
Added the explicit precedent and burndown filter cross-reference.
Raised agents_md_max_chars to 17000 so the base doctrine stays in context.

Tests: ward pre-commit-all passed locally.

closes #466
ward.workflow: pull-request-and-merge

This updates `AGENTS.md` with 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. - Added the engineer/QA live-deployment prohibition under `## Agent rules`. - Added the explicit precedent and burndown filter cross-reference. - Raised `agents_md_max_chars` to `17000` so the base doctrine stays in context. Tests: `ward pre-commit-all` passed locally. closes #466 ward.workflow: pull-request-and-merge

coilyco-ops added 2 commits

2026-07-14 09:38:15 +00:00

docs: add live-deployment prohibition for engineer and QA 200e3d8cda

docs: add doctrine cross references

ci / ward-doctor (pull_request) Successful in 25s

Details

ci / gate (pull_request) Failing after 26m22s

Details

d718ae3448

coilyco-ops referenced this pull request

2026-07-14 09:48:47 +00:00

AGENTS.md: prohibit warded engineers from debugging/iterating against live deployments #466

coilyco-ops commented

2026-07-14 09:48:47 +00:00

Author

Owner

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 running for 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.

WARDED_WORKFLOW: blocked 🛑 <details><summary>details</summary> 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 `running` for 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`. </details>