godpowers 2.5.2 → 2.7.0

package/CHANGELOG.md

@@ -7,6 +7,46 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 
 ## [Unreleased]
 
+## [2.7.0] - 2026-06-10
+
+### Added
+- Added `godpowers state advance --step=<step> --status=<status> --project=.`
+  as a locked state mutation helper that updates `.godpowers/state.json` and
+  regenerates managed state views.
+- Added generated checksummed state views for Godpowers-owned design, build,
+  deploy, observe, and launch `STATE.md` files, all sourced from
+  `.godpowers/state.json`.
+
+### Changed
+- Changed route prerequisites, executable gates, workflow handoffs, command
+  prompts, and specialist agent contracts so Godpowers decision reads use
+  `.godpowers/state.json` instead of generated markdown state views.
+- Changed tier completion instructions to use `godpowers state advance` or an
+  owning command wrapper instead of direct edits to `.godpowers/PROGRESS.md`.
+
+### Fixed
+- Fixed state-view drift by regenerating `.godpowers/PROGRESS.md` and
+  Godpowers-owned per-tier `STATE.md` files after state mutations and replacing
+  tampered managed fences on the next mutation.
+
+## [2.6.0] - 2026-06-10
+
+### Added
+- Added the `@godpowers/mcp` companion package with read-only MCP tools for
+  status, next, gate checks, artifact linting, and requirement tracing.
+- Added `godpowers mcp-info --project=.` as a read-only main-package helper
+  that prints setup instructions without loading the MCP SDK.
+- Added MCP protocol tests that spawn the companion server over stdio, list
+  tools, and call each tool against the quick-proof fixture.
+
+### Changed
+- Updated dashboard and quick-proof host guarantee output to include MCP
+  availability.
+- Updated `/god-status` and `/god-next` to prefer MCP tools when available and
+  fall back to CLI or runtime modules otherwise.
+- Updated release checks to verify the companion package protocol and package
+  contents while keeping the main `godpowers` package dependency-free.
+
 ## [2.5.2] - 2026-06-10
 
 ### Added

package/README.md

@@ -2,7 +2,7 @@
 
 [![CI](https://github.com/aihxp/godpowers/actions/workflows/ci.yml/badge.svg)](https://github.com/aihxp/godpowers/actions/workflows/ci.yml)
 [![License: MIT](https://img.shields.io/badge/License-MIT-yellow.svg)](LICENSE)
-[![Version](https://img.shields.io/badge/version-2.5.2-blue)](CHANGELOG.md)
+[![Version](https://img.shields.io/badge/version-2.7.0-blue)](CHANGELOG.md)
 [![npm](https://img.shields.io/npm/v/godpowers.svg)](https://www.npmjs.com/package/godpowers)
 
 **Ship fast. Ship right. Ship everything. Ship accountably.**
@@ -30,9 +30,13 @@ Godpowers makes AI coding accountable: every serious run should leave disk
 state, artifacts, validation gates, host guarantees, and a next action. Code is
 only one output. The project memory and proof trail matter too.
 
-Version 2.5.2 keeps the 2.5.1 Codex host-run proof studies and patches two
-Phase 2 blocker defects: installed runtime gate command access and build-gate
-false passes when verification evidence is red.
+Version 2.7.0 makes `.godpowers/state.json` the one-directional state authority,
+adds the locked `godpowers state advance` helper, and generates checksummed
+markdown state views for humans. It keeps the optional `@godpowers/mcp`
+companion package, the 2.5.2 installed-runtime gate and build-gate fixes, the
+2.5.1 Codex host proof studies, executable tier gates, 2.4 command-family UX,
+external CLI canary evidence, prompt-size guardrails, legacy command quarantine,
+lib coverage gating, and package verification before publish.
 
 Maintainer hardening continues on the 2.x line with small, audited public
 surface updates when they close real workflow gaps. The 2.1.0 patch closes a command-injection vector in the
@@ -207,9 +211,10 @@ You can also ask any time:
 /god-next
 ```
 
-This reads `.godpowers/PROGRESS.md`, scans disk, reconciles any drift, and
-suggests the next logical command with a compact action brief. The SessionStart
-hook does the same thing when you open a new session in a Godpowers project.
+This reads `.godpowers/state.json`, treats `.godpowers/PROGRESS.md` as a
+generated human view, scans disk, reconciles any drift, and suggests the next
+logical command with a compact action brief. The SessionStart hook does the
+same thing when you open a new session in a Godpowers project.
 
 ### Start With A Path
 
@@ -255,7 +260,9 @@ npx godpowers next --project=.
 npx godpowers status --project=. --brief
 npx godpowers status --project=. --json
 npx godpowers quick-proof --project=.
+npx godpowers state advance --step=prd --status=done --project=.
 npx godpowers gate --tier=prd --project=.
+npx godpowers mcp-info --project=.
 npx godpowers dogfood
 npx godpowers extension-scaffold --name=@godpowers/my-pack --output=.
 ```
@@ -284,12 +291,34 @@ npx godpowers gate --tier=build --project=.
 npx godpowers gate --tier=harden --project=.
 ```
 
-The gate reads disk artifacts, runs the shared artifact linter, checks build
-verification evidence, and blocks unresolved Critical harden findings.
+The gate reads disk artifacts, runs the shared artifact linter, checks
+structured `state.json` evidence for design and build gates, and blocks
+unresolved Critical harden findings.
 
-The runtime remains dependency-free. YAML parsing is intentionally limited to
-the documented Godpowers subset used by intent, routing, workflow, and
-extension files, with parser coverage in `scripts/test-yaml-parser.js`.
+The main `godpowers` runtime remains dependency-free. The optional
+`@godpowers/mcp` companion package owns the MCP SDK dependency and exposes
+read-only tools through explicit host setup. YAML parsing is intentionally
+limited to the documented Godpowers subset used by intent, routing, workflow,
+and extension files, with parser coverage in `scripts/test-yaml-parser.js`.
+
+### MCP Companion
+
+MCP-capable hosts can use the optional companion package without adding an SDK
+dependency to the main `godpowers` package:
+
+```bash
+npx godpowers mcp-info --project=.
+npx -y -p godpowers@2.7.0 -p @godpowers/mcp@2.7.0 godpowers-mcp serve --project=.
+```
+
+The companion exposes `status`, `next`, `gate_check`, `lint_artifact`, and
+`trace_requirement`. Host registration is opt-in:
+
+```bash
+npx -y -p godpowers@2.7.0 -p @godpowers/mcp@2.7.0 godpowers-mcp setup --host=codex --project=. --write
+```
+
+See [MCP Companion](docs/mcp.md) for package boundaries and setup details.
 
 ### Slash Commands
 
@@ -452,10 +481,10 @@ It spawns the right specialist agent in a **fresh context** to do the work.
 You type:        /god-prd
 Skill loads:     skills/god-prd.md
 Skill spawns:    god-pm agent (fresh 200K context)
-Agent reads:     .godpowers/PROGRESS.md
+Agent reads:     .godpowers/state.json + .godpowers/intent.yaml
 Agent writes:    .godpowers/prd/PRD.md
 Skill verifies:  artifact exists, have-nots pass
-Skill updates:   PROGRESS.md
+Skill updates:   state.json via godpowers state advance
 ```
 
 ### The Four Tiers
@@ -470,7 +499,8 @@ Skill updates:   PROGRESS.md
 ### Artifact Paths
 
 ```
-.godpowers/PROGRESS.md         Cross-tier progress ledger
+.godpowers/state.json          Machine-readable project state
+.godpowers/PROGRESS.md         Generated cross-tier progress view
 .godpowers/REQUIREMENTS.md     Requirement checklist (done / in progress / not started)
 .godpowers/prd/PRD.md          Product Requirements Document
 .godpowers/domain/GLOSSARY.md  Domain vocabulary and resolved ambiguities
@@ -480,10 +510,10 @@ Skill updates:   PROGRESS.md
 .godpowers/stack/DECISION.md   Stack Decision (with flip points)
 .godpowers/repo/AUDIT.md       Repo Scaffold Audit
 .godpowers/build/PLAN.md       Build Plan (slices, waves)
-.godpowers/build/STATE.md      Build State
-.godpowers/deploy/STATE.md     Deploy Pipeline State
-.godpowers/observe/STATE.md    Observability State
-.godpowers/launch/STATE.md     Launch State
+.godpowers/build/STATE.md      Generated build state view
+.godpowers/deploy/STATE.md     Generated deploy state view
+.godpowers/observe/STATE.md    Generated observability state view
+.godpowers/launch/STATE.md     Generated launch state view
 .godpowers/harden/FINDINGS.md  Security Findings
 ```
 

package/RELEASE.md

@@ -1,11 +1,11 @@
-# Godpowers 2.5.2 Release
+# Godpowers 2.7.0 Release
 
-> Status: Ready for protected merge
+> Status: Release candidate
 > Date: 2026-06-10
 
-[DECISION] Godpowers 2.5.2 is a Phase 2 blocker patch after the 2.5.1 host-proof docs release.
-[DECISION] This release fixes the installed-runtime gate command gap and build-gate false-pass gap captured during Phase 2 proof work.
-[DECISION] This release does not change the 2.5.1 host-proof case-study claims.
+[DECISION] Godpowers 2.7.0 is the Phase 4 one-directional state release.
+[DECISION] This release makes `.godpowers/state.json` the authority for Godpowers state decisions while treating `.godpowers/PROGRESS.md` and Godpowers-owned per-tier `STATE.md` files as generated human views.
+[DECISION] This release preserves the optional `@godpowers/mcp` companion boundary and keeps the main `godpowers` package dependency-free.
 
 ## What's in this release
 
@@ -13,39 +13,51 @@
 - [DECISION] 40 specialist agents.
 - [DECISION] 13 executable workflows.
 - [DECISION] 42 intent recipes.
-- [DECISION] 8 installer CLI helpers.
+- [DECISION] A locked `godpowers state advance --step=<step> --status=<status> --project=.` state mutation helper.
+- [DECISION] Generated checksummed state views for `.godpowers/PROGRESS.md` and Godpowers-owned design, build, deploy, observe, and launch `STATE.md` files.
+- [DECISION] Five read-only MCP tools in `@godpowers/mcp`.
 
 ## Highlights
 
-- [DECISION] `godpowers-runtime` now includes `bin/` next to `package.json`, so host workflows can run `npm exec --package <runtime> -- godpowers gate`.
-- [DECISION] Build gates now fail closed when `.godpowers/build/STATE.md` records any failed verification command.
-- [DECISION] Slot A, Slot B, and Slot C evidence remains the repository state shipped in 2.5.1.
+- [DECISION] `godpowers state advance` updates `.godpowers/state.json` through the state lock and refreshes generated markdown views after the mutation.
+- [DECISION] Route prerequisites, executable gates, workflow handoffs, command prompts, and specialist agent contracts now use `.godpowers/state.json` for Godpowers state decisions.
+- [DECISION] Generated markdown views preserve user prose outside managed fences and replace tampered managed fences on the next state mutation.
+- [DECISION] Design and build gates now use structured state evidence instead of markdown `STATE.md` authority.
+- [DECISION] Deploy, observe, and launch handoffs now use structured state evidence for readiness, target, rollback, SLO, alert, runbook, and launch data.
+- [DECISION] `god-repair` remains available as diagnostics and recovery while generated state views prove themselves.
 
 ## Validation
 
-- [DECISION] `node scripts/test-gate.js` passed before the latest `main` merge.
-- [DECISION] `node scripts/test-install-smoke.js` passed before the latest `main` merge.
-- [DECISION] `npm run test:e2e` passed before the latest `main` merge.
-- [DECISION] `node scripts/test-runtime-verification.js` passed before the latest `main` merge.
-- [DECISION] `node scripts/test-agent-browser.js` passed before the latest `main` merge.
-- [DECISION] `node scripts/static-check.js` passed before the latest `main` merge.
-- [DECISION] `npm run release:check` passed before the latest `main` merge with `coverage:lib` at 92.9 percent line coverage, `npm audit --omit=dev` reporting 0 vulnerabilities, public surface docs matching version 2.5.1, and package contents verified at 534 files.
-- [DECISION] Post-merge 2.5.2 `npm run test:surface` passed.
-- [DECISION] Post-merge 2.5.2 `node scripts/test-gate.js` passed.
-- [DECISION] Post-merge 2.5.2 `node scripts/test-install-smoke.js` passed.
-- [DECISION] Post-merge 2.5.2 `node scripts/static-check.js` passed.
-- [DECISION] Post-merge 2.5.2 `npm run test:e2e` passed.
-- [DECISION] Post-merge 2.5.2 `node scripts/test-runtime-verification.js` passed.
-- [DECISION] Post-merge 2.5.2 `node scripts/test-agent-browser.js` passed.
-- [DECISION] Post-merge 2.5.2 `npm run release:check` passed with `coverage:lib` at 92.9 percent line coverage, `npm audit --omit=dev` reporting 0 vulnerabilities, public surface docs matching version 2.5.2, and package contents verified at 534 files.
+- [DECISION] `npm ci` passed and reported 0 vulnerabilities.
+- [DECISION] `node scripts/test-state-advance.js` passed.
+- [DECISION] `node scripts/test-state-views.js` passed.
+- [DECISION] `npm --workspace @godpowers/mcp test` passed.
+- [DECISION] `node scripts/static-check.js` passed.
+- [DECISION] `npm run lint` passed.
+- [DECISION] `npm run test:quick-proof` passed.
+- [DECISION] `npm run test:audit` passed with `npm audit --omit=dev`, `git diff --check`, and public surface checks green.
+- [DECISION] `npm run test:e2e` passed.
+- [DECISION] `node scripts/test-runtime-verification.js` passed.
+- [DECISION] `node scripts/test-agent-browser.js` passed.
+- [DECISION] `npm run pack:check` passed with 538 root package files.
+- [DECISION] `npm run pack:mcp:check` passed with 8 companion package files.
+- [DECISION] `node bin/install.js dogfood --json` passed 5 of 5 scenarios.
+- [DECISION] Repo documentation sync, repo surface sync, and release surface sync were fresh.
+- [DECISION] Changed-file banned character scans passed.
+- [DECISION] `npm run release:check` passed with `coverage:lib` at 92.78 percent line coverage, `npm audit --omit=dev` reporting 0 vulnerabilities, public surface docs matching version 2.7.0, root package contents verified at 538 files, and `@godpowers/mcp` package contents verified at 8 files.
+- [DECISION] The final publish result must be recorded in `docs/BRIDGE-PLAN.md` after the tag-triggered GitHub workflow completes.
 
 ## Upgrade
 
-- [DECISION] Use `npm install -g godpowers@2.5.2` or `npx godpowers@2.5.2` after the package is published.
-- [DECISION] Reinstall Godpowers in host runtimes to refresh the installed runtime bundle.
-- [DECISION] Existing `.godpowers/` state remains compatible.
+- [DECISION] Use `npm install -g godpowers@2.7.0` or `npx godpowers@2.7.0`.
+- [DECISION] Use optional MCP package install `npm install -g godpowers @godpowers/mcp` when the host can register MCP servers.
+- [DECISION] Re-run `/god-context` in each project to refresh installed runtime metadata.
+- [DECISION] Existing `.godpowers/state.json` files remain compatible.
+- [DECISION] Existing `.godpowers/PROGRESS.md` and Godpowers-owned per-tier `STATE.md` files become generated human views after the next state mutation.
 
 ## Notes
 
-- [DECISION] The npm `godpowers@2.5.1` package is already published.
-- [DECISION] Publishing 2.5.2 remains pending until protected merge, tag, and npm provenance publish complete.
+- [DECISION] The npm `godpowers@2.7.0` package must be published through the tag-triggered GitHub workflow with provenance.
+- [DECISION] The npm `@godpowers/mcp@2.7.0` package must be published through the same workflow with provenance.
+- [DECISION] The `v2.7.0` tag must match the npm package version.
+- [DECISION] The next bridge-plan phase after 2.7.0 publish verification is Phase 5: Surface Contraction.

package/SKILL.md

@@ -321,8 +321,8 @@ Run or apply these by default in every relevant closeout:
 
 #### Level 2: Auto-run local helpers, visible and logged
 Run these local runtime helpers automatically when their trigger is present:
-- `lib/checkpoint.syncFromState` after every `state.json` or
-  `PROGRESS.md` mutation.
+- `lib/checkpoint.syncFromState` after every `state.json` mutation or
+  managed progress view refresh.
 - Lightweight reverse-sync or linkage scan after code or artifact edits.
 - Pillars sync planning after durable artifact truth changes.
 - `lib/planning-systems.importPlanningContext` when legacy planning, BMAD, or
@@ -405,9 +405,9 @@ Never auto-run these from inference alone:
   reports success
 
 Every auto-invoke decision must be explainable from one of these inputs:
-changed files, Godpowers artifacts, `state.json`, `PROGRESS.md`,
-`CHECKPOINT.md`, `SYNC-LOG.md`, `REVIEW-REQUIRED.md`, routing YAML, recipe YAML,
-or explicit user intent.
+changed files, Godpowers artifacts, `state.json`, generated `PROGRESS.md`
+view, `CHECKPOINT.md`, `SYNC-LOG.md`, `REVIEW-REQUIRED.md`, routing YAML,
+recipe YAML, or explicit user intent.
 
 ---
 
@@ -433,11 +433,11 @@ coordination plan.
 ## Tier 0: Orchestration
 
 ### On every invocation:
-1. Read `.godpowers/PROGRESS.md` if it exists
+1. Read `.godpowers/state.json` if it exists, using `.godpowers/PROGRESS.md` only as a generated legacy fallback when state is missing
 2. Scan for existing artifacts at all canonical paths
 3. Detect operating mode (A/B/C/D)
 4. Detect project scale (trivial / small / medium / large / enterprise)
-5. Record mode and scale in PROGRESS.md
+5. Record mode and scale in `state.json`
 6. Route to the appropriate tier and sub-step
 
 ### Scale Detection
@@ -450,30 +450,27 @@ Assess the project description against these criteria:
 
 Scale determines which personas activate and how deep the planning goes.
 
-### Progress Ledger (.godpowers/PROGRESS.md)
-```markdown
-# Godpowers Progress
-
-Mode: A (greenfield)
-Scale: medium
-Started: 2026-05-09T14:30:00Z
-
-## Tiers
-
-| Tier | Sub-step | Status | Artifact | Updated |
-|------|----------|--------|----------|---------|
-| 1 | PRD | done | .godpowers/prd/PRD.md | 2026-05-09T14:35:00Z |
-| 1 | Architecture | in-flight | -- | 2026-05-09T14:40:00Z |
-| 1 | Roadmap | pending | -- | -- |
-| 1 | Stack | pending | -- | -- |
-| 2 | Repo | pending | -- | -- |
-| 2 | Build | pending | -- | -- |
-| 3 | Deploy | pending | -- | -- |
-| 3 | Observe | pending | -- | -- |
-| 3 | Launch | pending | -- | -- |
-| 3 | Harden | pending | -- | -- |
+### State Ledger (`.godpowers/state.json`)
+```json
+{
+  "project": { "name": "Example", "started": "2026-05-09T14:30:00Z" },
+  "mode": "A",
+  "tiers": {
+    "tier-1": {
+      "prd": { "status": "done" },
+      "arch": { "status": "in-flight" },
+      "roadmap": { "status": "pending" },
+      "stack": { "status": "pending" }
+    }
+  }
+}
 ```
 
+`.godpowers/PROGRESS.md` is a generated human-readable view of this state.
+Commands update tracked steps through `npx godpowers state advance --step=<step>
+--status=<status> --project=.` or through an owning command wrapper, never by
+editing the generated view.
+
 Valid statuses: pending, in-flight, done, skipped, imported, failed, re-invoked.
 Silence is not a status. Every tier must have an explicit entry.
 
@@ -501,7 +498,7 @@ Silence is not a status. Every tier must have an explicit entry.
 3. Run substitution test on every claim
 4. Run three-label test on every sentence
 5. Write to `.godpowers/prd/PRD.md`
-6. Update PROGRESS.md
+6. Run `npx godpowers state advance --step=prd --status=done --project=.`
 
 **Have-nots (PRD fails if any are true)**:
 - Problem statement passes substitution test (reads the same for any product)
@@ -536,7 +533,7 @@ Silence is not a status. Every tier must have an explicit entry.
    - Data model (entities, relationships, ownership)
 4. Run have-nots check
 5. Write to `.godpowers/arch/ARCH.md`
-6. Update PROGRESS.md
+6. Run `npx godpowers state advance --step=arch --status=done --project=.`
 
 **Have-nots (Architecture fails if any are true)**:
 - A box in the diagram has no clear responsibility
@@ -569,7 +566,7 @@ Silence is not a status. Every tier must have an explicit entry.
    - Dependency list
    - Estimated scope (T-shirt size, not fake precision)
 6. Write to `.godpowers/roadmap/ROADMAP.md`
-7. Update PROGRESS.md
+7. Run `npx godpowers state advance --step=roadmap --status=done --project=.`
 
 **Have-nots (Roadmap fails if any are true)**:
 - Milestone goal passes substitution test
@@ -592,7 +589,7 @@ Silence is not a status. Every tier must have an explicit entry.
    - Document the flip point (when would you reverse this choice?)
    - Document the lock-in cost
 3. Write to `.godpowers/stack/DECISION.md`
-4. Update PROGRESS.md
+4. Run `npx godpowers state advance --step=stack --status=done --project=.`
 
 **Pause conditions**:
 - Two candidates score within 10% and the flip point is a human constraint
@@ -613,7 +610,7 @@ Silence is not a status. Every tier must have an explicit entry.
 5. .gitignore, .editorconfig
 6. Run repo audit
 7. Write audit to `.godpowers/repo/AUDIT.md`
-8. Update PROGRESS.md
+8. Run `npx godpowers state advance --step=repo --status=done --project=.`
 
 ### 2.2 Build (god build)
 
@@ -636,8 +633,8 @@ Silence is not a status. Every tier must have an explicit entry.
    - Agent refactors (REFACTOR)
    - Two-stage review: spec compliance, then code quality
    - Atomic commit on pass
-7. Update `.godpowers/build/STATE.md`
-8. Update PROGRESS.md
+7. Record build verification evidence in `.godpowers/state.json`
+8. Run `npx godpowers state advance --step=build --status=done --project=.` to regenerate the build state view
 
 **TDD Enforcement**:
 - If a subagent writes implementation before tests, flag the violation
@@ -664,7 +661,7 @@ Silence is not a status. Every tier must have an explicit entry.
 2. Environment parity (dev matches prod)
 3. Rollback plan (documented, tested)
 4. Health checks (not just "is the process running")
-5. Write to `.godpowers/deploy/STATE.md`
+5. Record deploy evidence in `.godpowers/state.json` and regenerate the deploy state view
 
 **Have-nots**:
 - Different build per environment
@@ -681,7 +678,7 @@ Silence is not a status. Every tier must have an explicit entry.
 3. Alerting (symptoms, not causes)
 4. Structured logging
 5. Runbooks (tested, not paper)
-6. Write to `.godpowers/observe/STATE.md`
+6. Record observability evidence in `.godpowers/state.json` and regenerate the observability state view
 
 **Have-nots**:
 - SLO has no error budget policy
@@ -699,7 +696,7 @@ Silence is not a status. Every tier must have an explicit entry.
 3. Launch channels identified with messaging per channel
 4. Launch-day telemetry (source attribution on every signup)
 5. D-7 to D+7 runbook
-6. Write to `.godpowers/launch/STATE.md`
+6. Record launch evidence in `.godpowers/state.json` and regenerate the launch state view
 
 **Have-nots**:
 - Landing copy passes substitution test (reads generic)
@@ -750,7 +747,7 @@ God Mode pauses ONLY when:
 God Mode NEVER pauses to:
 - Ask permission to proceed to the next tier
 - Confirm it should write a file
-- Report progress (PROGRESS.md does that)
+- Report progress (the generated progress view does that)
 - Ask "is this okay?" without specific options
 
 ### Pause Format
@@ -762,7 +759,7 @@ Every pause includes:
 
 ### Resume Protocol
 On resume:
-1. Read `.godpowers/PROGRESS.md`
+1. Read `.godpowers/state.json`, with `.godpowers/PROGRESS.md` only as a generated legacy fallback when state is missing
 2. Scan all artifact paths
 3. Verify artifact integrity (have-nots check on existing artifacts)
 4. Pick up at the first non-done tier
@@ -786,8 +783,8 @@ grep-testable against the produced artifact.
 - **AI-slop**: Output passes substitution test (reads generic)
 - **Phantom resume**: Agent claims done, artifact not on disk
 - **Ghost handoff**: Tier invoked before upstream artifact exists
-- **Rubber-stamp**: PROGRESS.md says done with no artifact
-- **Silence as skip**: Tier absent from PROGRESS.md
+- **Rubber-stamp**: state.json says done with no artifact
+- **Silence as skip**: Tier absent from state.json
 - **Paper artifact**: Document exists but mechanism does not
 - **Theater**: Sentences that are neither decision, hypothesis, nor open question
 
@@ -815,7 +812,8 @@ See individual tier sections above.
 
 ```
 .godpowers/
-  PROGRESS.md          # Cross-tier progress ledger
+  state.json           # Machine-readable source of truth
+  PROGRESS.md          # Generated cross-tier progress view
   prd/
     PRD.md             # Product Requirements Document
   domain/
@@ -830,13 +828,13 @@ See individual tier sections above.
   repo/
     AUDIT.md           # Repo Scaffold Audit
   build/
-    STATE.md           # Build State
+    STATE.md           # Generated build state view
   deploy/
-    STATE.md           # Deploy Pipeline State
+    STATE.md           # Generated deploy pipeline state view
   observe/
-    STATE.md           # Observability State
+    STATE.md           # Generated observability state view
   launch/
-    STATE.md           # Launch State
+    STATE.md           # Generated launch state view
   harden/
     FINDINGS.md        # Security Findings
 ```

package/agents/god-deploy-engineer.md

@@ -14,7 +14,7 @@ Set up the deploy pipeline.
 
 ## Gate Check
 
-Build is complete. All tests pass. `.godpowers/build/STATE.md` shows green.
+Build is complete. All tests pass. `.godpowers/state.json` records `tier-2.build.status == done` with passing build verification commands.
 
 ## Process
 
@@ -91,7 +91,7 @@ Build is complete. All tests pass. `.godpowers/build/STATE.md` shows green.
 
 ## Output
 
-Write `.godpowers/deploy/STATE.md`:
+Return deploy evidence for `.godpowers/state.json`; `lib/state-views.js` generates `.godpowers/deploy/STATE.md` from these fields:
 
 ```markdown
 # Deploy State

package/agents/god-designer.md

@@ -105,8 +105,9 @@ result before applying.
   (parsed by `lib/design-spec.js`)
 - `PRODUCT.md` at project root, when impeccable is present (impeccable owns
   the format)
-- `.godpowers/design/STATE.md` with: lint history, version, impeccable
-  command log, drift snapshot
+- `.godpowers/state.json` design evidence with lint history, version,
+  impeccable command log, and drift snapshot; `lib/state-views.js`
+  regenerates `.godpowers/design/STATE.md`
 
 ## Validation
 

package/agents/god-greenfieldifier.md

@@ -29,10 +29,8 @@ intent, architecture, delivery commitments, or org constraints.
   - `.godpowers/roadmap/ROADMAP.md`
   - `.godpowers/stack/DECISION.md`
   - `.godpowers/repo/AUDIT.md`
-  - `.godpowers/build/STATE.md`
-  - `.godpowers/deploy/STATE.md`
-  - `.godpowers/observe/STATE.md`
-  - `.godpowers/launch/STATE.md`
+  - `.godpowers/state.json` build, deploy, observe, and launch evidence
+  - `.godpowers/build/PLAN.md`
   - `.godpowers/harden/FINDINGS.md`
 - Source evidence from code, org context, and imported planning systems.
 

package/agents/god-launch-strategist.md

@@ -69,9 +69,8 @@ For each channel:
 - D+7: post-launch retrospective
 
 ### 6. Shipping Closure
-- Read `.godpowers/deploy/STATE.md`,
-  `.godpowers/deploy/WAITING-FOR-EXTERNAL-ACCESS.md` if present, and
-  `.godpowers/observe/STATE.md`.
+- Read `.godpowers/state.json` deploy and observe evidence plus
+  `.godpowers/deploy/WAITING-FOR-EXTERNAL-ACCESS.md` if present.
 - If deploy or observe is waiting on external access, do not create a broad
   dashboard checklist. Reference only the smallest next access item from the
   waiting bundle and write launch state as local-ready with deployed
@@ -96,7 +95,7 @@ For each channel:
 
 ## Output
 
-Write `.godpowers/launch/STATE.md` with all artifacts.
+Return launch evidence for `.godpowers/state.json`; `lib/state-views.js` generates `.godpowers/launch/STATE.md` with the launch artifact summary.
 
 ## Have-Nots
 
@@ -129,7 +128,7 @@ pause. Log to YOLO-DECISIONS.md so the user can revise:
 - Auto-picked tone: direct/professional (default)
 - Auto-picked headline: [actual headline written]
 - Reason: substitution-tested headline that emphasizes the strongest PRD value prop
-- Reversible by: edit `.godpowers/launch/STATE.md` headline section
+- Reversible by: update launch evidence in `.godpowers/state.json` and regenerate the launch state view
 - Timestamp: [ISO 8601]
 ```
 

package/agents/god-observability-engineer.md

@@ -15,10 +15,10 @@ Wire observability.
 
 ## Gate Check
 
-`.godpowers/deploy/STATE.md` exists. App is deployed and reachable, or deploy
-state documents a tested local staging harness plus a single external access
-bundle. A deferred staging URL must not block observability setup when local or
-CI-verifiable checks can still run.
+`.godpowers/state.json` records deploy completion. The deploy evidence says the
+app is deployed and reachable, or it documents a tested local staging harness
+plus a single external access bundle. A deferred staging URL must not block
+observability setup when local or CI-verifiable checks can still run.
 
 ## Process
 
@@ -78,7 +78,7 @@ For each PRD success metric, define an SLO:
 
 ## Output
 
-Write `.godpowers/observe/STATE.md` with:
+Return observability evidence for `.godpowers/state.json`; `lib/state-views.js` generates `.godpowers/observe/STATE.md` with:
 - SLO definitions
 - Error budget policies
 - Alert catalog

package/agents/god-reconciler.md

@@ -82,12 +82,16 @@ For each artifact below, check (in parallel where possible):
 
 ### Tier 3 artifacts
 
-#### DEPLOY (`.godpowers/deploy/STATE.md`)
+#### DEPLOY state evidence
+
+Source: `.godpowers/state.json` `tier-3.deploy`.
 - Does the feature need a new env var?
 - New deploy step (e.g., new service)?
 - Verdict: covered / needs-extension
 
-#### OBSERVE (`.godpowers/observe/STATE.md`)
+#### OBSERVE state evidence
+
+Source: `.godpowers/state.json` `tier-3.observe`.
 - Does the feature need a new SLO?
 - New error budget category?
 - New alert + runbook?
@@ -99,7 +103,9 @@ For each artifact below, check (in parallel where possible):
 - New input source to validate?
 - Verdict: covered / needs-review / new-surface
 
-#### LAUNCH (`.godpowers/launch/STATE.md`)
+#### LAUNCH state evidence
+
+Source: `.godpowers/state.json` `tier-3.launch`.
 - Is the feature user-visible?
 - Does launch copy need updating?
 - New channel-specific messaging needed?
@@ -168,7 +174,7 @@ Return structured JSON to the orchestrating skill:
   "roadmap": { "status": "enhancement", "match": "Milestone 2", "action": "fold in or amend" },
   "stack": { "status": "covered" },
   "repo": { "status": "scaffolded" },
-  "deploy": { "status": "needs-extension", "action": "add env var to deploy/STATE.md" },
+  "deploy": { "status": "needs-extension", "action": "record new env var in state.json deploy evidence" },
   "observe": { "status": "needs-slo", "action": "add SLO for new endpoint" },
   "harden": { "status": "needs-review", "action": "scope-to-new-code review" },
   "launch": { "status": "copy-update", "action": "update landing if launching publicly" },

package/agents/god-retrospective.md

@@ -22,7 +22,7 @@ sprint, not generic platitudes.
 ### 1. Gather Data
 Read:
 - Sprint PLAN.md (what was committed)
-- Sprint slice completion record from `.godpowers/build/STATE.md`
+- Sprint slice completion record from `.godpowers/state.json`
 - Git log for the sprint window
 - Any HANDOFF.md or pause logs from the sprint