Repository navigation
Add 7YA operating protocol docs and AGENTS.md control mode - #48
Conversation
There was a problem hiding this comment.
Pull request overview
This PR adds an operational “control mode” and durable governance/runbook documentation for operating 7ya.io, plus a machine-readable release state file intended to capture canonical production facts, blockers, and verification metadata.
Changes:
- Adds a new “7YA.IO Control Mode” section to
AGENTS.mddefining an operator/agent procedure and guardrails. - Introduces 7ya.io operations documentation under
docs/(operating contract, deployment runbook, live verification checklist, and ADRs). - Adds
docs/RELEASE_STATE.jsonto record canonical production metadata, known blockers, and verification/rollback placeholders.
Reviewed changes
Copilot reviewed 6 out of 6 changed files in this pull request and generated 4 comments.
Show a summary per file
| File | Description |
|---|---|
AGENTS.md |
Adds a 7ya.io-specific operating/control-mode section and required operating sequence. |
docs/7YA_OPERATING_CONTRACT.md |
Defines canonical systems, authority matrix, and an end-to-end publishing protocol. |
docs/DEPLOYMENT_RUNBOOK.md |
Documents the production deployment model, step-by-step publish procedure, and rollback flow. |
docs/LIVE_VERIFICATION_CHECKLIST.md |
Adds a checklist for pre/post publish evidence capture and live route verification. |
docs/ARCHITECTURE_DECISIONS.md |
Adds ADRs clarifying system-of-record and publishing target decisions. |
docs/RELEASE_STATE.json |
Adds machine-readable release metadata, known blockers, and placeholders for verification/rollback points. |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
| Canonical production facts to verify before making changes: | ||
|
|
||
| - Canonical repository: `7guard-io/7ya.io` | ||
| - Default branch: `main` | ||
| - Production workflow: `.github/workflows/pages.yml` | ||
| - Workflow name: `Publish 7YA Production Site` | ||
| - Publishing target: GitHub Pages | ||
| - Deployment trigger: manual `workflow_dispatch` | ||
| - Known blocker: GitHub Actions remains quarantined while issue `#83` is open | ||
|
|
| 1. Confirm the repository is `7guard-io/7ya.io` and the default branch is `main`. | ||
| 2. Confirm the production workflow file and workflow name have not changed. | ||
| 3. Confirm the live domain is `https://7ya.io`. | ||
| 4. Check open blockers, especially issue `#83` while GitHub Actions is quarantined. |
| - Workflow name: `Publish 7YA Production Site` | ||
| - Publishing target: GitHub Pages | ||
| - Deployment trigger: manual `workflow_dispatch` | ||
| - Known blocker: GitHub Actions remains quarantined while issue `#83` is open |
| { | ||
| "system": "GitHub Actions", | ||
| "issue": "#83", | ||
| "status": "quarantined until resolved" | ||
| } |
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: ea46179eec
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| - Canonical repository: `7guard-io/7ya.io` | ||
| - Default branch: `main` | ||
| - Production workflow: `.github/workflows/pages.yml` | ||
| - Workflow name: `Publish 7YA Production Site` |
There was a problem hiding this comment.
I checked the current canonical repo (7guard-io/7ya.io on main, .github/workflows/pages.yml) and the workflow is named Publish 7YA Redirect, not this value. Because the new control mode/runbook tell operators to start the workflow by name, 7YA publishing tasks will look for a non-existent workflow and remain blocked unless all new protocol references are corrected or keyed by the file path.
Useful? React with 👍 / 👎.
| - Target: GitHub Pages | ||
| - Trigger: manual `workflow_dispatch` | ||
|
|
||
| The production workflow validates the homepage, assets, public routes, GA4 coverage, builds an immutable `dist` artifact, and deploys through GitHub Pages. |
There was a problem hiding this comment.
In the current canonical .github/workflows/pages.yml, the deploy job only checks the CNAME and redirect URL, then copies index.html, 404.html, and CNAME into dist; it does not validate homepage/assets/routes or GA4 coverage. This runbook says those checks happen inside the production workflow, so operators may treat a successful Pages deploy as validation coverage that the workflow does not actually provide and skip the separate route/analytics checks.
Useful? React with 👍 / 👎.
Motivation
Description
## 7YA.IO Control Modesection toAGENTS.mdthat requires agents to verify canonical systems, read governance docs, inspect production, use dedicated branches/PRs, and avoid treating chat memory as authoritative.docs/:7YA_OPERATING_CONTRACT.md,DEPLOYMENT_RUNBOOK.md,LIVE_VERIFICATION_CHECKLIST.md, andARCHITECTURE_DECISIONS.mdthat define the operating contract, deployment runbook, live verification checklist, and ADRs respectively.docs/RELEASE_STATE.jsoncontaining machine-readable canonical repository, default branch, production workflow metadata, governance-room info, known blockers, and placeholders for latest verified production and rollback points.Testing
docs/RELEASE_STATE.jsonis valid JSON withpython3 -m json.tool docs/RELEASE_STATE.json, which completed successfully.Codex Task