@keighleykodric/weeve 0.1.0 → 0.1.2

package/spec/signals-schema.md

@@ -0,0 +1,685 @@
+---
+schema: signals
+version: v0.4
+date: 2026-05-26
+status: active
+---
+
+# Signals schema — v0.4
+
+*Authoritative versioned spec for the signals file format that all roads produce and Pilot reads.*
+
+This document is the authoritative spec. Every road's signals skill writes a file that conforms to this shape. `/pilot-priorities` reads those files and trusts them — it does not re-evaluate upstream sources. If a road's output diverges from this spec, Pilot's merge step degrades silently.
+
+---
+
+## 1. File naming convention
+
+```
+weeve/<road>/<road>-signals.md
+```
+
+| Road | File path |
+|---|---|
+| Compass | `weeve/compass/compass-signals.md` |
+| Layers+ | `weeve/layers-plus/layers-plus-signals.md` |
+| Ally | `weeve/ally/ally-signals.md` |
+| Rubric | `weeve/rubric/rubric-signals.md` |
+| Maven | `weeve/maven/maven-signals.md` |
+| Forge | `weeve/forge/forge-signals.md` |
+| Helm | `weeve/helm/helm-signals.md` |
+| Verify | `weeve/verify/verify-signals.md` |
+| Guard | `weeve/guard/guard-signals.md` |
+| Charter | `weeve/charter/charter-signals.md` |
+| Anchor | `weeve/anchor/anchor-signals.md` |
+| Ledger | `weeve/ledger/ledger-signals.md` |
+| Roster | `weeve/roster/roster-signals.md` |
+| Pitch | `weeve/pitch/pitch-signals.md` |
+
+The filename is stable across re-runs. The skill overwrites in place; the roadmap always reads the latest snapshot.
+
+---
+
+## 2. Required sections
+
+Every signals file must contain these sections, in this order:
+
+1. **Summary block** — open findings counts by severity, current bottleneck, 1–2 sentence strategy statement
+2. **Tier 1** — act now (🔴 High findings or Compass T1 moves)
+3. **Tier 2** — plan for (🟡 Medium or Compass T2)
+4. **Tier 3** — watch (🟢 Low or Compass T3)
+5. **What's working — don't disrupt** — strengths the signals preserve
+6. **Manual checks required** — findings that need live testing or operator judgement
+7. **Out of scope / accepted exceptions** — deferred items with rationale and revisit trigger
+
+Optional sections (present in some roads, allowed in all):
+
+- **Cross-pillar citations** — where this road's findings link to other roads
+- **Validation gaps** (Maven) — assumptions under 🔴 / 🟡 items not yet tested
+- **Evidence trace** (Compass) — source row IDs, confidence ratings, external signal count
+
+---
+
+## 3. Finding ID format
+
+Finding IDs must be stable across re-runs. If a finding is re-run and the underlying issue is unchanged, its ID does not change.
+
+### Format
+
+```
+<PREFIX>-<N>
+```
+
+Where `<PREFIX>` is a 3-letter road code and `N` is a monotonically increasing integer within the road's namespace. The dash separator is required. IDs are never reused for a different finding.
+
+### Registered road prefixes
+
+| Road | Prefix | Example |
+|---|---|---|
+| Compass | `CPS` | CPS-1, CPS-2 |
+| Layers+ | `LYR` | LYR-1, LYR-2 |
+| Ally | `ALY` | ALY-1, ALY-2 |
+| Rubric | `RBR` | RBR-1, RBR-2 |
+| Maven | `MVN` | MVN-1, MVN-2 |
+| Forge | `FRG` | FRG-1, FRG-2 |
+| Helm | `HLM` | HLM-1, HLM-2 |
+| Verify | `VFY` | VFY-1, VFY-2 |
+| Guard | `GRD` | GRD-1, GRD-2 |
+| Charter | `CHR` | CHR-1, CHR-2 |
+| Anchor | `ANC` | ANC-1, ANC-2 |
+| Ledger | `LDG` | LDG-1, LDG-2 |
+| Roster | `RST` | RST-1, RST-2 |
+| Pitch | `PCH` | PCH-1, PCH-2 |
+| Felt | `FLT` | FLT-1, FLT-2 |
+
+**v0.4 migration from 2-letter prefixes:** Existing findings retain their old IDs until the next re-run of each lane's signals skill. On re-run, skills adopt the new 3-letter prefix. Pilot accepts both old and new prefixes during the transition — it disambiguates by source file. The v0.3 Layers+/Ally `T1-`/`T2-`/`T3-` collision is resolved by this change.
+
+**Legacy prefix mapping (for Pilot backwards compatibility):**
+
+| Old prefix | New prefix |
+|---|---|
+| `SR` | `CPS` |
+| `T1-`/`T2-`/`T3-` (Layers+) | `LYR` |
+| `T1-`/`T2-`/`T3-` (Ally) | `ALY` |
+| `RR` | `RBR` |
+| `MR` | `MVN` |
+| `FR` | `FRG` |
+| `HR` | `HLM` |
+| `VR` | `VFY` |
+| `GR` | `GRD` |
+| `CR` | `CHR` |
+| `AR` | `ANC` |
+| `LR` | `LDG` |
+| `RO` | `RST` |
+| `PR` | `PCH` |
+| `FL` | `FLT` |
+
+**Registering a new road prefix:** add a row to the table above and increment the schema version. All prefixes must be exactly 3 uppercase letters.
+
+---
+
+## 4. Canonical finding shape
+
+This is the most important section. Every finding — whether written as a heading block (Compass/Maven style) or a table row (Layers+/Ally/Rubric style) — must carry these seven fields (five required, two optional).
+
+```
+id · severity · status · location · what's wrong · what to do
+```
+
+### Field definitions
+
+| Field | Required | Description |
+|---|---|---|
+| **id** | Yes | Stable road-prefixed ID in `PREFIX-N` format (see §3). Never changes between re-runs for the same finding. |
+| **severity** | Yes | Road-declared severity name that maps to one of the three framework tiers (see §5). Default road uses 🔴 High / 🟡 Medium / 🟢 Low. |
+| **status** | Yes | Lifecycle position of the finding. Road-declared vocabulary (see §5a). Default: `open` / `in-flight` / `blocked` / `closed`. Severity says *how urgent*; status says *who's holding it and where in the lifecycle*. |
+| **location** | Yes | File path, skill name, zone, route, or surface. Must be specific — not "everywhere" or "the codebase". |
+| **what's wrong** | Yes | One sentence describing the gap, drift, or risk. Describes the current state, not the desired state. |
+| **what to do** | Yes | One concrete action sentence. Describes the fix or move, not the problem. |
+| **evidence trace** | Optional | Source row IDs, confidence ratings, external signal count. Required for Compass lens skills. Recommended for any finding claiming Validated confidence. |
+| **gate-ship** | Optional | `true` / `false` (default: `false`). Set to `true` on findings that must be resolved before `/pilot-ship` proceeds. Only Guard and Verify set this by default; any lane may set it. `/pilot-ship` parses this field across all roads — do not use alternative names (`block`, `block-ship`, etc.). Gate-ship is itself a kind of status flag — roads may extend it with domain-specific blockers (e.g. "blocks discharge", "requires sign-off") declared in their manifest. |
+
+### Heading-block format (Compass / Maven)
+
+```markdown
+### CPS-1 · Short title
+
+**Status:** open
+**Move:** What to do — one concrete sentence
+**Why now:** What erodes or compounds if this is deferred
+**Effort signal:** Low / Medium / High
+**Closes findings:** [finding IDs this move resolves]
+**Evidence:** [source row IDs, confidence, weight — e.g. "P2 (Hypothesis, Central) · 0 external signals"]
+```
+
+The `**Move:**` field satisfies **what to do**. The heading title + `**Move:**` context satisfies **what's wrong** (implied from the finding being surfaced at all; "Why now:" makes the gap explicit). The `**Status:**` field uses the lane's effective vocabulary.
+
+### Table-row format (Layers+ / Ally / Rubric)
+
+```markdown
+| ID | Severity | Status | Location | Finding | What to do | Effort |
+|---|---|---|---|---|---|---|
+| LYR-1 | 🔴 High | open | [zone / file / path] | [one sentence — what's wrong] | [one sentence — what to fix] | M |
+```
+
+The columns map directly to the canonical shape. "Effort" is an extension field — allowed in all roads, not required by the schema.
+
+---
+
+## 5. Tier definitions and severity mapping
+
+The framework defines exactly three tiers. This is a framework-level primitive — all roads map into it.
+
+| Tier | Name | Meaning |
+|---|---|---|
+| T1 | Act now (Now) | Validated evidence of active erosion or a blocked user group. Deferring costs more. T1 findings must have at least one Validated input — Hypothesis-only evidence drops to T2. |
+| T2 | Plan for (Next) | Gap or misalignment that will compound. Not urgent today. Schedule deliberately. |
+| T3 | Watch | Could escalate if an external signal changes. Review quarterly or on trigger. |
+
+### Severity vocabulary
+
+Roads declare their own severity names and map each to one of the three framework tiers. The default startup road uses:
+
+| Severity name | Framework tier |
+|---|---|
+| 🔴 High | Now |
+| 🟡 Medium | Next |
+| 🟢 Low | Watch |
+
+Compass uses `T1 — Act now` / `T2 — Plan for` / `T3 — Watch` — these map directly.
+
+Roads targeting other industries may declare different scales. Example (healthcare/NCQA):
+
+```yaml
+severity_vocabulary:
+  critical: Now
+  high: Now
+  medium: Next
+  low: Watch
+  informational: Watch
+```
+
+The mapping is declared in the lane manifest (`lane.yaml`) or inherited from the road manifest (`road.yaml`) — see §8a. Schema validates that every declared severity name maps to exactly one of the three tiers. Pilot reads the effective vocabulary (lane > road > default) to resolve custom severity names.
+
+---
+
+## 5a. Status vocabulary
+
+Status and severity are orthogonal dimensions:
+
+| Dimension | Question | Granularity |
+|---|---|---|
+| Severity | How urgent? | Coarse — maps to 3 framework tiers |
+| Status | Where in the lifecycle? | Fine — varies per lane and industry |
+
+The schema defines the primitive: *every finding has a status drawn from the lane's effective vocabulary*. Vocabularies are declared in `lane.yaml` (lane-specific) or inherited from `road.yaml` (road default) — see §8a.
+
+### Default status vocabulary
+
+The default startup road's `road.yaml` declares:
+
+```
+open → in-flight → blocked → closed
+```
+
+- **open** — finding identified, not yet acted on
+- **in-flight** — work underway
+- **blocked** — work started but waiting on a dependency or decision
+- **closed** — resolved and verified
+
+This is the vocabulary used by all current lanes. No migration required for existing lanes — they already use these terms (previously implicit in §7, now explicit).
+
+### Road-declared vocabularies
+
+Lanes targeting other domains declare their own status vocabularies in `lane.yaml`. Examples:
+
+**Insurance claims:**
+```yaml
+status_vocabulary:
+  - draft
+  - prepared
+  - sent
+  - acknowledged
+  - accepted
+  - paid
+  - rejected
+  - denied
+  - void
+```
+
+**Eligibility check:**
+```yaml
+status_vocabulary:
+  - pending
+  - reviewed
+  - success
+  - failed
+```
+
+Status vocabularies may have branching terminal states (e.g. paid/rejected/denied are all terminal). The schema does not enforce a linear progression — it validates that every finding's status is a member of the lane's effective vocabulary.
+
+### Pilot and status
+
+Pilot's tier mapping (§7) stays severity-based — it maps findings to Now/Next/Watch by severity, not by status. Status is consumed differently:
+
+- **Tapestry** renders two orthogonal axes: Kanban view (grouped by status) + tier rollup (grouped by severity) on the same finding set.
+- **`/pilot-ship`** reads `gate-ship` (a boolean) for blocking decisions, not status directly. However, roads may declare domain-specific gate conditions tied to status (e.g. "blocks discharge" = gate-ship when status is not `acknowledged`).
+- **Triage skills** (`/<lane>-triage`) update status inline — this is where status transitions happen.
+
+---
+
+## 6. Confidence / evidence notation
+
+Use these terms consistently in evidence traces and frontmatter:
+
+| Term | Meaning |
+|---|---|
+| **Validated** | Confirmed by observed output, user data, or external signal. Anchors T1 eligibility. |
+| **Working** | Hypothesis that has been partially tested or is grounded in consistent observed behaviour. T2 default. |
+| **Hypothesis** | Assumed but not yet tested. Cannot anchor a T1 finding without at least one Validated or Working co-source. |
+
+**Frontmatter usage (Maven pattern, optional for other roads):**
+
+```yaml
+foundation: validated | hypothesis | missing
+note: "Built without validated positioning. Treat as working hypothesis."
+```
+
+**Finding row usage:**
+
+Confidence is expressed in the evidence trace field: `"P2 (Hypothesis, Central) · 0 external signals"`. If a finding has no evidence trace, Pilot assumes Working confidence.
+
+---
+
+## 7. What Pilot reads — how `/pilot-priorities` consumes this file
+
+`/pilot-priorities` reads each road's signals file as the authoritative source. It does not re-evaluate the upstream sources. The signals file is the unit of trust.
+
+**Extraction:** Pilot extracts per finding: ID, severity, status, title, brief description, evidence trace. The canonical finding shape (§4) makes this extraction deterministic.
+
+**Tier mapping:**
+
+Pilot reads each road's severity vocabulary from its manifest (§8a) and maps findings to roadmap tiers. For the default startup road:
+
+| Road output | Roadmap tier |
+|---|---|
+| Compass T1 (Act now) | **Now** |
+| 🔴 High from any other road | **Now** |
+| Compass T2 (Plan for) | **Next** |
+| 🟡 Medium from any other road | **Next** |
+| Compass T3 (Watch) | **Watch** |
+| 🟢 Low from any other road | **Watch** |
+| Status: closed or retired | Dropped |
+
+For lanes with custom severity vocabularies, Pilot resolves the mapping via `severity_vocabulary` in `lane.yaml` (or inherited from `road.yaml`). An unrecognised severity name is a parse error — Pilot stops and surfaces it.
+
+**Status handling:** Pilot drops findings with status `closed`. All other statuses are treated as active. Pilot does not interpret domain-specific status names — it passes them through to the roadmap as metadata for Tapestry rendering.
+
+**Validated-input gate:** if an item would land in **Now** but its evidence trace is Hypothesis-only or Assumed-only, Pilot demotes it to **Next** and adds a note. This gate is inherited from `/compass-signals` and applies across all pillars.
+
+**De-duplication:** if two roads surface findings that trace to the same source row or gap, Pilot collapses them into one roadmap item and notes that multiple pillars surfaced it. It does not write two items that rest on the same signal.
+
+**Conflict detection:** if two roads recommend opposing actions on the same surface, Pilot surfaces the conflict in the **Conflicts surfaced** section and does not silently pick a side.
+
+**Malformed file:** if a signals file is structurally unreadable (Pilot cannot extract IDs, tiers, or evidence), Pilot stops and surfaces the parse error. It does not write a degraded roadmap.
+
+---
+
+## 8a. Manifest hierarchy (`weeve.yaml` → `road.yaml` → `lane.yaml`)
+
+Configuration lives at three levels. Each level can override or extend the level above it. Ownership can attach at any level.
+
+```
+weeve.yaml          (repo root — framework instance)
+  └─ road.yaml      (per road — a bundle of lanes)
+       └─ lane.yaml  (per lane — a single domain)
+```
+
+### `weeve.yaml` — framework instance (repo root)
+
+Declares which roads are installed and repo-level defaults. Tapestry reads this file to discover lanes.
+
+```yaml
+# weeve.yaml
+schema_version: "0.4"
+
+# Ownership at the framework level (optional — small orgs may set it here)
+# ownership_adapter: codeowners
+
+roads:
+  - name: startup
+    path: roads/startup            # contains road.yaml + lane dirs
+  # Future: vertical roads
+  # - name: healthcare
+  #   path: roads/healthcare
+```
+
+### `road.yaml` — road manifest (per road)
+
+A road is a bundle of lanes. The default startup road ships the 14 lanes for tech/startup orgs. Vertical roads (healthcare, legal, finance) would bundle different lane sets.
+
+```yaml
+# roads/startup/road.yaml
+name: startup
+description: "14-lane road for tech startups and product teams"
+schema_version: "0.4"
+
+# Road-level defaults — lanes inherit these unless they override.
+severity_vocabulary:
+  🔴 High: Now
+  🟡 Medium: Next
+  🟢 Low: Watch
+
+status_vocabulary:
+  - open
+  - in-flight
+  - blocked
+  - closed
+
+# Ownership at the road level (optional)
+# ownership_adapter: codeowners
+
+# Lanes bundled in this road
+lanes:
+  - name: compass
+    path: compass/
+  - name: ally
+    path: ally/
+  - name: guard
+    path: guard/
+  # ... all 14
+```
+
+### `lane.yaml` — lane manifest (per lane)
+
+Each lane declares its own prefix, zones, and optionally overrides the road's vocabularies.
+
+**Required fields:**
+
+```yaml
+# guard/lane.yaml
+name: guard
+domain: security
+finding_prefix: GRD                   # registered 3-letter prefix (§3)
+```
+
+**Optional fields (override road defaults):**
+
+```yaml
+# Severity vocabulary — override road default for this lane.
+# Omit to inherit from road.yaml.
+severity_vocabulary:
+  critical: Now
+  high: Now
+  medium: Next
+  low: Watch
+  informational: Watch
+
+# Status vocabulary — override road default for this lane.
+# Omit to inherit from road.yaml.
+status_vocabulary:
+  - open
+  - in-flight
+  - blocked
+  - closed
+  - accepted-risk                     # Guard-specific extension
+
+# Gate-ship — does this lane block /pilot-ship?
+# Default: false. Set to true for lanes whose critical findings should
+# prevent shipping. See weeve spec/ship-gate.md for the full protocol.
+gate_ship: true                       # Guard and Verify set this; most lanes don't
+
+# Gate-ship extensions — domain-specific blocking conditions beyond the
+# boolean. These declare named blockers that appear in Tapestry and
+# /pilot-ship output.
+gate_ship_extensions:
+  - unresolved-critical               # Guard: any 🔴 Critical finding
+  - accepted-risk-expired             # Guard: accepted-risk past review date
+
+# Zones — named subdivisions of this lane's work area.
+zones:
+  - name: threat-model
+    skill_prefix: TM
+  - name: supply-chain
+    skill_prefix: SC
+  - name: appsec
+    skill_prefix: AS
+
+# Ownership at the lane level (most common granularity)
+ownership_adapter: codeowners
+# ownership_adapter: ldap
+# ownership_adapter: manifest         # inline in this file:
+# owners:
+#   - team: appsec
+#     members: [alice, bob]
+```
+
+**Healthcare lane example (overrides everything):**
+
+```yaml
+# insurance-billing/lane.yaml
+name: insurance-billing
+domain: claims
+finding_prefix: INS
+
+severity_vocabulary:
+  critical: Now
+  high: Now
+  medium: Next
+  low: Watch
+  informational: Watch
+
+status_vocabulary:
+  - draft
+  - prepared
+  - sent
+  - acknowledged
+  - accepted
+  - paid
+  - rejected
+  - denied
+  - void
+
+gate_ship: true
+gate_ship_extensions:
+  - blocks-discharge                  # finding blocks patient discharge
+  - requires-authorization            # finding requires payer auth before proceeding
+
+ownership_adapter: ldap
+```
+
+**Default startup road — Guard lane.yaml:**
+
+```yaml
+name: guard
+domain: security
+finding_prefix: GRD
+gate_ship: true
+gate_ship_extensions:
+  - unresolved-critical
+  - accepted-risk-expired
+status_vocabulary:
+  - open
+  - in-flight
+  - blocked
+  - closed
+  - accepted-risk
+```
+
+**Default startup road — Verify lane.yaml:**
+
+```yaml
+name: verify
+domain: qa
+finding_prefix: VFY
+gate_ship: true
+gate_ship_extensions:
+  - release-blocker
+```
+
+**Default startup road — Compass lane.yaml (no gate-ship):**
+
+```yaml
+name: compass
+domain: strategy
+finding_prefix: CPS
+# gate_ship defaults to false — strategy findings don't block shipping
+```
+
+### Inheritance and override rules
+
+1. **Severity vocabulary:** lane overrides road. If neither declares one, the framework default applies (🔴/🟡/🟢).
+2. **Status vocabulary:** lane overrides road. If neither declares one, the framework default applies (open/in-flight/blocked/closed).
+3. **Ownership adapter:** resolved at the most specific level declared. Lane > Road > Weeve. If none is set, no ownership routing (findings are unowned).
+4. **`finding_prefix`:** always lane-level. Required. Must be registered in §3.
+5. **`schema_version`:** declared at road level. Lanes inherit it. A lane cannot target a different schema version than its road.
+6. **`gate_ship`:** lane-level. Default `false`. Only lanes that set `true` are consulted by `/pilot-ship`. `gate_ship_extensions` are only meaningful when `gate_ship: true`.
+
+### Validation rules
+
+1. Every severity name must map to exactly one of: `Now`, `Next`, `Watch`.
+2. Every status value in a finding must be a member of the lane's effective `status_vocabulary` (own or inherited from road).
+3. `finding_prefix` must be registered in §3 — unregistered prefixes are a schema error. All prefixes must be exactly 3 uppercase letters.
+4. `schema_version` must match a published schema version. Roads targeting older schemas are accepted but generate a staleness warning.
+
+---
+
+## 8b. Current conformance
+
+Assessment against the canonical finding shape (§4): id · severity · status · location · what's wrong · what to do.
+
+**v0.4 note:** All lanes need to adopt the new 3-letter prefix (`CPS-`, `LYR-`, etc.) and add the `status` column. Conformance below reflects v0.3 state with v0.4 migration notes.
+
+### Compass (`/compass-signals`)
+
+**Status: Conformant with extensions. Needs v0.4 migration (prefix `SR` → `CPS`, add status field).**
+
+Compass uses heading-block format. All canonical fields are present:
+- ID: `SR<N>` prefix, stable. → migrate to `CPS-<N>`.
+- Severity: implied by tier (T1 = High, T2 = Medium, T3 = Watch).
+- Status: not yet present — add `**Status:**` field.
+- Location: "Closes findings: [lens finding IDs]" satisfies location indirectly.
+- What's wrong: `**Why now:**` field.
+- What to do: `**Move:**` field.
+- Evidence trace: present and required.
+
+---
+
+### Layers+ (`/layers-plus-roadmap`)
+
+**Status: Conformant. v0.4 migration complete (prefix `LYR-<N>`, status + location + finding columns present).**
+
+- ID: `LYR-<N>` prefix. Stable.
+- Status: present as column.
+- Location: present as column.
+- Finding (what's wrong): present as column.
+- What to do: present as column.
+- Effort: extension field, present.
+
+---
+
+### Ally (`/ally-plan`)
+
+**Status: Conformant with extensions. Needs v0.4 migration (prefix `T1-`/`T2-`/`T3-` → `ALY`, add status column).**
+
+- ID: `T1-<N>` / `T2-<N>` / `T3-<N>` → migrate to `ALY-<N>`. Resolves the Layers+/Ally namespace collision.
+- Status: not yet present — add column.
+- Minor gap: "Finding" (what's wrong) not restated inline.
+
+---
+
+### Rubric (`/rubric-status` → `rubric-signals.md`)
+
+**Status: Conformant. Needs v0.4 migration (prefix `RR` → `RBR`, add status field).**
+
+- ID: `RR<N>` → migrate to `RBR-<N>`.
+- Status: not yet present — add `**Status:**` field.
+
+---
+
+### Maven (`/maven-signals`)
+
+**Status: Conformant with extensions. Needs v0.4 migration (prefix `MR` → `MVN`, add status field).**
+
+- ID: `MR<N>` → migrate to `MVN-<N>`.
+- Status: not yet present — add `**Status:**` field.
+
+---
+
+### Forge (`/forge-signals`)
+
+**Status: Diverges — needs v0.4 migration (prefix `FR` → `FRG`).**
+
+Registered prefix: `FR` → `FRG`. Existing divergences (D2, D3, D4, D7) plus v0.4 additions (status field, 3-letter prefix).
+
+---
+
+### Helm (`/helm-signals`)
+
+**Status: Diverges. Needs v0.4 migration (prefix `HR` → `HLM`).**
+
+Registered prefix: `HR` → `HLM`. Same divergences as Forge.
+
+---
+
+### Verify (`/verify-signals`)
+
+**Status: Diverges. Needs v0.4 migration (prefix `VR` → `VFY`).**
+
+Registered prefix: `VR` → `VFY`. Ship-gate lane.
+
+---
+
+### Guard (`/guard-signals`)
+
+**Status: Diverges. Needs v0.4 migration (prefix `GR` → `GRD`).**
+
+Registered prefix: `GR` → `GRD`. Ship-gate lane. `accepted-risk` triage state is a Guard-specific extension.
+
+---
+
+### Charter, Anchor, Ledger, Roster, Pitch
+
+**Status: Scaffold only — signals skills not yet written.**
+
+Registered prefixes: `CHR` (Charter), `ANC` (Anchor), `LDG` (Ledger), `RST` (Roster), `PCH` (Pitch). Will adopt v0.4 format from first write.
+
+---
+
+### Summary table
+
+| Road | Prefix | v0.3 state | v0.4 migration |
+|---|---|---|---|
+| Compass | `CPS` | Conformant | Prefix + status field |
+| Layers+ | `LYR` | Conformant | v0.4 complete |
+| Ally | `ALY` | Conformant (minor gap) | Prefix + status (resolves namespace collision) |
+| Rubric | `RBR` | Conformant | Prefix + status field |
+| Maven | `MVN` | Conformant | Prefix + status field |
+| Forge | `FRG` | Diverges (D2/D3/D4/D7) | Prefix + status + reconciliation fixes |
+| Helm | `HLM` | Diverges | Prefix + status + reconciliation fixes |
+| Verify | `VFY` | Diverges | Prefix + status + reconciliation fixes |
+| Guard | `GRD` | Diverges | Prefix + status + reconciliation fixes |
+| Charter | `CHR` | Scaffold | Adopt v0.4 from first write |
+| Anchor | `ANC` | Scaffold | Adopt v0.4 from first write |
+| Ledger | `LDG` | Scaffold | Adopt v0.4 from first write |
+| Roster | `RST` | Scaffold | Adopt v0.4 from first write |
+| Pitch | `PCH` | Scaffold | Adopt v0.4 from first write |
+| Felt | `FLT` | Scaffold | Adopt v0.4 from first write |
+
+---
+
+## 9. Schema changelog
+
+_Section numbers updated in v0.4: former §8 (conformance) is now §8b. §8a (manifest hierarchy) is new._
+
+| Version | Date | Change |
+|---|---|---|
+| v0.1 | 2026-05-22 | Initial publication — making the implicit schema explicit. No changes to road skill specs in this version; conformance gaps noted above are addressed as follow-on work. |
+| v0.2 | 2026-05-24 | Register prefixes for 9 new lanes (FR/HR/VR/GR/CR/AR/LR/RO/PR). Add `gate-ship` field to canonical finding shape §4. Add §1 file paths and §8 conformance entries for all new lanes. |
+| v0.3 | 2026-05-24 | Register `FL` prefix for Felt (UX research lane). |
+| v0.4 | 2026-05-26 | **Status as first-class field.** Add `status` to canonical finding shape (§4) — severity and status are now orthogonal dimensions. Roads declare status vocabularies in `road.yaml`. Default vocabulary: open/in-flight/blocked/closed (no migration). **Severity-mapping decoupling.** Roads may declare custom severity names that map to the 3 framework tiers (Now/Next/Watch). Default retains 🔴/🟡/🟢. **3-letter finding prefixes.** All road prefixes migrated from 2-letter to 3-letter codes with dash separator (e.g. `SR1` → `CPS-1`). Resolves the Layers+/Ally `T1-` namespace collision. Legacy prefixes accepted during transition. **Road manifest spec** (§8a): `road.yaml` shape for declaring vocabularies, zones, gate-ship extensions, and ownership adapter. `weeve.yaml` repo-level registry for Tapestry discovery. **Vocabulary: "pack" → "road"** throughout — Lane/Road/Weave metaphor. |
+
+---
+
+_Maintained in `weeve` repo · `spec/signals-schema.md`_
+_Next review: when any road skill spec is updated to change its finding table shape, or when a new road is added._