Skip to main content
Verify a customer, answer with scoped facts, and request a refund through reviewed business operations.

​
Business capabilities

ontology, authorization, operations, approvals, agents, external-inference

​
Dataset

Synthetic Zürich and Lyon customers, orders, tickets and refund policies. License: Repository license; fictional people and example.com contact addresses. Bound: 512 rows, 1048576 bytes.
  • Bijection support-desk authors; data/dataset.json contains the initial facts.

​
Journeys

​
Verify and restrict customer identity

Actor: Support customer. A store credential can read policy but has no customer authority.
  1. Ask for policy before verification. Expected: Only public policy is available.
  2. Verify the caller and start a scoped session. Expected: The session binds its verified customer and store.

​
Request and review refunds

Actor: Verified customer and store lead. The fixture includes eligible, large and ineligible refunds.
  1. Request eligible and ineligible refunds. Expected: Rules return explicit business outcomes.
  2. Have a store lead review the request. Expected: Only the authorized lead can decide.

​
Enforce identity at tool dispatch

Actor: Untrusted caller. An agent token must confer only the session’s closed authority.
  1. Try direct functions outside the session. Expected: Calls outside the session are refused.
  2. End the session and try its token again. Expected: Ended sessions confer no access.

​
Recipes

​
Source and evidence

Application: examples/support-desk/bijection. The example’s overview, walkthrough and adaptation guide live beside usecase.json. Catalog source digest: eff412043688412658434bfdb986b1159a46490d104aeeeb0bc3276ed557af53. This identifies example inputs; it is not a successful execution or a runtime build claim.