The Pipeline Framework

Appearance

TPFGo Reference (TPF-Inspired) ​

This guide is a lightweight index for the TPFGo reference implementation, focused on checkpoint pipelines, immutable state progression, and workflow semantics.

Current completion scope:

  • The TPFGo completion scope covers the SYNC-path business/workflow and the transport-contract scope.
  • Queue/HA delivery (QUEUE_ASYNC, durable providers) is tracked in a separate epic and is not a TPFGo merge blocker.

  1. TPF and DDD Alignment

  2. Application Design Spectrum

  3. Roadmap (Pessimist's Notebook)

  4. Observer/Tap Contract (Diagnostics-First)

What this reference is aiming for ​

  • Checkpoint pipelines that produce stable, consistent states.
  • Explicit workflow composition without hidden branching behavior.
  • Operational clarity (errors, retries, and handoffs are visible and intentional).
  • Adoption-friendly paths (including slower JSON pipelines later).

Core terms used in this guide ​

  • Connector: the runtime handoff boundary between pipelines/contexts. In TPF v1 the runtime boundary is enabled by a first-class framework model: YAML declaration, build-time validation, and generated startup wiring. Bridge remains the compatibility label for manual application beans that replace that generated Connector lifecycle. Responsibilities:
    • idempotency/dedup
    • backpressure policy
    • retry/failure routing
    • lineage continuity
  • Tap: a non-primary observer branch attached to step output.
    • Checkpoint observer: observes stable, persisted outputs.
    • Mid-step tap: observes transient outputs with weaker persistence/durability guarantees.

If you are new to the conversation, start with the DDD alignment guide, then the design spectrum, then the Observer and Tap Contract guide, and finish with the roadmap.