AUTHORITY FOR AUTONOMOUS SYSTEMS

Intelligence can propose.
Authority decides.

Give AI bounded authority. Keep approval attached to the exact action. Preserve evidence through execution and recovery.

ICARUS 2.0 · Complete native test suite passed · 6 October 2026Inspect the evidence and tested scope

THE TECHNOLOGY, SIMPLY

Authority before action.Select a step to see how permission and evidence connect.

Grant limitsHuman authority
Propose an actionAgent
Check permissionICARUS
Act within limitsAllowed
Refuse the actionNot allowed
Record the resultEvidence

A responsible person grants bounded authority, including its purpose, scope and expiry.

Architecture illustration. Final receiver and recovery behaviour are tested for the selected local native profile; each receiving application requires integration and acceptance.

HOW ICARUS 2.0 WORKS

One contract from authority to the controlled result.

Authority reaches the last controlled step.

Bound the authority

Define identity, delegated scope, limits and expiry.

Approve the exact action

Bind the reviewed target, inputs, configuration and original deadline.

Check before publication

Reload current authority and refuse revoked, expired or changed work.

Recover with evidence

Retain the completed result. Block automatic repetition when the outcome is uncertain.

Bounded authority · exact approval · final receiver check · signed evidence

Implemented and tested in the selected native profile. The final-effect guarantee belongs to the owned local receiver; external applications require their own receiving integration.

Operating-environment footage

WHY IT MATTERS

Approval survives the handoff.

A reviewed request can wait in a queue, encounter an interruption or return as a retry. ICARUS 2.0 keeps its original inputs, configuration and authority deadline attached. The owned local receiver checks again before publication.

If that exact work already completed, a retry retrieves the retained result. If the outcome is uncertain, automatic repetition is blocked until authorized reconciliation. This gives the receiving application a defined recovery contract.

Demonstrated with one inert local publication. Payment providers, documents and other external effects require their own receiving integration and qualification.

ICARUS 2.0 / RECORDED NATIVE EVIDENCE

6 October 2026 · Internal engineering verification

A complete native run.
An installed demonstration.

1,183 / 1,183

Required primary test cases passed across 82 files. An additional 63 subtests passed, counted separately.

4 / 4

Native Wyrd CI gates passed. Source, environment, test outcomes, retained evidence and owned cleanup were checked.

182 / 182

Mapped audit and recovery cases passed. These are included within the 1,183 primary cases.

26 verified records

The isolated installed probe exercised 3 signed approvals and 1 inert local effect, with independently checked signed records.

Exact-input checks · original deadlines · revocation refusal · completed-result replay · uncertain-outcome recovery

Candidate 2.0.0rc1, source d660bb44. The installed probe used synthetic authority and published test keys. These figures concern the native candidate and do not rerun the separate 2 October workload shown on the Results page.

Download the native evidence summary

Tested scope and availability

Implemented and technically tested. The selected profile uses macOS arm64, local signed JSONL storage, admitted Ed25519 and offline OIDC/SCIM paths, a configured external checkpoint and the owned inert local receiver. It combines current authority checks, immutable approved inputs, preserved deadlines and signed recovery records. General callbacks and arbitrary external systems do not inherit its final-effect guarantee.

Signed qualification and release approval remain pending. Genuine independent signer, custody and approval evidence are still required. WUI adoption and its installed workflow are next. Linux, fleet-wide operation, hardware custody, physical safety and customer deployments require separate target-environment qualification. An external checkpoint file alone does not establish independent custody.

EARLIER RECORDED WORKLOADS

Explore the separate 2 October campaign