Ecosystems

One engine. Ecosystems plug in around it.

The decision engine holds no chain knowledge at all. Chains, intelligence sources and execution platforms sit behind contracts at the boundary, which is what makes adding one an implementation rather than a redesign.

The substitution model

Three replaceable edges, one unchanged decision.

A verdict produced on one chain and a verdict produced on another are the same kind of object, carrying the same reasoning structure — because the part that decides never knew which chain it was looking at.

Ecosystem adapterwhat a transaction means

Decoding, subject identity and structural discovery for one chain family. Everything it learns is expressed in canonical terms the engine already understands.

Intelligence providerwhat is known about a subject

Any source that can emit canonical coverage evidence — a compliance API, a sanctions feed, an internal list. The engine consumes the evidence contract, not the vendor.

Execution integrationwho actually signs

The wallet or custody platform on the far side of the decision. Argus forwards or withholds; it never holds a key.

TodayNo intelligence provider is connected on any ecosystem today, so no subject can be cleared anywhere yet. The boundary exists and is tested; the connection is milestone work.

Why it is built this way

Chain neutrality is enforced, not asserted.

Architecture tests fail the build if the core or the engine imports a chain SDK or reads a chain-specific field. The engine is exercised end to end against a fixture chain that does not exist — a chain with no SDK, no RPC and no reality — which is only possible if nothing in the decision path secretly depends on a real one.

Arc and Sui are implementations of that boundary. Neither is the identity of the product, and neither is load-bearing for the other.

What a new ecosystem needs

A decoder: Turning that chain's transaction shape into canonical terms, exactly or not at all.
Subject identity: A canonical way to name an address or object so evidence can attach to it.
Structural discovery: How provenance, control and dependency are expressed on that chain.
An endpoint contract: A transport the adapter is given rather than one it constructs, with chain identity verified before any response is trusted.

Current tracks

Two ecosystems, stated precisely.

Arc

Integration in progress

The EVM adapter, structural indexer and a Circle Wallets pre-sign gate are implemented and tested against injected transports and a fake execution port. No live Arc endpoint is configured and no Circle execution has been performed.

Arc implementation status →

Sui

Architecture ready

Graph intelligence and the adapter seams the Sui work depends on exist and are tested. Programmable-transaction-block pre-sign decoding is not implemented, so there is no complete Sui screening path.

Sui implementation status →

Proven offlineImplemented and covered by automated tests against fixtures or injected transports. No live endpoint involved.

Integration in progressImplemented against a fake or injected boundary; the real external integration has not been exercised.

Architecture readyThe contracts and seams exist and are tested; the specific implementation behind them has not been written.

PlannedScoped and sequenced, not yet built.

Not availableDoes not exist. No partial implementation to point at.

Other chains are not listed as integrations, because none is implemented.
The adapter contract is open by design — a new ecosystem does not require engine changes.

Evaluating Argus for an ecosystem?

If you are assessing pre-sign decision infrastructure for a chain, wallet platform or agent stack, the architecture and its current limits are available in detail.

Start a conversation Technical detail