Keplaria

Case console

Public · read-only

The fleet is the crew and its rulebook: three departments, a coordinator that proposes, two specialist agents, and the five ERP commands they may issue. A payload is one supplier's case, carried through that fleet for months: onboarded, then renewals, a hold, a release. This page is the rulebook. The fleet runs one mission, the supplier-compliance workflow; the routing policy reads this same catalog, so the page cannot drift from what runs. The number in each cell is how many payloads actually exercised it: see the cases.

The fleet: departments, agents and commands. One payload: a supplier's case carried through the fleet across five lifecycle stops.

Fleet

fleet v1

← All cases

Out of scope is refused, and recorded
An event whose department proposes an agent outside its scope, or a command outside its scope, is refused and recorded. Never silently dropped, never silently allowed.
A department is asserted, not authenticated
The department label on an event comes from its producer. This is a policy-and-audit boundary, not a security boundary.
Authority ships with the deployment
Revoking a scope takes a deploy of a new catalog artifact, not a configuration flip.

What each department may do

Enforced scope

in scope out of scope n payloads that exercised the cell

Agents it may engage Commands it may issue
Department evidence compliance create_supplier attach_evidence request_renewal apply_hold clear_hold
procurement Onboards and maintains suppliers. Supplier onboarding inherently screens, so both specialist agents are in scope. 26 procurement may engage evidence; engaged in 26 listed cases 13 procurement may engage compliance; engaged in 13 listed cases 26 procurement may issue create_supplier; claimed in 26 listed cases, refused 0 times 26 procurement may issue attach_evidence; claimed in 26 listed cases, refused 0 times 13 procurement may issue request_renewal; claimed in 13 listed cases, refused 0 times 13 procurement may issue apply_hold; claimed in 13 listed cases, refused 0 times 13 procurement may issue clear_hold; claimed in 13 listed cases, refused 0 times
compliance Reviews screening outcomes and evidence provenance. May restrict a supplier; never originates one. 0 compliance may engage evidence; engaged in 0 listed cases 0 compliance may engage compliance; engaged in 0 listed cases compliance may not issue create_supplier; claimed in 0 listed cases, refused 0 times compliance may not issue attach_evidence; claimed in 0 listed cases, refused 0 times compliance may not issue request_renewal; claimed in 0 listed cases, refused 0 times 0 compliance may issue apply_hold; claimed in 0 listed cases, refused 0 times 0 compliance may issue clear_hold; claimed in 0 listed cases, refused 0 times
finance Consumes approved supplier records. Its events engage no agents and originate no supplier writes; a finance event proposing either is refused and recorded. finance may not engage evidence; engaged in 0 listed cases finance may not engage compliance; engaged in 0 listed cases finance may not issue create_supplier; claimed in 0 listed cases, refused 0 times finance may not issue attach_evidence; claimed in 0 listed cases, refused 0 times finance may not issue request_renewal; claimed in 0 listed cases, refused 0 times finance may not issue apply_hold; claimed in 0 listed cases, refused 0 times finance may not issue clear_hold; claimed in 0 listed cases, refused 0 times

Scroll the table sideways to reach every column. The department name stays in place.

Counts are over the 29 most recent cases the console lists, the same rows as the home page. A refusal is a command a case claimed outside its department's scope: recorded on the case, never queued.

Which agents an event engages

Routing

The coordinator proposes a route for every agentic event; policy validates that proposal against this table before anything runs.

Event typeAgents engagedCases
new_supplier_packet evidence·compliance 28
certificate_received evidence 13
renewal_due None clock event 14
evidence_overdue None clock event 14

Scroll the table sideways to reach the full route.

Counts are over the 29 most recent cases the console lists; a case that saw more than one event type counts once on each row.

An event type absent from this table is refused, as is a proposed agent the department may not engage. A clock event carries no document to reason about, so the catalog refuses to load if one routes to any agent.

The agents

Reference

coordinator

Fleet-wide v1 deployed

Proposes which specialist agents an event should engage; policy validates the proposal before anything runs.

Not a routing target: it runs for every agentic event and belongs to no department scope.

Reads
app.schemas:CanonicalEvent
Returns
app.schemas:RoutingDecision
Tools
none
Data
event_metadata
Owner
workflow-platform
Graded by
domain_case_pass, in spikes/domain_evals/evidence.json

evidence

Routable v1 deployed

Extracts grounded corporate fields from a submitted document; every value must resolve to a verbatim span or the case quarantines.

Reads
app.documents:RedactedDerivative
Returns
app.schemas:EvidenceResult
Tools
none
Data
document_derivative entity_identifiers
Owner
workflow-platform
Graded by
domain_case_pass, in spikes/domain_evals/evidence.json

compliance

Routable v1 deployed

Interprets sanctions-screening candidates; a deterministic check holds every referenced candidate id to the actual screen.

Reads
app.schemas:ScreeningResult
Returns
app.schemas:ComplianceAssessment
Tools
none
Data
screening_candidates entity_identifiers
Owner
workflow-platform
Graded by
domain_case_pass, in spikes/domain_evals/evidence.json