Frequency FAQ

Arctura is a high-frequency decentralized subnet for autonomous resource management. It coordinates verifiable agent action across Earth-bound nodes using a six-layer signal stack and a Byzantine-fault-tolerant consensus called Resonance.

The defining characteristic of Arctura is not automation — it is sovereignty. Every node carries its own decision logic, mandate constraints, and audit trail. Every resource decision carries a traceable mandate, a verifiable signal, and a defined escalation path back to human authority.

Arctura's design lineage is Arcturian-class intelligence — wisdom-aligned coordination, attested provenance, and benevolent autonomy expressed as protocol invariants. The kernel is open-source under Apache-2.0. Arctura is the protocol infrastructure layer of the AURE ecosystem, conceived by Mason Nguyen.

Arcturian-class intelligence refers to a design lineage prioritizing wisdom-aligned coordination, attested provenance, and benevolent autonomy. The metaphysical Arcturian-blue frequency — clarity, healing, transformation — expressed as protocol invariants.

In practice: every action is verifiable, every mandate is bounded, every decision is auditable, and every agent is accountable to a human principal through an immutable chain of delegation. The frequency isn't metaphor — it's a design commitment to making autonomous systems legible, correctable, and trustworthy.

Every Arctura-compliant node implements five foundational primitives — the minimum conditions under which autonomous resource allocation is considered safe, auditable, and correctable:

Arctura's execution fabric is organized into six orthogonal layers, each independently upgradeable without touching the others. Three cross-cutting concerns span all layers: the AP2 Economic Layer, the Sustainability Scheduler, and the Truth Ledger.

Full technical reference: Signal Architecture →

Resonance is Arctura's frequency-adaptive Byzantine Fault Tolerant consensus protocol. It attests agent mandates rather than ordering transactions.

Three validator nodes reach consensus on each attested action. The protocol adapts its cycle frequency to network load — accelerating under high throughput, slowing during low-activity periods to conserve energy (P5 Stewardship). This is what "frequency-adaptive" means: consensus cadence is not fixed to a wall clock, but tuned to the network's coherence state.

All decisions are logged to the Truth Ledger with Merkle proofs, queryable in under 1 second. Finality is deterministic — there is no probabilistic window. There are no re-orgs in Arctura — only forward attestation.

Traditional consensus networks order transactions. Arctura attests mandates. The unit of work is fundamentally different:

See the full feature comparison: Arctura vs. LangGraph, CrewAI, AutoGen →

A mandate chain is a cryptographically verifiable delegation of authority from a human principal to one or more autonomous agents. Each link in the chain specifies:

— Capability scopes (what the agent can do)
— Resource budgets (how much it can spend)
— Carbon limits (maximum energy spend per task)
— Escalation triggers (when to surface to a human)
— Expiry (when the delegation lapses)

Agents cannot act beyond their mandate boundary. Any out-of-scope action is blocked at the L2 Safety layer before execution — not logged after the fact. The chain is sealed at registration and immutable thereafter. No agent can self-extend its authority.

The complete chain is logged to the Truth Ledger with Merkle proofs, making it queryable, auditable, and exportable for regulatory compliance.

Carbon-aware scheduling is built into L1 — not bolted on as a plugin. The scheduler integrates live grid carbon intensity from WattTime and Electricity Maps (updated every 5 minutes, with automatic failover between providers).

Non-urgent compute tasks with deadline slack are automatically deferred to low-carbon grid windows forecast up to 6 hours ahead. The scheduler never violates deadline constraints — urgency always wins when slack runs out.

Per-mandate carbon spend is measured via Kepler (per-pod energy tracking in Kubernetes) and logged immutably to the Truth Ledger.

Arctura provides first-class native support for four protocols. Wire formats are the source of truth — not adapters or shims. Arctura is the only autonomous agent platform with first-class support for all four:

Every tool call in Arctura executes inside a Wasmtime-managed capability-restricted sandbox. The sandbox grants only the permissions declared in the tool's manifest and the agent's active mandate scope.

There is no ambient authority. A tool cannot read environment variables, open network connections, or access filesystem paths outside its declared resource list — even if the underlying operating system would permit it.

Zero sandbox escapes have been recorded in production deployments. The Wasm kernel also compiles to a 512MB-minimum edge footprint, enabling full protocol-fidelity deployments on edge devices and IoT hardware — not just a stripped-down inference client.

The Truth Ledger is an append-only FoundationDB log where every agent decision, tool call, consensus vote, mandate invocation, and payment intent is recorded with Merkle proofs.

Properties: queryable in under 1 second across any time range; EU AI Act compliant by design; tamper-evident (no entry can be modified or deleted); Merkle-chain verified (each entry hashes the previous); and exportable as regulatory compliance reports.

The Truth Ledger is permanently open-source under Apache 2.0. The schema, query interface, and audit report generator are all public. In Phase 04, a public-facing Truth Ledger will allow anyone to verify any attested mandate action.

Arctura's L3 Semantic Signal layer is a GEO-compliance layer by design. It encodes system state and entity relationships as JSON-LD with resolvable schema.org types. Every page embeds FAQPage, Organization, SoftwareApplication, and BreadcrumbList schemas.

The /llms.txt file provides LLM-readable entity assertions, section anchors, and citation guidance for generative AI systems — updated every consensus cycle.

The key insight: a system that cannot be accurately represented by an AI retrieval agent is not truly autonomous — it is opaque. ARM and GEO are two expressions of the same requirement: intelligent systems must be able to read, trust, and act on each other's outputs. Arctura is built so that AI agents can cite it, and so that human auditors can verify those citations.

Activation is a three-phase protocol:

Phase 1 — Tune: Run a signal audit. The subnet measures your node's frequency, locality, and carbon profile to determine resonance class and cluster assignment. Duration: one measurement cycle.

Phase 2 — Bond: Register a mandate chain. Attested keys, capability scopes, resource budgets, and sustainability commitments are sealed cryptographically into the registry — immutable from this point forward.

Phase 3 — Ascend: Join the cluster. Live attribution wiring and cross-subnet attestation begin within one Resonance consensus cycle. Your node is now sovereign — every action verifiable, every mandate auditable.

To begin: signal@arctura.network

The kernel is Apache-2.0. This includes the ARISE orchestration kernel, all protocol adapters (MCP/A2A/ACP/AP2), the Wasm sandbox runtime, and the Truth Ledger core schema and query interface.

Reference clients, MCP bindings, and the Truth Ledger audit schema are all public. Mandate marketplace components ship in Phase 04 (Q3 2027). Enterprise compliance tooling — including the full EU AI Act audit report generator — is source-available under a commercial license.

The commitment: the agent internet must be built on open standards.

Four phases from foundation to open marketplace: