Skip to content

Clarification

Runtime vs Generative Agent

Clarification between a runtime that serves precompiled packs and an agent that interprets, generates or decides.

CollectionClarification
TypeClarification
Version0.1-proposed
Stabilization2026-07-10
Published2026-07-10
Updated2026-07-10

Evidence layer

Probative surfaces brought into scope by this page

This page does more than point to governance files. It is also anchored to surfaces that make observation, traceability, fidelity, and audit more reconstructible. Their order below makes the minimal evidence chain explicit.

  1. 01
    Evidence artifactdoctrine-glossary.json
Artifact#01

doctrine-glossary.json

/doctrine-glossary.json

Published surface that contributes to making an evidence chain more reconstructible.

Makes provable
Part of the observation, trace, audit, or fidelity chain.
Does not prove
Neither total proof, obedience guarantee, nor implicit certification.
Use when
When a page needs to make its evidence regime explicit.

Runtime vs Generative Agent

A generative agent may interpret a request, select an objective, produce an answer and call tools. The Governed Context Runtime does not do that.

Its role is narrower: receive a closed token, serve a precompiled pack and expose the manifest needed to verify its integrity.

If a free request must be interpreted, that operation happens outside the runtime. The site declares possible intents, but does not turn the runtime into a qualification engine.

This separation prevents a major drift: confusing distribution infrastructure with a decision agent.