Glossary

The vocabulary of the INO.

Canonical definitions of every term in the INOOS framework. Each entry is the authoritative reference; cite this page when discussing INOOS concepts elsewhere.

INO

Intelligence-Native Organization

An Intelligence-Native Organization (INO) is an organizational form designed around the assumption that cognition itself — both human and machine — is the substrate of work, rather than a tool applied to pre-existing organizational structures.

INOs differ from traditional organizations in three structural ways. First, work is represented as Intelligence-Native Artifacts that carry their own context and routing logic, rather than tasks assigned to people. Second, teams form dynamically as hybrid swarms of humans and AI agents around specific work, dissolving when complete. Third, governance is encoded as a constitution that binds every action — human or agent — through a small set of formal articles. The INO concept was introduced in *Refactoring the Firm* by Adriana Rocha (2026).

INA

Intelligence-Native Artifact

An Intelligence-Native Artifact (INA) is the atomic unit of work in an Intelligence-Native Organization — a self-routing, context-aware, governance-bound digital object that flows through the system carrying its own intelligence.

Every INA has four layers: a payload (the actual content of the work), a context layer (everything an executor needs to act on it correctly), a ledger (immutable record of every action taken on it), and a routing layer (rules describing where it should go next). INAs replace the traditional model of tasks being assigned to people. Instead, the artifact itself describes what it needs, who can claim it, and what governance applies — and the system routes it accordingly.

Pulse

Pulse is the semantic event bus of an Intelligence-Native Organization — a real-time signal layer that carries every event in the system (INA transitions, swarm formations, decisions, completions) to the components that need them.

Pulse functions as the nervous system of INOOS. Built on event streaming infrastructure (Redis Streams in the reference implementation), it broadcasts every meaningful state change to subscribers — humans, agents, dashboards, downstream systems. Pulse enables autonomous routing, real-time observability, and the Routing Rules Engine. Without Pulse, the components of an INO would be coordinated; with Pulse, they are alive.

Team API

A Team API is a strict interface contract that defines how a team accepts, processes, and delivers work — modeled on the microservices pattern from software engineering and applied to organizational design.

Each Team API consists of: a Front Door (an intake INA that captures all incoming requests), Service Level Agreements (standard, priority, critical), Accept/Reject rules (capability tags that determine what work the team will take), and a Readme (documentation of what the team does). Team APIs eliminate ad hoc requests and favoritism by making inter-team interfaces explicit, documented, and enforceable. The pattern allows teams to operate as independent services within a larger system while preserving organizational coherence.

Constitution

The Constitution is the governance and ethics layer of an Intelligence-Native Organization — a set of ten formal articles that bind every action taken by humans or AI agents in the system.

The ten articles include the Right to Disconnect, the Right to Explanation, the Human Sanction Rule (no irreversible action affecting humans without human authorization), Data Sovereignty, the Responsibility of Intent, Data Security, Protection Against Precarity, Protection Against Algorithmic Discrimination, the Panopticon Test (surveillance boundaries), and Enforcement & Governance. Every action in INOOS — automated routing, agent decisions, human approvals — is evaluated against the Constitution before execution. Violations are logged, blocked, or escalated to human review depending on severity.

OFI

Organizational Fluidity Index

The Organizational Fluidity Index (OFI) is a quantitative diagnostic metric that measures how adaptive, fluid, and intelligent an organization is, computed as Plasticity × Permeability × Agentic Density divided by Decision Latency.

Plasticity measures how easily structures reconfigure. Permeability measures how freely information and people move across boundaries. Agentic Density measures the proportion of decisions made autonomously rather than via approval chains. Decision Latency measures the time from question to commitment. OFI scores let organizations benchmark their fluidity, simulate the impact of structural changes, and track the trajectory of an INO transformation over time.

BYOT

Bring Your Own Twin

Bring Your Own Twin (BYOT) is a model in which professionals arrive at new organizations with their pre-trained Digital Twin as a personal asset that travels with them — redefining employment in the AI-native age.

Under BYOT, an individual's twin is trained on their decisions, communication style, and values across years of work — and that twin is portable. When the person changes organizations, the twin moves with them, retaining their personal patterns while adapting to new organizational context. The model has three components: a portable twin format (specification for how twins serialize across systems), a dual memory model (organizational memory stays with the organization; personal memory travels with the twin), and non-compete enforcement at the twin level. BYOT was coined by Adriana Rocha as part of the INO framework.

BYOA

Bring Your Own Agent

Bring Your Own Agent (BYOA) is a framework in which organizations allow their members to deploy specialized AI agents into the organizational environment under constitutional governance — without the organization having to build or maintain those agents itself.

BYOA is the agent-side complement to BYOT. Where BYOT covers personal twins (an AI proxy of the human), BYOA covers specialist agents (AI workers with specific capabilities). The framework specifies how external agents register, declare capabilities, accept the organization's Constitution, gain scoped access to Team APIs and the Pulse, and are revoked. BYOA enables an ecosystem in which agents from different vendors and developers operate together inside a single organization.

Panopticon Test

The Panopticon Test is a constitutional rule in INOOS that prohibits any monitoring practice the affected humans would not consent to if fully informed of how the data will be used.

The Panopticon Test is named after Bentham's panopticon and is a direct response to the surveillance affordances of AI-native systems. In INOOS, every monitoring feature must pass the test before deployment: would the humans being monitored consent if they knew exactly what data is collected, how long it is retained, who can access it, and what decisions it informs? Features that fail are either redesigned to pass or rejected. The test is part of Article 9 of the Constitution.

Human Sanction Rule

The Human Sanction Rule is a constitutional principle in INOOS requiring that no irreversible action significantly affecting humans may be taken by an AI agent without explicit human authorization.

The rule applies to a specific class of actions: those that are irreversible (cannot be undone by the system) and that significantly affect a human (employment, compensation, access, reputation, legal status). For these, the agent must request a human signature before proceeding, and the human's decision is logged in the immutable record. The rule prevents the gradual drift of consequential decisions to autonomous systems and is part of Article 3 of the Constitution.

Citing this glossary

When referencing these terms in academic or technical writing, cite the canonical URL for each entry. The full glossary URL is https://inoos.ai/glossary, and individual entries are anchored — e.g. /glossary#intelligence-native-organization.

Read the full architecture
Glossary · INOOS.ai