TPFGo Roadmap ​
TPFGo explores how typed checkpoint pipelines can model business progress without turning domain decisions into rollback orchestration.
This page is the current roadmap front door. The older detailed notebook is archived at Roadmap Archive.
Current Direction ​
- Model business progress as typed checkpoints.
- Keep unhappy business paths explicit instead of encoding them as operational failures.
- Preserve backpressure when pipelines are chained synchronously.
- Treat durable queue/HA delivery as a separate compatibility epic from synchronous business correctness.
- Keep transport-contract parity visible across REST, gRPC, LOCAL, and protobuf-over-HTTP paths, while treating
FUNCTIONas a platform mode that generates function entry points and provider-specific handlers.
Current Reading Path ​
| Need | Page |
|---|---|
| DDD and boundary alignment | DDD Alignment |
| Application design tradeoffs | Design Spectrum |
| Example implementation notes | TPFGo Example |
| User-facing checkpoint boundary | Checkpoint Handoff |
| Public state model | State Model |
Open Work ​
- Clarify which checkpoint concepts belong in Design, Deploy, and Evolve.
- Keep durable checkpoint handoff documentation tied to current runtime support.
- Avoid presenting speculative TPFGo patterns as general TPF guidance until examples and tests prove them.