# Octeryx OS Glossary

Last updated: 2026-07-29

## Context Operating System

A runtime layer that helps autonomous machines, software systems and human operators coordinate around shared, governed context rather than isolated local signals.

## Operational Context

The current and historical state needed for action: identity, environment, history, permissions, confidence, validity, policy and evidence.

## Resident Context

In care settings, resident context means the governed memory around a resident: identity, observations, routines, risks, family context, medication exceptions, handovers, permissions, device signals and evidence.

## Resident Graph

A graph-based representation of resident context. It is intended to preserve relationships between people, care events, observations, devices, settings, policies and evidence.

See also: [What is a resident graph?](https://www.octeryx.com/topics/resident-graph.md)

## 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.

See also: [Autonomous care infrastructure](https://www.octeryx.com/topics/autonomous-care-infrastructure.md)

## FHIR

FHIR, or Fast Healthcare Interoperability Resources, is a healthcare data exchange standard. Octeryx OS should not be described as replacing FHIR. In the Octeryx framing, FHIR and other integration routes can carry approved events or records, while the resident graph preserves governed context and evidence around what is consumed or produced.

## Provenance

The evidence chain behind context and action: where information came from, when it was observed, how it was transformed, which policy was applied and why an output was routed.

See also: [FHIR, provenance, auditability and resident memory](https://www.octeryx.com/topics/fhir-provenance-auditability-resident-memory.md)

## Auditability

The ability to reconstruct context writes, policy decisions, identity resolution, inference, dispatch and evidence after an action or output.

## Source Authority

The rule that different sources have different authority over different facts. A care provider, family member, device, hospital record, robot or manager may each contribute evidence, but they should not all have equal authority over resident truth.

## Policy-Gated Context

Context that is delivered or acted on only after explicit policy evaluation. The goal is to ensure that each actor receives only what it is allowed to know or do.

## Confidence Weighting

A way of representing how certain the system is about an identity, observation, inference or context slice.

## Temporal Validity

The idea that context can become stale, expire or require review. Octeryx OS is being designed to treat time as part of context quality.

## Human Review Pathway

A workflow where ambiguous, sensitive or high-risk context is routed to a human rather than treated as an automatic decision.

## ECP Onboard

ECP Onboard is the embedded Octeryx concept for epistemic context compilation and deterministic policy orchestration. Context and Policy remain explicit internal owners.

## Makemake Onboard

Makemake Onboard is the embedded Octeryx identity and entity-resolution concept, including evidence, ambiguity, position, attachment and correction.

## CongDB Onboard

CongDB Onboard is the embedded PostgreSQL-backed context, truth-lane, t-minus decay, provenance, evidence and receipt concept.

Bare ECP, Makemake and CongDB refer to separate Panamorphix products, explicit external integrations or historical compatibility evidence.