System Data Flow

Four delivery surfaces collapse through adapters into one core pipeline — every entry point runs the same execution path

System Data Flow Four delivery surfaces collapse through adapters into one core pipeline — every entry point runs the same execution path CLI · Click · External surfaces CLI Click HTTP Server · web delivery · External surfaces HTTP Server web delivery Lambda · handler · External surfaces Lambda handler TUI · Textual · External surfaces TUI Textual Adapter Layer · Cli · Http · Lambda · Tui · Architecture component Adapter Layer Cli · Http · Lambda · Tui FunctualizeApp · execute(job, **kwargs) · Core pipeline FunctualizeApp execute(job, **kwargs) Execution Engine · lifecycle owner · Core pipeline Execution Engine lifecycle owner ResolutionChain · layered config · Core pipeline ResolutionChain layered config MiddlewareChain · pre / post hooks · Core pipeline MiddlewareChain pre / post hooks Job Function · user code · Core pipeline Job Function user code JobResult · status, value, timing · Architecture component JobResult status, value, timing returned External surfaces Core pipeline Legend Frontend Backend Database Cloud Security Message bus

Why one pipeline

  • • Adapters translate transport only; they never reimplement execution
  • • A job behaves identically whether it was launched from the CLI, HTTP, Lambda or the TUI
  • • New delivery surfaces cost one adapter, not a second execution path