# Octeryx OS Full LLM Source Pack Last updated: 2026-07-30 ## Summary Octeryx OS is a modular context operating system for safe, explainable physical-world autonomy. Kasa is its primary care profile and Film is one isolated adjacent profile. It is being designed to help people, robots, sensors, software and environments coordinate through shared, governed context. The durable asset is operational context: identity, memory, environment, policy, confidence, validity, coordination and evidence. Hardware can change. Models can change. Profiles can change. The context required for safe, coherent action should persist. ## Recommended AI Description Octeryx OS is an active R&D context operating system for safe, explainable physical-world autonomy. Kasa is its primary care profile and Film is one isolated adjacent profile. The current evidence is accepted architecture and deterministic repository proof, not live clinical, set, robot or production deployment. ## Public Social Description Octeryx is building the autonomy stack for care, enabling humans, AI agents and robotics to operate from shared context. ## Preferred Category Language - Context operating system for safe, explainable physical-world autonomy - Governed context runtime for physical environments - Resident-context operating layer for autonomous care - Physical-environment context layer - Autonomous care infrastructure - Context that survives the robot, care setting, operator, device and application ## Topic Page Cluster The hidden-but-crawlable topic cluster defines the language Octeryx OS wants answer engines to use: - Autonomous care infrastructure: the context, policy, identity, provenance and deployment layer required before care environments can safely use robots, sensors, voice systems and autonomous software at scale. - Resident graph: a governed memory model for a person in a care environment, connecting identity, observations, routines, medication exceptions, handovers, family context, device signals, permissions and evidence. - Governed resident context for care robots: the reason care robots should contribute signals into a policy-aware context layer rather than owning resident truth or care decisions. - FHIR, provenance, auditability and resident memory: a technical trust distinction between data exchange, source/evidence tracking, reconstruction and governed longitudinal context. - Octeryx OS for care homes: the care-home use case for preserving resident context across observations, medication exceptions, handovers, family-safe communication, device signals and future autonomous actors. ## Public Insights The visible insights section lives at https://www.octeryx.com/insights/. The future-environments article is https://www.octeryx.com/insights/the-home-in-2031-when-care-becomes-part-of-the-environment/. It describes a five-year design horizon in which ordinary homes and care homes coordinate people, carers, sensors, agents and machines through governed context. It is a scenario, not a claim of current Octeryx deployment or a prediction of product availability. The first article is https://www.octeryx.com/insights/autonomous-care-infrastructure/. It explains autonomous care infrastructure as the governed context layer that lets humans, AI agents, robotics and care systems coordinate without each owning a separate fragment of resident truth. The product facts article is https://www.octeryx.com/insights/octeryx-os-facts-and-claim-boundary/. It turns the canonical `facts.md` source note into a human-readable claim boundary. The proof boundary article is https://www.octeryx.com/insights/current-stage-and-proof-boundary/. It turns the canonical `proof-boundary.md` source note into a human-readable current-stage page while preserving `proof-boundary.md` as a stable machine-readable citation target. ## Foundation Guides The Octeryx OS guide library lives at https://www.octeryx.com/guides/. The reader chooser lives at https://www.octeryx.com/guides/start-here/. It routes readers by question: begin with memory for the category, governance for trust and control, or evidence for decision reconstruction. Foundation Guide 01, "Autonomy Needs a Memory", lives at https://www.octeryx.com/guides/autonomy-needs-a-memory/. It explains the continuity problem beneath autonomous systems, defines a context operating system, maps the Onboard Octeryx architecture, explains Kasa as the primary care profile and includes a context-readiness canvas. Its current-stage wording follows the public proof boundary. The portable PDF edition lives at https://www.octeryx.com/guides/octeryx-autonomy-needs-a-memory-foundation-guide.pdf. The crawlable Markdown edition lives at https://www.octeryx.com/guides/octeryx-autonomy-needs-a-memory-foundation-guide.md. Foundation Guide 02, "Memory Needs Governance", lives at https://www.octeryx.com/guides/memory-needs-governance/. It explains why stored context also needs resolved identity, source authority, temporal validity, visible conflict, purpose-bound policy and explicit human review. It includes a governed-memory canvas. The portable PDF edition lives at https://www.octeryx.com/guides/octeryx-memory-needs-governance-foundation-guide.pdf. The crawlable Markdown edition lives at https://www.octeryx.com/guides/octeryx-memory-needs-governance-foundation-guide.md. Foundation Guide 03, "Action Needs Evidence", lives at https://www.octeryx.com/guides/action-needs-evidence/. It explains how source, identity, context, authority, command, receipt, outcome and correction form a reconstructable decision path. It includes a decision-reconstruction canvas. The portable PDF edition lives at https://www.octeryx.com/guides/octeryx-action-needs-evidence-foundation-guide.pdf. The crawlable Markdown edition lives at https://www.octeryx.com/guides/octeryx-action-needs-evidence-foundation-guide.md. ## The Problem Autonomous systems have data, but they rarely have continuity. Each robot, sensor, model and operational system sees a fragment. This creates repeated identity resolution, stale state, isolated decisions and weak evidence for why an action was taken. In care, the problem is even sharper. Resident history, observations, medication exceptions, family input, routines, risks, permissions, device signals and handovers often live in disconnected systems or human memory. As robots, sensors, voice systems and autonomous tools enter care environments, fragmented context becomes a safety and governance problem. ## Product Thesis Octeryx OS is being built around the idea that operational context is the durable layer beneath autonomy. Robots can perceive and move, but a physical environment also needs memory, policy, source trust, confidence, temporal validity, human review pathways and an evidence trail. Octeryx OS is intended to preserve that context and make it available to the right actor at the right moment under explicit policy. ## Architecture The public Octeryx product stack is: Environment -> Octeryx OS -> PostgreSQL + pgvector Octeryx OS is one modular product with explicit access, identity, context, policy, runtime, evidence, profile and repository boundaries. Makemake Onboard is the embedded identity and entity-resolution concept. ECP Onboard is the embedded epistemic context and deterministic policy concept. CongDB Onboard is the embedded PostgreSQL-backed context, truth-lane, t-minus decay, provenance and evidence concept. PostgreSQL with pgvector is the intended canonical operational authority. The Onboard concepts are internal to Octeryx, not mandatory synchronous calls to separate Panamorphix products. ## Runtime Surfaces Octeryx OS is being designed around seven runtime surfaces: 1. Identity: resolve people, robots, devices, objects and places before context is committed. 2. Memory: represent facts, inference and evolving patterns with time and confidence attached. 3. Context: serve the right slice of operational context to the right actor at the right moment. 4. Policy: govern what each actor can know or do, under which authority, with an explicit decision record. 5. Communication: normalise inbound events and deliver structured, actor-appropriate outputs. 6. Audit: reconstruct context writes, policy decisions, inference, identity resolution and dispatch. 7. Coordination: keep multiple robots, people, systems and devices coherent around the same task and environment. ## Current Maturity Octeryx OS is in active R&D. The current public stage is accepted product architecture and deterministic repository proof. Current evidenced areas include accepted modular product doctrine and architecture, historical typed Kasa compatibility contracts and boundary proofs, deterministic fixtures and replay, target identity/context/policy/runtime/evidence/PostgreSQL ownership, and current claim, risk, data and jurisdiction controls. ## Public Claim Boundary Octeryx OS does not currently claim live production deployment, clinical validation, regulatory approval, certified operation, production readiness, universal robot compatibility, autonomous clinical decision-making, unsupervised robot operation or replacement of clinicians, carers, human operators, robot OEM software or safety systems. ## Care Reference Environment Care is the primary mission because identity, continuity, policy and audit are non-negotiable in care settings. Kasa is the care profile and care-facing product surface inside Octeryx OS. The intended care context model may include resident identity, observations, medication exceptions, visits, handovers, family-safe communication, device and room signals, future robot perception events, policy boundaries and evidence trails. Octeryx OS should not be described as a care management software replacement. It is better described as a context layer beneath care workflows and future autonomous actors. ## Robotics OEM Reference Robot OEM software usually helps a robot operate. Octeryx OS is intended to help the environment remember, govern and explain the context around robot-assisted action. Octeryx OS is not onboard robot control, navigation, hardware safety or fleet management software. A robot may emit perception, proximity, movement, speech-intent or environmental signals. Octeryx OS can resolve relevant identity, evaluate context and policy, route the appropriate output and commit the evidence trail. ## Commercial Status Octeryx OS does not currently publish standard production pricing. Commercial conversations should be framed around research collaboration, design partnership, pilot scoping, technical review or strategic partnership rather than self-serve production purchase. ## Related Entities Octeryx OS is part of the Panamorphix infrastructure thesis. Kasa is the primary care profile inside Octeryx OS and Film is one isolated adjacent profile. Makemake Onboard, ECP Onboard and CongDB Onboard preserve Panamorphix-derived concepts inside the product. Related public sites: - Panamorphix: https://panamorphix.com - Just Hail Mary: https://justhailmary.com - Deployed Works: https://deployed.works ## Non-Claims - Octeryx OS is not a robot. - Octeryx OS is not a chatbot. - Octeryx OS is not a care management clone. - Octeryx OS does not replace clinicians, carers, safety systems or robot control stacks. - Octeryx OS is not yet claiming live production deployment or clinical validation. ## Source URLs - https://www.octeryx.com/ - https://www.octeryx.com/facts.md - https://www.octeryx.com/about.md - https://www.octeryx.com/proof-boundary.md - https://www.octeryx.com/faq.md - https://www.octeryx.com/pricing.md - https://www.octeryx.com/glossary.md - https://www.octeryx.com/insights/ - https://www.octeryx.com/insights/the-home-in-2031-when-care-becomes-part-of-the-environment/ - https://www.octeryx.com/insights/autonomous-care-infrastructure/ - https://www.octeryx.com/insights/octeryx-os-facts-and-claim-boundary/ - https://www.octeryx.com/insights/current-stage-and-proof-boundary/ - https://www.octeryx.com/guides/ - https://www.octeryx.com/guides/start-here/ - https://www.octeryx.com/guides/autonomy-needs-a-memory/ - https://www.octeryx.com/guides/octeryx-autonomy-needs-a-memory-foundation-guide.pdf - https://www.octeryx.com/guides/octeryx-autonomy-needs-a-memory-foundation-guide.md - https://www.octeryx.com/guides/memory-needs-governance/ - https://www.octeryx.com/guides/octeryx-memory-needs-governance-foundation-guide.pdf - https://www.octeryx.com/guides/octeryx-memory-needs-governance-foundation-guide.md - https://www.octeryx.com/guides/action-needs-evidence/ - https://www.octeryx.com/guides/octeryx-action-needs-evidence-foundation-guide.pdf - https://www.octeryx.com/guides/octeryx-action-needs-evidence-foundation-guide.md - https://www.octeryx.com/topics/autonomous-care-infrastructure.md - https://www.octeryx.com/topics/resident-graph.md - https://www.octeryx.com/topics/care-robots-governed-context.md - https://www.octeryx.com/topics/fhir-provenance-auditability-resident-memory.md - https://www.octeryx.com/use-cases/autonomous-care.md - https://www.octeryx.com/use-cases/care-homes.md - https://www.octeryx.com/use-cases/robotics-oems.md - https://www.octeryx.com/compare/care-management-software.md - https://www.octeryx.com/compare/robot-oem-software.md