godpowers 2.6.0 → 3.0.0

package/CHANGELOG.md

@@ -7,6 +7,51 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 
 ## [Unreleased]
 
+## [3.0.0] - 2026-06-10
+
+### Added
+- Added `/god-plan`, `/god-fix`, `/god-ship`, `/god-capture`, and
+  `/god-extend` as thin verb dispatchers over existing leaf commands.
+- Added routing metadata for the new verb dispatchers so repository surface
+  checks keep skills and routes aligned.
+
+### Changed
+- Changed the omitted installer profile default from `full` to `core`.
+- Updated the `core` profile to install the front door, status, verb
+  dispatchers, and `/god-mode` compatibility while preserving every command in
+  `--profile=full`.
+- Routed `/god-observe` through the `ship` verb boundary based on Phase 2 host
+  proof evidence.
+- Updated public docs, profile tests, command-family tests, and Phase 5
+  surface evidence for the 117-command surface.
+
+### Deprecated
+- Deprecated `/god-locate` in favor of `/god-status --locate`.
+- Deprecated `/god-lifecycle` in favor of `/god-status --lifecycle`.
+- Added `successor` metadata to deprecated compatibility commands.
+
+## [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

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.6.0-blue)](CHANGELOG.md)
+[![Version](https://img.shields.io/badge/version-3.0.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,15 +30,16 @@ 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.6.0 adds the optional `@godpowers/mcp` companion package with
-read-only MCP tools for status, next-route, gate, artifact lint, and requirement
-trace workflows. It keeps 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.
+Version 3.0.0 makes the omitted installer profile `core`, adds five verb
+dispatch commands, and folds locate and lifecycle views into `/god-status`
+flags while preserving full-profile compatibility aliases. It keeps the
+one-directional state authority from 2.7.0, the optional `@godpowers/mcp`
+companion package, the installed-runtime gate and build-gate fixes, Codex host
+proof studies, executable tier gates, command-family UX, external CLI canary
+evidence, prompt-size guardrails, lib coverage gating, and package verification
+before publish.
 
-Maintainer hardening continues on the 2.x line with small, audited public
+Maintainer hardening continues on the 3.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
 agent-browser driver, guards runtime file parsing against corrupt state,
 makes data-directory installs a clean replace, and reconciles documentation
@@ -120,8 +121,9 @@ The installer copies:
 - Codex agent metadata to `<runtime>/agents/*.toml`
 - SessionStart hook (Claude Code only) to `<runtime>/hooks/`
 
-Installer profiles keep the visible command surface calm. Start with `core` or
-`builder` unless you already know you need the full maintainer surface:
+Installer profiles keep the visible command surface calm. The default omitted
+profile is `core`; choose `builder` or `maintainer` only when you already know
+you need those leaves:
 
 ```bash
 npx godpowers --claude --global --profile=core
@@ -129,10 +131,11 @@ npx godpowers --codex --local --profile=builder
 npx godpowers --all --profile=maintainer
 ```
 
-Profiles are `core`, `builder`, `maintainer`, `suite`, and `full`. `full`
-preserves the complete command surface, while the smaller profiles install the
-commands most relevant to the role. `--minimal` is an alias for
-`--profile=core`.
+Profiles are `core`, `builder`, `maintainer`, `suite`, and `full`. `core`
+installs the front door, status, verb dispatchers, and `/god-mode`
+compatibility. `full` preserves the complete command surface, while the smaller
+profiles install the commands most relevant to the role. `--minimal` is an
+alias for `--profile=core`.
 
 Use profiles as journeys:
 
@@ -211,9 +214,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
 
@@ -226,13 +230,13 @@ commands remain direct shortcuts.
 
 | Goal | Starter path |
 |---|---|
-| Start a product | `/god-init`, `/god-prd`, `/god-design`, `/god-arch`, `/god-roadmap`, `/god-stack`, `/god-repo`, `/god-build` |
+| Start a product | `/god-init`, `/god-plan`, `/god-build` |
 | Add a feature | `/god-reconcile`, `/god-feature`, `/god-sync`, `/god-review` |
-| Fix production | `/god-hotfix`, `/god-postmortem`, `/god-status` |
+| Fix production | `/god-fix`, `/god-postmortem`, `/god-status` |
 | Audit an existing repo | `/god-preflight`, `/god-archaeology`, `/god-reconstruct`, `/god-audit`, `/god-tech-debt` |
-| Ship a release | `/god-sync`, `/god-docs`, `/god-version`, `/god-automation-setup`, `npm run release:check` |
+| Ship a release | `/god-ship`, `/god-sync`, `/god-docs`, `/god-version`, `npm run release:check` |
 | Maintain project health | `/god-hygiene`, `/god-update-deps`, `/god-docs`, `/god-check-todos` |
-| Extend Godpowers | `/god-extension-scaffold --name=@godpowers/my-pack --output=.`, `/god-test-extension`, `/god-extension-add`, `/god-extension-list` |
+| Extend Godpowers | `/god-extend scaffold --name=@godpowers/my-pack --output=.`, `/god-extend test`, `/god-extend add`, `/god-extend list` |
 
 ### Outcome Metrics
 
@@ -259,6 +263,7 @@ 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
@@ -289,8 +294,9 @@ 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 main `godpowers` runtime remains dependency-free. The optional
 `@godpowers/mcp` companion package owns the MCP SDK dependency and exposes
@@ -305,14 +311,14 @@ dependency to the main `godpowers` package:
 
 ```bash
 npx godpowers mcp-info --project=.
-npx -y -p godpowers@2.6.0 -p @godpowers/mcp@2.6.0 godpowers-mcp serve --project=.
+npx -y -p godpowers@3.0.0 -p @godpowers/mcp@3.0.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.6.0 -p @godpowers/mcp@2.6.0 godpowers-mcp setup --host=codex --project=. --write
+npx -y -p godpowers@3.0.0 -p @godpowers/mcp@3.0.0 godpowers-mcp setup --host=codex --project=. --write
 ```
 
 See [MCP Companion](docs/mcp.md) for package boundaries and setup details.
@@ -322,6 +328,11 @@ See [MCP Companion](docs/mcp.md) for package boundaries and setup details.
 | Command | What it does | Spawns agent |
 |---------|--------------|--------------|
 | `/god` | Front door: match free-text intent to a command sequence | (built-in) |
+| `/god-plan` | Route planning intent to planning leaves | (built-in) |
+| `/god-fix` | Route bug and outage intent to debug or hotfix | (built-in) |
+| `/god-ship` | Route deploy, observe, and launch intent | (built-in) |
+| `/god-capture` | Route notes, todos, backlog items, and seeds | (built-in) |
+| `/god-extend` | Route extension install, inspection, testing, and authoring | (built-in) |
 | `/god-mode` | Full autonomous project run | god-orchestrator |
 | `/god-next` | Auto-detect and suggest the next command | (built-in) |
 | `/god-init` | Start a project, detect mode and scale | (built-in) |
@@ -478,10 +489,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
@@ -496,7 +507,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
@@ -506,10 +518,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
 ```
 
@@ -587,7 +599,7 @@ Pi. T3 Code inherits from the underlying agent (Codex / Claude / OpenCode).
 - [Quick Proof](docs/quick-proof.md)
 - [First 10 Minute Proof Case Study](docs/case-studies/first-10-minute-proof.md)
 - [Concepts](docs/concepts.md)
-- [Command reference (all 112 skills + 40 agents)](docs/reference.md)
+- [Command reference (all 117 skills + 40 agents)](docs/reference.md)
 - [Feature awareness](docs/feature-awareness.md)
 - [Adoption Canary](docs/adoption-canary.md)
 - [Repository documentation sync](docs/repo-doc-sync.md)

package/RELEASE.md

@@ -1,60 +1,72 @@
-# Godpowers 2.6.0 Release
+# Godpowers 3.0.0 Release
 
-> Status: Release candidate
+> Status: Prepared
 > Date: 2026-06-10
 
-[DECISION] Godpowers 2.6.0 is the Phase 3 MCP companion package release.
-[DECISION] This release keeps the main `godpowers` package dependency-free while adding an optional `@godpowers/mcp` package for MCP-capable hosts.
-[DECISION] This release preserves the 2.5.2 installed-runtime gate command fix and build-gate false-pass fix.
+[DECISION] Godpowers 3.0.0 is the Phase 5 surface contraction release.
+[DECISION] This release makes the omitted installer profile resolve to `core` instead of `full`.
+[DECISION] This release keeps `--profile=full` as the complete compatibility surface for every shipped command.
+[DECISION] This release preserves the optional `@godpowers/mcp` companion boundary and keeps the main `godpowers` package dependency-free.
 
 ## What's in this release
 
-- [DECISION] 112 slash commands.
+- [DECISION] 117 slash commands.
 - [DECISION] 40 specialist agents.
 - [DECISION] 13 executable workflows.
 - [DECISION] 42 intent recipes.
-- [DECISION] 9 installer CLI helpers.
-- [DECISION] 5 read-only MCP tools in `@godpowers/mcp`.
+- [DECISION] Five thin verb dispatch commands: `/god-plan`, `/god-fix`, `/god-ship`, `/god-capture`, and `/god-extend`.
+- [DECISION] `core` installs the front door, status, verb dispatchers, and `/god-mode` compatibility.
+- [DECISION] `full` preserves all direct leaf commands and compatibility aliases.
+- [DECISION] Five read-only MCP tools remain available in `@godpowers/mcp`.
 
 ## Highlights
 
-- [DECISION] `@godpowers/mcp` exposes `status`, `next`, `gate_check`, `lint_artifact`, and `trace_requirement` over stdio.
-- [DECISION] `godpowers mcp-info --project=.` prints setup instructions without requiring or loading the MCP SDK in the main package.
-- [DECISION] `godpowers-mcp setup --host=codex --project=. --write` writes a managed Codex MCP registration only after the user explicitly asks for it.
-- [DECISION] Dashboard and Quick Proof host guarantee lines now include MCP availability.
-- [DECISION] The main `godpowers` package still has no production dependencies.
+- [DECISION] Omitted installer profile selection now writes `GODPOWERS_PROFILE` as `core`.
+- [DECISION] `/god-plan` routes planning intent to PRD, design, architecture, roadmap, stack, or reconstruction leaves.
+- [DECISION] `/god-fix` routes fix intent to debug or hotfix leaves.
+- [DECISION] `/god-ship` routes shipping intent to deploy, observe, or launch leaves.
+- [DECISION] `/god-capture` routes capture intent to note, todo, backlog, or seed leaves.
+- [DECISION] `/god-extend` routes extension intent to scaffold, add, list, info, remove, test, or agent-authoring leaves.
+- [DECISION] `/god-locate` is deprecated in favor of `/god-status --locate`.
+- [DECISION] `/god-lifecycle` is deprecated in favor of `/god-status --lifecycle`.
+- [DECISION] `/god-roadmap-check` now has `successor` metadata pointing to `/god-reconcile`.
 
 ## Validation
 
-- [DECISION] `npm --workspace @godpowers/mcp test` passed before the latest `main` merge.
-- [DECISION] `npm --workspace @godpowers/mcp run pack:check` 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] `npm run release:check` passed before the latest `main` merge with `coverage:lib` at 92.85 percent line coverage, `npm audit --omit=dev` reporting 0 vulnerabilities, public surface docs matching version 2.6.0, root package contents verified at 535 files, and MCP package contents verified at 8 files.
-- [DECISION] Post-merge 2.6.0 `npm --workspace @godpowers/mcp test` passed.
-- [DECISION] Post-merge 2.6.0 `npm --workspace @godpowers/mcp run pack:check` passed.
-- [DECISION] Post-merge 2.6.0 `node scripts/test-gate.js` passed.
-- [DECISION] Post-merge 2.6.0 `node scripts/test-install-smoke.js` passed.
-- [DECISION] Post-merge 2.6.0 `node scripts/static-check.js` passed.
-- [DECISION] Post-merge 2.6.0 `npm run test:e2e` passed.
-- [DECISION] Post-merge 2.6.0 `node scripts/test-runtime-verification.js` passed.
-- [DECISION] Post-merge 2.6.0 `node scripts/test-agent-browser.js` passed.
-- [DECISION] Post-merge 2.6.0 `npm run release:check` passed with `coverage:lib` at 92.88 percent line coverage, `npm audit --omit=dev` reporting 0 vulnerabilities, public surface docs matching version 2.6.0, root package contents verified at 535 files, and MCP package contents verified at 8 files.
+- [DECISION] `npm ci` passed and reported 0 vulnerabilities.
+- [DECISION] `node scripts/test-installer-profiles.js` passed.
+- [DECISION] `node scripts/test-surface-contraction.js` passed.
+- [DECISION] `node scripts/test-command-families.js` passed.
+- [DECISION] `node scripts/validate-skills.js` passed.
+- [DECISION] `node scripts/test-quick-proof.js` passed.
+- [DECISION] `node scripts/test-doc-surface-counts.js` passed with public surface docs matching version 3.0.0.
+- [DECISION] `node scripts/test-repo-doc-sync.js` passed.
+- [DECISION] `node scripts/test-repo-surface-sync.js` passed.
+- [DECISION] `node scripts/test-automation-surface-sync.js` passed.
+- [DECISION] `node scripts/test-router.js` passed.
+- [DECISION] `npm run test:e2e` passed.
+- [DECISION] `node scripts/test-runtime-verification.js` passed.
+- [DECISION] `node scripts/test-agent-browser.js` passed.
+- [DECISION] `node scripts/test-install-smoke.js` passed.
+- [DECISION] `node bin/install.js dogfood --json` passed 5 of 5 scenarios.
+- [DECISION] `npm --workspace @godpowers/mcp test` passed.
+- [DECISION] `npm run pack:check` passed with 548 root package files.
+- [DECISION] `npm run pack:mcp:check` passed with 8 companion package files.
+- [DECISION] `npm run lint` passed.
+- [DECISION] `npm run test:audit` passed with `npm audit --omit=dev`, `git diff --check`, and public surface checks green.
+- [DECISION] `npm run release:check` passed with `coverage:lib` at 92.79 percent line coverage, `npm audit --omit=dev` reporting 0 vulnerabilities, public surface docs matching version 3.0.0, root package contents verified at 548 files, and `@godpowers/mcp` package contents verified at 8 files.
+- [DECISION] Publish status remains pending until branch review, protected merge, registry credentials, and release hooks are all green.
 
 ## Upgrade
 
-- [DECISION] Use `npm install -g godpowers@2.6.0` or `npx godpowers@2.6.0` after the package is published.
+- [DECISION] Use `npm install -g godpowers@3.0.0` or `npx godpowers@3.0.0`.
+- [DECISION] Use `npx godpowers --profile=full` when the complete pre-3.0 command surface should be installed.
+- [DECISION] Use `npx godpowers --profile=core` or omit `--profile` for the contracted default surface.
 - [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 remains compatible.
 
 ## Notes
 
-- [DECISION] The npm `godpowers@2.5.2` package is published with provenance.
-- [DECISION] GitHub release `v2.5.2` was created at `https://github.com/aihxp/godpowers/releases/tag/v2.5.2`.
-- [DECISION] The 2.5.2 release-status closeout confirmed GitHub workflow `27289417888`, npm `latest` version 2.5.2, published-install verification, `npm run lint`, and `npm run release:check`.
-- [DECISION] GitHub release `v2.6.0` should be created only after the release gate passes on the merged branch.
-- [DECISION] The tag should match the npm package version.
-- [DECISION] The companion package should publish as `@godpowers/mcp@2.6.0` after the release gate passes.
-- [DECISION] The `v2.6.0` tag is not pushed yet because the current tag workflow publishes only the root `godpowers` package and does not publish `@godpowers/mcp`.
+- [DECISION] No npm publish has been attempted from this prepared release note.
+- [DECISION] No GitHub release has been created from this prepared release note.
+- [DECISION] The next bridge-plan action is protected review and merge for the Phase 5 behavior slice.

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.