Patterns
Work patterns for governed software action.
These patterns explain how YAI connects cases, evidence, runtime operation, account-backed authorization and client surfaces without claiming finished case studies or production metrics.
Patterns
How the work model is framed publicly
| Pattern | What it means | What it avoids |
|---|---|---|
| Governed action | Actions are shaped by policy, reviewability and downstream consequence instead of being treated as disposable prompts. | Not a chat transcript model and not blind workflow firing without records. |
| Case-centered work | Work is anchored to case boundaries so history, evidence, clients and runtime operation have a durable context. | Not free-floating tasks, tabs or unbound threads as the sole unit of work. |
| Evidence and reviewability | Consequential automation should leave reviewable records so results can be inspected, challenged and continued later. | Not opaque autonomy and not logs without accountable context. |
| Local runtime with account-backed authorization | Runtime stays local-first while account posture and later authorization decisions shape what the runtime may do. | Not local operation as authority unto itself and not the website acting as runtime truth. |
| Clients as entry points | CLI, Loom and VS Code are ways into governed work, not substitutes for runtime, account or release authority. | Not client-owned identity, entitlement or release policy. |
| Serious automation beyond chat and logs | YAI is aimed at operational work where records, evidence, review and authorization matter as much as generation quality. | Not generic assistant chat, not workflow glue alone and not observability-only tooling. |
Practical boundary
What this route is not doing
This route does not publish fake customer stories, adoption metrics, incident timelines or production screenshots. It explains the work model at the level needed to understand why runtime, account, download, cases and evidence are separate surfaces.
Follow Interfaces for client entry points, Account for create-account-first entry and Status for the current public readiness boundary.