Representative Use Cases

Status: Live customer guide for Supply-Y Protocol 1.0. The catalog below is generated from six committed protocol scenario fixtures paired one-to-one with the six interactive demo scenarios; it is not a list of unverified marketing claims.

How to use this catalog

Choose the loop that is closest to one real cross-company decision. Compare the business problem, participant sequence, transport availability and acceptance criteria before discussing integration. Each loop links to the exact interactive scenario and its source fixture.

The scenarios are representative starting points. A customer pilot narrows one of them to named participants, an approved Skill, a specific decision window and an explicit disclosure boundary.

What stays the same across every loop

Every use case uses the same Protocol 1.0 envelope, identity binding, Package and Response lifecycle, signed policy evidence, recipient receipt, thread semantics and ciphertext-safe audit model. The scenario Skill changes the shared business meaning and allowed fields; it does not replace the protocol.

One Package uses one transport path. Native Mode stores one encrypted Package in Supply-Y. Catena-X Mode moves the Package through the participants' EDC data plane while Supply-Y stores references and audit evidence, not a duplicate payload.

From representative fixture to pilot

A passing fixture proves that the intended object shape and scenario rules are executable. It does not prove that a customer's data mapping, Agent, KMS, EDC connector or operating process is ready.

Start with fictional or sanitized data in the Protocol Playground, open the matching 3D loop, and then use Plan a Managed Pilot to define customer-specific responsibilities, stage gates, acceptance evidence and exit rules.

Six representative loops

Compare the business problem and first acceptance criteria at a glance. Expand any loop to inspect its complete participant sequence and success criteria, then open the exact 3D scenario or source fixture.