Platform Foundations — floor (id/idempotency/correlation convention, keyless CI floor, legacy-quarantine registry)

At a glance

Goals

Lay the cross-cutting floor every later item builds on: one ID/idempotency/correlation convention, a no-secrets deterministic CI target, and the legacy-route quarantine registry + CI guard that blocks P&C exit if any production path bypasses a P-contract.

Spec document

P9-platform-foundations → · source ↗

Implementation — what to build

Checklist

• ✓ ID/idempotency/correlation convention (operation/request/correlation/causation + key scope/format/replay)
• ✓ Keyless CI floor: no-secrets target running P1 fixtures + P5 direct-write/idempotency + P6 RLS/leakage + P7 mock
• ✓ Legacy-quarantine registry encoding the D32 table + CI guard that blocks P&C exit on a bypass

Gates & testing

• ○ P9 Platform Foundations: app/edge API envelope + DTO boundary, ID/idempotency/correlation convention, cross-version compatibility registry, keyless CI floor, and the legacy-route quarantine registry that blocks P&C exit on any contract bypass.
  CODE TEST

Requirements

No linked requirements.

Verify (done when)

ID/idempotency/correlation convention (operation_id/request_id/correlation_id/causation_id + key scope/format/replay) consumed by P5/P8; keyless CI floor runs P1 fixtures + P5 direct-write/idempotency + P6 RLS/leakage structural + P7 mock/current-tool tests with no secrets; legacy-quarantine registry encodes the D32 classification + a CI guard that fails P&C exit on a detected bypass. Per P9 spec + D32.

Cost triggers

No paid API / infra spend triggered by this item.

Status & editing

done   Sprint: P&C Wave 1: Foundations

Edit status / sprint on the ★ Live Board → — changes are logged live with who / when / why.

Human-in-the-loop

No human tasks linked.

Findings

• Per D33 the invocation style is the server/edge gateway; the API/DTO half is WI-069 (Wave 4, after G12+P6).
• The keyless CI floor is the TroveSnap structural-floor equivalent the gap analysis (G15) called for.
• A test I wrote caught a real bug: base36 timestamps without zero-padding don’t sort lexicographically ("rs">"1jk") — fixed with padStart(9).
• Resolved the WI-010↔WI-068 coordination: floor IDs are a gateway wrapper (D33), so P1 needs no schema change.
• CI floor KEYLESS list auto-extends as P5/P6/P7 ship keyless suites.

Concerns

None recorded yet.

Risks

None recorded yet.

Tech debt

None recorded yet.

Tools used

• Write — packages/platform/src/ids.mjs (ID/idempotency/correlation convention)
• Write — packages/platform/quarantine/registry.json + scripts/check-quarantine.mjs (D32 guard)
• Write — packages/platform/scripts/ci-floor.mjs (keyless CI floor) + test/*.test.mjs
• Bash — npm test (13 pass) + npm run ci:floor (PASS, runs scan-contracts + platform + quarantine)

Files & artifacts

• new packages/platform/src/ids.mjs — convention: IDs + context + idempotency
• new packages/platform/CONVENTION.md — the documented convention (P1/P5/P7/P8 consume)
• new packages/platform/quarantine/registry.json — D32 legacy-quarantine registry
• new packages/platform/scripts/check-quarantine.mjs — exit-gate guard (D31)
• new packages/platform/scripts/ci-floor.mjs — keyless CI floor (G15)
• new packages/platform/test/ids.test.mjs — + quarantine.test.mjs
• new packages/platform/package.json

Update log