Architecture
Flowesome applications and integrations use FxChain capabilities. The eight-component pipeline below maps target responsibilities; it is not a trace of an executed transaction or an active network.
The organs of FxChain
Follow the canonical pipeline from external input to verifiable block results. Each dossier distinguishes the design from the narrower local profile.
FxWire
Receives external messages and produces an FxIntent.
FxIntent
Carries the user-facing action, constraints and authorization context.
FxCore
Normalizes an FxIntent into an FxCell under the applicable rules.
FxCell
Carries one internal causal execution unit and its declared dependencies.
FxDAG
Orders FxCell objects with deterministic local causality.
FxVM
Executes the ordered units under a defined deterministic profile.
FxState
Commits the state transitions established by the execution profile.
FxBlock
Packages verifiable block results; production finality remains future work.
Three principles of the architecture
Laws first
Native laws form the constitutional layer every mechanism must satisfy before it is allowed to exist.
Explicit authority boundaries
The design requires each capability to state its permitted and refused powers. Local typed boundaries and future portable refusal evidence have separate implementation scope.
Prior art confronted, never hidden
Known results are reused as known results - never as identity. Divergences are stated, not implied.