SSlops Discuss pilot

Stevinn Route Cards

Route first. Hydrate only through the source.

Slops Route Cards turn an operational intent into coordinates, owner paths, safe next moves, and receipt requirements without exposing customer payloads, private memory, or internal runbooks.

Discuss managed pilot See a safe example
Coordinate-only Owner route Source-required hydration Receipt burden

A public-safe route card

This demo card uses placeholders. It shows the shape Slops can share in a coordination lane while keeping the underlying payload, memory, and source system private.

Demo route card

RC-DEMO-042

redacted coordination packet

Intent Prepare a safe change plan for a demo billing automation rule.
Coordinate class public.demo.billing-rule-coordinate
Owner/steward route Customer operations steward, approved change lane, source system owner confirms.
Hydration verdict Source-required. The card may identify the source path but must not copy payload values.
Receipt burden Approval receipt, source-check receipt, test evidence, and final verification receipt.
Next safe move Ask the named steward to open the approved source view and attach the required receipts.

What a card can say safely

Route Cards are designed for teams that need agents and operators to coordinate without turning private source systems into chat payloads.

Authorized path

Identify which source or steward is allowed to hydrate, mutate, approve, or verify the work.

Allowed move

Name the next action: ask owner, request access, open source first, run a check, or issue a receipt.

Receipt burden

Make the proof obligation explicit before work starts, so completion is not just a claim in prose.

The boundary is the product

Route cards identify authorized paths and receipts. They do not hydrate payloads, expose internal memory, reveal private runbooks, copy customer data, or claim that a receipt proves business correctness by itself.

01 / Intent

Start with the work request

Capture the operational intent without asking an agent to rummage through every system.

02 / Route

Find the lawful coordinate

Return admitted coordinates, owner/steward paths, access obstructions, and allowed next moves.

03 / Prove

Attach receipts after source work

Hydration and mutation happen through the owning source surface, then receipts prove the process trail.

Back to Proof Suite View Solutions