Institutions

Institutional discipline, made provable

TradFi asks you to trust institutions; DeFi asks you to trust code. FxChain is built so you can verify both the powers and the refusals. That conversation starts now - the services come later, staged.

Start a conversation See where it lands in your stack

Audiences

Built with your constraints in mind

Financial institutions

Rails designed for institutional discipline: provable refusals, auditable state, no legal fiction about what the chain can and cannot do.

Keep executed, finalised, delivered, legal and complete as five facts your auditor can read.

Payment providers

A staged path toward payment surfaces (FxPay) with explicit authority boundaries at every step.

Replace the pending state and the support inbox with receipts, denials and a declared dispute grammar.

Markets and trading

Market infrastructure (FxTrade) built above a foundation where ordering, conflicts and fills are provable objects.

Order, fill and settle as separate evidence; conflicts explicit, never buried in sequencing.

Treasuries

Programmable finance (FxBank) explored in stages: sandbox first, regulated partners next, never a claimed license before it exists.

Give an agent a mandate, not a key: scope, amount, time - and a portable refusal when evidence is missing.

Enterprise

Integration paths that inherit the protocol discipline: what is not proven is not promised to your stack either.

Integrate a discipline, not a dialect: one grammar of authority, evidence and refusal across your stack.

Two scenarios

What the discipline changes, on two familiar cases

Design scenarios, not services: they show what the protocol is built to establish and what it refuses to compress. No amounts, no dates - the shape of the record.

Tokenised delivery versus payment

A securities leg and a cash leg move against each other. The usual answer is one word: settled.

FxChain keeps five facts apart and seals each of them: executed on the protocol, finalised by consensus, delivered on the external rail, legally effective, economically complete. A trade can be executed and finalised while the cash leg on a bank rail is still pending and the legal effect still unconfirmed - and the record says exactly that, instead of a single flag. Missing evidence is recorded as missing, never as false.

Executed on the protocol: yes
Finalised by consensus: yes
Delivered on the external rail: pending
Legally effective: unconfirmed
Economically complete: not yet

An agent under mandate

An AI agent holds a key to a treasury. The key says nothing about what it may do.

Under FxChain the agent acts under a declared mandate - bounded in scope, amount and time - that is checked before anything executes. When the mandate is exhausted, the key is still valid and the authority is gone. When the evidence a claim needs is missing, the refusal is sealed as an artefact the institution can carry to its auditor: what was declined, at which boundary, for which reason.

Key valid: yes
Mandate in scope: no - exhausted
Outcome: refused before execution
Refusal: sealed, reasoned, portable
Money moved: none

Both scenarios describe the direction of the architecture programme (research) and the receipts, denials and mandates the organs are designed to produce. No settlement, custody or agent service is offered today.

Where it lands in your stack

What breaks today, and what stays apart here

No other axis of the institutional stack is left out, and every row maps to a mechanism with a stated status. Nine systems every institution runs, the problem each one produces every week, and the answer FxChain is built to give - one grammar of authority, evidence, refusal and settlement truth across the whole stack, not a product per problem.

Payment hub and rail gateways

What breaks today

Payments sit in "pending" for hours; confirmations do not match; reconciliation breaks are settled by e-mail and screenshots.

What stays apart here

The settlement truth vector: executed, finalised, delivered on the rail, legally effective, economically complete - five facts, each with its evidence, and missing evidence recorded as missing, never as false.

Direction (research)Receipts, denials and capsules

Treasury and TMS automation

What breaks today

API keys carry standing authority; bots and agents act without a bounded mandate; entitlements sprawl faster than reviews.

What stays apart here

A key is not a mandate. Authority is a capability with scope, amount and time that can only narrow; an exhausted mandate leaves a valid key with no power, and a refusal sealed for the auditor.

Proven mechanism, direction for the deskThe authority algebra

Custody and securities settlement

What breaks today

A "settled" flag hides a cash leg still pending on a bank rail and a legal effect nobody has confirmed.

What stays apart here

Delivery versus payment kept as separate facts, sealed separately, with the external rail an external claim bound by reconciliation rather than assumed.

Direction (research)FxBlock

Finance operations and reconciliation

What breaks today

Evidence is scattered across ten systems; disputes are argued from logs nobody sealed; the reason for a refusal is lost or over-disclosed.

What stays apart here

Receipts of what execution observed; denials with a public reason class and claimant-scoped detail; a refusal that travels to the auditor with its rule, its missing evidence class and its remediation path.

Proven mechanism, direction for the deskReceipts, denials and capsules

Compliance and screening

What breaks today

Legal judgement is coded into transaction systems; audit trails are reconstructed after the fact; nobody can say why a rule was active at a given moment.

What stays apart here

A compliance determination is an external claim with a source, an epoch, a disclosure class and a revocation; the protocol verifies its presence and binding, never performs legal judgement; bitemporal lineage answers "why was rule R active at coordinate C".

Direction (research)Privacy by disclosure class

Internal control and change management

What breaks today

Nobody can prove which software version ran, under which controls, with which evidence - a green pipeline is taken for a proof.

What stays apart here

The acceptance discipline, practised on every crossing: falsifiers, negative controls, hostile review; and the Sovereign Assurance & Attestation programme (SAA) to make the version, its controls and its evidence verifiable.

Practised on the lineThe acceptance discipline

Risk, limits and collateral

What breaks today

Risk scores silently become authority; a better score unlocks more; incomparable models are averaged into one number.

What stays apart here

Risk is attributed evidence that may constrain exercise, never expand a grant; integer tiers, not floating-point formulas in consensus; incomparable dimensions stay incomparable; every change of power carries its duty.

Direction (research)The authority algebra

Data platforms and regulatory reporting

What breaks today

Warehouses and dashboards are treated as sources of truth; views drift from the ledger; nobody can rebuild a report from first principles.

What stays apart here

Canonical truth and projections are different species: every view is reconstructible and non-authoritative by type; state itself is a projection over sealed evidence, and a preserved history can be rebuilt through two independent paths.

Proven mechanism, direction for the deskThe replay domain

Incident management and audit

What breaks today

Incidents are closed by a ticket; the same failure returns; history is rewritten to fit the current system.

What stays apart here

Every material incident becomes a reproducer, a negative control and a permanent regression vector with a signed law disposition; sealed history is never rewritten - a correction is a new artifact.

Practised on the lineThe evidence algebra

Why this is a system, not a feature list

The nine answers above are the same four objects seen from nine desks: a capability that can only narrow, evidence judged before anything computes, a refusal sealed as a result, and settlement kept as five facts. That is what makes the coverage complete and transverse - and it is why a mechanism proven in one row is already the mechanism the next row needs.

Statuses are stated per row. What is proven today is proven on the local development line; what is direction is research in the architecture programme. No service operates, and no row above is an offer.

By question

How this differs, asked the way a risk committee asks it

Not a vendor table. Six questions an institution puts to any ledger, the answer most systems give, and the answer FxChain is built to give - each with its status.

Question	Common practice	FxChain	Status
Is settlement one word or five facts?	One flag - "settled" - covering execution, finality, delivery, legal effect and completion at once.	Five facts kept apart and sealed separately; missing evidence recorded as missing, never as false.	Direction (research)
Is a refusal an error or a result?	An error code, unlogged or overwritten, with the reason lost or exposed in full.	A typed result: public reason class, claimant-scoped detail, sealed past the admissibility threshold.	Proven today, locally
Is authority a role or a capability?	Roles and admin keys: authority by status, with no scope, expiry or provenance to narrow.	Capabilities only: scoped, expiring, revocable, with provenance; composition can only narrow.	Proven today, locally
Is finality a number or a function?	A block count or a probability, the same for a coffee and a bond.	Declared planes derived from the effects a claim declares, each with its own window and caps.	Direction (research)
Is state a substance or a projection?	A stored ledger that is the truth, with proofs derived from it afterwards.	A projection over sealed evidence; any cache is non-authoritative by type; the core stays small.	Direction (research)
Does the history ever get rewritten?	Migrations, re-orgs and hot fixes that edit what was recorded.	Never. A correction is a new artifact; sealed bytes stay frozen, and the refusals stay in the record.	Proven today, locally

The systems the architecture programme reads as frames of reference - public chains, permissioned ledgers and messaging rails - are named in its sources, not characterised here. The organ-level version of this table is on Technology.

Boundaries

What we will not tell you

An institutional relationship starts with the limits stated plainly.

Flowesome holds no banking license and operates no live financial service today.
No custody, no accounts, no payments are offered on any surface.
There is no token and no investment product of any kind.
Engagement today means design conversations and staged partnerships - in writing, with explicit boundaries.

Dedicated pages per audience (compliance, treasury, infrastructure) ship in a later phase, each under the same discipline.

Partner with us - in writing, with boundaries.

Reach info@flowesome.com with your use case; we answer with what is provable today and what is staged for tomorrow.

Contact The roadmap