Kraton / start with a task
Useful work, without the unnecessary handover.
Choose a familiar job. See what can stay on your machine, what access it really needs, and where the example stops.
Four source-backed scenarios
Start with the part that matters to you.
These are real examples in the Kraton codebase, not hosted services or promises of finished products.
01 / Personal scheduling
Find time without handing over your calendar.
Find open slots from the availability you choose to share.
Explore this scenario02 / Document checks
Check invoice math before it moves on.
Validate totals and line items with a bounded local calculation.
Explore this scenario03 / AI tool access
Give an assistant one narrow job.
Let an assistant request a calendar action without granting broad device access.
Explore this scenario04 / Streaming data
Redact card-like numbers as data passes through.
Mask payment-card-shaped number sequences without loading a whole stream at once.
Explore this scenarioTrust is a boundary, not a badge.
When you want the internals, they are here.
Every scenario links to the format, runtime, or research page behind it. No terminal command needed to understand the idea.
Each scenario is grounded in code and its stated limits.See what is implemented