Skip to content
Flowesome
Resources

Changelog

Progress, stated factually as it ships. This is the primary source for what actually changed.

  1. 2026-10-21

    protocol

    FxPay continuity design connects action, exposure and evidence

    The reviewed FxPay design direction brings useful, already-authorised continuation together with explicit capture and exposure limits. Capacity for lasting local duties and reusable evidence support this single direction. Counterexamples and a defined comparison framework deepen the design and make its intended value assessable. This is a reviewed design contribution within planned FxPay; product implementation, integrations and measured service results have their own qualification stages.

  2. 2026-10-21

    protocol

    Systemic M1 foundations selected for complete implementation

    In-depth design work connects states, evidence and obligations with lifetime resource accounting and usable causal explanations. The implementation mandate carries every necessary M1 foundation into complete code, actual callers and integrated verification, reusing work that already satisfies the requirement. Implementation, qualification and reception retain the complete milestone criteria. This mandate concerns M1 foundations, including those that may later support FxPay.

  3. 2026-10-21

    protocol

    Evidence-aware execution and independent comparison refined

    Internal SDK contracts preserve distinct execution outcomes and bound retained wire data. Independent comparison fixes the expected context before assessing a result. Targeted source work addresses repeated reconstruction, indexing, interpretation and encoding while preserving complete comparison semantics. The contribution is scoped to internal contracts and source work; public developer releases follow their own roadmap.

  4. 2026-10-21

    protocol

    Terminal evidence made more precise

    Private terminal-evidence preparation brings acquired facts, real errors, identity, publication eligibility and lifecycle events into a more precise account. Its documented component checks record 646 assertions with no failures, nine affected translation units compiled and a non-executable relocatable link. This component contribution feeds the broader integration and native runtime qualification path.

  5. 2026-10-21

    protocol

    Caller and state alignment strengthened

    A targeted source correction reinforces the relationship between the eligible caller, expected shared state and return observed in its parent context. The engineering work was checked through 59 finite controls: five synthetic acceptance cases and 54 expected refusals. Scope: source correction and synthetic fixtures, with acceptance cases ending before native effects.

  6. 2026-10-13

    portal

    Native capabilities and a clearer progress reading

    The portal adds the native-capabilities chapter and dated news, connects the Network menu to direction, local capabilities, evidence and next steps, and updates the roadmap and What exists today. APP, the RC3 plans and SCC have distinct explanations. Light frames, restrained status marks and vertical yellow direction bars replace repeated green ticks and large filled accent panels. The existing dossier collection, historical closures and their scoped evidence are retained.

  7. 2026-10-13

    protocol

    First native capabilities qualified locally

    The RC3 V1.1 implementation programme completed its available local engineering increment: original results recovered after tested interruptions, consented service work, a qualified numerical application and a separately qualified composition. The delivery is documented and reconstructible in its defined local profiles. Human observation, distinct formal acceptance acts and source-repository publication remain open. This is a local delivery milestone, not closure of the whole RC3 programme or a public network launch.

  8. 2026-10-02

    portal

    Products presented as products

    Each product page now opens with what the product is, who it is for, its status and what is available today, then its blueprint, why FxChain, and the FxChain capabilities it is built on, shared rather than owned. FxWallet is the wallet and financial application, FxTrade the trading platform, FxBank the programmable banking platform under research, FxPay the payments platform and merchant services, FxScan the exploration, verification and audit interface. No status changed, and nothing new is available.

  9. 2026-09-28

    protocol

    Sovereign Assurance & Attestation closed

    Sovereign Assurance & Attestation closed on the development line. The closing commit, 11c96351, was qualified locally (10,487 Rust tests, 195 Python tests, 170 of 170 official entries, the same result under two user identities), reviewed by a separate reviewer, and passed 50 of 50 hosted jobs before integration (run 36392880837) and after it (run 36399021626), each on its first attempt. The red runs of 26 and 27 September stay on the record. An internal closure, not an external audit; no network, token or service.

  10. 2026-09-28

    protocol

    Evidence snapshot moved to the assurance closure

    Public figures re-measured on the sealed development line at the assurance closure, verified on 28 September 2026: eras D0-D6 sealed (7), accepted crossings 372, conformance checks 50/50 green on the push run of the closing commit. The note that set aside the later amendments of the line as failing is withdrawn: the closure supersedes them, and their runs stay on the record. Reference: dev 11c96351.

  11. 2026-09-28

    portal

    News opens

    The newsroom opens with its first article, on the closure of Sovereign Assurance & Attestation. Each article carries its section and status, a standfirst, an illustration drawn from its own data, the key facts at a glance, the record of references it rests on, and what it does not establish. Articles are dated and in the Atom feed; a revision shows its own date.

  12. 2026-09-18

    portal

    Use cases, and an easier read

    A Use cases section lists five categories with their status and opens with one internal example measured on synthetic data; client references will be listed by category, each only with the client's written consent. Across the portal, running text is darker with shorter lines, key sentences stand as quotes, sequences read as numbered paths, and every dossier opens its short answer in its own box.

  13. 2026-09-07

    portal

    Dossiers: the Reference series, a glossary

    Every term the portal uses precisely, grouped by theme, each pointing to the dossier that develops it.

  14. 2026-09-07

    portal

    Dossiers: the Direction series

    Three planes, receipts, denials and capsules, the storage constitution, six axes, the authority algebra, the living node, the evidence algebra and contradiction escrow, and privacy by disclosure class. Direction, not capability: each opens with that note.

  15. 2026-09-07

    portal

    Dossiers: the Engineering discipline series

    The acceptance discipline, the evidence lab, sealed history and the replay domain: how the line advances, how a candidate is admitted, and how the reconstruction family was built and closed.

  16. 2026-09-07

    portal

    Dossiers: the Protocol series, eight organ dossiers

    FxWire, FxIntent, FxCore, FxCell, FxDAG, FxVM, FxState and FxBlock, each with a claim table (proven today, research, planned, reserved, not claimed), ASCII figures and a sources section. Linked from Technology and Foundations.

  17. 2026-09-07

    protocol

    Evidence snapshot moved to the era D6 reconstruction closure

    Public figures re-measured on the sealed development line at the closure merge of 2 August 2026: eras D0-D6 sealed (7), accepted crossings 372, conformance checks 48/48 green on the closure run. A later amendment of 21 August carries one failing check under assurance recovery and is not counted. Reference: merge d98d7364, crossing Q-372.

  18. 2026-09-07

    portal

    FxChain Foundations, the programmes page and a refreshed Technology page

    FxChain Foundations (four chapters: overview, architecture, evidence, comparison), the programmes page naming the three programmes, and a rebuilt Technology page with the eight organs, the transaction path and the anatomy table. Protocol status unchanged: foundations implemented locally, no public network.

  19. 2026-07-19

    portal

    Content engine online

    News, FAQ and changelog managed from the admin; public contact form storing submissions with rate limiting.

  20. 2026-07-19

    portal

    Core pages shipped

    Home, network overview, architecture, roadmap, products family including five product pages, technology, developers, institutions, about, contact and legal - every claim carrying an explicit status.

  21. 2026-07-19

    portal

    Design system applied

    Applied the Flowesome design system: a single token source for color, typography and surfaces, across light and dark themes.

  22. 2026-07-18

    portal

    Portal foundation online

    flowesome.com online over HTTPS behind access protection: Laravel with an Inertia React front and a Filament admin. Staging only - nothing public yet.

  23. 2026-07-16

    protocol

    Development line sealed through era D6

    FxChain eras D0-D6 sealed on the development line under deterministic conformance. Crossings at 360; conformance checks 36/36 green.