D5-S17 — The proof: two databases, two hosts, contention and offline

[The-Running-Dev]

Anyone deciding whether to adopt Platform can look at one CI run and see each of the nine capabilities pass or fail on its own — on both databases, with the offline deployment and the several-instances deployment actually exercised rather than assumed.

Done when

• S17.1 CI runs the operated scenarios against SQLite and against PostgreSQL, and reports each of the nine capabilities as a separately named result. Starting successfully is not one of them.
• S17.2 The contention scenarios — concurrent licence verification, concurrent organization creation, one invitation redeemed twice, and concurrent audit appends — run against PostgreSQL with at least two host instances.
• S17.3 The local host's scenarios run with outbound network unavailable, and the run fails if any outbound connection is attempted.
• S17.4 The operated proof uses at least two principals, two organizations and two tenants.
• S17.5 Nine mutation fixtures, one per capability, each violating a negative criterion from the brief's capability table, and CI fails against every one of them.
• S17.6 The local host's scenarios assert it has no package or project reference to Identity, Organizations, Billing or Licensing, requires no configuration or storage for them, and uses the system:local audit actor.

---

Agent instructions

Run /slice S17.

• Scope and criteria: design/30-slices.md § S17 @ d752008
• Signatures: design/20-contract.md
• Depends on: S16.
• Out of scope here: deploying or operating the sample — it is a CI proof, not an environment. Performance, throughput, latency and capacity measurement, and any comparison between the two database providers.

Stop conditions and procedure: .claude/commands/slice.md. Not restated here.