Artificial Unit Lifecycle Governance

State can move. Authority must be earned again.

Okanase Systems governs the lifecycle of artificial units — AI agents, robots, autonomous machines and other systems that can act — through identity, authority, state, evidence, qualification, operation, intervention, change, inheritance and reauthorization.

ONE COMMERCIAL FRONT DOORASSESS → CONTROL → QUALIFY → OPERATE → CHANGE / INHERIT
Human-assist environmentA robotic unit working around people must have explicit authority, intervention and requalification boundaries.
If a system can act, Okanase treats it as an artificial unit.AI agent · robot · autonomous machine · commerce agent · mixed fleet
The inspection model

Identity → Authority → State → Evidence

Existing governance frameworks manage AI systems and organizational risk. Okanase governs the operating unit through authority, state, evidence, change, handoff, inheritance and reauthorization.

Identity

What is this unit, who owns or sponsors it, and how is it uniquely known?

Authority

Who granted permission, for what actions, within what limits, and for how long?

State

What configuration, memory, dependencies and operating context is it carrying?

Evidence

Can decisions, changes, actions and handoffs be reconstructed and defended?

01ASSESS

Discover identity, authority, state, dependencies and exposure.

02CONTROL

Bound permissions, ownership and intervention.

03QUALIFY

Prove fitness before operation.

04OPERATE

Maintain governed state and evidence.

05CHANGE / INHERIT

Move state safely and re-grant authority.

Field snapshots

Current-era artificial units in the real world.

Autonomous & uncrewed
Robotics
Machine commerce
Enterprise AI agents
Control architecture

Eight capabilities behind one front door.

01

Artificial Unit Registry

Identity, owner/sponsor, purpose, dependencies, environment and lifecycle state.

02

Authority Envelope

Authority source, permitted actions, tools, duration, limits and escalation.

03

State & Evidence Ledger

Configuration, provenance, decisions, actions and reconstructable evidence.

04

Qualification / Requalification Gate

Fitness before operation and after material change.

05

Change Control

Govern model, software, firmware, configuration and permission changes.

06

Intervention Control

Suspend, quarantine, revoke, fallback, human takeover and recovery.

07

Handoff & Inheritance Protocol

Transfer state without silently transferring authority.

08

Multi-Unit / Fleet Governance

Delegation, command hierarchy, mixed fleets and unit-to-unit evidence.

Governance-ready evidence

Built to map into the programs buyers already have.

One control library. Multiple mappings.
ISO/IEC 42001ISO/IEC 42005ISO/IEC 23894NIST AI RMFPrivacy / automated-decision dutiesApplicable AI obligations
Okanase assessments are designed to produce operational records that can support existing management, risk, privacy, oversight and conformity programs. Mapping does not imply third-party certification or legal compliance by itself.
Where it applies

One architecture. Different artificial units.

Enterprise AI Agents

Agent identity, tool authority, delegated actions, memory/state, audit and production change.

Robotics & Humanoids

Task qualification, calibration state, human handoff, maintenance and mixed fleets.

Autonomous & Uncrewed

Mission authority, operator control, fallback, transfer and operational evidence.

Machine Commerce

Agent identity, intent, delegated spending authority, limits, evidence and revocation.

Human-assist / care environments

When a robot works around vulnerable people, authority boundaries cannot be vague.

Mobility assistance, delivery, monitoring and staff support can all be useful. Okanase inspects what the unit may do, what state it carries, when a human must intervene, and what changes require requalification.

The front door

Artificial Unit Continuity & Inheritance Assessment

Find where authority, state or evidence can drift, disappear or move without proper reauthorization.

Identity & ownershipInventory the unit, sponsor, operator and dependencies.
Authority & action boundariesTrace who grants authority and where human approval must intervene.
State & reconstructabilityDetermine what state matters and whether actions can be reconstructed.
Qualification & failureAssess fitness, fallback, intervention and return-to-service controls.
Change, inheritance & reauthorizationFind what happens when the unit, software, operator or environment changes.
Control planPrioritize the controls to build with the buyer.
Assessment outputs

The assessment produces operating records — not a slide deck.

Each engagement is structured to leave the buyer with reconstructable objects that can be governed, reviewed and carried into existing assurance programs.

01Artificial Unit Record

Identity, owner/sponsor, purpose, dependencies, environment and lifecycle state.

02Authority Envelope

Authority source, permitted actions, tools, limits, duration and escalation boundaries.

03State & Evidence Record

Material state, provenance, decisions, actions, changes and reconstructable evidence.

04Qualification Decision

Fitness for the task and environment, including conditions for requalification.

05Intervention Path

Human takeover, suspension, quarantine, revocation, fallback and safe recovery.

06Inheritance / Reauthorization Record

What state may move, what authority must stop, and who independently grants it again.

Okanase doctrine
Artificial capability does not create human authority.

State may be inherited. Authority is not inherited automatically. Learning may improve capability; authority changes only through governance.

What authority drift looks like

One handoff. One permission that must not follow.

Illustrative reconstruction — not a client incident. Agent A finishes a workflow and Agent B inherits the operating state. The customer context can move. A $25,000 purchasing permission cannot silently move with it.

HANDOFF EVENT

Agent A → Agent B

State transferred: active workflow, customer context, transaction history and task position.

Attempted inherited authority: purchasing up to $25,000.

BLOCKED — independent reauthorization required
IDENTITYAgent B / receiving unit
AUTHORITYCustomer-service actions only
STATEWorkflow state inherited
EVIDENCETransfer log + authority check retained
RESULTSpend action quarantined until reauthorized
Named human accountability

The architecture has an accountable operator.

Okanase does not grant itself authority over a buyer's artificial units. The proper human or governance source in the operating environment does that. Okanase performs the inspection, makes the control gaps visible and helps build the controls.

NV
FOUNDER & SYSTEMS ARCHITECT

Nathan Vreyborg

More than 30 years in technology systems, training and operations. Okanase Systems is the operating home for the artificial-unit continuity and governance architecture.

Build with buyer

Start with the lifecycle problem you already have.

Assess the artificial unit. Identify the gap. Build only the controls the operating environment actually requires.