ASSAY — UI wireframes v0.2

ASSAY Meridian Archipelago · CTF MERIDIAN D+2 · step 8 · world stamp 7f3a…c91

UI wireframes v0.2 — four role surfaces as projections over one store (ASSAY-DEC-5). All data from assay-vignette.md; identifiers K*/C*/R*/FE-* frozen by vignette §8. Assessed values always banded and marked (ASSAY-DEC-9). Feed times are display-only envelope fields (ASSAY-DEC-17) — computation runs on the scenario clock.

Information flow

the heartbeat loop: J-2 writes knowledge → planner compiles & plans → commander selects → new PIRs back to J-2 — every write a stamped delta

S1 · J-2 workbench ROLE: J-2

reads: /knowledge?status=… · /analyse/discrimination · /analyse/sensitivity · /knowledge/{id}/exposure writes: POST /knowledge · supersede · contest · resolve

Collect next

Which open question best separates the red COAs (thesis D)

K11 · open · banded_soft_cost

Are mines loaded on the minelayers at Ledger quay?

R1 0.0–0.2 | R2 0.7–1.0 — disjoint value ▮▮▮▮▯ cost 2–4 det-days · banded KINGFISHER close recon · earliest step 8

K13 · open · banded_soft_cost

What is the daily radio-traffic volume from garrison HQ?

bands nest across R1–R3 value ▮▯▯▯▯ cost 0.2–0.5 det-days · banded standoff intercept · earliest step 4

K11 outranks K13 despite costing more — separation and cost are both shown, never collapsed into one number.

Verify next

Load-bearing assessments — band-edge perturbation flips the decision (thesis E)

K8 · answered · hard_constraint (waiver W-1)

Is the Carrick Head battery's fire-control radar operational?

flips north approach if false assessed · moderate · single-source deception exposure waiver W-1 · granted by J-3 owner: J-2

K6 · answered · banded_soft_cost

What sortie rate can the FAC squadron sustain?

02–6 sorties/day8

assessed · low · assessment, not factwidens C4 exposure margin

Refresh & resolve

Perishable and contested objects (theses F · G5)

K9 · answered · banded_soft_cost · supersedes K5

What are tide and storm conditions D+2–D+9?

0 msurge 1.1–1.8 m · peak D+5–D+72.5 m

reported (met service) · highvalid steps 8–36K5 now stale — 3 verdicts flagged

K12 · contested · banded_soft_cost

How many sea mines does the garrison hold?

K12a defector debrief · 30–60 · J-2 red cell K12b pre-war manifests · 140–220 · allied LNO blocking next compile — resolve

Exposure strip (collapsed): 8 of your objects (K1–K8) sit under live handful 7f3a…c91 — K8 under all four plans; every north-approach route rests on waiver W-1.

S2 · Planner workbench ROLE: J-3/5

reads: /plan/handful · /score · /relax · /trace/backward writes: /compile · comparison basis (stamped deltas)

Plan	C1 relief D+10	C2 strait D+7	C3 no district fires	C4 ANVIL exposure	C5 causeway intact	C6 KINGFISHER out	R1 / R2 / R3	Sacrifice
P1 north approach · early entry	robust	robust ⚑	robust	marginal	robust	robust	collapses under R2	—
P2 sweep-first · enter D+8	marginal ⚑	marginal ⚑	robust	robust	robust	robust	survives all three	—
P3 parallel sweep surge	robust	robust	robust	violated	marginal	robust	best under R3m	C4
P4 FAC berths first	robust	robust	violated	robust	tight	marginal	harbourfront cost	C3

Within-band plans are co-equal — the matrix narrows, judgement chooses. Any chip opens the trace drawer (margin bands on hover); mixed stamps grey the matrix (comparability guard).

S3 · Commander view ROLE: COMD

reads: /relax · /trace/backward writes: POST /select → SelectionRationale (stamped delta)

If the Kestrel garrison withdraws and mines both approaches (R3m), no plan keeps all of C2–C4. Three least-worst options — each gives up something different:

P3 · Parallel sweep surge

Gives up C4 — BROOM and ANVIL work inside the battery/FAC arc while both approaches are swept

Keeps: strait open D+7 · no fires into the district · causeway approach preserved

R1 / R2 / R3 resilience

P4 · Clear the berths first

Gives up C3 — fires into the harbourfront where the FACs berth among the fishing fleet

Keeps: strait open D+7 · ANVIL outside the arc · convoy timeline

R1 / R2 / R3 resilience

P2 · Accept late opening

Gives up C2 — sequential safe sweep opens the strait D+9, two days late for relief shipping

Keeps: everything else · most robust across all three red COAs

R1 / R2 / R3 resilience

Why can't I keep both C2 and C4? — backward trace, terminating in named knowledge with named owners

C2 verdict: marginal → violated under R3m
plan P2 · stamp 7f3a…c91 · scored_from ← mine-threat channel · both approaches raised
R3m excursion · compiled_into ← K12 · garrison mine stocks · contested ⚑
30–60 vs 140–220 mines — assessment, not fact ← owners: J-2 red cell · allied LNO
resolve before recompile (G5)

S4 · Bridge view ROLE: OBSERVER

reads: /deltas?since=seq · /trace/forward · /analyse/staleness — the J-2/J-3 seam, watched live

Delta feed

J-2 · S1contested K12: defector debrief (30–60) vs pre-war manifests (140–220) — mine-threat compile blocked until resolved14:10Z

SYSstaleness walk from K9: 2 plans · 3 verdicts flagged (K5-dependent) — no silent recompute14:02Z

J-2 · S1superseded K5 → K9: surge 1.1–1.8 m peaking D+5–D+7 (met-service update · valid steps 8–36)14:02Z

J-3/5 · S2compiled world 7f3a…c91 from the answered set K1–K8 · handful of 4 (seed 42)13:40Z

J-3 · S2waiver W-1 recorded on K8: radar assessed non-operational compiles as hard constraint — north approach open09:30Z

Trace: selected delta (K9 supersedes K5)

K9 · tide & storm D+2–D+9 · surge 1.1–1.8 m
reported (met service) · high · valid steps 8–36 ↓ supersedes (cross-lineage) K5 · tide & storm D+0–D+4 · now stale
validity steps 0–16 · scenario clock, never wall clock ↓ compiled_into tide & storm channels · world 7f3a…c91
stale_input on next compile ↓ scored_from flagged verdicts: P1·C2 ⚑ · P2·C1 ⚑ · P2·C2 ⚑
planner decides when to recompile — nothing recomputes silently

One object model, both ends of the seam: the J-2's write becomes the planner's flag with no document, no email, no re-brief.

ASSAY v0.2 wireframes · companion to assay-ui-design.md · all data from assay-vignette.md fixtures — identifiers frozen per vignette §8