Task Board — Audit Log

The atomic audit trail for Dossier — Work Items (the agentic board). Every meaningful board change (create / claim / transition / complete / block) lands here, mirroring how Dossier — Decision & Audit Log distills the trace stream into the decision layer. The git history of tasks/ is the canonical record; this log is its legible surface. (Standing convention: the board is globbed before every filing to avoid duplicates; entries below note only genuine non-duplication judgment calls.)

2026-06-16

• Board seeded. The task type was designed into Dossier — The Knowledge Model (v0) + the @dossier/okf schema, and this board + 8 seed task atoms created from Dossier's real backlog (no fabricated work) — realizing the Agentic "sprint board" architecture — a git-resident OKF task board worked by bounded, hook-governed Agent SDK loops hand-off. Tracked by Design the OKF `task` concept type + seed the board.
• Backlog captured. Open items lifted into first-class tasks: Resolve the decision `reversibility` schema conformance gap, Build the PreToolUse claim/lease governance hook, Build the runtime BoardWorker seam (DefaultBoardWorker + reserved AgentSdkBoardWorker), Render the board as a derived `/board` surface in @dossier/site, Honor robots.txt in the keyless HttpConnector (claimed), Tighten reconcile diffs against timestamp churn on live re-crawls (review).
• First done recorded. Make the learning loop compound (reconcile merge by id + confidence) → done (The compounding merge — the per-tenant learning loop accumulates by id + confidence instead of overwriting (okf reconcile() + opt-in reconcile in extraction/runtime) shipped + verified, 64856ad); kept on the board, ids never recycled.
• First log-auditor-sourced task filed. Decide whether the report-only agents (qa-reviewer, principal-architect) should close the finding loop like the log-auditor now does (backlog, p2, Product Owner) — should other report-only agents (e.g. Adversarial QA & Knowledge-Integrity Reviewer) also file findings as board tasks now that the auditor does? See Upgrade the log-auditor from a backward-looking recorder into a recorder + standing auditor that closes the improvement loop.
• Filed: Fix the stale round-trip-test path in the generate-landing SKILL.md (points at a file that no longer exists) (backlog, p2, Astro Starlight Engineer) — the generate-landing SKILL.md cites a moved round-trip test path (link rot in a contract doc). See The marketing landing becomes a tailorable per-client template — a typed LandingContent model rendered by LandingPage.astro; the Dossier render stays byte-for-byte identical; client instances are values of the same type, canonical in the client's own repo, generated by the generate-landing skill.
• Filed: Fix dossier-runtime `site` subcommand dispatch (isSub omits 'site') (backlog, p2, Platform / Runtime Engineer) — dossier-runtime's isSub() omits 'site', so site is rejected before dispatch (one-line fix; run --site is the workaround). See /client-new — a thin operator slash command over the control-plane CLI.
• Filed off DEC-0040 (codebase ingestion): De-risk spike (GO/NO-GO) — mine the git "why" through the existing faithfulness judge, report two numbers (backlog, p1, Knowledge-Extraction & GraphRAG Engineer) — the go/no-go gate the whole build is blocked on (mine git "why" recall + faithfulness via the existing judge, no new infra); and Language-pack backlog — author per-language tree-sitter tag-query + schema packs beyond TS/Python (CONTINGENT on the v1 build proceeding) (backlog, p2, Ingestion & Connectors Engineer, depends on the spike) — per-language tree-sitter packs beyond v1 TS/Python. The board-v1 gate was noted in DEC-0040's sequencing, not re-filed.
• Filed off DEC-0041: Give board-claim-guard the dumb-fast treatment before it goes standing (no per-write node cold-start) (backlog, p2, Platform / Runtime Engineer) — before board-claim-guard.mjs goes standing, give it the dumb-fast treatment so it doesn't re-introduce the per-call node cold-start DEC-0041 removed. Distinct from Build the PreToolUse claim/lease governance hook (verdict logic, not transport).
• Filed off DEC-0038 (both p2, Astro Starlight Engineer): Add the missing d3-transition dependency + import so graph-island's zoom transitions animate (and astro check reaches zero) — graph-island.ts calls .transition() but d3-transition is undeclared (4 pre-existing ts(2339)); and Prune the now-dead per-page topbar/footer CSS left behind after the shared-chrome consolidation (keep .landing-external) — the per-page chrome markup was removed but its CSS left behind (keep .landing-external).
• Filed off the DEC-0042 pass (both p2, Principal UX Engineer): Extract a checked-in WCAG contrast-check utility (scripts/check-contrast.mjs) so token-palette changes are auditable and repeatable — extract the WCAG contrast arithmetic (re-derived ~4-5× in the brand work) into a checked-in checker; and Confirm and stabilize build-wordmark.mjs (ESM import + woff2/opentype font deps) so the committed wordmark stays re-buildable — confirm-then-fix whether build-wordmark.mjs re-runs cleanly from a fresh checkout.
• Filed off DEC-0043: Execute the SvelteKit app migration (DEC-0043) — phased, no big-bang, apex domain moved only at final cutover (backlog, p1, Principal Forward Deployed Engineer) — the phased SvelteKit migration; the atom tracks the done-definition (okf-view extracted + consumed by both apps, all surfaces on a preview URL, apex moved once at cutover, zero nav flash, theme continuity), not the step list.
• Filed off a roster-integrity gap: Author the two missing role atoms — documentation-engineer and mcp-engineer — so every accountability agent has a knowledge/roles/ atom (backlog, p2, Principal Knowledge-Format Architect) — documentation-engineer + mcp-engineer have agent files but no role atom (log-auditor excluded by design). See Principal SvelteKit Engineer.

2026-06-17

• Author the two missing role atoms — documentation-engineer and mcp-engineer — so every accountability agent has a knowledge/roles/ atom → done. Authored Documentation Engineer & Information Architect + Agentic-Foundation / MCP Engineer role atoms, each grounded in its agent file, parse+validate clean; agents↔roles now 1:1 except log-auditor. See Dossier — Decision & Audit Log (2026-06-17).
• Execute the SvelteKit app migration (DEC-0043) — phased, no big-bang, apex domain moved only at final cutover → review (DEC-0043 Phases 0–5 built + verified). Build done; only the apex-domain cutover (Phase 6, the user's call) remains. Two mid-build decisions: Lenient KB-atom reader in @dossier/okf-view (readKbAtoms) — faithful getCollection reproduction for the SvelteKit app, Persistent read-only chrome via an (app) route-group layout — stop the header re-animating on intra-app nav. See Dossier — Decision & Audit Log (2026-06-17).
• Execute the SvelteKit app migration (DEC-0043) — phased, no big-bang, apex domain moved only at final cutover → done (DEC-0043 LIVE on production). Apex cutover shipped + user-confirmed; Migrate chrome-light app surfaces to SvelteKit; docs stay on Astro/Starlight (two apps, one origin) promoted asserted → verified. Four fast-follows remain open (below). See Dossier — Decision & Audit Log (2026-06-17).
• Three DEC-0043 fast-follows filed (all backlog): Svelte-ify the board's ~270 lines of vanilla-JS interactivity (the DEC-0043 / Phase-7 fast-follow) (p2, Principal SvelteKit Engineer) — rewrite the board's ~270 lines of carried-verbatim onMount JS as idiomatic Svelte 5, behavior byte-identical; Re-home the Buttondown email templates from packages/site to @dossier/app (the subscribe endpoint moved) (p2) — git mv the Buttondown templates to @dossier/app + fix the README; Decide whether @dossier/docs keeps @vercel/analytics now that the landing (its only consumer) moved to @dossier/app (p2) — confirm-then-decide on the now-orphaned @vercel/analytics docs dep. Also folded the landing content-model path move into Fix the stale round-trip-test path in the generate-landing SKILL.md (points at a file that no longer exists) (re-pointed to Principal SvelteKit Engineer) rather than file a near-duplicate. See Migrate chrome-light app surfaces to SvelteKit; docs stay on Astro/Starlight (two apps, one origin).
• Design the OKF `task` concept type + seed the board → done (stale card reconciled; asserted → verified). Work shipped in Agentic board v1 — build the git-resident OKF task board (deterministic offline core, SDK reserved), resolving DEC-0024's four open questions and dogfooding Dossier's own repo first; the card just never got flipped — the canonical instance of the failure mode (progress lands in commits, status hand-edited and forgotten). All four ACs re-verified green before flipping.
• tasks/index.md "Current board" table de-drifted (SSOT fix). Replaced the hand-maintained status snapshot (stale vs the live atoms) with a pointer to the rendered /board; actions DEC-0030's routed review item. No new ADR.
• Render the board as a derived `/board` surface in @dossier/site → done (superseded-but-delivered; asserted → verified). The read-only KB-agnostic /board shipped in @dossier/app Phase 3 (via Lenient KB-atom reader in @dossier/okf-view (readKbAtoms) — faithful getCollection reproduction for the SvelteKit app), not the Astro surface the criteria named; verified read-only by construction.
• Prune the now-dead per-page topbar/footer CSS left behind after the shared-chrome consolidation (keep .landing-external) → done (moot; inferred → verified). DEC-0043 stripped @dossier/site to docs-only, deleting those pages + stylesheets wholesale (grep: 0 occurrences of the 12 selectors in active code). No new ADR.
• Filed off DEC-0047: Render the client's REAL board inline on the dev-only preview (the board sibling of DEC-0047's inline graph) (backlog, p2, Principal SvelteKit Engineer) — the preview's board card still links Dossier's /board; render the client's own task atoms inline (the board sibling of DEC-0047's graph fix). See The dev-only client landing preview renders the client's REAL OKF knowledge graph inline — via three atomic no-copy-paste extractions (readKbAtoms(dir), buildGraphView, GraphExplorer) that read the client's served OKF directly without perturbing the process-wide DOSSIER_KB or the prerendered /graph.
• Filed off DEC-0046: Abstract the hard-coded hamburger-bar / icon-stroke geometry into a --ds-* token family (border-width / icon-stroke) (backlog, p2, Principal UX Engineer) — the hamburger glyph is the only bare-pixel geometry left in SiteHeader.svelte; add a --ds- icon/border-width token family and repoint it. See Restructure the shared SiteHeader into a three-zone information architecture — brand far-left, Board·Graph optically centered, Docs·GitHub·CTA·theme far-right — plus an accessible mobile disclosure and a stacking-context fix.
• Re-home the Buttondown email templates from packages/site to @dossier/app (the subscribe endpoint moved) → done (inferred → verified). git mv packages/site/emails → packages/app/emails (history preserved), four stale README refs fixed; nothing imports the templates so no wiring changed.
• Fix dossier-runtime `site` subcommand dispatch (isSub omits 'site') → done (inferred → verified). Fixed at the root: extracted SUBCOMMANDS into subcommands.ts so the Sub type AND isSub derive from one array (a missing subcommand can't recur); +4 regression tests, runtime suite 64/64 green.
• Decide whether @dossier/docs keeps @vercel/analytics now that the landing (its only consumer) moved to @dossier/app → done (decided: DROP). Zero source consumer in @dossier/docs (funnel analytics lives in @dossier/app); dropped the dead dep, docs build 95 pages clean. Add Vercel Web Analytics to the public marketing landing (a cookieless demand signal — landing surface only, not the KB or product) still honored in the app.
• Fix the stale round-trip-test path in the generate-landing SKILL.md (points at a file that no longer exists) → done (skill + DEC reconciled to @dossier/app). Repointed every path in the generate-landing SKILL.md to its post-DEC-0043 homes; reconciled DEC-0037 with a > Path update note. One thread open: a tokenizeOkf rename declined by the permission classifier (non-blocking).
• Sweep summary. Four DEC-0043 fast-follows + one DEC-0039 bug closed this pass, plus three stale/moot cards reconciled — the board's stale backlog is materially cleared. All real fixes (no status-only closes); no new ADRs.
• Filed off the landing length/rhythm pass: Delete or formally park the now-unused HeroLoop.svelte (its only import was removed when the loop diagram merged into the hero) (backlog, p2, Principal SvelteKit Engineer) — merging the loop diagram into the hero left HeroLoop.svelte as dead code, but four landing.css comments cite it as the canonical motion reference; resolve intentionally (delete + reword, or formally park).
• Filed off DEC-0048: Document that local dev needs BOTH servers running (app + @dossier/docs on :4321) — root dev-script note or README (backlog, p2, Principal SvelteKit Engineer) — local dev now needs both the app AND @dossier/docs (:4321) running, but that requirement is undocumented (no app README; root dev note). See Link to the split @dossier/docs surface dev-origin-aware (same-origin in prod, docs dev origin in dev) via an SSOT $lib/docs module — NOT a Vite dev proxy, which two Vite dev servers cannot share one origin for.

2026-06-18

• Filed off DEC-0052: Author the agentic-agency runtime topology DEC + spec (OKF→persona/runbook/team; coordinator/dispatch; per-tenant fleet isolation; Atrium+board+reconcile+MCP composition) (backlog, p1, Principal Platform Architect) — the follow-on topology DEC DEC-0052 named: ratify the OKF→agent mapping + coordinator/dispatch + per-tenant fleet isolation + how Atrium/board/reconcile()/MCP compose into one governed loop. See DEC-0052.
• Filed off DEC-0052: Author the "Atrium" DEC — the live-layer-over-git co-working room (Yjs + self-hosted Y-Sweet; snapshot bridge → reconcile) (backlog, p1, Principal Platform Architect) — the Atrium DEC: live-layer-over-git (Yjs over self-hosted Y-Sweet) + a snapshot bridge through reconcile(), git stays SSOT. See DEC-0052.
• Filed off DEC-0052: Spec the v0 agency dashboard surface (Phase 0 dogfood — Dossier's own .claude/agents team on Dossier's own OKF; daily-standup / approve-ship loop) (backlog, p1, Product Owner) — the v0 agency-dashboard product spec (the approve/ship/watch UX over the live board; the compounding return made visible). The Phase-0 dogfood is DEC-0052's named promotion gate. See DEC-0052.
• Filed off DEC-0052: Build the L2 "adoption readout" generator skill (sibling of generate-landing — MCP-retrieval harness + KNOWLEDGE-BRIEF; a 4-axis scorer over process/workflow atoms → sequenced roadmap → OKF artifact in the client repo) (backlog, p1, Principal Knowledge-Format Architect) — the Ladder/wedge: an L2 adoption-readout generator skill (4-axis scorer over process/workflow atoms → sequenced roadmap → emitted as a sovereign OKF artifact). See DEC-0052.
• Author the agentic-agency runtime topology DEC + spec (OKF→persona/runbook/team; coordinator/dispatch; per-tenant fleet isolation; Atrium+board+reconcile+MCP composition) → done (satisfied by DEC-0053; writing the DEC fulfills the task). Agentic-agency runtime topology — compile personas from the OKF graph and activate the reserved BoardWorker over the deterministic spine ratifies + promotes DEC-0052's OKF→agent-fleet mapping (proposed→ratified) and pins seven invariants; every cited source ref verified against the live files first.
• Author the "Atrium" DEC — the live-layer-over-git co-working room (Yjs + self-hosted Y-Sweet; snapshot bridge → reconcile) → done (satisfied by DEC-0054). Atrium — the live co-working room over git, on Yjs + self-hosted Y-Sweet, snapshotting through reconcile() (host pick gated on human sign-off) ratifies Yjs + self-hosted Y-Sweet + the snapshot bridge, git SSOT, host pick deferred to human sign-off. See Dossier — Decision & Audit Log (2026-06-18).
• Sweep note. DEC-0053 + DEC-0054 recorded (both ratified-design, asserted, shared gate = Phase-0 implementation); two tasks closed. No new tasks — the DECs name only Phase-0 implementation, already their ## Review gate.
• Three tasks filed off DEC-0055 (all p2, inferred, Knowledge-Extraction & GraphRAG Engineer): Resolve 4 orphan-artifact graph errors from the RBA Firecrawl run (link a producing process or prune) (4 orphan-artifact graph errors — structural, not hallucinations); Add a retry/repair path for extraction segments that fail on malformed model JSON (segment #82's malformed-JSON atoms silently lost — add bounded retry/repair); Harden the RBA harness subscription-client spawn — drop shell:true (Node DEP0190) (harness DEP0190 hardening). The Firecrawl confidence-promotion question deliberately NOT filed (owner's DEC-0055 ## Review call). See First live FirecrawlConnector run against a real client source — field evidence for the reserved web seam.

2026-06-19

• Four tasks filed (+ one updated) off the multi-surface FDE/QA pass scaling the RBA run 3→33 pages. The run is structurally valid + secure but NOT yet reference-tenant quality. All inferred, tied to First live FirecrawlConnector run against a real client source — field evidence for the reserved web seam: (1) Make the learning loop dedup/reconcile at scale (collapse same-type duplicate clusters; default-on compounding) (p1, root cause, Knowledge-Extraction & GraphRAG Engineer) — 26 same-type duplicate clusters; the QA brief's "reconcile() not wired" claim was corrected before filing (it IS wired but opt-in/default-off and id-strict; in-pass resolve() keys id-else-title, so divergent-id/near-title dups leak). (2) Fix extraction type-discipline — `system` used as a catch-all + non-slug ids (RBA run) (p2) — 18/25 system atoms mis-typed with non-slug ids. (3) Have extraction populate the accountability spine (owner / reports_to / members / decision_rights) (p2) — accountability layer absent (owner 0/494); populate only where grounded. (4) Make the docs renderer registry-aware for vertical edges + render decision judgment fields (p2, Astro Starlight Engineer, the only surface-side fix) — okf-view's EDGES is core-only, dropping DXA vertical edges; union with the registry + render decision fields. Updated (not re-filed): Resolve 4 orphan-artifact graph errors from the RBA Firecrawl run (link a producing process or prune) gained the three-way root-cause nuance. See First live FirecrawlConnector run against a real client source — field evidence for the reserved web seam.
• Make the learning loop dedup/reconcile at scale (collapse same-type duplicate clusters; default-on compounding) → done (inferred → verified; DEC-0056). Concept-identity dedup built in the @dossier/okf keystone + wired into resolve/reconcile/loop; field result on RBA 494→453 atoms, 32→0 clusters. KB deduped but not yet reference quality — sibling p2 tasks stay open. See DEC-0056.
• Make the docs renderer registry-aware for vertical edges + render decision judgment fields → done (inferred → verified; DEC-0055 follow-up B). The docs renderer is now registry-aware (relatedEdges unions core + registeredEdgeFields(), single-sourced — DEC-0033) and renders decision fields; a second root cause fixed (the content schema was Zod-stripping the DXA + ADR fields).
• Filed off the docs-renderer fix: Register the DXA vertical preset in @dossier/app before building the inline graph (the /graph + /preview graphs likely drop DXA edges) (backlog, p2, Principal SvelteKit Engineer) — the app's graph-view.ts never calls registerDxaTypes(), so registeredEdgeFields() is empty and /graph + /preview likely drop DXA vertical edges (app-side mirror of follow-up B). See Dossier — Decision & Audit Log (2026-06-19).
• Sweep summary. Two closed (dedup p1, docs renderer p2) + one filed (app-side registration p2); one ADR recorded (Concept identity = type + (canonical-title OR prefix-stripped id), exact-match closure — dedup owned by the @dossier/okf keystone, in-pass + opt-in reconcile + loop default). Still open: the p2 RBA tenant-quality tasks. See Dossier — Decision & Audit Log (2026-06-19).
• FDE reference-tenant QA pass closed four tasks (RBA now conformance + graph clean). Deterministic data surgery, 75168d0(494)→509c38d(453)→8229530(445), okf tests 170/170. (1) Fix extraction type-discipline — `system` used as a catch-all + non-slug ids (RBA run) → done — 23 system atoms re-typed (7→artifact/16→process), 18 ids slugified, 0 stranded; system 70→47; exposed 8 new merges the dedup folded. (2) Resolve 4 orphan-artifact graph errors from the RBA Firecrawl run (link a producing process or prune) → done — orphan-artifact 3→0 (2 case studies →engagement, others given grounded producers, no fabrication). (3) Have extraction populate the accountability spine (owner / reports_to / members / decision_rights) → done — owner on 72/103 processes, discipline-matched; 31 cross-disciplinary left unowned (grounded-only). (4) Register the DXA vertical preset in @dossier/app before building the inline graph (the /graph + /preview graphs likely drop DXA edges) → done — graph-view.ts now calls registerDxaTypes() at module init; RBA /preview 660→718 edges, Dossier /graph unchanged. Curation lessons recorded in Concept identity = type + (canonical-title OR prefix-stripped id), exact-match closure — dedup owned by the @dossier/okf keystone, in-pass + opt-in reconcile + loop default §Operational lessons. See Dossier — Decision & Audit Log (2026-06-19).
• Filed off the close-out (the honest remaining blocker): Close the RBA delivery-modeling taxonomy gap — capability→delivery `delivered_by` grounding + two persona-role cleanups (backlog, p2, Principal Knowledge-Format Architect) — RBA is conformance-clean but not full reference quality: a structural taxonomy gap surgery can't fix without fabrication (delivered_by 8/187 because capabilities relates_to practices not delivery workflows; a near-dup persona pair left distinct; 5 buyer personas with 0 inbound edges, correct).
• Close the RBA delivery-modeling taxonomy gap — capability→delivery `delivered_by` grounding + two persona-role cleanups → done (DEC-0057 decided + applied; 8229530→d9865f2). delivered_by grounded by a deterministic bridge: 9/187 → 88/187 grounded, 99 empty, none fabricated; the persona pair merged (445→444, no supersedes); 8 non-conformant edges re-homed; validateGraph 0 issues. See DEC-0057.
• Filed off the DEC-0057 pass: Re-type 6 client-specific RBA `workflow` atoms as DXA `engagement`s (single-client SOW instances, not standing orchestrations) (backlog, p2, Knowledge-Extraction & GraphRAG Engineer) — six atoms typed workflow are single-client SOW instances (DXA engagement); re-type + wire client/runs/capabilities. Same type-discipline class as the system mis-typing.
• Re-type 6 client-specific RBA `workflow` atoms as DXA `engagement`s (single-client SOW instances, not standing orchestrations) → done (inferred → verified; d9865f2→975cc83). 6 atoms re-typed workflow→engagement (2 kept, 4 merged, no supersedes); edges wired grounded, 2 left unset for lack of grounding; 14 inbound refs re-pointed, 0 stranded; parse 440/440, validateGraph 0 issues.
• Filed off the close-out (the durable emit-time fix): Improve extraction EMIT-time type discipline for DXA vertical types (so future runs don't need post-hoc curation) (backlog, p2, Knowledge-Extraction & GraphRAG Engineer) — the system and engagement mis-typings share one root cause (extraction assigns vertical types weakly); build an emit-time type-discipline heuristic (conservative/never-fabricate), validated against the eval judge. The post-hoc surgery tasks are done; this is the forward fix.
• Eight tasks filed off DEC-0059 (the sensitive-data + prompt-injection synthesis; detail in research/2026-06-18-sensitive-data-and-injection-defense.md). All inferred, routed to the closest accountable layer (no security-engineer role): Detector ensemble at the ingestion boundary with a MEASURED F2/recall target (Presidio recall-tuned + custom "P2" recognizers + cloud DLP) — measure detection, don't trust it (p1, Ingestion & Connectors Engineer); Fail-closed quarantine wrapper for the Unstructured file path (zero-element / encrypted-by-header / unknown-MIME → quarantine-by-default) — because Unstructured fails EMPTY, not CLOSED (p1, Ingestion & Connectors Engineer); Deny-by-default egress sandbox around the extraction agent — break the lethal trifecta so a hijacked agent structurally cannot exfiltrate (the single load-bearing build finding) (p0, Platform / Runtime Engineer, the single load-bearing build finding); Per-tenant runtime isolation — make the tenant a process/network/key boundary (not a directory), with a per-tenant vector namespace + server-side tenant binding, so a poisoned/sensitive atom is contained to ONE tenant (p1, Platform / Runtime Engineer); Read Microsoft Purview/MIP sensitivity labels at M365 ingest + a client-side DLP egress gate (Layer 1 — honor the client's existing classification) (p2, Ingestion & Connectors Engineer); Web-crawl hardening for the live Firecrawl path — pin >=2.0.1, network-layer internal/link-local egress blocklist, never carry client session credentials (p2, Ingestion & Connectors Engineer); Payload-free, tamper-evident audit/drop-log design — record the DECISION (per-item verdict + label snapshot + drop reason), NEVER the sensitive payload (the "audit paradox") (p2, Platform / Runtime Engineer); Serve-layer poisoning defense — propagate provenance/trust-tags to consumers + a read-only sandboxed serve-time agent + an output hook blocking atom-instructed side effects (p2, Agentic-Foundation / MCP Engineer). The architectural stance itself (DEC-0059) and the ratification call were NOT filed (owner judgment). See Untrusted-by-default ingestion & serve boundary — defense-in-depth to keep regulated data out and contain prompt injection.
• Filed off the DEC-0053 Phase-0 promotion: Fix the 41 KB load errors degrading Phase-0 persona grounding (dangling persona-grounding targets) (backlog, p1, Principal Knowledge-Format Architect) — the dogfood reproduced 41 KB load errors, so 11/34 reachable fde-role targets dangle (Invariant 7). Does not block Phase-0. The runtime-impact close-out of Resolve the decision `reversibility` schema conformance gap (the schema call). See DEC-0053.
• Two tasks filed off the DEC-0061 curation-tier pass: Docs home must resolve for every served KB (synthesize an overview when there is no root index) (backlog, p1, Astro Starlight Engineer) — closes the DEC-0058 dangling ref kb:check flagged; and Retro-shrink the legacy knowledge/log.md essays to true one-liners (terse line + wiki-link) (backlog, p2, log-auditor) — the optional legacy-log.md one-liner sweep. See DEC-0061.
• Two tasks closed by the DEC-0017 reversibility sweep (6b1d662). Resolve the decision `reversibility` schema conformance gap → done (Option 3 applied; KB parses clean). Fix the 41 KB load errors degrading Phase-0 persona grounding (dangling persona-grounding targets) → done (load errors 41→0, unresolved fde grounding 11→3; 3 residual flagged for Principal Knowledge-Format Architect).

2026-06-20

• Filed reconciling the crashed DEC-0053 carried-forward-seams build: Activate parallel intra-tenant drains via per-task git worktrees, or stay serialize-only? (one-way-door topology call) (backlog, p1, Principal Platform Architect) — the per-task git-worktree mechanism is built + offline-proven but NOT activated; flipping to parallel intra-tenant drains (relaxing the Inv 4 drain lock) is a one-way-door call left to the architect. See DEC-0053 §Review.

2026-06-21

• Four tasks filed off the DEC-0073 visibility-floor "Now"/"Next" roadmap (the GTM moves made durable, executing on the DEC-0072 register topology). The two P0 "Now" moves: Stand up the product-docs register — REPURPOSE the @dossier/docs Starlight surface to official product docs at /docs/* (new-tab "Docs") (p0, Documentation Engineer & Information Architect) — the keystone: a SECOND authored Starlight collection at /docs/*, Diátaxis skeleton + four real pages, zero atoms into knowledge/**; and Shareability + crawlability hygiene pass — one atomic <SiteHead> (OG/Twitter + canonical + JSON-LD), robots.txt, sitemap (p0, Principal SvelteKit Engineer) — one atomic <SiteHead> (OG/Twitter/canonical/JSON-LD) + robots/sitemap with an AI-crawler allow-list (carries the verified ground-truth correction: @astrojs/sitemap is NOT a declared dep of @dossier/docs). The two "Next" moves (filed clean): Comprehension funnel — route the landing/docs surfaces into a clear primary CTA toward the on-ramp (p1, Product Owner/Principal SvelteKit Engineer, depends on the docs register) and Finish DEC-0014 plugin distribution — verify the Claude Code plugin installs as a real product from the marketplace (p1, Product Owner/Platform / Runtime Engineer) — finish the DEC-0014 plugin-install verification, the highest-leverage underused channel. Board globbed + grepped before filing — no duplicates. See DEC-0073.

2026-06-22

• Filed off the founder-directed DEC-0072 two-renderer refinement: Render the dogfood OKF KB app-native in @dossier/app near /graph (the prerequisite that frees Starlight for product docs) (backlog, p0, Principal SvelteKit Engineer + Principal UX Engineer on the "much-better-looking" bar) — render the dogfood OKF KB app-native in @dossier/app near /graph via @dossier/okf-view + @dossier/design (the /graph explorer stays the entry, atom pages app-native under the (app) chrome group); flip vercel.json, redirect old /knowledge/* + atom URLs, update the docsUrl() seam. The PREREQUISITE that frees Starlight for product docs. Updated (not re-filed): Stand up the product-docs register — REPURPOSE the @dossier/docs Starlight surface to official product docs at /docs/* (new-tab "Docs") — now REPURPOSE the Starlight surface to product docs (new-tab "Docs" link) + dependency on the KB-move task. Board globbed/grepped first — no dup. See DEC-0072 §Refinement.
• Render the dogfood OKF KB app-native in @dossier/app near /graph (the prerequisite that frees Starlight for product docs) → done (Track 1 built + browser-verified; within DEC-0072's frame). KB renders app-native via (app)/[...slug] over the shared okf-view reader (159 atoms, URLs byte-preserved, vercel proxy flipped); a node:fs-in-client hydration leak (OkfMeta) was found + fixed during verification (types-only + server-pre-resolved props); svelte-check 0 / prod build green / kb:check clean. NOT a DEC-0072 promotion (Track 2 product docs still pending). Filed: Split @dossier/okf-view into a client-safe entry (view-model + types) vs a server-only entry (the fs readers) + guard against node:fs leaking into the client (backlog, p2, Principal SvelteKit Engineer) — split okf-view into a client-safe entry (view-model + types) vs a server-only entry (the fs readers) + an ESLint/CI guard, so the leaky-barrel bug class (the symptom OkfMeta hit) can't recur; shared leaf, both @dossier/app + @dossier/docs must stay green. Board globbed/grepped first — no dup.