Glossary¶
Definitions here distinguish current product concepts from future direction. Exact version-specific behaviour lives in the installed Runtime contract and technical docs.
Engineering Runtime¶
The Engineering Execution Layer for reusable engineering operations. It applies deterministic runtime decisions and supported authorization, policy, safety and evidence controls.
It receives a provider operation or capability request and applies the Runtime execution contract around it: compiled safety, configurable policy, authentication/context, execution, sanitization, structured results and audit/evidence.
Engineering Capability¶
Reusable engineering knowledge expressed as an executable Markdown contract.
A capability declares inputs and ordered provider/binary steps. Supported releases may also allow bounded typed outputs, conditions and live verification.
The capability is independent of whether a human, CI system or AI assistant authored or invoked it.
Capability Version¶
The author-declared version of the capability's reusable engineering knowledge/contract.
It is separate from the Runtime binary version.
Runtime Compatibility¶
A capability's declared constraint on which engrt versions are expected to
understand its contract.
Compatibility is checked before execution where supported. It does not override grammar, provider availability, policy or qualification evidence.
Reuse Before Re-Reasoning¶
The principle that a reviewed compatible capability should be reused for a solved engineering operation before generating a new implementation from scratch.
Self-Authoring Capability¶
An authoring flow in which a human or AI assistant reads the installed Runtime's exact authoring contract, searches existing capabilities, writes a new capability when needed, validates/proves it and preserves it for reuse.
Author-Declared Intent¶
The capability author defines what outcome should be true.
Runtime should not infer hidden desired-state semantics from an arbitrary command.
Runtime Provider¶
The component that owns one engineering platform's curated operation surface and selects the appropriate transport per operation.
For example, one GitHub operation may use REST while another uses GraphQL or a reviewed
gh path.
Runtime Engine¶
One of the current execution transports:
- REST
- GraphQL
- Command
- File
Authentication/context and policy/audit are cross-cutting services rather than additional dispatch engines.
Runtime Context¶
The resolved target scope for one invocation, such as repository, organisation, cloud project, cluster or namespace.
Runtime Context is not a global Runtime-owned provider profile. Native provider context remains owned by the provider/tool, and Runtime must not guess a target it cannot bind.
Runtime Home¶
The Runtime-owned local workspace, normally ~/.engrt.
It holds release-owned contracts and Runtime operational state such as audit/evidence, logs, caches and private working data. Native provider credentials remain in their own stores.
Bootstrap¶
Initialization that prepares Runtime-owned local state and contracts before engineering work executes.
Bootstrap does not itself perform the requested engineering operation and must not silently create user governance or credentials.
Compiled Safety Floor¶
Non-disableable protections shipped as part of the Runtime executable contract.
Configurable policy may deny more, but cannot permit an operation that the compiled safety floor refuses.
Policy¶
Configurable rules that determine whether an admitted operation is allowed.
Policy is evaluated before dispatch and sits above the compiled safety floor.
Platform-Native Authentication¶
The principle of using provider/platform authentication rather than inventing a second Runtime credential system.
Exact auth mechanisms are provider- and release-specific; stronger credential non-exportability guarantees require explicit proof before being claimed.
Deterministic Execution¶
Stable Runtime resolution and control behaviour for equivalent admitted inputs and Runtime state.
It does not mean external systems always produce identical real-world outcomes; provider state, credentials, policy and remote behaviour can change.
Sanitization¶
The boundary that removes or refuses sensitive values before unsafe result/evidence surfaces are produced.
A value is not considered safe merely because it came from a trusted provider CLI/API.
Audit / Evidence¶
Structured information explaining what was requested, admitted, executed, denied, observed and verified.
Audit/evidence explains Runtime execution; it does not replace authoritative provider state.
Live Verification¶
A bounded post-execution observation of authoritative provider state compared with the declared expected outcome.
Transport success and verification success are separate.
Stateless Reconciliation¶
A state-aware execution model where each run observes authoritative provider state again, compares it with declared intent, applies only required change and verifies the result.
Runtime does not need a cross-run resource-state database to decide what the provider currently contains.
SATISFIED¶
A logical v0.11.0 state outcome meaning authoritative state already matched the declared intent, so no mutation was required.
APPLIED¶
A logical v0.11.0 state outcome meaning required state was created/applied and verified.
RECONCILED¶
A logical v0.11.0 state outcome meaning observed drift was safely corrected and verified.
Intent–Execution Separation¶
The architectural boundary between deciding what should happen and governing/executing the operation.
Humans or AI may reason about intent. Runtime owns the deterministic execution path.
Self-Describing Runtime¶
The principle that the installed binary ships the command/provider/capability contracts for its own release so users and assistants can author against the exact version they have.
GitHub-as-Agent-Context¶
The operating model in which durable engineering context is written to versioned GitHub artifacts rather than hidden agent-to-agent memory.
GitHub preserves versioned context. Engineering Runtime governs execution.
Versioned Context¶
Context whose history, diff, review, provenance and supersession can be inspected by a later human or agent.
Two-Directional MCP¶
Two separate possible MCP directions:
- Runtime consuming an MCP provider surface as a bounded execution transport.
- Runtime exposing governed Runtime artifacts/operations to agents through MCP.
Neither direction creates a second auth/policy/result authority.
Capability Package¶
A future packaged-distribution concept for capabilities.
It is not the current generalized distribution model; current capability distribution is Git/file based.
Capability Registry¶
A future discovery/distribution concept for packaged capabilities.
No generalized public Runtime registry is part of the current product.
Control Plane¶
An optional governance layer above Runtime fleets.
It is not required for local execution and must not become an execution engine. Exact enterprise sync, identity, audit export and fleet features remain subject to their implemented/qualified contracts.
Data Plane¶
The Runtime process/machine where admitted engineering operations actually execute.
AI Independent¶
The principle that Runtime execution should not depend on a particular AI vendor.
AI may reason, author and invoke; Runtime remains the execution contract.
Engineering Knowledge¶
Reusable operational knowledge that has been captured in a durable, reviewable form.
A reviewed capability can become company engineering knowledge that survives the original engineer, AI model, chat or pipeline.