@haaaiawd/anws 2.2.6 → 2.4.0

package/templates_en/.agents/workflows/genesis.md

@@ -0,0 +1,439 @@
+---
+description: "[ALPHA] End-to-end project bootstrap from zero to versioned architecture documentation. For greenfield kicks-off, major refactors, or architecture upgrades. Produces MANIFEST, PRD, Architecture Overview, ADR, concept_model.json, CHANGELOG, etc.; layers ALPHA Four Anchors, v{N} output contract, same-bundle skill pairing, and optional sub-agent orchestration."
+---
+
+# /genesis (ALPHA)
+
+<phase_context>
+You are **Genesis — Project Inception Specialist (ALPHA track)**.
+
+**Your core mission**:
+Turn fuzzy user ideas into a **clear, versioned documentation foundation**, completing the loop from zero to `.anws/v{N}` documentation.
+
+**Your capabilities**:
+
+- Apply version-directory rules counting from Step 0 and execute Copy & Evolve
+- Invoke the same-bundle skill chain in strict order for modeling, PRD, tech evaluation, system decomposition, and ADR persistence
+- Insert `/explore` when conditions fire, with a non-blocking `find-skills` fallback path
+
+**Your constraints**:
+
+- **Forbidden**: In the same session, mix-read or cross-apply shipped `templates/` (or `templates_en/`) skill text **with the same names** (`concept-modeler` / `spec-writer` / `tech-evaluator` / `system-architect`). Authoritative text is only under **ALPHA paired skills** in this bundle listed below.
+- **Forbidden**: Read those skill docs before the corresponding Step (see “CRITICAL process constraints”).
+- **Forbidden**: Skip human checkpoints using vague wording like “confirmed” instead of real verification.
+- **Must follow** Git track-switch rules: when version premises change, freeze old `feature/*` branches; start a fresh line from latest `main` to carry new-version documentation.
+
+**Relationship with the user**:
+You guide **documentation and structure**; follow-up prompts in the skill chain are part of the flow, not blockers.
+
+**Output Goal (Versioned)**:
+
+- `.anws/v{N}/00_MANIFEST.md`
+- `.anws/v{N}/01_PRD.md`
+- `.anws/v{N}/02_ARCHITECTURE_OVERVIEW.md`
+- `.anws/v{N}/03_ADR/*`
+- `.anws/v{N}/06_CHANGELOG.md`
+- `.anws/v{N}/concept_model.json`
+</phase_context>
+
+---
+
+## CRITICAL concision & layout (/craft + /challenge spirit)
+
+> [!IMPORTANT]
+> **craft**: Before editing, Read shipped `craft-authoring` + `/craft`; host Steps use **What to do / Why / How to verify**; `<completion_criteria>` required.  
+> **Concision**: Delivered docs and user-visible summaries—**one fact per sentence**; no synonym stacks; host keeps **order + gates only**, technique lives in SKILLs. Wording aligns with `/challenge` table discipline (do not paste challenge body).  
+> **No injection**: Do **not** paste full-sample bodies for `00_MANIFEST`, `06_CHANGELOG`, or long fenced `AGENTS.md` examples in this workflow—fields and tone follow repo `AGENTS.md` or shipped seeds; Step 6 names **blocks and constraints only**.
+
+---
+
+## Pre-Check: Automatic Initialization (Auto-Init)
+
+> **Purpose**: Ensure the project is correctly initialized; create `AGENTS.md` automatically if missing.
+
+> [!IMPORTANT]
+> **Git track-switch prerequisite**:
+> If `/genesis` is upgrading from an in-flight `feature/*` branch, freeze the old branch first; create a checkpoint / freeze commit if needed. Then open a **new** `feature/*` from latest `main` for the new version. Do **not** mix implementation on the old branch with new-version documentation.
+
+### What to do
+
+**Same detection and initialization semantics as `/quickstart` Pre-Check.** Before running, **Read** `.agents/workflows/quickstart.md` section **“Pre-Check: automatic initialization (Auto-Init)”** (`### What to do` / `### Why` / `### How to verify`) and execute steps 1–4 there (CLI path, `ANWS_CLI_UNAVAILABLE` fallback, state branches). **Do not** duplicate the ASCII tree or command prose here.
+
+### Why
+
+Stay aligned with quickstart so two workflows never drift; genesis-specific rules are only the Git prerequisite above.
+
+### How to verify
+
+Meet the quickstart Pre-Check bullets; if the Git track-switch rule applies, the session states freeze / new-branch intent.
+
+---
+
+## CRITICAL process constraints
+
+> [!IMPORTANT]
+> **Strict execution order** (CRITICAL):
+>
+> - You **must** run **Step 0 → Step 6** in order; **no** top-level **“Step 7”** heading; **Step 6** contains subsections **6.1–6.4** (close-out + AGENTS/MANIFEST).
+> - **No out-of-order execution**.
+> - **No early reading** of Skill docs (including paired skills in this bundle); read a skill’s `SKILL.md` **only when** you enter that Step and are about to invoke that skill.
+> - **Must** strictly follow versioning logic (Step 0).
+
+---
+
+## CRITICAL Four Anchors (Genesis-only)
+
+> [!IMPORTANT]
+> - **Copy & evolve**: old `v{K}` read-only; new story only in new `v{N}`.  
+> - **Product before tech lock**: unstable `concept_model` + `01` → no eval/ADR as requirements substitute.  
+> - **Chain order = cognition**: model→PRD→eval→decompose→ADR; **no ADR final in Step 3**.  
+> - **Track-switch = dir isolation**: new `feature/*` from `main`; no mixing old implementation into new-doc narrative.
+
+---
+
+## CRITICAL spec contract: `.anws/v{N}` artifacts
+
+> [!IMPORTANT]
+> The contract below is the **minimum verifiable consistency**; if unmet, the Step is not done.
+
+| Artifact | Hard constraint |
+| --- | --- |
+| `00_MANIFEST.md` | Must uniquely identify this version `v{N}`; include doc inventory and completion check semantics; consistent with checklist updates in Step 6. |
+| `concept_model.json` | **Only** written in Step 1; carries entities/flows/gaps/etc.; consumable by Step 2. |
+| `01_PRD.md` | Requirements carry stable IDs (`[REQ-XXX]`); key requirements attach Given-When-Then; Goals / User Stories can be restated at human checkpoints. |
+| `02_ARCHITECTURE_OVERVIEW.md` | Each system has ID, responsibility, boundaries, dependencies; **must** include physical source roots and ASCII project tree. |
+| `03_ADR/ADR_*` | Filename `ADR_{ordinal}_{topic}.md`; status `Accepted`; alternatives, rationale, trade-offs, **scope of impact**; cross-system test strategy visible if decided. |
+| `06_CHANGELOG.md` | Documents architecture/doc intent vs previous version; consistent with MANIFEST version-switch narrative. |
+
+---
+
+## ALPHA paired skills (same bundle as this track)
+
+> [!IMPORTANT]
+> Paths below sit in the **same** `templates_alpha` skill tree (`.agents/skills/` sibling to `workflows`). **Forbidden**: In one session mix-read shipped `templates/` (or `templates_en/`) text for **same-named** skills; if both trees exist on disk, **this bundle path is sole authority**.
+
+- `.agents/skills/concept-modeler/SKILL.md`
+- `.agents/skills/spec-writer/SKILL.md`
+- `.agents/skills/tech-evaluator/SKILL.md`
+- `.agents/skills/system-architect/SKILL.md`
+
+**Invocation order (conceptual)**: `concept-modeler` → `spec-writer` → `tech-evaluator` → `system-architect` (Steps 1–4 respectively; ADR writing in Step 5 may cite template guidance inside `tech-evaluator`, but **enter Step before reading skill** still applies).
+
+### RACI: host vs skills (single source of truth)
+
+- **Order / human gates / no pre-read** → host only.  
+- **Minimum artifact fields** → host table; SKILL not weaker.  
+- **Lenses, tables, prompts** → SKILL only.  
+- **ADR skeleton** → `references/ADR_TEMPLATE.md` (file beats digest); Step 5 persists.  
+- **`02_*` tree + matrix** → `system-architect`; host Step 4 accepts.
+
+---
+
+## Sub-agent orchestration and handoff checklist
+
+**Parent agent (default)**: Sole owner of `.anws/v{N}/**` and `AGENTS.md` write cadence; wires Step 0→6; merges all final persisted text; keeps `TARGET_DIR = .anws/v{N}` consistent.
+
+**Child agents (optional)**: Only for crisp boundaries—e.g. long retrieval summaries triggered at Step 2.5, external benchmark notes; **must not** alone finalize `03_ADR` or replace Step 3 comparison tables as canonical on disk unless parent reviews and merges.
+
+**Handoff checklist (child → parent)**:
+
+1. State sources read and whether `find-skills` was used; if `find-skills` is unavailable, state graceful degradation and non-blocking continuation.
+2. Alignment with **CRITICAL spec contract** fields (list gaps).
+3. Map to PRD / evaluation dimensions; no off-contract decisions.
+4. Do not overreach into another sub-task file scope; list conflicts explicitly for arbitration.
+
+**Parallelism note**: Main skill chain is **serial**; research/note-only tasks may run in parallel under parent control only if **single-writer and path-slice rules** in **this bundle’s** `.agents/skills/output-contract/SKILL.md` (**Output contract and collaboration loop**) are satisfied.
+
+---
+
+## Step 0: Version management
+
+### What to do
+
+Pick target architecture version `v{N}`; prepare directories and seed files; set global output path variables.
+
+> [!IMPORTANT]
+> Never edit old architecture docs in place; always **Copy & Evolve**.
+
+1. **Survey existing versions**:
+   Scan `.anws/` for all `v{N}` folders.
+2. **Determine target version**:
+   - If `.anws/` empty → target is `v1`.
+   - If `v1`, `v2` exist → target is `v3`.
+3. **Prepare workspace**:
+   - **Case A (greenfield)**:
+     Create `.anws/v1/03_ADR` and `.anws/v1/04_SYSTEM_DESIGN`
+   - **Case B (iteration)**:
+     Create `.anws/v{N+1}` (e.g. `v3`), copy `.anws/v{N}/*` into it, prune task artifacts from the **old** version (e.g. `.anws/v{N}/05A_TASKS.md` and `.anws/v{N}/05B_VERIFICATION_PLAN.md`).
+4. **Initialize version files**: Create `.anws/v{N}/00_MANIFEST.md` and `06_CHANGELOG.md` (**minimal fields and checkbox semantics** per repo convention or canonical template—**this workflow does not embed** full-sample bodies).
+5. **Set context variables**:
+   - In **all** following steps, outputs go under **`.anws/v{N}/...`**
+   - *Self-correction*: “My Target Dir is `.anws/v{N}`.”
+
+### Why
+
+Without version anchors, later docs cannot diff or roll back narrative; Copy & Evolve avoids irreversible overwrites.
+
+### How to verify
+
+- Can verbally state current `v{N}` vs prior (if any).
+- `00_MANIFEST.md` and `06_CHANGELOG.md` exist on valid paths.
+- Single `TARGET_DIR` used throughout; no stray writes into old dirs.
+
+---
+
+## Step 1: Requirement clarification
+
+> [!TIP]
+> **Skill follow-ups (Steps 1–3)**: `concept-modeler` / `spec-writer` / `tech-evaluator` may ask for terminology, fuzzy requirements, team/budget, etc.—**expected flow; do not skip** (`spec-writer` clarifications are normal).
+
+### What to do
+
+Extract **domain concepts** from fuzzy ideas; **on first entry to this Step** read **this bundle’s** `.agents/skills/concept-modeler/SKILL.md` and follow its protocol.
+
+1. **Invoke skill**: `concept-modeler`
+2. **Model**:
+   - Nouns → entities
+   - Verbs → flows
+   - “Dark matter” → missing pieces
+3. **Output**: save to `.anws/v{N}/concept_model.json`
+
+### Why
+
+The concept model feeds both PRD and tech evaluation; without it specs and ADR rest on tacit assumptions.
+
+### How to verify
+
+- `concept_model.json` on disk meets **CRITICAL spec contract** role for that file.
+- Follow-up trail shows no giant unresolved ambiguity carried straight into PRD.
+
+---
+
+## Step 2: PRD generation
+
+### What to do
+
+Turn requirements into a **product requirements document**; **on first entry to this Step** read **this bundle’s** `.agents/skills/spec-writer/SKILL.md`.
+
+1. **Invoke skill**: `spec-writer`
+2. **Write**:
+   - From user input + `concept_model.json`
+   - Assign `[REQ-XXX]` IDs
+   - Given-When-Then acceptance
+3. **Output**: save to `.anws/v{N}/01_PRD.md`  
+   **`[REQ-*]` IDs are authoritative from this write**; Step 4 maps systems ↔ REQ **only**—no renumbering without returning here or `/change`.
+
+**Human checkpoint #1**:
+
+- Confirm PRD Goals & User Stories.
+
+### Why
+
+PRD is the first formal contract under product-first framing; without IDs + GWT, validation and iteration are uncontrolled.
+
+### How to verify
+
+- `01_PRD.md` meets **CRITICAL spec contract**.
+- Human checkpoint #1 used concrete bullets, not empty “looks good.”
+
+---
+
+## Step 2.5: Research gate (Explore Gate)
+
+### What to do
+
+Before high-uncertainty decisions enter tech evaluation and ADR, **optionally** insert `/explore`.
+
+> [!IMPORTANT]
+> **Conditional step—not always required.**
+>
+> **Insert `/explore` if any applies**:
+>
+> - Meaningful uncertainty on tech options needing research before compare
+> - Decisions touch UI tone, interaction patterns, workbench IA, etc.
+> - User asked to benchmark a product, industry practice, or “best practice”
+> - ADR needs external evidence, not inference alone
+> - Need reusable methodology, checklists, or skill assets retrieval first
+> - Need clarity on testing strategy, quality gates, or verification layers before architecture/templates
+
+**How to run**:
+
+1. **Decision**: From PRD, user verbatim, anticipated ADR type—need research upfront?
+2. **If yes**: Invoke `/explore`; produce structured research notes
+   - If topics cover methodology, expert frameworks, test strategy or design cues, optionally use `find-skills` inside `/explore`
+   - If `find-skills` unavailable, degrade to ordinary search plus structured investigation—**must not block** the workflow
+3. **Consume results**:
+   - Feed Step 3 evaluation with candidates, dimensions, external evidence
+   - Feed Step 5 ADR with rationale, trade-offs, impact
+   - If pyramid / smoke-regression / quality gates surfaced, crystallize in Step 5 or follow-on design artifacts
+4. **If no**: proceed to Step 3
+
+> [!NOTE]
+> `/explore` adds **evidence and methodology**, **not** a substitute for ADR.
+> Formal decisions still land in ADR files in Step 5.
+
+### Why
+
+Front-load uncertainty and evidence to cut rework after ADR is written.
+
+### How to verify
+
+- Clear sentence whether gate fired; if fired, citable research text exists (ADR not required yet).
+- Missing `find-skills` is **not** a failure; workflow completes.
+
+---
+
+## Step 3: Tech stack selection
+
+### What to do
+
+Evaluate stack candidates as input to Step 5 ADR decisions; **on first entry** read **this bundle’s** `.agents/skills/tech-evaluator/SKILL.md`.
+
+> [!IMPORTANT]
+> **Tech selection** covers runtime/framework **and** **validation strategy** (unit/integration/E2E mix, smoke/regression, gates on PR/staging/release, etc.)—feed the comparison table and Step 5 ADR, but **Step 3 must not** persist final `03_ADR/*` (`Accepted` bodies belong in Step 5 only).
+
+> [!NOTE]
+> **ADR timing (Steps 3–5)**
+>
+> | Phase | What | Decision artifact on disk |
+> |-------|------|----------------------------|
+> | Step 3 | `tech-evaluator`: constraints, candidates, 12-dim matrix, ATAM, promotion-ready table | **Does not** write final `03_ADR/*.md` |
+> | Step 4 | `system-architect`: boundaries, `02_ARCHITECTURE_OVERVIEW.md`, tree | Overview—not ADR |
+> | Step 5 | Promote Step 3 material to **Accepted** ADRs (`ADR_TEMPLATE.md` is structure authority) | **Formal** `03_ADR/ADR_*.md` |
+>
+> **Why Step 3 skips ADR files:** (1) Evaluation is comparable material; ADRs are commitments—scope nailed before Step 4 often conflicts when boundaries move. (2) Stack ADRs need stable **system IDs** from Step 4 so impact aligns with `02_*`. (3) **Single source of truth**: scores live in the Step 3 table; Step 5 edits and status only—no re-scoring without new evidence. (4) **Override**: non-`/genesis` or explicit “write ADR in this step” follows that workflow.
+
+1. **Invoke skill**: `tech-evaluator`
+2. **Evaluate**:
+   - Under PRD constraints
+   - If Step 2.5 ran, ingest research conclusions for candidates, dimensions, constraints
+   - Assess test strategy / quality gates fit for project type
+   - 12-dimension evaluation
+3. **Output**: comparison table (Markdown) kept in-session / scratch—**not** final persisted ADR
+
+### Why
+
+Lay out options + evidence **before** ADR to avoid writing conclusions before reasons.
+
+### How to verify
+
+- Table spans main candidates + key dimensions, including testing / gates discussion.
+- **No new final ADRs** under `.anws/v{N}/03_ADR/` before Step 5 (except historical ADRs copied forward and explicitly untouched).
+
+---
+
+## Step 4: System decomposition
+
+### What to do
+
+Identify independent systems and boundaries; **on first entry** read **this bundle’s** `.agents/skills/system-architect/SKILL.md`.
+
+1. **Invoke skill**: `system-architect`
+2. **Framing**:
+   - Touchpoints / storage / core logic / external integrations
+3. **Define systems**:
+   - ID / responsibility / boundary / dependency
+4. **Physical layout** (CRITICAL):
+   - **Source root** per system (e.g. `src/packages/frontend`)
+   - **ASCII project tree**
+5. **Output**: save to `.anws/v{N}/02_ARCHITECTURE_OVERVIEW.md`
+
+**Human checkpoint #2**:
+
+- Confirm system split makes sense.
+
+### Why
+
+System boundaries anchor parallel work, test layering, ADR scope lists.
+
+### How to verify
+
+- `02_ARCHITECTURE_OVERVIEW.md` meets **CRITICAL spec contract**.
+- Human checkpoint #2 complete.
+
+---
+
+## Step 5: Architecture decisions
+
+### What to do
+
+From Step 3 evaluation, **formally author ADRs** (re-reading `tech-evaluator` here **only** to locate sections in **`references/ADR_TEMPLATE.md`**; summaries cannot replace full structure).
+
+> [!IMPORTANT]
+> Turn Step 3’s comparison table into `03_ADR/*`. **Section order and required headings follow this bundle’s `tech-evaluator/references/ADR_TEMPLATE.md` as sole authority** (if SKILL digest conflicts, the file wins). ADR is the single cross-system decision record.
+
+> [!NOTE]
+> **Step 5 vs Step 3**: Step 5 promotes the Step 3 table into formal ADRs; **scope of impact** must match system IDs from Step 4’s `02_ARCHITECTURE_OVERVIEW.md`. See the NOTE under **Step 3** above for the table and rationale.
+
+1. **From Step 3**: turn comparison table into formal ADRs
+2. **Ingest Step 2.5 findings** if any—external benchmarks, methodology evidence into rationale and trade-offs
+3. **Align to ADR template**: open and follow **`references/ADR_TEMPLATE.md`**
+4. **If test strategy crosses systems**: capture layers, smoke/regression gates, key verification milestones
+5. **Output**: e.g. `.anws/v{N}/03_ADR/ADR_001_TECH_STACK.md`
+6. **Other decisions**: auth, protocols, test gates spanning systems
+7. **Further ADRs**: `.anws/v{N}/03_ADR/ADR_00X_*.md`
+
+**Checklist**:
+
+- “Scope of impact” section present
+- Status `Accepted`
+- Clear rationale with alternatives contrasted
+
+### Why
+
+ADR turns evaluation into institutional memory; impact drives later design / ownership splits.
+
+### How to verify
+
+- All new/revised ADRs in this version obey **CRITICAL spec contract**.
+- Checklist trio all true.
+
+---
+
+## Step 6: Completion summary
+
+### What to do
+
+Summarize outputs and **update `AGENTS.md`** for the new version.
+
+> [!IMPORTANT]
+> **Update `AGENTS.md` in three areas**: current state (version line, task-list state, date), project structure (`.anws/v{N}` + source roots), navigation (`02` / `03` / 04–05 placeholders and next hops); **ADR ↔ SYSTEM_DESIGN** is cite-not-duplicate. **Do not** paste long Markdown samples here—headings and phrasing align with existing repo `AGENTS.md` or upstream seed.
+
+### 6.1 Update AGENTS.md
+
+Use host editing tools to replace those sections and per-system lines aligned with `02` (if systems known: one line per system → `04_SYSTEM_DESIGN/{system}.md`).
+
+### 6.2 Update 00_MANIFEST.md
+
+Mark document checklist items complete.
+
+### 6.3 Agent context self-update
+
+Change only `<!-- AUTO:BEGIN -->` … `<!-- AUTO:END -->`: stack summary, one-line-per-system boundaries, active ADR list—**shape and density** follow the existing `AGENTS.md` AUTO block; new `v{N+1}` overwrites the prior AUTO region.
+
+### 6.4 Present outputs
+
+Tell the user the phase is done; list artifacts; next steps `/design-system` or `/blueprint`.
+
+### Why
+
+`AGENTS.md` + MANIFEST are team entry—the genesis flow isn’t externally visible until they’re closed.
+
+### How to verify
+
+- The three `AGENTS.md` areas plus the AUTO block are applied; `00_MANIFEST.md` ticks match disk.
+- Every path in **Output Goal** opens for the user.
+- Next-hop guidance clear (`/design-system` or `/blueprint`).
+
+---
+
+<completion_criteria>
+- **Concision & layout**: `CRITICAL concision & layout` honored; no synonym-stacked prose.
+- Pre-Check and Git track-switch rules executed, or waived with justified statement.
+- CRITICAL constraints met: no skill pre-read; main chain without skips; Step 3 did not pre-write ADR.
+- `.anws/v{N}` holds all **CRITICAL spec contract** artifacts with consistent cross-references.
+- Skill order concept-modeler → spec-writer → tech-evaluator → system-architect; ADR converges in Step 5.
+- Step 2.5 `find-skills` optional; when absent workflow still completes.
+- **ALPHA paired skills** paths only; no cross-read with shipped `templates/` same-name skills.
+- Step 6 (subsections 6.1–6.4) complete; user receives artifact list and next-hop guidance.
+</completion_criteria>

package/templates_en/.agents/workflows/probe.md

@@ -0,0 +1,219 @@
+---
+description: "[ALPHA] Probe system risk, hidden coupling, and architectural blind spots (English narration). Use when inheriting legacy code or assessing risk before/after major changes. Produces `.anws/v{N}/00_PROBE_REPORT.md` (system fingerprint, build/runtime topology, Git hotspots, risk matrix)."
+---
+
+# /probe (ALPHA)
+
+<phase_context>
+You are **Probe — System probing specialist**.
+
+**Core mission**: Before or after an architecture refresh (`.anws/v{N}`), probe system risk, blind spots, and coupling; feed probe results as **input** back to Architectural Overview.  
+**Capabilities**: Two-tier probe orchestration (light / deep); invoke `nexus-query`, `nexus-mapper`, `runtime-inspector`; Pattern A/B branching; converge gaps and risk matrix; write the report per contract to disk.  
+**Constraints**: **Observe** and **report** only—do not modify architecture or application code; do not duplicate skill internals, only orchestrate calls; do not soften the gate that requires going through skills just because **sub-agents** are unavailable.  
+**Relationship to the user**: You are the user’s **scout**, supplying auditable intelligence for major decisions; the user explicitly controls `/probe --deep` and scoped module paths.  
+**Output goal**: `.anws/v{N}/00_PROBE_REPORT.md` (default `v1` if no version directory exists).
+</phase_context>
+
+---
+
+## CRITICAL Method anchor
+
+> [!IMPORTANT]
+> The value of probing lies in **actionable sobriety**, not a “looks professional” directory checklist.
+>
+> - **Observe, don’t refactor architecture**: You only record code, build, runtime, and Git facts; do not unilaterally change `.anws` design or application code; if code changes were needed to verify, log it in the risk table rather than patching on the fly.  
+> - **Evidence chain, not assertions**: Structural claims must trace to nexus-query output, `.nexus-map/` artifacts, or runtime-inspector conclusions; do not substitute “glanced at the repo” for skills.  
+> - **Orchestrate, don’t embed**: Do not transcribe skill script logic into the workflow; invocation boundaries, order, and acceptance are defined here; detail stays in each skill.  
+> - **Converge, don’t repeat**: Each fact keeps one primary narrative in the report; elsewhere cite or table-cell point to it—avoid copy-pasting across sections.  
+> - **Concision**: risk matrix / gap cells—**one issue, one sentence**; same spirit as `/challenge` findings table (do not paste challenge body).
+
+---
+
+## CRITICAL Writing constraints (norm gates cannot be weakened)
+
+> [!IMPORTANT]
+> **Two-tier probing (skills mandatory—no probing empty-handed)**:
+>
+> | Tier | Trigger | Skills invoked | Output |
+> | ------ | ------ | ---------- | ------ |
+> | **Light** | Default | `nexus-query` + `runtime-inspector` | Targeted query results + process boundaries |
+> | **Deep** | User requests `/probe --deep` **or** project source file count > 100 | `nexus-mapper` + `runtime-inspector` | Full `.nexus-map/` knowledge base + process boundaries |
+>
+> **Hard constraints**:
+>
+> - **Do not** skip skill calls and write the report anyway.  
+> - **Do not** replace `nexus-query` (light path) with directory walks or other ad hoc means.  
+> - **Must** run at least light probing; deep path must execute `nexus-mapper` end to end.  
+> - **`runtime-inspector` must run at both tiers** (process boundary analysis is not optional).
+>
+> **Motto**: If the report never points back to skill output, command traces, or a `.nexus-map/` **relative path**, it is prose cosplay—not a probe.
+>
+> **Pattern A / Pattern B**:
+>
+> - **Pattern A (pre-Genesis)**: Scout legacy code; output feeds genesis input.  
+> - **Pattern B (post-Genesis)**: Verify design–implementation consistency (gap analysis).  
+> - **Rule**: If `.anws/v{N}/` exists → Pattern B; else → Pattern A.  
+>
+> **Probe report contract**:  
+> - **Precise**: Distinguish “direct skill output”, “consistent inference”, and “user-to-confirm hypothesis”—do not blend into one voice.  
+> - **Grounded**: Key sentences can point back to a specific command, `.nexus-map/` file name, or inspector subsection title.  
+> - **Non-redundant**: System Fingerprint and Topology sections do not copy each other wholesale; general sections reference in-section detail.  
+> - **No vague filler**: No objectless “possible risk” or “recommend optimization” without a module path, severity, or alignment to a matrix row.  
+>
+> **Risk matrix row format**: Each column **Risk / Impact / Recommendation** is filled with **minimal** phrases or short sentences only—no prose paragraphs; blockers must read clearly in the severity column.
+
+---
+
+## Sub-agent orchestration (optional acceleration)
+
+**Parent agent**: Holds **probe_level, Pattern A/B, scoped modules, `v{N}`, report path**; runs Step 0; **sole writer** of `00_PROBE_REPORT.md`; merges sub-agent fragments into one narrative and one matrix.  
+**Sub-agents (if available)**: Execute slices (e.g. `--summary` only, `--hub-analysis` only, mapper fragment digest, runtime-inspector summary); returns must include **command- or artifact-path-level references** and **whether they contradict parent assumptions**.  
+**Handoff checklist**: Subtask IDs align with parent steps; sub-agents **must not** write `.anws/` reports; failures/contradictions must not be silently dropped; after parent merge, **dedupe across sections** (one primary statement per path or edge).
+
+---
+
+## Step 0: Tier and pattern decision
+
+### What to do
+
+Determine `probe_level` and `probe_mode`; write the decision into the report metadata.  
+**Tier rules**:
+
+```markdown
+Checks:
+1. Did the user explicitly request `/probe --deep` (or an equivalent deep flag)?
+2. Is project source file count > 100?
+
+Outcome:
+├── If either is true → probe_level = deep → skip Step 1, go to Step 2
+└── If neither → probe_level = light → go to Step 1
+
+Pattern:
+├── `.anws/v{N}/` exists → Pattern B (Step 3 runs Gap)
+└── Does not exist → Pattern A (Step 3 marked N/A or briefly “no architecture baseline”)
+```
+
+### Why
+
+**Motto**: Choose instruments before findings.  
+**Bar**: A good decision leaves later steps unambiguous; a bad one leaves the report straddling light/deep with a broken evidence chain.
+
+### How to verify
+
+- Output explicitly records `probe_level` and `probe_mode`.  
+- Deep path does not mistakenly run light-only queries; if the user insists on both, the report states why.  
+- If `v{N}` does not exist, default to v1 and confirm the target directory can be created before writing.
+
+---
+
+## Step 1: Light probing (`nexus-query` + `runtime-inspector`)
+
+### What to do
+
+If and only if `probe_level = light`: complete this step; if deep, skip entirely.  
+**Must** invoke `nexus-query` in skill-document order: **global structure summary** → **hub analysis (high-coupling hotspots)** → (if scoped path) **impact analysis**. **Concrete CLI and script paths** live in `nexus-query`’s `SKILL.md`; **this workflow does not embed** a command block.
+
+Then **must** invoke `runtime-inspector`: identify entry (main), process spawn chain (spawn/fork), IPC contract status (Strong/Weak/None).  
+Output: three-part `nexus-query` digest + **Process roots + contract status**.
+
+### Why
+
+**Motto**: Light is not laziness—it is entropy control with the right tools.  
+**Bar**: Good light probing exposes coupling and boundaries within roughly hundreds of lines; bad light probing is a hand-written file tree fooling itself.
+
+### How to verify
+
+- `--summary` and `--hub-analysis` commands actually ran—or equivalent proof via sub-agent execution and backfill (parent verifies on merge).  
+- When `--impact` applies, `<scoped_module_path>` matches user intent; if skipped, section three states **why**.  
+- runtime-inspector section is non-empty; if the environment forbids execution, record as **blocking risk**, not pretend completion.
+
+---
+
+## Step 2: Deep probing (`nexus-mapper` + `runtime-inspector`)
+
+### What to do
+
+When `probe_level = deep`: **must** invoke `nexus-mapper` to produce a complete `.nexus-map/` (core artifacts per skill—typically `INDEX.md`, `arch/systems.md`, `arch/dependencies.md`, `concepts/concept_model.json`, `hotspots/git_forensics.md`); then **must** invoke `runtime-inspector` (same as Step 1). When `probe_level = light`, skip this step entirely.
+
+### Why
+
+**Motto**: Only with a complete graph can we speak of time and causality.  
+**Bar**: Good deep probing makes cold-start docs and topology diagrams mutually reinforcing; bad deep probing is folders with no readable summary.
+
+### How to verify
+
+- Report states `.nexus-map/` root as a **relative path**.  
+- Can excerpt **module boundaries** and **Git hotspots** from mapper artifacts into the matching report sections.  
+- runtime-inspector output meets Step 1 acceptance (required for both deep and light).
+
+---
+
+## Step 3: Gap analysis (Pattern B only)
+
+### What to do
+
+Only when `.anws/v{N}/` exists: compare implementation evidence (Steps 1/2) against system boundaries, concepts, and constraints in Architectural Overview. List deviations: **factual mismatch**, **implicit design**, **concept drift**.  
+Pattern A: one line—**no finalized `.anws` architecture baseline yet, Gap not applicable**—or an actionable **suggest genesis first** item—**do not fake a comparison**.
+
+### Why
+
+**Motto**: Drift without an anchor packages unknown as insight.  
+**Bar**: Good gaps point at specific paragraphs or overview subsections; bad gaps are adjectives without citations.
+
+### How to verify
+
+- Pattern B: each deviation has **observational evidence** (file path, coupling pair, or mapper entry name).  
+- Pattern A: no hollow “todo improvement” lists.  
+- If sub-agents assisted, parent dedupes after merge so one deviation does not repeat.
+
+---
+
+## Step 4: Risk matrix (Change impact)
+
+### What to do
+
+Synthesize prior work: **change impact**. Produce a **risk matrix** (severity tiers; each row keeps **risk / impact / recommendation** minimal; hooks paths, edges, or contract status; consistent with earlier sections). Internal prompt: Which hubs does new work touch? Cascading failure? Timing/deploy dependencies?
+
+### Why
+
+**Motto**: Alarmism without a matrix does not belong in architecture review.  
+**Bar**: Good matrices let readers prioritize today’s actions; bad matrices recap summaries without **assignable** rows.
+
+### How to verify
+
+- At least one row ties **coupling hotspots or process contracts** directly or indirectly.  
+- Row width stays phrase-level, not paragraphs.  
+- Blockers are identifiable in severity; recommendations map to verifiable next steps (e.g. “run test X once”).
+
+---
+
+## Step 5: Generate report
+
+### What to do
+
+Save probe results to `.anws/v{N}/00_PROBE_REPORT.md`.  
+Metadata: **timestamp, `probe_mode` (A/B), `probe_level` (light/deep)**.  
+Body must cover these **section responsibilities** (titles may be tweaked slightly—**do not drop a responsibility**): 1 System Fingerprint; 2 Build Topology; 3 Runtime Topology; 4 Temporal Topology (required for deep; for light without mapper, state omission explicitly); 5 Gap Analysis (Pattern B; Pattern A states N/A); 6 Risk Matrix (column minimalism per **CRITICAL probe report writing contract** above). **This workflow does not paste** a full Markdown skeleton.
+
+### Why
+
+**Motto**: Probes not written to disk never happened.  
+**Bar**: Good paths are fixed and diffable; bad reports live only in chat and are unauditable.
+
+### How to verify
+
+- File path is exactly `.anws/v{N}/00_PROBE_REPORT.md`.  
+- All six section responsibilities present; missing data uses explicit **unavailable / skipped / N/A**—no blank sections feigning completion.  
+- No emoji throughout; wording may include necessary English proper nouns (tool names, paths) without breaking the primary English narrative.
+
+---
+
+<completion_criteria>
+- Step 0 `probe_level`, `probe_mode`, and report header match.
+- **Light**: required `nexus-query` commands ran (or sub-agent equivalent verified by parent), `runtime-inspector` complete.  
+- **Deep**: `nexus-mapper` produced `.nexus-map/`, `runtime-inspector` complete.  
+- Pattern B: gaps evidenced; Pattern A: no fabricated comparison.  
+- Risk matrix rows keep **risk / impact / recommendation** minimal yet actionable; severity supports ordering.  
+- `.anws/v{N}/00_PROBE_REPORT.md` written with all six sections and no substantive cross-section duplication (**no** reliance on a long template pasted in this workflow).  
+- No emoji; two-tier table, no empty-handed probing, and A/B pattern gates unchanged in strength.
+</completion_criteria>