How to Build Agentic Software on Sunstone Atlas
Add agents. Keep control. A hands-on walkthrough of the building blocks, using a real production system as the worked example.
Most "agentic" software today is an LLM in a loop with tool access and a prompt that says please be careful. That works right up until the agent is allowed to do something that costs money — approve an expense, send a quote, create an order — and someone from Risk or Compliance asks the only question that matters: how do you know it stayed inside the rules, every time, and can you prove it?
If the honest answer is "we trust the prompt," the deployment stops there.
Sunstone Atlas takes a different position: agents should be able to act autonomously and the system should be able to prove, after the fact, that letting them act was safe. Not with a gateway that blocks everything interesting, but with a substrate where every capability, every fact, every procedure, and every participant is a signed, versioned artifact, and every decision at runtime — model judgment, deterministic rule, or human sign-off — is a cryptographically signed, replayable event on an append-only ledger. Conformance + signing + grounding: defendable by construction, not by assurance.