FE-1090: Data-model legibility reference substrate

.agents/skills/ln-build/SKILL.md

@@ -111,6 +111,7 @@ After the build lands and verification passes, ask:
 - [ ] Did this retire or create an assumption?
 - [ ] Did this establish a new seam-level invariant?
 - [ ] Did this change a frontier-level cross-cutting obligation or verification architecture layer?
+- [ ] Did this complete the **last member frontier of an initiative (arc)** in `memory/PLAN.md` §Initiatives?
 - [ ] Did this change the topology of a directory that owns a `README.md` (moved/renamed/retired files, changed dependency direction, completed or invalidated a migration note, or shipped a state previously described as pending)?
 
 ### If all answers are no
@@ -138,6 +139,7 @@ Update only the touched traceability items.
    - If the change closes, blocks, or unblocks a frontier item, reflect that in `Sequencing`, the affected `Frontier Definitions` entry, or `Recently Completed`
    - If the build changed a frontier-level cross-cutting obligation, update the affected frontier definition explicitly; do not hide the change behind bare traceability IDs
    - Do not mirror detailed slice/card history into `memory/PLAN.md`; cards live in the scope file under `memory/cards/`. At most, the frontier definition may carry a lightweight `Current execution pointer` listing active scope file path(s).
+   - **Arc completion:** if this build completed the **last member frontier of an initiative (arc)** in `§Initiatives`, run that arc's **done-definition before** marking the arc done — including reconciling co-located topology READMEs and discharging any standing-obligation residue scoped to the arc (the residue that no future frontier would otherwise touch). Mark the arc `✓ done` only once the done-definition actually holds; if residue remains, the arc stays `◐ active` with the residue named.
 
 2. **Assumptions**
    - evidence answered it → update to `validated` or `invalidated`

.agents/skills/ln-plan/SKILL.md

@@ -8,7 +8,7 @@ argument-hint: "[feature or project area to plan]"
 
 Plan the **rolling frontier**, not the whole historical timeline.
 
-`memory/PLAN.md` is the canonical record of what's next. `docs/archive/PLAN_HISTORY.md` is the only sanctioned archive for retired plan history. `memory/cards/` is the sanctioned derivative location for prepared scope cards; one file per concern, named `<frontier-id>--<slug>.md` (or `dev--<slug>.md`, `tooling--<slug>.md`, `docs--<slug>.md` for non-frontier work). Scope files are not canonical planning state. Do not invent other sidecar plan docs, milestone ledgers, or alternate memory locations without explicit permission.
+`memory/PLAN.md` is the canonical record of what's next. `docs/archive/PLAN_HISTORY.md` is the only sanctioned archive for retired plan history. `memory/cards/` is the sanctioned derivative location for prepared scope cards; one file per concern, named `<frontier-id>--<slug>.md` (or `dev--<slug>.md`, `tooling--<slug>.md`, `docs--<slug>.md` for non-frontier work). Scope files are not canonical planning state. Do not invent other sidecar plan docs, milestone ledgers, or alternate memory locations without explicit permission. The one sanctioned exception is the in-`PLAN.md` `## Initiatives` section (see [§Initiatives (arcs)](#initiatives-arcs)) — it lives inside the canonical file, not as a sidecar, and is not a new tracker/branch altitude.
 
 ## Frontier vs slice vocabulary
 
@@ -25,6 +25,7 @@ The vertical-slicing instinct still applies at planning time: frontier items sho
 Prefer the conflict-resistant mature shape:
 
 - `Context` — short rolling narrative for re-entry
+- `Initiatives` — *optional*; thin arc index when an architectural through-line spans several frontiers (see [§Initiatives (arcs)](#initiatives-arcs))
 - `Sequencing` — small, frequently edited ordering/status references by stable frontier id
 - `Frontier Definitions` — relatively stable per-frontier definitions keyed by stable id
 - `Recently Completed` — last 2-3 completed frontier items only
@@ -107,6 +108,22 @@ Do not split one frontier item into several new PLAN entries just because execut
 
 But do not let anti-fragmentation erase cross-cutting architecture. If a subsystem or mechanism spans multiple frontier items and is not getting its own frontier id, thread it explicitly through the affected frontier definitions as an obligation in Objective, Acceptance, Verification, or a dedicated cross-cutting note.
 
+### Initiatives (arcs)
+
+Anti-fragmentation keeps the frontier list flat, but a flat list loses the **through-line** of an architectural initiative that deliberately spans several frontiers (e.g. populate-then-weed-then-lock a skill substrate, or build a capability spine across planes). When that happens the initiative's "why" and its "done" survive only as a SPEC decision dependency chain — which records *events*, not a roster — so "was this captured thoroughly?" becomes a reconstruction job, and trailing cleanup can orphan when no future frontier's blast radius touches it.
+
+An **initiative (arc)** is the answer, and it is **not** a new tracking altitude: frontiers stay 1:1 with Linear issues and branches (`AGENTS.md`), Graphite stacks still mirror frontier dependencies, and arcs get no issue or branch of their own. An arc is a thin legibility + completability index living in the in-`PLAN.md` `## Initiatives` section. Reach for one only when a through-line genuinely spans ≥2 frontiers and would otherwise be invisible; a single-frontier effort does not need an arc.
+
+Each arc entry stays thin:
+
+- **id + status** (`✓ done` / `◐ active` / planned)
+- **Goals** — the through-line in 1–3 bullets (the user-facing "why")
+- **Members** — the frontier ids that compose it, with per-member status
+- **Done-definition** — the arc-level completion test, which **must** include reconciliation of co-located topology READMEs and discharge of any standing-obligation residue scoped to the arc
+- **Anchors** — the SPEC decision/assumption ids the arc rests on
+
+`ln-plan` creates and updates arcs (and the member roster as frontiers are added/retired); `ln-sync` closes them and verifies the done-definition actually holds; `ln-build` fires the arc-completion check when a build lands the last member frontier (see each skill). The done-definition is what closes the "standing obligation rides the triggering frontier = never" hole: arc completion is itself a trigger.
+
 ### Sequencing vs definition edits
 
 When priorities change, edit `Sequencing` first. Do not move or rewrite frontier definitions merely to reorder work.

.agents/skills/ln-sync/SKILL.md

@@ -136,6 +136,7 @@ Rules:
 - keep dependency diagrams limited to active / next frontier ids
 - keep enough `Why now / unlocks` context that a fresh thread can understand frontier ordering without reading the full archive
 - do not archive handoffs, refactor plans, or sync reports
+- reconcile the `## Initiatives` (arc) index if present: refresh each arc's member roster and per-member status against `Sequencing`, and **close an arc only when its done-definition actually holds** — including reconciliation of co-located topology READMEs and discharge of any standing-obligation residue scoped to the arc. An arc whose members are all done but whose trailing README/residue cleanup is outstanding is **not** done; keep it `◐ active` with the residue named. Retire a fully-closed arc to a one-line `Recently Completed`-style note (or drop it) rather than carrying its full block indefinitely.
 
 ### 5. Drift and ontology check
 
@@ -158,6 +159,7 @@ Scan recent code / commits for:
 - verification strategy that is present in canonical docs or frontier definitions but absent from `memory/SPEC.md` §Verification Design
 - chosen module/API shapes or seam obligations from `ln-design` output that active frontier work still depends on
 - **topology READMEs under `src/**/` out of sync with reality**: SPEC decision IDs cited in a README that this sync just renumbered or retired; named files/modules that have moved, been renamed, or been retired; dependency-direction assertions that no longer match actual imports; layout sketches whose entries no longer match the directory's contents; migration notes describing state that has since shipped or been abandoned (see `AGENTS.md` §topology READMEs)
+- **arcs (`## Initiatives`) out of sync**: an arc marked done whose done-definition does not actually hold (outstanding topology-README reconciliation or undischarged residue); an arc roster missing a member frontier that clearly belongs to the through-line; an active multi-frontier through-line visible in the SPEC decision chain but absent from the arc index; a completed arc still carrying a full block long after closure
 
 ### 6. Garbage-collect derivative artifacts
 
@@ -204,6 +206,7 @@ Before finishing, perform a cross-skill preservation check:
 - What cross-cutting obligations would disappear because they are carried only by links, not by live rows or frontier definitions?
 - Would they know which temporary sweep ledgers are still live, which promoted rows still keep those ledgers open, and why those rows sequence where they do?
 - Do any topology READMEs under `src/**/` still cite SPEC IDs or describe topology this sync just changed? Reconcile those READMEs as part of the sync, not as a follow-up.
+- If a multi-frontier through-line exists, would they see it as an arc in `§Initiatives` with an honest done-definition, or would they have to reconstruct it from the SPEC decision chain?
 
 If any answer is non-empty, sync is incomplete.
 

.oxlintrc.json

@@ -26,41 +26,40 @@
       }
     },
     {
-      "files": ["src/renderers/**/*.ts", "src/renderers/**/*.tsx"],
+      "files": ["src/workspace/**/*.ts", "src/workspace/**/*.tsx"],
       "rules": {
         "no-restricted-imports": [
           "error",
           {
             "patterns": [
               {
-                "group": ["**/.pi/**", "**/app/**", "**/rpc/**", "**/web/**", "**/db/**"],
-                "message": "D52-L: renderers/ must not import adapter, transport, or db layers."
+                "group": [
+                  "**/.pi/**",
+                  "**/app/**",
+                  "**/db/**",
+                  "**/graph/**",
+                  "**/projections/**",
+                  "**/rpc/**",
+                  "**/session/**",
+                  "**/web/**"
+                ],
+                "message": "D52-L: workspace/ is a cwd-owned leaf; it must not import domain or adapter layers."
               }
             ]
           }
         ]
       }
     },
     {
-      "files": ["src/workspace/**/*.ts", "src/workspace/**/*.tsx"],
+      "files": ["src/agents/contexts/**/*.ts", "src/agents/contexts/**/*.tsx"],
       "rules": {
         "no-restricted-imports": [
           "error",
           {
             "patterns": [
               {
-                "group": [
-                  "**/.pi/**",
-                  "**/app/**",
-                  "**/db/**",
-                  "**/graph/**",
-                  "**/projections/**",
-                  "**/renderers/**",
-                  "**/rpc/**",
-                  "**/session/**",
-                  "**/web/**"
-                ],
-                "message": "D52-L: workspace/ is a cwd-owned leaf; it must not import domain or adapter layers."
+                "group": ["**/.pi/**", "**/app/**", "**/db/**", "**/rpc/**", "**/web/**"],
+                "message": "D52-L/D83-L: agents/contexts/ is model-facing render code; it must not import adapters, app entrypoints, transports, web, or db."
               }
             ]
           }