Slice 2 — Messages on the Spine

HITL verification · 2026-07-11 · PR #765 (stacked on #763) · preview refreshed at localhost:4180 · 10/10 tests verified independently

0 / 6 verified

What this slice is. The context fabric — VP as the layer that replaces the email/WhatsApp chase. Threads with your counterparties carry live VP objects, and the RBAC model reaches into every draft: what's Hidden for an audience physically can't ride along without a logged override. Sending context is granting access, and every grant is audited. The spine's "Chase →" links now land somewhere real.

The checklist

1 · Chase lands in the right thread. On the spine, click "Chase →" on the late Atlas Verde PO.TP-PO-3 · SPINE-2

You land in the Steinbach ↔ Atlas Verde thread — the chase names the counterparty, and the thread is about that PO.

2 · The thread knows the PO. Look at the thread header.TP-MSG-1

Live PO status badge (the 8-day slip) sits in the header — Messages and PO Tracker are one world, not two apps.

3 · The context rail guards your economics. In the Atlas Verde thread, find "landed cost" in the context rail.TP-MSG-2 · RBAC-5

Amber "Internal only" with the reason: sharing it with a producer exposes your buy price and margin. "Share anyway" demands a typed reason.

4 · Different audience, different guards. Open the Lindenhof (pharmacy) thread's rail.RBAC-3

Producer identity is the guarded item there — a pharmacy must never learn who you buy from. Same rail, audience-specific valves.

5 · Send = logged grant. Add a shareable item (e.g. the CoA) to a draft and send.SPINE-3

In-thread system row: "✓ [party] granted access to N sources" — the grant is now an audit-log fact, not a vibe.

6 · Three lenses still hold + clean console. Spot-check /demo/producer/messages; devtools open.LENS-2 · SPINE-7

Producer sees their side of the thread, no Steinbach economics anywhere; zero console errors.

Verdict: "slice 2 pass" → gates flip green with this page as evidence · "slice 2 redo: [what you saw]" → back to codex.

In flight: slice 3 (Connections & Entity Profiles — the 8×4 access matrix with cascade + approval-gated sensitive grants) building on codex now; slices 4 (Data queue) and 5 (demo DB + schema DDL) queued. · Clay ⇄ Claude · VP Completion Campaign