Examples
See how intent reads before any code is written.
Each example is a self-contained sketch. Read it top to bottom, that is the point. They are illustrative drafts, not runnable programs.
A complete mission
The canonical CreateInvoice mission: a goal, its inputs and outputs, the guarantees that must always hold, forbidden behavior, targets, and how it is verified.
1Mission CreateInvoice23Goal4 Generate an invoice from approved orders56Requires7 Customer8 ApprovedOrders910Input11 customer: Customer12 orders: List<Order>1314Output15 invoice: Invoice1617Guarantees18 invoice.total is never negative19 duplicate invoices are not created20 every invoice is auditable2122Never23 create invoice for unapproved order24 expose payment token in logs2526Target27 TypeScript28 Python29 DotNet3031Verify32 unit tests33 duplicate prevention test34 audit trail test35 security scanThree layers
One mission, three levels of precision.
The same ResetPassword mission, written from beginner-friendly human intent down to compiler-ready executable intent.
Human Intent
Readable and structured. Anyone on the team, or an AI agent, can follow it on first read.
1Mission ResetPassword23Goal4 Let a user securely reset their password56Requires7 verified email8 reset token910Guarantees11 token expires after 15 minutes12 token can only be used once13 password is never loggedTyped Intent
A precise engineering mode with semantic types and explicit constraints.
1Mission ResetPassword23Input4 email: Email5 token: ResetToken6 newPassword: Secret78Output9 result: PasswordResetResult1011Constraints12 token.ttl <= 15 minutes13 password.minLength >= 121415Never16 log(newPassword)17 return tokenExecutable Intent
Compiler-ready mode that names a target, its implementation choices, and the checks to run.
1Mission ResetPassword23Target DotNet45Implementation6 use ASP.NET Core7 use EntityFramework8 use BCrypt910Verify11 test token expiration12 test one time use13 test password hash stored14 test raw password not loggedBeyond a single function
Intent for whole systems.
Intent is architecture aware. Services, APIs, events, and tests are all first-class, so the meaning of a system lives in one place.
Architecture as code
Intent understands services: what they own, consume, and publish, their data store, and who owns them.
1Service Billing23Owns4 Invoice5 PaymentAttempt67Consumes8 OrderApproved910Publishes11 InvoiceCreated1213Database14 Postgres1516Owner17 Finance Platform TeamAPI intent
Method, path, required permissions, inputs, outputs, and the errors an endpoint can return.
1API CreateInvoice23Method4 POST56Path7 /invoices89Requires10 authenticated user11 permission invoice:create1213Input14 CreateInvoiceRequest1516Output17 InvoiceResponse1819Errors20 400 InvalidOrder21 401 Unauthorized22 409 DuplicateInvoiceEvent intent
Who publishes an event, who consumes it, its payload, and the guarantees it must uphold.
1Event InvoiceCreated23PublishedBy4 BillingService56ConsumedBy7 NotificationService8 ReportingService910Payload11 invoiceId: InvoiceId12 customerId: CustomerId13 total: Money1415Guarantees16 event is idempotent17 event contains no payment secretsBehavior-first tests
Given, When, Then. Tests describe behavior in the same language as the intent they verify.
1Test DuplicateInvoicePrevention23Given4 approved order already invoiced56When7 CreateInvoice runs again89Then10 no duplicate invoice is created11 existing invoice is returnedWant to try writing intent?
The playground is a preview where you can sketch missions today. Execution and compilation are coming later.