Skip to content

Clarification

Runtime vs MCP

Clarification between governed context infrastructure and the MCP protocol that may expose read tools.

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 MCP

The runtime and MCP are not the same kind of object.

The runtime is the infrastructure that serves precompiled packs. MCP is a protocol channel that may expose selected read tools, such as listing intents, retrieving a pack or verifying a digest.

MCP does not create a new governance layer. It must not add write tools, free intent resolution, response scoring or recommendation.

The rule remains the same: the protocol gives access to governed artifacts, but it does not become an autonomous interpretive authority.