Architecture, assurance and governed operations

The assurance and attestation programme, born from the internal acceptance arc, develops the mechanisms that bind a software version to its controls, its evidence and the conditions of its qualification. Its envisaged product evolution keeps the admission decision in the hands of each organisation.

SAA aims to make verifiable the identity of a software version, the controls applied to it and the evidence that supports its qualification.

SAA establishes the evidence; the operator keeps the decision.

Assurance

technical confidence supported by controls and evidence

Attestation

a statement attributed to an issuer about a precise subject and policy

Sovereign

the organisation keeps control of its trust policy and of its admission decision

The Mission Control programme covers governed execution, the tracking of transitions and the verifiable custody of operational evidence. It aims to make responsibilities and outcomes explicit, without confusing observation, authority and action.

What matters is the scope of an operation, its steps, its responsibilities, its outcomes and the evidence that is kept.

Mission Control lets you follow an operation and verify what actually happened.

Governed operations

an operation runs inside a declared scope, with named responsibilities and recorded steps

Evidence custody

the material that allows the operation to be verified is preserved, not merely logged

The architecture and protocol programme, referenced V1.2-RC3, organises FxChain's target architecture, interfaces and roadmap. It distinguishes capabilities already demonstrated, designs proposed and future developments subject to validation. Producing the plan authorises no implementation by itself.

Within it, the envisaged governance capability is the Sovereign Change Core (SCC): a small core of typed authority, subject, obligation, observation, gate, witness, verdict and transition-receipt objects - who may change what, and under which conditions. Its antecedents are practised today as the acceptance discipline; the core itself has not been started, and by its own genesis law it cannot authorise its own birth.

This programme defines how the capabilities of FxChain must fit together, and in which stages they may be implemented and validated.

Target architecture

the shape the capabilities must take - shared kernel, planes and typed contracts - stated as laws before any code

Roadmap

ordered stages, each with its own validation, none activated by the plan alone

Sovereign Change Core (SCC)

Its antecedents - the acceptance discipline and the evidence lab - are practised today; the compact typed core that compresses them is planned, not built