The realm
The import document names the realm claims-ops, version 0.2.0, and the commit its files came from. It gives the realm the namespace https://acme.example/realm/claims-ops#. Its types are Policyholder, Claim (joined to its Policyholder), and Payment (joined to its Claim), each with an identity property. Its producers are claimsByHolder (remote, the operation listClaims), paymentDetail (api, getPayment), paymentsLedger (sql, the datasource ledger), and riskScore (compute, a risk score computed from a claim's key). Its one API, claims-api, is an OpenAPI document with listClaims, getPayment, and orderPayment, and it lists operation-ids: [listClaims, getPayment]. Its apps are claims-desk and ledger-view. Its agent triage carries its prompt file inline.
namespace and commit, an app's reads, and an agent's promptText, which holds the agent's prompt file.What the import makes
claims-ops/riskScore come once a fleet package serves that kind.| Realm part | What reaches the group, once a person approves it |
|---|---|
the types Policyholder, Claim, Payment | three entry types, such as https://acme.example/realm/claims-ops#Claim |
claimsByHolder and paymentDetail | two AssetCards, listClaims and getPayment, from the REST connector |
paymentsLedger | one AssetCard for the query, from the SQL connector |
riskScore | the AgentCards of a fleet package that serves the agent kind claims-ops/riskScore, once such a package exists |
claims-api | the FlowManifest realm-claims-ops-claims-api: two code stages on the lane claims-api, listClaims and getPayment; orderPayment is not listed, and so not a stage |
the triage agent's prompt file | the prompt claims-ops/triage, in the group's prompt set |
claims-desk and ledger-view | two AppCards with origin.ref claims-ops/claims-desk and claims-ops/ledger-view, origin.version 0.2.0, and the links app://claims-ops/claims-desk and app://claims-ops/ledger-view; the first carries realm.reads Claim,Payment |
The fleet for this use case
After approval the claims fleet holds these cards:
| In the group | Published by |
|---|---|
two AssetCards, listClaims and getPayment | the REST connector |
one AssetCard, paymentsLedger | the SQL connector |
AgentCards for claims-ops/riskScore | a fleet package's agents, once a package serves the kind |
the FlowManifest realm-claims-ops-claims-api | the reconciler applies it, and its two stages run |
two AppCards | the issuer that ran the import |
the AgentCards of your Embabel agents | each agent's peer, through embabel-agentspaces |
An Embabel agent that maps its com.acme.claims package to the realm's namespace plans over these types. Each of those pieces has its own test, and no example runs the whole chain yet. The Embabel guide shows that agent from the Embabel side.