Learn Cayu
Follow these worked guides in order. Each has runnable code or a released executable fixture, commands to run it, and assertions that establish its result. Use the setup specified by each guide.
The tool, structured-output and support fixtures run without model-provider credentials. The first-project guide distinguishes those deterministic checks from a later live-model run.
1. Build and inspect a first project
Section titled “1. Build and inspect a first project”Generate an application with cayu new. Run inspection, the strict check, tests and a scripted eval before configuring a provider.
Try it: Keep the generated factory inert at import time. Explain which checks run without provider credentials and which later run measures live-model behavior.
2. Implement and test one tool
Section titled “2. Implement and test one tool”Run the complete downloadable lookup tool. Follow the schema, effect declaration, context and returned result through the implementation and assertions.
Try it: Change the fixture’s lookup result and update its assertion. Identify the separate policy check needed before a protected tool can execute.
3. Repair a structured result
Section titled “3. Repair a structured result”Run the complete structured-output example. Its scripted provider produces an invalid attempt and a corrected result, so you can observe validation and repair.
Try it: Inspect both attempts and the successful structured result. Explain why a tool-strategy result can succeed without final answer text.
4. Resume an approval-gated service job
Section titled “4. Resume an approval-gated service job”Run the released support fixture one command per process. Clarify the request, record an exact approval, deliver the receipt and verify the domain state.
Try it: Try approve and deny in separate fixture directories. Repeat receipt delivery and confirm that approval permits one replacement while denial permits none. Explain which evidence belongs to Cayu and which belongs to the domain service.
Continue into the runtime
Section titled “Continue into the runtime”After the worked path, study sessions, authority, tasks and workers and recovery. Use the API reference for exact contracts.
The dining walkthrough shows a larger public application through real code excerpts. It has its own older Cayu git pin, separate from these release-matched guides.