A validity rollup already proves upward to its base chain. FAEI asks what happens when verifiable evidence travels across systems, and the destination refuses to act until it checks.
A source event becomes evidence. The destination verifies it before a contract acts.
FAEI is a verification-first financial systems studio. The work starts at settlement, becomes programmable business infrastructure, then adds constrained software assistance without handing it the keys.
Settlement
A source system commits an event. A destination verifier checks the evidence before it authorizes a mint, release, payment, or other action. Relayers may deliver the proof, but they do not get to decide whether it is true.
Prover availability, finality, verifier code, custody, upgrades, and application logic still matter.
Business
Once evidence can authorize settlement, the same surface can gate treasury flows, exchanges, lending, or issuer logic. This is the commercial pivot: from a safer pipe to a programmable cross-system operating layer.
It does not create solvency, legal fungibility, truthful price feeds, sound economics, or compliance.
Assurance
A Shadow Agent is a future assurance role, not a trading bot. It may watch signed intent, identify drift, and draft a change. Invariants, independent review, human approval, and a timelock determine whether anything ships.
The agent holds no general signing key. Emergency powers, if any, must be narrow and pre-authorized.
Suwappu tests how people and agents ask for execution. Lattice tests parts of the trust, attestation, and data plane. They share a direction, not a claim of completed convergence.
APPLIED SYSTEMS / OPEN BETA
Suwappu's public interfaces run on today's rails.
Cross-chain execution products for people and software agents span chat, terminal, REST, SDK, and MCP. They aggregate multiple liquidity networks and support both managed-wallet and bring-your-own-key paths.
Suwappu is not proof-native settlement today. That makes it useful: routing, wallet policy, simulation, permissions, and agent access become observed operating requirements instead of presentation slides.
PROTOCOL LAB / RESEARCH
The reviewed Lattice repository contains prototype code and records testnet addresses; production assurance is not claimed.
The Lattice Transfer Protocol explores receiver-bound post-quantum envelopes, encrypted distributed availability, signed commitments, and on-chain anchors.
Its specific claim is a constant-size receiver handoff after encrypted shards have been distributed. Multi-node production operation, direct aggregate verification, and external code audit remain open work.
The useful business plan is smaller than the vision. Prove one rail, measure it, then decide what deserves to scale.
Its public products and machine interfaces create a near-term execution business. Modeled revenue surfaces include fees, subscriptions, metered organization access, referrals, and machine payments. This site makes no revenue or traction claim.
One controlled settlement corridor can be measured on latency, cost, availability, operational work, and reduced signer risk. It is a cleaner first proof than an issuer launch with legal and liquidity obligations.
Paid architecture, verifier and contract integration, enterprise support, usage-based settlement, and continuous assurance are plausible FAEI businesses. They remain design options until a pilot earns them.
Defensibility would come from verifier engineering, invariant tooling, operating data, application knowledge, test infrastructure, and credible chain, issuer, and auditor relationships.
No token economics, settlement pricing, network launch date, or sales motion is specified in the source material. None is invented here.
The point is to move truth out of a private signer set and into public evidence, then keep a plain ledger of everything evidence cannot settle.
| Surface | Public status | What the label means |
|---|---|---|
| Bridgeless Bridge | Architecture brief | A vendor-neutral design and business thesis. It is not a deployed FAEI settlement network. |
| Suwappu | Open beta | Public execution surfaces run on existing liquidity and interoperability providers. Formal third-party assurance remains roadmap work. |
| Lattice | Research prototype | The reviewed repository contains transfer, cryptography, storage, and contract components, plus records of testnet addresses. Production decentralization, direct verifier enforcement, and external audit remain open. |
| Shadow Agent | Forward design | A no-general-key, propose-only assurance role. No FAEI implementation is claimed. |
| Proof-gated corridor | Next experiment | One end-to-end pilot with explicit measurements, not a universal network promise. |
The June 2026 brief sets out the settlement pattern, shadow contracts, the Shadow Agent control model, and the risks that remain. It is explanatory and vendor-neutral.
