How to read this section
Concept pages explain the user-facing model. They intentionally avoid internal ADR detail and focus on what operators and builders need to understand.
Start with core concepts and relationships, then follow the implemented objects and contracts that make them reliable.
The value chain: describe → model → derive
One thread runs through every page below. Awaken Workforce turns domain knowledge into a typed substrate, and the process, automation, and governance you build on top are consequences of it — not features wired up per workflow.
- Describe the domain. Domain meaning lives in domain packs — declarative bundles of the objects, operations, and events your world has. The kernel itself is domain-neutral; a pack adds the semantics. (Plain, near-natural declaration is the authoring direction; today a pack is declarative YAML plus scripts.)
- It becomes an object model. The system models each thing as a typed
ResourceType— properties (including computed getters), actions (open_pr), events, and lifecycle hooks. Agents act on typed objects with operations, not a flat bag of tools. - Workflows and automation derive from it. Workflows route on structured output and reactions fire on typed events — never on free text. “Done” requires a declared terminal transition and any configured verification, not merely a model’s opinion.
One model, many uses: the same typed world drives workflows, automation, authorization, and audit — which is exactly why the type system can call every promise a consequence, checked once and true everywhere.
Four concept groups
| Group | Read in this order |
|---|---|
| Foundations | Core concepts and relationships → Issue-based workflows → object model |
| Work model | Issues → intake → Workflows → parts → Reactions |
| Resources and governance | Resource model → authorization and readiness → credentials → Connectors → Environments → Domain Packs |
| Execution boundary | Agents, WorkUnits, and Awaken Runs |
The type-system page is a cross-cutting explanation, not a second object inventory. Exact fields and enums belong to Reference and the generated OpenAPI contract.