# Glossary

## `.one`

The bounded source envelope containing compact or explicit System IDL semantic
documents and isolated native-One or foreign executable sections.

## System IDL

The bounded, non-executable semantic language used to author stable meaning and
governed intent.

## Native One

The coherent executable programming language owned by System IDL. It consumes
exact contracts and compiles to governed target artifacts; it is not a
universal transpiler.

## Semantic domain

An owner-controlled closed declaration vocabulary, schemas, invariants,
defaults, compatibility, dependencies, and normalization rules.

## Declaration namespace authority

The owner of an authored declaration's identity and values under the selected
domain's rules.

## OCS

One Contract Schema: the canonical content-addressed, language-neutral contract
package from which exact projections are generated.

## Source-language definition

The exact owner and revision for a programming language's grammar, static
semantics, module model, frontend contracts, bounds, and diagnostic contract.

## Implementation-language profile

The governed contract that connects executable source to an OCS projection,
allowed dependencies, targets, runtime behavior, effects, capabilities, and
required evidence.

## Implementation claim

An untrusted semantic declaration associating an exact contract/component with
an executable entry and implementation profile.

## Root

One independently composed, planned, built, deployed, or delivered closure.

## Provider

A replaceable realization of an owned contract.

## Adapter

An explicit mapping of a foreign contract at the narrowest useful boundary,
including lifecycle, authority, faults, costs, and losses.

## Requirement

A need derived for an exact root. It is not permission.

## Grant

An Authority-owned approved permission for a principal, scope, operation, and
conditions. It is not a runtime token or host enforcement.

## Effect

A typed description of externally meaningful state impact and its
determinism, idempotency, unknown-outcome, reversal, compensation, and
irreversibility behavior.

## Plan

An immutable, inspectable selection of exact semantic inputs, providers,
topology, targets, artifacts, permissions, costs, observations, and actions.
It is not authority to mutate.

## Apply

Begin or resume authorized reconciliation of one exact reviewed plan without
replanning, rebuilding, reselecting, or widening authority.

## Receipt

Evidence that a specific parse, normalization, analysis, projection, action,
effect, build, deployment, or observation occurred under exact inputs.

## Provenance

The inspectable source and proof path that explains where a value, decision,
artifact, or action came from.

## Outcome unknown

An effect may have reached an external target, but available evidence cannot
prove committed or aborted. It must be reconciled before unsafe repetition.

## Conformance

Evidence that one exact implementation satisfies one exact owned contract
under a named suite, target, configuration, and limitations.

## Unsupported

A typed result stating that the responsible owner has no admitted realization
for the requested operation. It is never simulated success.