ASSAY component gallery

Live components — the demonstrator's actual code, rendered over Meridian vignette fixture data (SPEC-04). Components, not product: no service, no compute, no plan exists behind this page. Every assessed value is banded with provenance welded on (ASSAY-DEC-9); the Meridian scenario is engineered fiction (ASSAY-DEC-8).

The knowledge base, K1–K14

Minimal S1 knowledge table (SPEC-05)

The knowledge service's four discipline moments, rendered by the actual firewall over the same fixtures: the refused K10 save (banner), the contested K12 pair (compile-blocking flag), K8's waiver and single-source markings, and confidence-lint cautions. Banded honesty holds — no bare assessed scalar appears (G2).

Compile — knowledge → CompiledWorld (SPEC-06)

The Stage-2 demo moment, run by the actual compile service. Contested never compiles (G5): with the K12 mine-stock pair disputed, the compile refuses rather than average an irreconcilable band into a channel —

Resolve the contest, and the recompile builds the world. Channels are stored sparse — a per-channel default plus named region overrides (the MCOO idiom; no dense 1.2M-cell surface is ever stored or hashed). Every channel value walks back to the named knowledge it came from, with its owner (G3). stamp daf11dafaedb6190… · 9 knowledge objects consumed · sparse channels (no dense cell stored)

Score & organise — the honest matrix (SPEC-07 · SPEC-08)

The Stage-3 demo moment, run end-to-end by the actual machinery: /plan/handful (SPEC-08) fans out over Meridian's four axes — approach, suppression, causeway, extraction — scores every candidate with the SPEC-07 scorer, and organises by banded non-domination into the genuinely distinct plans below. No author picked the set: a plan is kept only when no other conservatively beats it on every commitment (overlapping bands are honestly incomparable and both survive), and dropped only when strictly beaten everywhere — never on a scalar total (DEC-19). Each plan's reason is derived from the organiser, not captioned:

The same handful, as the S2 planner matrix. Verdicts are a four-stop scale — robust / marginal / tight / violated, one colour language, no decimals anywhere; the banded margin rides on hover, never a headline number (G2). Each verdict propagates its metric by interval arithmetic — worst-and-best-case on pure bands, no midpoint (DEC-15) — validated by the vignette §9 oracle cases (O-1–O-3 exact, O-4 containment). Pick a verdict, walk it to the assessment and owner it rests on: every cell was written with a scored_from edge back to the world, whose channels trace to named knowledge above. handful stamp f244e2ce7209c096… · 4 genuinely distinct plans, organised not authored · same stamp + seed ⇒ identical handful (G1) · every verdict carries a scored_from edge to the world (G3)

Relax — least-worst, never silence (SPEC-09)

The Stage-4 demo moment, run end-to-end by the actual machinery. Against the R3m world (both approaches mined, the causeway dropped) no plan satisfies C2, C3 and C4 together — by construction (vignette §6) — and the dropped causeway forecloses C5 ("taken intact") for every plan, so C5 rides in every sacrifice set as a scenario-imposed, computed loss (SPEC-20). /relax does not pick one compromise and hide the trade: it returns every inclusion-minimal way forward, each naming what it gives up in command language. The sacrifices are computed — a commitment is sacrificed only when the SPEC-07 scorer returns violated for it — not authored. Ranked least-worst first by the commander's ordinal tiers (must / should / prefer, no numeric weight — DEC-19): the two should-sacrifices lead, the must-sacrifice (C2, "the strait opens two days late") is ranked last but present — never dropped, never silent (G4). Plans that give up more — {C2,C4,C5}, {C3,C4,C5} — are inclusion-dominated and never shown as separate options. relax stamp afffeecf288bac02… · 3 least-worst candidates over R3m, computed not authored · never empty, never a silent drop (G4) · tie-break stated (DEC-19) · each candidate cited_in the report back to named knowledge (G3)

Scenario robustness — don't plan on most-likely (SPEC-10)

The Stage-5 demo moment (thesis C; JP 2-01.3: "don't plan on most-likely"). The generated handful scored across BASE, R1, R2, R3 — the adversary COA set from the vignette. Each cell is a four-stop verdict chip; a ▼ marks a verdict that dropped from its BASE value under that scenario ("collapse"). The worst column is the minimax: the plan's worst verdict for that commitment across all scenarios — a real verdict on a real scenario, not a weighted blend (DEC-15/19). Toggle R2 (Strait Denial) and watch the strait-early plan die on C1/C2 while robust alternatives hold. Above the grid, the attention block (SPEC-22) renders the K14a–c likelihood bands under the interval order: R1 (45–70 %) ranks strictly above the level pair {R2, R3}, whose bands visibly overlap — the system refuses, in public, to rank what the bands don't rank. The block is labelled "orders attention — never compiles" (knowledge model §9): the verdicts below owe it nothing. robustness stamp 0e216aabfed5f773… · 4 scenarios × 4 plans × 6 commitments · worst-case (minimax) verdict per plan×commitment · stamps_compatible=true

Sensitivity — which beliefs bear load (SPEC-11)

The Stage-6 sensitivity demo moment (thesis E). Band-edge perturbation of each consumed knowledge object against the first handful plan: push each answer to its lo and hi edges, re-score, and count how many commitment verdicts change. K8 tops the ranking with single_source: true — its band-edge perturbation changes C4 verdicts via the battery fire-control threshold. The single_source flag is carried through from provenance, never used in the ranking arithmetic (DEC-19) — shown alongside so the commander sees the collection risk without it being laundered into a scalar. sensitivity stamp 55059bb7a57d38eb… · 9 knowledge objects perturbed · ranked by verdict-change count · single_source carried, not used in ranking (DEC-19)

Discrimination — which questions separate COAs (SPEC-12)

The Stage-6 discrimination demo moment (thesis D). COA-pair band separation over open questions' expected-answer miniatures (DEC-18): for each open question with expected_answers, measure how well the answer bands separate each pair of adversary COAs. K11 ranks above K13 despite higher collection cost — the R1/R2 expected-answer bands are disjoint (mines loaded vs not), while K13's radio-traffic bands overlap across all COAs. Cost is shown alongside, never collapsed with value (DEC-19): the commander sees both and decides. No Shannon entropy, no VOI, no scenario weights (research note 08-analysis.md §3). discrimination stamp a0d0916b1a4cf0b7… · 2 open questions ranked · COA-pair separation over expected-answer bands (DEC-18) · cost alongside, never collapsed (DEC-19) · operative pairs derived from the verdict tensor (SPEC-23, never curated)

Decision support — decisions in time (SPEC-24)

The keystone demo moment (review §4.2 — "the artefact a J-3 actually recognises"). The doctrinal decision support matrix, derived, never drawn (research note 12): a commitment is a decision point iff its verdict turns on open information — scenario-divergent across the adversary COA set, or margin-class under the selected world. The commit step is read from the plan's own geometry (the first route leg whose channel read differs across the scenario worlds — past it, the branch is taken); LTIOV = commit step − lead (lead 0, stated); each collection option renders in time (slack as a step count) or the honest red "cannot answer in time" with its arithmetic visible — never dropped. On P2 (sweep-first) the port decision (C1) holds open to step 10 and DET KINGFISHER's step-8 report arrives in time with 2 steps of slack — where strait-early (P1) commits at step 4, a day before recon can report: the DSM shows, computed, why sweep-first buys decision space. The system ranks and derives, never tasks — tasking KINGFISHER is a human act with its own commitment consequence (C6). decision-support stamp 2c5848b43c2c531a… · 3 decision points, derived not drawn · LTIOV = commit step − lead (lead 0, stated) · red states rendered with their arithmetic, never dropped (G4) · every row cited_in back to its evidence (G3) · no urgency scalar anywhere (DEC-19)

Staleness — what goes stale when knowledge changes (SPEC-13)

The Stage-6 staleness demo moment (thesis F). Transitive forward trace walk from K9 (the storm-window knowledge that superseded K5): follow every downstream edge — consumed_by, scored_from, compiled_into — using the EDGE_ORIENTATION map from traceView.ts. The walk flags exactly the dependent verdicts and nothing else. It does not recompute — the constitution says flags, then humans decide. staleness stamp 90afb9dedfe9ea2f… · 98 verdicts + 1 worlds invalidated · transitive walk from K9 · flags only, no recompute (constitution)

Verdict legibility — the mapping, the consequence, the challenge (SPEC-25)

The legibility slice, over machinery ASSAY already has (review §3.1/§3.3, note 14). First, the verdict legend (US1): the four-stop mapping laid open, CRT-style — each verdict a region of the signed-margin sign rule, illustrated by the frozen oracle O-3 sweep (the verdict changes only at the band edges 9 and 13, never inside). It renders a mapping, never a score (DEC-19), and is oracle-derived — a change to it is a register/oracle matter, not a data event.

Next, the consequence preview (US2, the substantive build): arm a mutating act — here resolve K12 — and see the real diff before committing, computed by the live pipeline over a byte-faithful shadow of the store, never an estimate (Into the Breach's telegraphed-consequence contract applied to knowledge work). The ghost persists nothing, emits no delta, mutates no stamp; the previewed diff equals the post-commit glow set element-for-element (G1/DEC-34) — the ghost is what will happen, not a picture of what might.

The challenge affordance (US4): on any verdict, one act re-renders the SPEC-11 sensitivity ranking scoped to that verdict — the knowledge that, pushed to its band edge, flips it, with single-source flags co-shown and a deep link to the knowledge row. It routes challenge, it does not adjudicate it (the Red Teaming Handbook's warning against lip-service challenge). On Meridian under BASE the honest C4 flipper is K6 (the documented band-propagation) — the plans route clear of the threatened water, so K8 is genuinely insensitive there; surfacing it would be false.

Finally, the per-role action menus (US5): who may do what, made legible — each role's legal write verbs, marked live / runs on recompute / not yet built (never a dead button faking a write, DEC-4). The observer exposes no write — the bridge watches the seam, it never touches it. Menus reorganise what the seam already permits (DEC-33); they never restrict.

Generated from fixtures/ by npm run gallery · identifiers frozen per assay-vignette.md §8 · compile per research note docs/research/02-compile.md · score per docs/research/03-score-plan.md · relax per docs/research/04-relaxation.md · robustness per docs/research/06-robustness.md · analysis per docs/research/08-analysis.md · attention per docs/research/11-attention.md · decision support per docs/research/12-decision-support.md · legibility per docs/research/14-legibility.md