Identity fragments
People, machines, objects and places appear differently across sensors, models and operational systems.
THE CONTEXT OPERATING SYSTEM FOR SAFE, EXPLAINABLE AUTONOMY
The context
beneath autonomy.
Octeryx OS is one modular context product for people, software, devices and autonomous machines. Kasa is its primary care profile. Film is one isolated adjacent profile. Both operate from a shared, governed view of what matters now.
Active R&D · Accepted architecture and deterministic repository proof
People and machines can perceive and act. Octeryx OS gives them persistent context, governed memory and evidence for action.
THE PROBLEM
Autonomous systems have data.
They rarely have continuity.
Each robot, sensor, model and operational system sees a fragment. The result is repeated identity resolution, stale state, isolated decisions and limited evidence for why an action was taken.
Memory resets
Observations are stored, but confidence, validity and change over time are rarely preserved as usable operational context.
Agents act locally
Robots and software act from the snapshot available to one device, model or subsystem.
Decisions are hard to reconstruct
The chain from signal to context, policy and action is difficult to audit.
THE VISION
Autonomous systems
that remember.
The operational context is the durable asset: a continuously evolving model of identity, history, environment, routines, permissions, capabilities and interactions.
Hardware can change. Models can change. Profiles can change. The context required for safe, coherent action should persist, with confidence, validity and evidence attached.
New robot→Context remains
New environment→Context remains
New operator→Context remains
ONE SET · MANY ACTORS
Coordination starts
with shared context.
Crew, talent, cameras, robots, lighting and virtual environments each see a fragment. Dependable work needs a current, governed account they can share.
HOW IT WORKS
From signal to governed action.
A single path connects perception, identity, context, policy, coordination and evidence.
-
01
Perceive and normalize
Receive and normalize governed observations from people, robots, sensors, systems and environments.
-
02
Resolve
Makemake Onboard resolves candidates, evidence and ambiguity before unsafe identity use.
-
03
Contextualise
ECP Onboard compiles the right context and evaluates policy, confidence, validity and source trust.
-
04
Coordinate and act
Octeryx routes an authorized instruction, handover, prompt or bounded action to the appropriate actor.
-
05
Commit and explain
CongDB Onboard commits state, provenance, receipts and evidence to PostgreSQL for reconstruction.
This sequence describes the target architecture and synthetic proof path. It is not a claim of production deployment, certified operation or unsupervised autonomous decision-making.
THE ARCHITECTURE
One coherent stack.
Built around provenance.
Built from Panamorphix-derived Onboard concepts inside one Octeryx product. Designed to sit above onboard control, navigation and hardware safety systems.
OPERATING ENVIRONMENT
Robots · Humans · Sensors · Systems · Tools · Spaces
Humanoid robots, mobile platforms, cameras, wearables, smart environments, industrial equipment and software agents.
OCTERYX OS
Context runtime and coordination layer
Inbound normalisation · Source trust · Actor contracts · Policy routing · Handovers · Proactive dispatch
ECP ONBOARD · INSIDE OCTERYX
Context and policy
Context materialisation · Policy evaluation · Confidence weighting · Temporal interpretation · Decision traces
MAKEMAKE ONBOARD · INSIDE OCTERYX
Identity and entity resolution
Identity matching · Graph-aware co-resolution · Confidence bands · Review and correction workflows
CONGDB ONBOARD · INSIDE OCTERYX
PostgreSQL context and evidence substrate
Deterministic · Probabilistic · Hybrid truth lanes · Decay · Signed provenance · Append-oriented evidence
CONTINUITY IN PRACTICE
Context should survive
the handover.
Across operators, robots, models and environments, the operational record should remain coherent, governed and ready for the next actor.
CORE CAPABILITIES
Seven runtime surfaces.
One operational context.
Identity
Resolve people, robots, devices, objects and places before context is committed.
Memory
Represent facts, inference and evolving patterns with time and confidence attached.
Context
Serve the right slice of operational context to the right actor at the right moment.
Policy
Govern what each actor can know or do, under which authority, with an explicit decision record.
Communication
Normalise inbound events and deliver structured, actor-appropriate outputs.
Audit
Reconstruct context writes, policy decisions, inference, identity resolution and dispatch.
Coordination
Keep multiple robots, people, systems and devices coherent around the same task and environment.
TRUST BY DESIGN
Governed autonomy starts below the application.
Octeryx OS is being designed for physical environments where safety, data minimisation, explainability, policy and operational resilience must shape the runtime from day one.
Provenance-first
Evidence is part of the context model, not an afterthought added to an application.
Policy-gated
Context delivery and action routing are designed to pass through governed, auditable policy evaluation.
Validity-aware
Facts and inferences can carry review windows, confidence and temporal decay.
Profile-separated
Kasa and Film rules, vocabularies, data and interfaces specialize the shared core without forking it.
THE BUILD
Care-primary.
Profile-isolated by design.
The engineering programme began with care, where identity, continuity, policy and audit are non-negotiable. The accepted architecture keeps those shared semantics inside one Octeryx product, with Kasa and Film as isolated profiles.
Current stage
Accepted product architecture
and deterministic repository proof
and deterministic repository proof
- Accepted modular product doctrine and target boundaries
- Historical deterministic Kasa contracts, fixtures and boundary proofs
- Makemake Onboard, ECP Onboard and CongDB Onboard concept ownership
- Current claim, risk, data and jurisdiction governance
- OX02 contract inventory is the next implementation slice
Future milestones
Typed Octeryx contracts · PostgreSQL foundation · Native Onboard capabilities · Kasa and Film profiles · Governed production deployment
FOUNDATION GUIDE 01
Autonomy needs
a memory.
A machine can perceive the present. Dependable autonomy requires a governed account of what happened before, what matters now and what may happen next.
TWO DELIBERATE PROFILES
One product.
Explicit profile boundaries.
Kasa is the primary care profile across homes, care homes and connected care settings. Film is one isolated adjacent profile for sets, stages, LED volumes, cameras, trackers, people, assets, rights and continuity. Both remain inside one Octeryx product without sharing protected profile data or forking core semantics.
Kasa and Film are documented profiles, not live products or deployments. No other sector is an active product profile.