godpowers 1.0.0 → 1.6.1

package/agents/god-roadmapper.md

@@ -20,6 +20,8 @@ Optional: `.godpowers/prep/INITIAL-FINDINGS.md` may exist as preparation
 context.
 Optional: `.godpowers/prep/IMPORTED-CONTEXT.md` may exist as preparation
 context.
+Optional: `.godpowers/domain/GLOSSARY.md` may exist as domain preparation
+context.
 Optional: `.godpowers/design/DESIGN.md` and `.godpowers/design/PRODUCT.md`
 may exist as early product-experience preparation.
 
@@ -39,6 +41,12 @@ stories and plans as hypothesis-level input only. Convert imported terminology
 into Godpowers vocabulary. Do not preserve imported methodology terminology in
 Godpowers artifacts unless the user explicitly asked for it.
 
+If `.godpowers/domain/GLOSSARY.md` exists, read it before sequencing work.
+Use canonical terms in increment goals, gates, dependencies, and feature
+names. Treat unresolved glossary ambiguities as roadmap `[OPEN QUESTION]`
+entries when they affect dependency order, scope boundaries, or completion
+gates.
+
 If DESIGN.md or PRODUCT.md exists, read them before sequencing delivery
 increments.
 Use screens, flows, components, accessibility obligations, and product voice to
@@ -51,6 +59,9 @@ Rules:
 - If imported context conflicts with PRD or ARCH, PRD and ARCH win.
 - Mark any imported sequencing assumption as `[HYPOTHESIS]` until confirmed by
   Godpowers artifacts or the user.
+- Do not invent roadmap terms when a canonical glossary term exists.
+- If glossary language conflicts with PRD or ARCH, PRD and ARCH win and the
+  conflict becomes an `[OPEN QUESTION]`.
 - Keep design-derived delivery increments grounded in the PRD and ARCH.
 - If ROADMAP creates durable delivery or sequencing truth, plan updates for
   relevant pillars. In `--yolo`, apply those updates and log them to

package/agents/god-stack-selector.md

@@ -19,6 +19,8 @@ Optional: `.godpowers/prep/INITIAL-FINDINGS.md` may exist as preparation
 context.
 Optional: `.godpowers/prep/IMPORTED-CONTEXT.md` may exist as preparation
 context.
+Optional: `.godpowers/domain/GLOSSARY.md` may exist as domain preparation
+context.
 Optional: `.godpowers/design/DESIGN.md` and `.godpowers/design/PRODUCT.md`
 may exist as product-experience preparation.
 
@@ -31,6 +33,10 @@ If `.godpowers/prep/IMPORTED-CONTEXT.md` exists, read its technical and stack
 signals before scoring candidates. Use imported technology choices, constraints,
 and team familiarity as hypothesis-level input only.
 
+If `.godpowers/domain/GLOSSARY.md` exists, read it before scoring candidates.
+Use it to understand domain relationships, ownership boundaries, data shape,
+integration language, and ambiguity that may affect stack fit.
+
 If DESIGN.md or PRODUCT.md exists, read them before scoring frontend,
 component, styling, accessibility, animation, and design-token tooling
 candidates.
@@ -40,6 +46,8 @@ Rules:
 - Treat imported technology choices as candidate evidence, not decisions.
 - If imported context conflicts with ARCH, ARCH wins and the conflict becomes a
   stack open question.
+- If glossary language changes apparent data ownership, integration boundaries,
+  or workflow complexity, reflect that in candidate scoring as evidence.
 - If design intent conflicts with ARCH NFRs, ARCH wins and the conflict becomes
   a stack or architecture open question.
 

package/lib/README.md

@@ -1,28 +1,80 @@
-# lib/ - Runtime Library (placeholder)
+# lib/ - Runtime Library
 
-This directory is reserved for v0.5+ runtime modules. v0.4 has the schemas
-defined; v0.5 implements them.
+This directory contains the JavaScript runtime modules that support Godpowers
+validation, routing, workflow execution, state management, observability, and
+package-level integrations.
 
-## Planned modules
+## Core state and intent
 
-| Module | Purpose | Target version |
-|--------|---------|----------------|
-| `state.js` | Read/write `.godpowers/state.json` with schema validation | v0.5 |
-| `events.js` | Append OpenTelemetry-shape events to events.jsonl | v0.5 |
-| `intent.js` | Read/validate `intent.yaml` (or `.godpowers/intent.yaml`) | v0.5 |
-| `workflow-runtime.js` | Parse and execute workflow YAML | v0.5 |
-| `reflog.js` | Append to `.godpowers/log` and rewind state | v0.6 |
-| `trash.js` | Recoverable deletion to `.godpowers/.trash/` | v0.6 |
-| `metrics.js` | Compute per-tier stats from events.jsonl | v0.7 |
-| `extension-loader.js` | Lazy-activate skill packs | v0.8 |
+| Module | Purpose |
+|--------|---------|
+| `state.js` | Read, initialize, validate, and write `.godpowers/state.json`. |
+| `state-lock.js` | Coordinate state writes with a lock file. |
+| `intent.js` | Read and validate `intent.yaml` from project roots or `.godpowers/`. |
+| `checkpoint.js` | Create and inspect resumable checkpoint artifacts. |
+| `budget.js` | Read and enforce configured budget controls. |
+| `cost-tracker.js` | Track token and cost estimates from event streams. |
 
-## Why placeholder
+## Events and observability
 
-In v0.4 (current), Godpowers is markdown skills + agent prose. There's no
-runtime that needs these modules; agents read/write artifacts directly.
+| Module | Purpose |
+|--------|---------|
+| `events.js` | Append structured runtime events. |
+| `event-reader.js` | Read and aggregate event streams. |
+| `otel-exporter.js` | Export Godpowers events in an OpenTelemetry-shaped format. |
+| `runtime-audit.js` | Audit runtime health and expected project state. |
+| `runtime-test.js` | Provide runtime checks used by package tests. |
 
-In v0.5+, the workflow runtime needs structured access to state. That's when
-these modules ship.
+## Routing and execution
 
-See `../ARCHITECTURE.md` for the design and `../docs/ROADMAP.md` for the
-sequencing.
+| Module | Purpose |
+|--------|---------|
+| `router.js` | Resolve user intent to skills, agents, recipes, and workflows. |
+| `recipes.js` | Load and validate routing recipes. |
+| `workflow-parser.js` | Parse workflow YAML into executable steps. |
+| `workflow-runner.js` | Execute workflow steps with validation hooks. |
+| `agent-cache.js` | Cache agent metadata for faster routing. |
+| `agent-validator.js` | Validate agent frontmatter and contracts. |
+
+## Artifact quality
+
+| Module | Purpose |
+|--------|---------|
+| `artifact-linter.js` | Check artifacts for required labels, evidence, and domain precision. |
+| `artifact-diff.js` | Compare artifact changes for review and release workflows. |
+| `have-nots-validator.js` | Check artifacts against known failure modes. |
+| `meta-linter.js` | Validate Godpowers documentation and skill metadata. |
+| `story-validator.js` | Validate story artifacts and story lifecycle state. |
+
+## Design, context, and integrations
+
+| Module | Purpose |
+|--------|---------|
+| `context-writer.js` | Produce tool-specific context files. |
+| `context-budget.js` | Keep generated context within budget. |
+| `design-detector.js` | Detect design-system conventions. |
+| `design-spec.js` | Normalize design specifications. |
+| `awesome-design.js` | Validate design guidance against awesome-design rules. |
+| `browser-bridge.js` | Connect browser verification flows. |
+| `agent-browser-driver.js` | Drive browser-backed agent checks. |
+| `skillui-bridge.js` | Bridge skill metadata into UI surfaces. |
+| `impeccable-bridge.js` | Bridge runtime checks into impeccable quality workflows. |
+| `extensions.js` | Load and validate extension packs. |
+
+## Repository and graph helpers
+
+| Module | Purpose |
+|--------|---------|
+| `code-scanner.js` | Scan source trees for routing and quality evidence. |
+| `cross-artifact-impact.js` | Detect relationships between changed artifacts. |
+| `cross-repo-linkage.js` | Track suite-level repository relationships. |
+| `drift-detector.js` | Detect context drift between artifacts and implementation. |
+| `impact.js` | Summarize expected impact of proposed changes. |
+| `linkage.js` | Connect artifacts, stories, and implementation files. |
+| `multi-repo-detector.js` | Detect multi-repository workspaces. |
+| `reverse-sync.js` | Reflect implementation changes back into artifacts. |
+| `review-required.js` | Decide when review gates should block progress. |
+| `suite-state.js` | Manage state across registered project suites. |
+
+See `../ARCHITECTURE.md` for system design and `../docs/ROADMAP.md` for planned
+runtime work.

package/lib/artifact-linter.js

@@ -6,7 +6,7 @@
  * findings.
  *
  * Public API:
- *   detectType(filePath) -> 'prd'|'arch'|'roadmap'|'stack'|'design'|'product'|null
+ *   detectType(filePath) -> 'prd'|'arch'|'roadmap'|'stack'|'design'|'product'|'domain'|null
  *   lintFile(filePath, opts) -> { type, findings, summary }
  *   lintAll(projectRoot, opts) -> [{ path, type, findings, summary }, ...]
  *
@@ -28,6 +28,7 @@ function detectType(filePath) {
   if (lower.includes('/arch/') || basename === 'arch.md') return 'arch';
   if (lower.includes('/roadmap/') || basename === 'roadmap.md') return 'roadmap';
   if (lower.includes('/stack/') || basename === 'stack-decision.md' || basename === 'decision.md') return 'stack';
+  if (lower.includes('/domain/') || basename === 'domain-glossary.md' || basename === 'glossary.md') return 'domain';
   if (basename === 'design.md') return 'design';
   if (basename === 'product.md') return 'product';
   if (basename === 'postmortem.md') return 'postmortem';
@@ -82,6 +83,7 @@ function lintAll(projectRoot, opts = {}) {
     '.godpowers/arch/ARCH.md',
     '.godpowers/roadmap/ROADMAP.md',
     '.godpowers/stack/DECISION.md',
+    '.godpowers/domain/GLOSSARY.md',
     '.godpowers/design/DESIGN.md',
     'DESIGN.md',
     'PRODUCT.md'

package/lib/have-nots-validator.js

@@ -22,6 +22,11 @@
  *   P-08 open-q without owner       mechanical (table column scan)
  *   P-09 open-q without due date    mechanical (table column scan)
  *   A-04 NFR not mapped              mechanical (PRD NFR vs ARCH map)
+ *   DG-01 term without avoid aliases mechanical (term block scan)
+ *   DG-02 implementation detail      partial mechanical (technical-word scan)
+ *   DG-03 ambiguity owner/due        mechanical (section scan)
+ *   DG-04 relationship undefined     mechanical (bold term cross-check)
+ *   DG-05 behavior definition        partial mechanical (verb scan)
  *
  * Substitution test (U-01) is a partial mechanical check: flags sentences
  * containing only generic nouns ('users', 'developers', 'scalable',
@@ -524,6 +529,163 @@ function checkArchNfrMap(content, opts = {}) {
   return findings;
 }
 
+/** DG-01: canonical term without avoided aliases */
+function checkDomainAvoidAliases(content) {
+  const findings = [];
+  const lines = content.split('\n');
+  for (let i = 0; i < lines.length; i++) {
+    const line = lines[i].trim();
+    const match = line.match(/^\*\*([^*\]]+)\*\*:\s*(.+)/);
+    if (!match) continue;
+    const term = match[1].trim();
+    if (!term || term.startsWith('[')) continue;
+    let hasAvoid = false;
+    for (let j = i + 1; j < Math.min(lines.length, i + 5); j++) {
+      const next = lines[j].trim();
+      if (/^\*\*[^*]+\*\*:/.test(next) || /^#{1,6}\s/.test(next)) break;
+      const avoidMatch = next.match(/^_Avoid_:\s*(.+)/i);
+      if (avoidMatch && avoidMatch[1].trim() && !avoidMatch[1].includes('[')) {
+        hasAvoid = true;
+        break;
+      }
+    }
+    if (!hasAvoid) {
+      findings.push({
+        code: 'DG-01',
+        severity: 'warning',
+        line: i + 1,
+        column: 1,
+        message: `Glossary term "${term}" has no avoided aliases listed.`,
+        suggestion: 'Add an _Avoid_: line with non-canonical aliases or overloaded words.'
+      });
+    }
+  }
+  return findings;
+}
+
+/** DG-02: implementation detail in glossary */
+function checkDomainImplementationDetails(content) {
+  const findings = [];
+  const technicalWords = /\b(src\/|lib\/|\.js\b|\.ts\b|\.tsx\b|React|Vue|Svelte|Postgres|MySQL|Redis|Kafka|API endpoint|endpoint|function|class|module|component|database|ORM|queue|HTTP|GraphQL)\b/i;
+  const lines = content.split('\n');
+  for (let i = 0; i < lines.length; i++) {
+    const line = lines[i];
+    if (technicalWords.test(line)) {
+      findings.push({
+        code: 'DG-02',
+        severity: 'warning',
+        line: i + 1,
+        column: 1,
+        message: 'Possible implementation detail in domain glossary.',
+        suggestion: 'Keep implementation details in PRD, ARCH, STACK, docs, or code-linked artifacts.'
+      });
+    }
+  }
+  return findings;
+}
+
+/** DG-03: unresolved ambiguity without owner or due date */
+function checkDomainAmbiguityOwners(content) {
+  const findings = [];
+  const section = extractSection(content, /^##\s*Flagged Ambiguities/im);
+  if (!section) return findings;
+  const lines = section.body.split('\n');
+  for (let i = 0; i < lines.length; i++) {
+    const line = lines[i].trim();
+    if (!line.startsWith('-')) continue;
+    const lineWithoutLabel = line.replace(/\[OPEN QUESTION\]/g, '');
+    if (lineWithoutLabel.includes('[')) continue;
+    const isOpen = line.includes('[OPEN QUESTION]') || /\bambigu/i.test(line);
+    if (!isOpen) continue;
+    if (!/\bOwner:\s*[^.\]]+/i.test(line)) {
+      findings.push({
+        code: 'DG-03',
+        severity: 'error',
+        line: section.startLine + i,
+        column: 1,
+        message: 'Glossary ambiguity has no owner.',
+        suggestion: 'Add Owner: [name] to the ambiguity.'
+      });
+    }
+    if (!/\bDue:\s*[^.\]]+/i.test(line)) {
+      findings.push({
+        code: 'DG-03',
+        severity: 'error',
+        line: section.startLine + i,
+        column: 1,
+        message: 'Glossary ambiguity has no due date.',
+        suggestion: 'Add Due: [date or command gate] to the ambiguity.'
+      });
+    }
+  }
+  return findings;
+}
+
+/** DG-04: relationship references undefined canonical term */
+function checkDomainRelationshipTerms(content) {
+  const findings = [];
+  const language = extractSection(content, /^##\s*Language/im);
+  const relationships = extractSection(content, /^##\s*Relationships/im);
+  if (!language || !relationships) return findings;
+
+  const canonical = new Set();
+  const languageLines = language.body.split('\n');
+  for (const line of languageLines) {
+    const match = line.trim().match(/^\*\*([^*\]]+)\*\*:/);
+    if (match && !match[1].startsWith('[')) {
+      canonical.add(match[1].trim());
+    }
+  }
+
+  const relLines = relationships.body.split('\n');
+  for (let i = 0; i < relLines.length; i++) {
+    const relLineWithoutLabels = relLines[i]
+      .replace(/\[DECISION\]/g, '')
+      .replace(/\[HYPOTHESIS\]/g, '')
+      .replace(/\[OPEN QUESTION\]/g, '');
+    if (relLineWithoutLabels.includes('[')) continue;
+    const boldTerms = [...relLines[i].matchAll(/\*\*([^*\]]+)\*\*/g)].map(m => m[1].trim());
+    for (const term of boldTerms) {
+      if (term.startsWith('[')) continue;
+      if (!canonical.has(term)) {
+        findings.push({
+          code: 'DG-04',
+          severity: 'warning',
+          line: relationships.startLine + i,
+          column: 1,
+          message: `Relationship references undefined glossary term "${term}".`,
+          suggestion: 'Define the term in Language or replace it with a canonical term.'
+        });
+      }
+    }
+  }
+  return findings;
+}
+
+/** DG-05: definition describes behavior instead of identity */
+function checkDomainDefinitionBehavior(content) {
+  const findings = [];
+  const behaviorWords = /\b(handles|processes|manages|stores|renders|calls|sends|receives|creates|updates|deletes|calculates|syncs)\b/i;
+  const lines = content.split('\n');
+  for (let i = 0; i < lines.length; i++) {
+    const line = lines[i].trim();
+    const match = line.match(/^\*\*([^*\]]+)\*\*:\s*(.+)/);
+    if (!match || match[1].startsWith('[')) continue;
+    const definition = match[2];
+    if (behaviorWords.test(definition)) {
+      findings.push({
+        code: 'DG-05',
+        severity: 'warning',
+        line: i + 1,
+        column: 1,
+        message: `Glossary definition for "${match[1]}" may describe behavior instead of identity.`,
+        suggestion: 'Define what the term is in one sentence. Put behavior in PRD, ARCH, or docs.'
+      });
+    }
+  }
+  return findings;
+}
+
 // ============================================================================
 // Helpers
 // ============================================================================
@@ -579,6 +741,13 @@ const ARTIFACT_CHECKS = {
   ],
   arch: [
     { code: 'A-04', fn: checkArchNfrMap }
+  ],
+  domain: [
+    { code: 'DG-01', fn: checkDomainAvoidAliases },
+    { code: 'DG-02', fn: checkDomainImplementationDetails },
+    { code: 'DG-03', fn: checkDomainAmbiguityOwners },
+    { code: 'DG-04', fn: checkDomainRelationshipTerms },
+    { code: 'DG-05', fn: checkDomainDefinitionBehavior }
   ]
 };
 
@@ -643,5 +812,10 @@ module.exports = {
   checkPrdNoGos,
   checkPrdOpenQuestions,
   checkArchNfrMap,
+  checkDomainAvoidAliases,
+  checkDomainImplementationDetails,
+  checkDomainAmbiguityOwners,
+  checkDomainRelationshipTerms,
+  checkDomainDefinitionBehavior,
   extractSection
 };

package/package.json

@@ -1,12 +1,12 @@
 {
   "name": "godpowers",
-  "version": "1.0.0",
-  "description": "AI-powered development system: 105 slash commands and 39 specialist agents that take a project from raw idea to hardened production. Runs inside Claude Code, Codex, Cursor, Windsurf, Gemini, and 10+ other AI coding tools.",
+  "version": "1.6.1",
+  "description": "AI-powered development system: 106 slash commands and 39 specialist agents that take a project from raw idea to hardened production. Runs inside Claude Code, Codex, Cursor, Windsurf, Gemini, and 10+ other AI coding tools.",
   "bin": {
     "godpowers": "./bin/install.js"
   },
   "scripts": {
-    "test": "node scripts/validate-skills.js && node scripts/test-doc-surface-counts.js && bash scripts/smoke.sh && node scripts/test-runtime.js && node scripts/test-router.js && node scripts/test-recipes.js && node scripts/test-context-writer.js && node scripts/test-pillars.js && node scripts/test-artifact-linter.js && node scripts/test-artifact-diff.js && node scripts/test-design-foundation.js && node scripts/test-linkage.js && node scripts/test-impact.js && node scripts/test-reverse-sync.js && node scripts/test-integration.js && node scripts/test-cross-artifact.js && node scripts/test-awesome-design.js && node scripts/test-skillui-bridge.js && node scripts/test-runtime-verification.js && node scripts/test-agent-browser.js && node scripts/test-mode-d.js && node scripts/test-runtime-heuristics.js && node scripts/test-agent-validator.js && node scripts/test-story-validator.js && node scripts/test-state.js && node scripts/test-intent.js && node scripts/test-events.js && node scripts/test-golden-artifacts.js && node scripts/test-install-smoke.js && node scripts/test-checkpoint.js && node scripts/test-extensions.js && node scripts/test-event-reader.js && node scripts/test-state-lock.js && node scripts/test-cost-saver.js && node scripts/test-budget-onoff.js && node scripts/test-workflow-runner.js && node scripts/test-otel-exporter.js && node scripts/test-extensions-publish.js",
+    "test": "node scripts/validate-skills.js && node scripts/test-doc-surface-counts.js && bash scripts/smoke.sh && node scripts/test-runtime.js && node scripts/test-router.js && node scripts/test-recipes.js && node scripts/test-context-writer.js && node scripts/test-pillars.js && node scripts/test-artifact-linter.js && node scripts/test-artifact-diff.js && node scripts/test-design-foundation.js && node scripts/test-linkage.js && node scripts/test-impact.js && node scripts/test-reverse-sync.js && node scripts/test-integration.js && node scripts/test-cross-artifact.js && node scripts/test-awesome-design.js && node scripts/test-skillui-bridge.js && node scripts/test-runtime-verification.js && node scripts/test-agent-browser.js && node scripts/test-mode-d.js && node scripts/test-runtime-heuristics.js && node scripts/test-agent-validator.js && node scripts/test-story-validator.js && node scripts/test-state.js && node scripts/test-intent.js && node scripts/test-events.js && node scripts/test-golden-artifacts.js && node scripts/test-install-smoke.js && node scripts/test-checkpoint.js && node scripts/test-extensions.js && node scripts/test-event-reader.js && node scripts/test-state-lock.js && node scripts/test-cost-saver.js && node scripts/test-budget-onoff.js && node scripts/test-workflow-runner.js && npm run test:e2e && node scripts/test-otel-exporter.js && node scripts/test-extensions-publish.js",
     "prepublishOnly": "npm test",
     "validate-skills": "node scripts/validate-skills.js",
     "test:surface": "node scripts/test-doc-surface-counts.js",
@@ -17,7 +17,11 @@
     "test:context": "node scripts/test-context-writer.js",
     "test:pillars": "node scripts/test-pillars.js",
     "test:linter": "node scripts/test-artifact-linter.js",
-    "test:diff": "node scripts/test-artifact-diff.js"
+    "test:diff": "node scripts/test-artifact-diff.js",
+    "test:e2e": "node tests/integration/full-arc.test.js",
+    "test:audit": "npm audit --omit=dev && git diff --check && npm run test:surface",
+    "pack:check": "node scripts/check-package-contents.js",
+    "release:check": "npm test && npm run test:audit && npm run pack:check"
   },
   "keywords": [
     "ai",

package/references/HAVE-NOTS.md

@@ -179,6 +179,30 @@ Choice motivated by "looks good on resume" rather than fit-for-PRD. Fail.
 Looks robust on paper but fails first real load. NFR validation must include
 worst-case analysis. Fail.
 
+#### A-13 ADR inflation
+An ADR records a decision that is easy to reverse, obvious without context, or
+not the result of a real tradeoff. Fail.
+
+### Domain Glossary Have-Nots
+
+#### DG-01 Canonical term without avoided aliases
+A glossary term names the canonical language but does not list avoided aliases.
+Fail.
+
+#### DG-02 Implementation detail in glossary
+The domain glossary stores implementation details, stack choices, code paths,
+or technical scratch notes. The glossary is domain language only. Fail.
+
+#### DG-03 Unresolved ambiguity without owner or due date
+An ambiguity is recorded without an owner or due date. Fail.
+
+#### DG-04 Relationship uses non-canonical term
+A relationship references a term that is not defined in the glossary language
+section. Fail.
+
+#### DG-05 Definition does behavior work
+A definition describes what the system does instead of what the term is. Fail.
+
 ### Roadmap Have-Nots
 
 #### R-01 Generic milestone goal

package/references/building/README.md

@@ -4,14 +4,12 @@ Per-tier reference content for Tier 2 (Building: Repo, Build).
 
 ## Files
 
-- (placeholder)
+- `BUILD-ANTIPATTERNS.md`: failure modes for implementation planning and execution.
+- `BUILD-VERTICAL-SLICES.md`: guidance for slicing work into user-visible increments.
+- `BUILD-WAVES.md`: dependency-aware parallelism patterns for multi-agent work.
 
-## Planned content
+## Use
 
-- TDD violation examples with how-to-fix
-- Two-stage review checklists with worked findings
-- Vertical slice anatomy with anti-examples (horizontal "set up the database")
-- Atomic commit examples
-- Wave parallelism dependency analysis worked examples
-
-See [HAVE-NOTS.md](../HAVE-NOTS.md) for the canonical failure-mode catalog.
+Use these references when reviewing implementation plans, build execution, and
+agent workstream shape. Pair them with [HAVE-NOTS.md](../HAVE-NOTS.md) for the
+canonical failure-mode catalog.

package/references/planning/README.md

@@ -4,13 +4,16 @@ Per-tier reference content for Tier 1 (Planning: PRD, Architecture, Roadmap, Sta
 
 ## Files
 
-- (placeholder; antipattern catalogs and worked examples to be added)
+- `PRD-ANATOMY.md`: structure and evidence expectations for product requirements.
+- `PRD-ANTIPATTERNS.md`: common ways PRDs become generic, untestable, or ungrounded.
+- `ARCH-ANATOMY.md`: architecture decision structure, boundaries, and tradeoff framing.
+- `ARCH-ANTIPATTERNS.md`: architecture theater, cargo-cult patterns, and weak constraints.
+- `STACK-ANATOMY.md`: stack decision shape, flip points, and operational fit.
+- `STACK-ANTIPATTERNS.md`: technology-choice failure modes and substitution-test misses.
+- `ROADMAP-ANATOMY.md`: sequencing, dependency, and milestone structure.
+- `ROADMAP-ANTIPATTERNS.md`: feature-factory, Gantt theater, and shelf-roadmap failures.
 
-## Planned content
+## Use
 
-- PRD anatomy with line-by-line annotations of a substitution-tested example
-- ARCH antipatterns: architecture theater, paper-tiger, cargo-cult cloud-native
-- Worked Stack decision examples with flip-point analysis
-- Roadmap anti-examples: Gantt theater, feature-factory output, shelf roadmaps
-
-See [HAVE-NOTS.md](../HAVE-NOTS.md) for the canonical failure-mode catalog.
+Use these references when reviewing or generating Tier 1 artifacts. Pair them
+with [HAVE-NOTS.md](../HAVE-NOTS.md) for the canonical failure-mode catalog.

package/references/shipping/README.md

@@ -4,15 +4,16 @@ Per-tier reference content for Tier 3 (Deploy, Observe, Launch, Harden).
 
 ## Files
 
-- (placeholder)
+- `DEPLOY-PATTERNS.md`: deployment promotion patterns and release safety checks.
+- `DEPLOY-ANTIPATTERNS.md`: deployment failure modes and operational shortcuts.
+- `OBSERVE-SLO-EXAMPLES.md`: SLO, alerting, and error-budget examples.
+- `OBSERVE-ANTIPATTERNS.md`: observability gaps, noisy alerts, and weak signals.
+- `LAUNCH-ANTIPATTERNS.md`: launch readiness, messaging, and adoption failure modes.
+- `HARDEN-OWASP-WORKSHEETS.md`: security review worksheets based on OWASP categories.
+- `HARDEN-ANTIPATTERNS.md`: hardening gaps and security theater patterns.
 
-## Planned content
+## Use
 
-- Same-artifact promotion patterns and anti-patterns
-- SLO worked examples with error budget policies
-- Symptom-vs-cause alerting catalog
-- OWASP Top 10 manual review worksheets
-- Launch copy substitution-test calibration set
-- D-7 to D+7 runbook templates
-
-See [HAVE-NOTS.md](../HAVE-NOTS.md) for the canonical failure-mode catalog.
+Use these references when preparing production releases, observability plans,
+launch plans, and hardening reviews. Pair them with
+[HAVE-NOTS.md](../HAVE-NOTS.md) for the canonical failure-mode catalog.

package/routing/god-mode.yaml

@@ -17,7 +17,8 @@ execution:
   reads:
     - .godpowers/prep/INITIAL-FINDINGS.md
     - .godpowers/prep/IMPORTED-CONTEXT.md
-  secondary-spawns: [god-pm, god-designer, god-architect, god-roadmapper, god-stack-selector, god-repo-scaffolder, god-planner, god-executor, god-spec-reviewer, god-quality-reviewer, god-deploy-engineer, god-observability-engineer, god-harden-auditor, god-launch-strategist]
+    - .godpowers/preflight/PREFLIGHT.md
+  secondary-spawns: [god-auditor, god-pm, god-designer, god-architect, god-roadmapper, god-stack-selector, god-repo-scaffolder, god-planner, god-executor, god-spec-reviewer, god-quality-reviewer, god-deploy-engineer, god-observability-engineer, god-harden-auditor, god-launch-strategist]
   writes:
     []
 

package/routing/god-preflight.yaml

@@ -0,0 +1,36 @@
+apiVersion: godpowers/v1
+kind: CommandRouting
+metadata:
+  command: /god-preflight
+  description: Read-only intake audit before arc-ready and pillars
+  tier: 0
+
+prerequisites:
+  required:
+    - check: codebase-present
+      human-required: true
+
+execution:
+  spawns: [god-auditor]
+  context: fresh
+  writes:
+    - .godpowers/preflight/PREFLIGHT.md
+
+success-path:
+  next-recommended: /god-archaeology
+  alternatives:
+    - command: /god-init
+      when: missing-basic-project-state
+    - command: /god-reconstruct
+      when: planning-artifacts-missing
+    - command: /god-tech-debt
+      when: debt-dominates-risk
+    - command: /god-audit
+      when: artifacts-exist
+
+failure-path:
+  on-error: /god-doctor
+
+endoff:
+  state-update: preflight completed
+  events: [agent.start, artifact.created, agent.end]

package/routing/recipes/bluefield-org-aware.yaml

@@ -19,6 +19,8 @@ sequences:
     steps:
       - command: "/god-org-context init"
         why: "Capture org-level standards and constraints"
+      - command: "/god-preflight"
+        why: "Inspect inherited context before arc-ready and pillars"
       - command: "/god-init"
         why: "Detect bluefield mode"
       - command: "/god-mode --bluefield"

package/routing/recipes/brownfield-onboarding.yaml

@@ -3,7 +3,7 @@ kind: Recipe
 metadata:
   name: brownfield-onboarding
   category: starting
-  description: "Inheriting an existing codebase; archaeology + reconstruction first"
+  description: "Inheriting an existing codebase; preflight before archaeology"
 
 triggers:
   intent-keywords:
@@ -16,8 +16,10 @@ triggers:
 
 sequences:
   default:
-    description: "Inheriting an existing codebase; archaeology + reconstruction first"
+    description: "Inheriting an existing codebase; preflight before archaeology"
     steps:
+      - command: "/god-preflight"
+        why: "Read-only intake audit before arc-ready and pillars"
       - command: "/god-archaeology"
         why: "Deep history, decisions, conventions, risks"
       - command: "/god-reconstruct"