Pages
Index Three Cards v1
Source: c68 index-overview — Mark's manual three-card design, transcribed 2026-08-27
The landing as three cards — Inventory · Compliance · SLA Findings, Inventory first. The Inventory verdict is a visibility judgment (derived from coverage, never authored), per-class deltas carry the change axis, and the exceptions footer speaks intake language (shadow · unvetted), not findings language — the possibility-space seam applied: Inventory is the physical exam, Findings the diagnosis.
render state — the toggle flips only what visibility owns; Compliance and SLA read the same world in both
Inventory
Go ▶!Partial Visibility
34 of 39 installs monitored · 87%
Models6—
MCP Servers9+1 ▲
Tools / Skills41+3 ▲
Harnesses7—
Workspaces12+1 ▲
Machines14—
! 5 shadow installs — newest: Windsurf on chen-mba
! Unvetted MCP server: pg-tools
SLA Findings
Go ▶Findings
1
High
3
Med
Upcoming Remediation Deadlines
13Sep27 days from now
25Oct69 days from now
10Nov85 days from now
11Nov86 days from now
Composition notes
- Meridian numbers, not the design's. The manual design reads enterprise-scale (12k models · 637 MCP servers); this mock reads the shared staged world from report-fixtures.ts (6 · 9 · 41 · 7 adapters/39 installs · 12 · 14) so it stays composable with fleet-overview-v3 and the report pages.
- The verdict is derived, never authored. Full/Partial Visibility comes from monitored / installs (39/39 vs 34/39 · 87%). The toggle flips only what visibility owns — Compliance and SLA read the same world in both states, because full visibility and open findings coexist: the seam in action.
- The exceptions footer is intake language, not findings language. "5 shadow installs" and "unvetted pg-tools" come straight from inventoryReport.shadow / .mcpServers — the same facts SLA Findings adjudicates (F-1038 is pg-tools), told in Inventory's register: where, not by when.
- Figure tint follows the exceptions — a deliberate divergence. The manual design tints the Tools/Skills arm; the Meridian exceptions are shadow installs (install substrate → legs) and an unvetted MCP server (→ MCP arm), so those are the lit parts. The footer and the figure must name the same facts.
- Deltas are the one authored value. No per-class history exists in any fixture; the 7d deltas are hand-set (pg-tools's +1 matches its "added this week" note). Muted gray — change is judgment but not alarm.
- Placeholder figure. InventoryBodyFigure renders blocky stand-in shapes; Mark's SVG drops in over the same data-part ids and tone API. Connector lines simplified to leading ticks until the real art lands.
- Compliance shows the fixture's frameworks (SOC 2 Type II, NIST 800-53) rather than the design's five-row list (GDPR, EU AI Act) — Meridian has two instrumented frameworks; scores derive per framework the same way complianceScore() does (non-failing / total).
- SLA deadlines are fully derived: due = first seen + slaTargets[severity], "N days from now" against FIXTURE_NOW. In this world nothing is near breach (nearest: F-1041, 27d), so the design's red/amber deadline inks (≤7d · ≤14d) don't fire — the calm list is the honest render. Backend honesty: finding_states.sla_due is a never-written stub; this mock renders what it would carry (c79 territory).
- Analysis substrate: fleet-overview-v3 (four-report frame) · c68 inventory-card-possibility-space.md (the seam, the taxonomy, the tint ruling).