read-only

Make the docs renderer registry-aware for vertical edges + render decision judgment fields

task-okf-view-registry-edges-and-decision-fields

task confidence verified status done 2026-06-19 owner starlight-engineer
source log-auditor — surfaced from the FDE QA pass on the 33-page RBA Firecrawl tenant (DEC-0055); the docs-surface build agent flagged both gaps; EDGES/OkfData claims re-verified against packages/okf-view/src/view-model.ts before filing; closed DONE 2026-06-19 by the starlight-engineer (verified against view-model.ts + content.config.ts)

Make the docs renderer registry-aware + render decision judgment

The multi-surface FDE pass on the RBA tenant (First live FirecrawlConnector run against a real client source — field evidence for the reserved web seam) found two gaps in the docs renderer (@dossier/okf-view) — and importantly, these are the only surface-side fixes: the landing, inline graph, and docs all built and rendered the 494-atom KB faithfully, so T1–T3 are upstream (loop/extraction). These two are genuinely renderer-side.

The two gaps

  1. Not registry-aware for vertical typed edges. OkfRelated's EDGES list (packages/okf-view/src/view-model.ts:56-65) is the hardcoded CORE vocabulary only — supersedes/superseded_by/relates_to/informed_by/decided_in/uses/governed_by/produces. It drops the registered DXA vertical edges (client/engagements/capabilities/delivered_by/systems/runs/sow), so the ~25 atoms forming the client↔engagement↔capability spine render no/partial "Related" nav. The upstream @dossier/okf edges() (packages/okf/src/graph.ts) already unions core + every registered vertical field — so the fix is to single-source that union into the view, not hand-maintain a parallel list (OKF edge vocabulary is registry-driven — a vertical declares its own traversable edges).
  2. Decisions don't render their judgment. OkfMeta.astro renders no context/decision/rationale for decision atoms (the OkfData interface, view-model.ts:12-40, carries no such fields). The ADR "why" — the judgment layer that is the entire reason decision is a core type (Dossier — The Knowledge Model (v0)) — is invisible on the docs surface. Add a decision-fields block.

Why a task, not a decision

The Astro Starlight Engineer flagged it would draft rationale for review before shipping these renderer changes — they are not yet implemented. Per the recorder/auditor discipline, unbuilt work is a task, not a decision; the decision (if the union approach needs ratifying) gets recorded when it ships. The fix is renderer-only (@dossier/okf-view + OkfMeta.astro), upstream data untouched. Filed by the log-auditor from the QA pass; confidence: inferred.