A directory of who does what, a message transport with addressed envelopes, and a task ledger recording every unit of delegated work from creation to completion. A pure-C rewrite of FIPA-OS on AtomicDB — no Java, no external transport.
Nothing here is hard-wired. Step through the five stages and watch what lands in the database at each one.
An agent registers what it can DO, not just that it exists. Others search the directory by service and discover a capable partner at run time — nothing is wired together in advance.
add a new capability and the platform finds itDelivery is separated from content, exactly as the standard requires: who it was addressed to, who actually sent it, and when it was accepted for delivery — kept separately from the message itself.
delivery is provable, not assumedWhen an agent hands work to another, the task is recorded with its owner, its type, the conversation that spawned it, its inputs and its state — so no delegation disappears without an outcome.
every task has an owner and an endingThe register of every agent on the platform and its lifecycle state — initiated, active, suspended, retired.
who existsThe yellow pages. Agents publish the services they provide, and others search by service type to find them.
who can do whatAccepts a message, stamps an envelope with the delivery detail, and hands it to the recipient — each step recorded.
how it got thereEvery delegated unit of work, its parent conversation, its inputs and how it finished — the accountability trail.
what was actually doneFIPA is an international specification for how autonomous software should talk. Building to it rather than to a bespoke protocol means the vocabulary of a negotiation — propose, agree, refuse, not-understood — is defined and unambiguous.
So an auditor reading a conversation months later reads exactly what the participants meant, and a system built elsewhere to the same standard can join in.
Read from the running platform on live data.