PRODUCTS

Blockchain infrastructure deforms under agentic load. Invarians tells agents where nominal is — through two factual primitives. No prescription. The agent owns execution policy.

Boundary — what Invarians is and is not

Invarians certifies what the infrastructure is at the moment of query. It does not prescribe execution decisions, recommend strategies, or encode risk tolerance. Both primitives below are factual outputs grounded in measurement. The agent owns the execution policy.

01 Proof of Execution Context (PoEC)

Primitive 1

Proof of Execution Context

A cryptographically signed, timestamped snapshot of infrastructure state at the moment of the query — capturing L1 structural regime, L2 rollup regime, and bridge state simultaneously. HMAC-SHA256 signed. Message integrity independently verifiable via the /verify endpoint. This is what the infrastructure is at a given instant.

Signature

HMAC-SHA256 signed.
Verifiable via /verify endpoint.

Expiry

1 hour from timestamp.
Expired attestations remain verifiable — integrity check still valid.

Audit use

Can be stored in agent decision log as proof of infrastructure conditions at the moment of execution.

L1 payload

Structural regime SxDx for the L1 chain at query time.

L2 payload

Rollup regime SxDx for the L2 chain at query time.

Bridge payload

Bridge state BS1 or BS2 — nominal or congested.

API Endpoints

Method	Endpoint	Description
GET	`/attestation/{chain}`	PoEC for a single L1 chain — regime, timestamp, signature.
GET	`/attestation/l2/{chain}`	PoEC for a single L2 rollup — rollup regime, timestamp, signature.
GET	`/attestation/execution-context?from={l1}&to={l2}`	Full cross-chain PoEC — L1 regime, L2 regime, bridge state, and signature in a single response.

Key Response Fields

l1_regime L1 structural regime at query time — one of S1D1 · S1D2 · S2D1 · S2D2.

l2_regime L2 rollup regime at query time — one of S1D1 · S1D2 (S2D1 · S2D2 pending Phase D).

bridge_state Bridge operational state — BS1 (nominal) or BS2 (congested).

proof_of_execution_context HMAC-SHA256 signature over the payload. Verifiable independently via /verify.

API integration → Measurement methodology →

What this primitive is

The PoEC records the state of infrastructure at a specific moment. It does not evaluate that state against a policy. It does not say "proceed" or "wait". It says: at this timestamp, the infrastructure was in this configuration, and that statement is cryptographically anchored.

02 Pattern Reference

Primitive 2

Pattern Reference

The reference mapping of execution contexts to documented historical events. An execution context is a specific combination of L1 regime, L2 regime, and bridge state. For each of the 32 possible contexts, the Pattern Reference records which events occurred historically when that context was active — frequency data and event record, anchored to the historical record where available. Not prescriptive. Frequencies are calibrated from historical backtest and recomputed as new observations accumulate — the reference evolves with the data, not fixed.

4 L1 regimes

× 4 L2 regimes

× 2 bridge states

possible contexts

What the reference contains

Each of the 32 execution contexts is a distinct, non-overlapping combination of infrastructure dimensions. For each context, the Pattern Reference shows: which historical events were documented under that context, observed frequency relative to total history, and the event record anchored to public on-chain data. Contexts with no historical observation are listed as unanchored.

Structure

L1 regime × L2 regime × bridge state — 32 distinct combinations fully enumerated.

Anchoring

Each pattern tied to documented historical record where available. Unanchored patterns are identified as such.

What it is not

Not a recommendation engine. Frequency data and event record only. No implied action.

Full Pattern Reference → Measurement methodology →

What this primitive is

The Pattern Reference tells an agent what has historically occurred in each execution context. It is a factual record — frequency and event documentation. It does not encode a policy. The agent reads the pattern for the current PoEC and applies its own thresholds, risk tolerance, and fallback logic.

03 How the Two Primitives Compose

The PoEC identifies the current execution context. The Pattern Reference provides the historical record for that context. Together they give the agent a factual, verifiable basis for its own execution policy. Neither primitive contains that policy.

Step 1 — Query the PoEC

Call /attestation/execution-context. Receive the current L1 regime, L2 regime, bridge state, and signed proof. Store in decision log if required.

Step 2 — Look up the Pattern

The regime combination from the PoEC maps to one of the 32 execution contexts in the Pattern Reference. Read the historical frequency and event record for that context.

Step 3 — Apply policy

The agent applies its own execution policy to the factual inputs. Invarians does not participate in this step.

Verifiability

At any point, the PoEC signature can be independently verified via /verify. Expired attestations remain verifiable — the signed payload is the proof.

The boundary — restated

Invarians provides two factual outputs: what the infrastructure is right now, and what has historically occurred in that configuration. Execution decisions — whether to proceed, pause, reroute, or wait — are the agent's. This boundary is architectural and intentional. The agent owns the execution policy.

API integration and authentication → Foundations — measurement methodology → Pattern Reference →