Architecture ​
This page is the current architecture map for TPF internals.
Use public Design/Develop/Deploy docs for application usage. Use this page when changing framework internals, compiler behavior, runtime ownership, or portability seams.
Current Architecture Reading Path ​
| Area | Start here |
|---|---|
| Build-time compiler phases, IR, bindings, renderers | Annotation Processor |
| Generated artifacts and module ownership | Pipeline Compilation |
| Runtime layout vs build topology | Runtime Layouts |
| Queue-async durable execution | Queue-Async Runtime |
| Queue-async immutable segment/boundary model | Immutable Segment And Boundary Model |
| Await and callback admission | Await Boundaries and Await Runtime Setup |
| Checkpoint handoff | Checkpoint Handoff |
| Brokered runtime boundaries | Brokered Runtime Boundaries |
| Runtime portability and Spring status | Runtime Core Decoupling and Spring Support Status |
Current Control-Plane Shape ​
The current durable direction is a queue-driven async control plane:
- generated ingress accepts work over the configured transport,
- execution state is persisted,
- work is dispatched,
- a worker claims a lease,
- one transition runs,
- state is committed,
- terminal state is exposed through status/result APIs or failures move to the configured DLQ.
This is not a full event-sourced runtime in the current milestone. The target direction is described in Immutable Segment And Boundary Model: immutable segment and boundary facts first, with stores maintaining projections for efficient lookup.
Legacy Reference ​
The older broad architecture overview is preserved at Architecture Reference. Treat it as background, not as the canonical reading path.