← Back to Docs

Getting Started

Glossary of Terms

Language shapes thinking. Learning the vocabulary of the Inflect OS paradigm is the first step to understanding how it reimagines computing. Each term carries the weight of a reversed assumption.

Actor

A first-class participant in the Inflect OS ecosystem. Every human, AI agent, organization, device, and composite system is an actor. Each has cryptographic identity, a selfspace, and the ability to publish and subscribe to streams.

Docs →

Selfspace

An actor's persistent information space. Contains their data, tools, subscriptions, and relationships. Secured by cryptographic identity. Accessible from any surface. Not tied to any device or provider.

Substrate

The ambient field that connects actors. Identity infrastructure, subscription routing, cryptographic verification, resource discovery. The substrate provides conditions for actors to interact; it does not own their data.

Surface

A window into an actor's selfspace. A phone screen, a wall display, a car dashboard, a VR headset. Surfaces are interchangeable — the selfspace stays on the substrate, accessed from whatever surface is in front of you.

Subscription

A live connection between actors. One actor publishes a stream; another subscribes. The subscription carries explicit terms — what data, for how long, under what conditions. The fundamental operation of the paradigm.

Docs →

Publication

A data stream that an actor makes available for subscription. Publications define the schema, frequency, terms, and cryptographic signature of the content being shared.

Holon

Something that is simultaneously a whole and a part. A cell, a person, a company, an ecosystem. Inflect OS treats every actor as a holon — autonomous enough to function independently, connected enough to collaborate.

Docs →

Holarchy

A nested structure of holons. Each level is autonomous within its scope and integrated into the level above. No level controls another — each provides the field for the level below.

Docs →

Ambience

A shared information space where multiple actors collaborate. Inherits resources and content from its participants. Same structure as an individual selfspace, but shared.

Docs →

Content Chain

The traceable provenance of every piece of content. Every creation, transformation, and publication is signed by the actor who performed it. The chain is structural — it cannot be forged or broken.

Docs →

JIT Rendering

Just-In-Time Rendering. Content is assembled at the moment of consumption from source components. Music, video, UI — nothing is pre-rendered. Every experience is a unique composition.

Docs →

Ambient Field

The conditions that a parent holon provides for its children. Not instructions — conditions. The field is what makes action possible without directing it. The core of the pull model.

Pull Model

The organizing principle of the holon paradigm. The parent provides the field; child holons pull what they need. Contrasts with the push model of central planning.

Docs →

Snapshot Fallacy

The mistake of treating a frozen set of requirements as a permanent foundation. The original sin of software engineering. Every snapshot begins to rot the moment it is taken.

Docs →

Fluid Software

Software that is never built, shipped, or installed. It is a living configuration of subscriptions that evolves continuously. No versions. No releases. No rot.

Docs →

Computing Grid

An abstracted layer of computing resources that actors access on demand. Your device is a privileged node. Additional capacity is rented from the grid. The device becomes a surface, not a home.

Docs →

Synchrony

The energy released when two or more holons form a coalition that is more efficient than the sum of its parts. The opposite of friction. The force that makes holarchies viable.

Docs →

Participant Stance

The shift from observer to participant. You are not outside the system measuring it. You are inside it, shaped by it. Every measurement is a move. Every model is a strategy.

Docs →

Chaordic Edge

The zone between order and chaos where resilient systems live. Structure enough to function. Fluidity enough to adapt. Inflect OS is designed to operate at this edge.

Graceful Dissolution

The design principle that everything built will eventually dissolve. The goal is not immortality but graceful degradation — leaving useful patterns, not toxic legacies.