Stage 10 — Sovereign Capability Layer

Arcform Plugin Catalogue

Sovereign Capability Layer

Arcform Plugins are sovereign capability modules that extend the trust rail without altering its core guarantees. Each plugin binds to the Arcform transport layer, emits sovereign trust packets, and operates under the same non‑custodial, consensus‑attested, ledger‑anchored principles as the platform itself.

Plugins do not store identity.

Plugins do not issue identity.

Plugins do not evaluate identity.

Plugins provide movement, not possession.

What Plugins Are

Plugins are capability adaptors that allow Arcform to interface with external ecosystems while preserving:

Deterministic provenance

Dual‑node consensus

Jurisdictional routing

Ledger‑anchored evaluation logs

Event‑driven hybrid emission

Each plugin exposes a sovereign capability contract, defining:

Signal type

Envelope schema

Compliance mode

Routing path

Supervisory metadata

This keeps Arcform's trust spine intact while enabling ecosystem expansion.

Plugin Categories

Arcform supports six sovereign plugin categories:

Identity Signals

Authoritative identity sources

Verification Signals

External verification providers

Compliance Signals

Regulatory or supervisory feeds

Financial Signals

KYC / KYB / AML‑aligned trust signals

Operational Signals

Infrastructure health, zone integrity, telemetry

Ecosystem Signals

Cross‑provider interoperability modules

Each category is sovereign‑scoped and transport‑bound.

How Plugins Work

A plugin binds to Arcform through:

Capability Contract

Adaptor Binding

Permission Scope

Transport Routing

Consensus Validation

Ledger Anchoring

Supervisory Snapshot Emission

This ensures every plugin behaves like part of the trust rail — not an external service.

Plugin Category Descriptions

Each sovereign plugin category serves a distinct purpose within the trust rail. Expand each category below to understand its role, guarantees, and transport model.

Identity Signal Plugins

Identity Signal Plugins interface with authoritative identity sources — registries, providers, and custodial identity systems — without ever storing or evaluating identity content. They wrap incoming identity signals in provenance envelopes, apply dual‑node consensus, and emit sovereign trust packets that preserve origin integrity and jurisdictional context.

Purpose

Move identity safely across ecosystems.

Guarantee

Non‑custodial, provenance‑anchored, consensus‑attested.

Verification Signal Plugins

Verification Signal Plugins bind Arcform to external verification providers. They convert verification outcomes into deterministic trust packets with canonical checksums, divergence detection, and supervisory metadata. Arcform does not perform verification — it transports verified outcomes with cryptographic integrity.

Purpose

Transport verification results without altering them.

Guarantee

Deterministic reproducibility, dual‑evaluation consensus.

Compliance Signal Plugins

Compliance Signal Plugins integrate regulatory or supervisory feeds into the trust rail. They emit compliance posture signals, zone integrity evaluations, and supervisory snapshots — all ledger‑anchored and consensus‑attested. These plugins form the backbone of Arcform's continuous compliance telemetry.

Purpose

Provide regulators with real‑time, anchored compliance signals.

Guarantee

Event‑driven hybrid emission, anchored evaluation logs.

Financial Signal Plugins

Financial Signal Plugins interface with KYC, KYB, AML, sanctions, and financial trust ecosystems. They transform financial trust signals into sovereign packets with jurisdictional routing and supervisory clarity. Arcform does not evaluate financial risk — it transports verified financial trust signals.

Purpose

Move financial trust signals across regulated ecosystems.

Guarantee

Jurisdiction‑aware routing, supervisory‑readable metadata.

Operational Signal Plugins

Operational Signal Plugins monitor infrastructure health, zone integrity, orchestration consistency, and transport reliability. They emit telemetry signals on schedule, on degradation, on recovery, and on consensus failure — forming the event‑driven hybrid telemetry layer.

Purpose

Provide deterministic operational visibility.

Guarantee

Consensus‑attested telemetry, anchored operational logs.

Ecosystem Signal Plugins

Ecosystem Signal Plugins enable cross‑provider interoperability. They route trust packets between identity providers, wallets, verification services, and regulated ecosystems while preserving provenance, consensus, and supervisory clarity.

Purpose

Bind ecosystems together without creating custody or authority.

Guarantee

Sovereign routing, non‑evaluative transport, multi‑jurisdiction alignment.

Unified Category Declaration

Arcform Plugins extend the sovereign trust rail into identity, verification, compliance, financial, operational, and ecosystem domains — without storing, issuing, or evaluating identity.

Each plugin binds external systems to Arcform's deterministic trust spine through provenance envelopes, dual‑node consensus, ledger‑anchored evaluation logs, and event‑driven hybrid emission.

Plugins extend the rail — they never alter it.

Plugin Capability Contracts

These are not API docs. They are constitutional capability contracts — the rules that govern how each plugin binds to the trust rail.

Every contract begins with a Guided Link so you can expand it later. Each defines schema, provenance envelope, consensus requirements, routing path, supervisory metadata, anchoring policy, and emission triggers.

Identity Signal Capability Contract

Identity Capability Contract

Defines how authoritative identity signals enter the trust rail.

Contract Fields

origin_authority— registry or provider of the identity signal

identity_schema— canonical structure of the identity artefact

provenance_envelope— origin metadata + jurisdiction context

consensus_requirements— dual‑node checksum + divergence detection

routing_path— jurisdiction‑aware transport route

supervisory_metadata— regulator‑readable fields

emission_trigger— scheduled / event‑driven / consensus‑failure

ledger_anchor_policy— anchoring rules for identity signals

Guarantee

Identity is moved, not stored; transported, not evaluated.

Verification Signal Capability Contract

Verification Capability Contract

Defines how external verification outcomes are transformed into sovereign trust packets.

Contract Fields

verification_source— provider of the verification outcome

verification_outcome_schema— canonical structure of the result

checksum_policy— primary + secondary checksum rules

consensus_verdict— required consensus state for emission

envelope_integrity_rules— tamper‑proofing requirements

jurisdiction_routing— compliance‑aligned pathing

supervisory_snapshot_fields— regulator‑visible metadata

anchor_requirements— anchoring of verification outcomes

Guarantee

Verification is transported with integrity, never performed by Arcform.

Compliance Signal Capability Contract

Compliance Capability Contract

Defines how regulatory or supervisory signals enter Arcform's telemetry layer.

Contract Fields

compliance_mode— US_flexible / EU_strict / UK_standard

evaluation_schema— structure of compliance posture

telemetry_anchor_policy— anchoring of evaluation logs

consensus_requirements— dual‑evaluation + divergence detection

trigger_matrix— scheduled / degradation / recovery / consensus‑fail

supervisory_visibility_rules— regulator access guarantees

reporting_lag_policy— zero‑lag emission requirements

Guarantee

Compliance signals are consensus‑attested and ledger‑anchored.

Financial Signal Capability Contract

Financial Capability Contract

Defines how KYC, KYB, AML, sanctions, and financial trust signals are transported.

Contract Fields

financial_signal_schema— canonical structure of financial trust artefacts

risk_origin_authority— source of the financial trust signal

jurisdictional_constraints— routing rules for regulated ecosystems

consensus_requirements— dual‑node attestation

checksum_policy— canonical + secondary checksum

supervisory_metadata— regulator‑readable financial trust fields

anchor_policy— anchoring of financial trust packets

Guarantee

Financial trust signals move across ecosystems without custody or evaluation.

Operational Signal Capability Contract

Operational Capability Contract

Defines how infrastructure health, zone integrity, and orchestration consistency are emitted.

Contract Fields

operational_schema— structure of zone health + orchestration state

evaluation_rules— deterministic operational checks

consensus_requirements— dual‑evaluation + divergence detection

telemetry_anchor_policy— anchoring of operational logs

trigger_matrix— scheduled / degradation / recovery / consensus‑fail

supervisory_snapshot_fields— regulator‑visible operational metadata

routing_rules— jurisdiction‑aware operational packet paths

Guarantee

Operational telemetry is continuous, anchored, and consensus‑attested.

Ecosystem Signal Capability Contract

Ecosystem Capability Contract

Defines how Arcform binds external ecosystems together without creating custody.

Contract Fields

ecosystem_source— identity provider / wallet / verification service

interoperability_schema— canonical structure for cross‑ecosystem signals

provenance_envelope— origin + jurisdiction metadata

consensus_requirements— dual‑node attestation

routing_matrix— multi‑jurisdiction pathing rules

supervisory_metadata— regulator‑readable interoperability fields

anchor_policy— anchoring of ecosystem packets

Guarantee

Ecosystems interoperate without Arcform becoming an authority.

Unified Capability Contract Declaration

Every Arcform Plugin is bound by a sovereign capability contract that defines its schema, provenance envelope, consensus requirements, routing path, supervisory metadata, anchoring policy, and emission triggers.

These contracts ensure plugins extend the trust rail without altering its sovereignty, custody model, or constitutional guarantees.

Plugins extend the rail — they never alter it.

Plugin Developer Intro

A constitutional introduction for developers building sovereign capability modules on the Arcform trust rail.

This is not an API guide. It defines the mindset, responsibilities, and guarantees required to build plugins that extend — but never alter — the sovereign trust spine.

What Arcform Plugins Are

Arcform Plugins are sovereign capability modules that allow developers to connect external systems to the Arcform trust rail without ever taking custody of identity or trust content.

A plugin is not a microservice.

A plugin is not an integration.

A plugin is not an API wrapper.

A plugin is a capability adaptor that binds your system to Arcform's deterministic trust spine through:

provenance envelopes

dual‑node consensus

ledger‑anchored evaluation logs

event‑driven hybrid emission

jurisdiction‑aware routing

Plugins extend the rail — they never alter it.

The Developer Mindset

When building a plugin, you are not "adding features." You are defining a sovereign capability.

Your plugin must:

preserve origin integrity

preserve jurisdictional context

preserve supervisory visibility

preserve consensus attestation

preserve ledger anchoring

preserve non‑custodial architecture

Arcform does not store identity.

Arcform does not evaluate identity.

Arcform does not issue identity.

Your plugin must uphold these guarantees.

The Plugin Binding Model

Every plugin binds to Arcform through a capability contract.

This contract defines:

the signal schema

the provenance envelope

the consensus requirements

the routing path

the supervisory metadata

the anchoring policy

the emission triggers

This contract is constitutional — it governs how your plugin behaves inside the trust rail.

The Developer Workflow

Building a plugin follows a deterministic sequence:

Define Capability Contract

Describe the signal type, schema, provenance, consensus rules, and supervisory metadata.

Implement Adaptor Binding

Bind your system to Arcform's transport layer using the adaptor interface.

Emit Provenance Envelope

Wrap your signal in a sovereign envelope containing origin metadata and jurisdiction context.

Compute Dual‑Node Consensus

Generate primary and secondary checksums; detect divergence; produce consensus verdict.

Anchor Evaluation Logs

Anchor operational or compliance evaluations to the Arcform ledger.

Emit Sovereign Trust Packet

Emit the packet using scheduled, degradation, recovery, or consensus‑failure triggers.

Provide Supervisory Snapshot

Expose regulator‑readable metadata for auditability and reproducibility.

This workflow ensures your plugin behaves like part of the trust rail.

Developer Responsibilities

As a plugin developer, you are responsible for:

Signal integrity

Provenance correctness

Consensus computation

Checksum reproducibility

Jurisdiction routing

Anchoring evaluation logs

Emission trigger accuracy

Arcform handles transport, supervision, and ledger anchoring — you handle capability correctness.

Developer Guarantees

Your plugin must guarantee:

deterministic provenance

dual‑node consensus

divergence detection

ledger anchoring

supervisory clarity

non‑custodial architecture

jurisdiction‑aligned routing

event‑driven hybrid emission

These guarantees are not optional. They are sovereign.

Unified Developer Declaration

Arcform Plugins allow developers to bind external systems to the sovereign trust rail through capability contracts, provenance envelopes, dual‑node consensus, anchored evaluation logs, and event‑driven hybrid emission.

Developers do not store identity, evaluate identity, or issue identity. Developers extend the rail — they never alter it.

This is sovereign development.

Plugin Onboarding Checklist

Every plugin must complete nine sovereign steps before it becomes part of the trust rail. This checklist ensures capability contract integrity, consensus alignment, and supervisory completeness.

9 steps · 0 shortcuts · sovereign‑complete.

Capability Contract Definition

Define capability contract

Signal schema declared

Provenance envelope rules defined

Consensus requirements specified

Routing matrix declared

Anchoring policy defined

Supervisory metadata fields listed

Emission triggers defined

OUTCOMEPlugin has a constitutional definition.

Adaptor Binding Implementation

Implement adaptor binding

Input validation implemented

Envelope construction logic correct

Transport routing rules applied

Jurisdiction tagging correct

Non‑custodial architecture preserved

OUTCOMEPlugin can safely emit sovereign envelopes.

Provenance Envelope Construction

Construct provenance envelope

Origin authority included

Jurisdiction metadata included

Timestamp canonical

Envelope signature correct

No identity content stored

No identity content evaluated

OUTCOMEPlugin preserves origin integrity.

Consensus Computation

Compute consensus verdict

Primary checksum computed

Secondary checksum computed

Divergence detection implemented

Consensus verdict produced

Consensus failure triggers emission

OUTCOMEPlugin emits only consensus‑attested packets.

Anchoring Policy Enforcement

Anchor evaluation logs

Ledger anchor ID generated

Anchor reproducibility verified

Anchor metadata included in supervisory snapshot

Anchoring failure triggers emission

OUTCOMEPlugin produces immutable supervisory evidence.

Emission Trigger Matrix

Implement emission triggers

Scheduled emission

Degradation emission

Recovery emission

Consensus‑failure emission

Trigger metadata included in packet

OUTCOMEPlugin emits telemetry with zero reporting lag.

Supervisory Metadata Completion

Provide supervisory metadata

Consensus verdict

Anchor ID

Routing path

Jurisdiction tag

Trigger context

Envelope integrity status

OUTCOMEPlugin is supervisory‑readable.

Registry Registration

Capability contract stored

Consensus rules stored

Anchoring policy stored

Routing matrix stored

Supervisory metadata stored

Trigger matrix stored

OUTCOMEPlugin becomes part of the trust rail.

Sovereign Audit Pass

Run plugin audit

Capability contract integrity

Adaptor binding correctness

Provenance envelope compliance

Consensus requirements

Anchoring policy

Supervisory metadata completeness

OUTCOMEPlugin is sovereign‑complete.

Unified Onboarding Declaration

Every Arcform Plugin must pass capability contract definition, adaptor binding, provenance envelope construction, dual‑node consensus, ledger anchoring, event‑driven hybrid emission, supervisory metadata completion, registry registration, and sovereign audit.

This checklist ensures plugins extend the trust rail without altering its sovereignty, custody model, or constitutional guarantees.

Plugins extend the rail — onboarding preserves its sovereignty.

Plugin Registry Structure

The Plugin Registry is the authoritative index of all sovereign capability modules bound to Arcform.

It is not a database table.

It is not a list of plugins.

It is a sovereign ledger of capability contracts, provenance envelopes, consensus rules, and supervisory metadata.

The registry ensures:

deterministic discovery

supervisory visibility

provenance integrity

consensus alignment

routing correctness

anchoring completeness

This is the backbone of the plugin layer.

Registry Core Fields

Each plugin entry begins with a Guided Link.

capability_contractDefines the constitutional rules of the plugin.

provenance_envelopeOrigin authority + jurisdiction metadata.

consensus_rulesPrimary checksum, secondary checksum, divergence detection.

anchoring_policyRules for ledger anchoring of signals and evaluation logs.

routing_matrixJurisdiction‑aware transport paths.

supervisory_metadataFields exposed to regulators.

emission_triggersScheduled / degradation / recovery / consensus‑failure.

plugin_categoryIdentity / Verification / Compliance / Financial / Operational / Ecosystem.

These fields form the constitutional spine of each plugin.

Registry Structural Layers

The registry has three sovereign layers.

Layer 1Capability Layer

Stores:

capability contract

schema

envelope rules

consensus requirements

This is the plugin's constitution.

Layer 2Operational Layer

Stores:

emission triggers

anchoring policy

routing matrix

supervisory metadata

This is the plugin's behaviour.

Layer 3Supervisory Layer

Stores:

audit checks

divergence history

anchor IDs

consensus verdicts

last supervisory snapshot

This is the plugin's regulator‑facing truth.

Together, these layers make the registry supervisory‑complete.

Registry Indexing Model

The registry indexes plugins across five axes:

1.Category Axis

Identity / Verification / Compliance / Financial / Operational / Ecosystem

2.Jurisdiction Axis

US_flexible / EU_strict / UK_standard / Global

3.Consensus Axis

Achieved / Diverged / Single‑node / Failed

4.Anchoring Axis

Anchored / Not anchored / Anchor count / Anchor IDs

5.Trigger Axis

Scheduled / Degradation / Recovery / Consensus‑failure

This indexing model ensures deterministic discovery and supervisory clarity.

Registry Governance Rules

The registry enforces:

non‑custodial architecture

immutable anchoring

dual‑node consensus

provenance correctness

supervisory visibility

jurisdiction alignment

event‑driven hybrid emission

If a plugin violates any rule, it cannot be registered.

This prevents drift.

Unified Registry Declaration

The Arcform Plugin Registry is the sovereign ledger of capability contracts, provenance envelopes, consensus rules, anchoring policies, routing matrices, supervisory metadata, and emission triggers.

It ensures every plugin behaves like part of the trust rail — deterministic, reproducible, anchored, and supervisory‑readable.

Plugins extend the rail — the registry preserves its sovereignty.

Plugin Sovereign Audit — Stage 10.5

This audit has six layers, matching the six plugin categories. Each layer begins with a Guided Link so you can expand it later.

We check:

1.Capability Contract Integrity

2.Adaptor Binding Correctness

3.Provenance Envelope Compliance

4.Consensus Requirements

5.Anchoring Policy

6.Supervisory Metadata Completeness

This is the sovereign audit spine.

Identity Signal Plugins

Audit Checks

Contract defines origin authority

Provenance envelope includes jurisdiction

Consensus is dual‑node

Checksums reproducible

Anchoring policy defined

Supervisory metadata present

PASSIdentity plugins are fully sovereign‑aligned.

Verification Signal Plugins

Audit Checks

Verification outcome schema canonical

Consensus verdict required before emission

Divergence detection implemented

Envelope integrity rules defined

Anchoring required

Supervisory snapshot fields present

PASSVerification plugins meet all sovereign requirements.

Compliance Signal Plugins

Audit Checks

Compliance mode defined (US/EU/UK)

Evaluation schema canonical

Telemetry anchor policy present

Consensus dual‑evaluation

Trigger matrix complete

Supervisory visibility rules defined

Zero‑lag policy enforced

PASSCompliance plugins are sovereign‑corrected and telemetry‑aligned.

Financial Signal Plugins

Audit Checks

Financial trust schema canonical

Jurisdiction constraints defined

Consensus dual‑node

Checksums reproducible

Supervisory metadata present

Anchoring required

PASSFinancial plugins meet sovereign routing and supervisory clarity.

Operational Signal Plugins

Audit Checks

Operational schema defined

Evaluation rules deterministic

Consensus dual‑evaluation

Telemetry anchor policy present

Trigger matrix complete

Supervisory snapshot fields present

Routing rules defined

PASSOperational plugins are fully aligned with the corrected telemetry layer.

Ecosystem Signal Plugins

Audit Checks

Interoperability schema canonical

Provenance envelope correct

Consensus dual‑node

Routing matrix multi‑jurisdiction

Supervisory metadata present

Anchoring required

PASSEcosystem plugins preserve sovereignty and interoperability.

Unified Plugin Audit Verdict

All six plugin categories meet sovereign capability requirements, consensus rules, anchoring policies, supervisory metadata expectations, and non‑custodial architecture guarantees.

The plugin layer is now fully aligned with the trust spine, telemetry layer, regulator brief, sovereign identity statement, and plugin catalogue.

Arcform's plugin system is sovereign‑complete.

Why Plugins Exist

Plugins allow Arcform to integrate with:

Identity providers

Verification services

Registries

Compliance frameworks

Financial ecosystems

Operational telemetry sources

without ever taking custody of identity or trust content.

Plugins extend Arcform outward, not inward.

Unified Plugin Declaration

Arcform Plugins are sovereign capability modules that bind external ecosystems to the trust rail with deterministic provenance, dual‑node consensus, ledger‑anchored evaluation logs, and event‑driven hybrid emission.

They preserve Arcform's non‑custodial architecture while enabling regulated ecosystems to exchange trust safely, reproducibly, and transparently.

Plugins extend the rail — they never alter it.

Arcform Sovereign Systems · London, United Kingdom28 July 2026