# Design-partner pilot

The included pilot runs one logical model service with three isolated tenants:

- **Northstar Support** — approved refund/escalation memory and a disclosure
  boundary.
- **Meridian Operations** — signed line telemetry, an operator-confirmation
  policy, and exact compute.
- **Atlas Research** — evidence language, negative-result preservation, and
  exact compute.

These are fictional scenarios, not customer claims.

## Pilot success criteria

1. Zero cross-tenant memory, card, or receipt reads under concurrent load.
2. Every response includes the exact ordered card-stack digest.
3. Policy-blocked requests never reach the backend.
4. Compatible requests batch; incompatible stacks do not.
5. A signed package change produces a new stack digest and can be rolled back.
6. The same workload runs through the evidence, Transformers, and vLLM backends
   with capability differences reported rather than silently ignored.
7. The customer records a measurable improvement over its current prompt/RAG/
   adapter path in at least one of cost, latency, operational safety, or rollout
   time.

## External partner boundary

No organization should be described as a design partner until it has agreed to
the pilot and supplied a success criterion. The repository provides a
design-partner-ready bundle; it does not fabricate traction.

