ARCHITECTURE / AUTHORITY MODEL

The system topology follows the work.

UX → CAPELLA → SFC → GOVERN → A4LAYER → SAP → OBSERVATORY. Every role has a boundary.

SFC 0.13.1 architecture reconciled

The detailed release identity and source-tree hash remain available with the load-on-demand topology.

AUTHORITATIVE BASELINE

INTERACTIVE AUTHORITY EXPLORER

Inspect ownership before detail.

Start with the operating contract, then load the complete diagram only when its full topology is needed.

LAYER 01 / 6

CAPELLA AFEP

Product shell

Coordinates operator workflows, status, approvals, delivery surfaces and evidence continuity.

AUTHORITY BOUNDARYCoordinates the system without replacing downstream authorities.

AUTHORITATIVE ARCHITECTURE · SFC 0.13.1

Full topology, loaded on demand.

This clean CAPELLA-authored SVG is bound to release SFC-0.13.1-20260907T000000Z-8c522b7be71f and source-tree SHA256 8c522b7be71f9709b779d204ada93f66ed85734268ae9eaeccb40addbe4b81ba.

LOAD ON DEMAND · SFC 0.13.1

Open the authoritative architecture when you need it.

The detailed SVG is intentionally excluded from the landing page and does not download until requested.

TWO PRODUCT FLOWS

Related, but not falsely unified.

CAPELLA contains an Agentic Runs path and a governed FullStack delivery path. Both are real; current evidence does not yet provide one native correlation envelope across every layer.

AGENTIC RUNS

User → Runs UI → dispatch → durable record → role-scoped TaskGraph → telemetry

Proves activity and execution observability. It does not yet prove outcome-changing effectiveness.

FULLSTACK DELIVERY

User → CAPELLA → SFC → Govern → A4Layer → SAP → Observatory

Proves the bounded managed RAP create path with explicit authority separation.

See the correlation roadmap

“SAP remains the final runtime and authorization authority.”

CAPELLA engineering contract