MD-OS compiles Markdown knowledge into runtime cognition, not only memory.
The compiler turns the repository graph into bounded operational indexes:
Markdown vault
-> semantic index
-> claim graph
-> capability graph
-> link graph
-> context packs
-> epistemic health
-> eval readback
-> replayable state
Canonical command:
cortex compile-runtime
Equivalent direct builder:
node md-os/os/build_runtime_compiler.js
Generated runtime output lives under md-os/ops/runtime/:
md-os/ops/runtime/semantic_operational_compiler.json
md-os/ops/runtime/semantic_index.json
md-os/ops/runtime/claim_index.json
md-os/ops/runtime/capability_index.json
md-os/ops/runtime/link_index.json
md-os/ops/runtime/context_packs/
md-os/ops/runtime/eval_results.json
md-os/ops/runtime/epistemic_health.json
md-os/ops/runtime/semantic_drift_report.md
These files are generated readback. Source remains in Markdown, schemas, connectors, programs, project definitions, and other canonical source paths.
Every compiled semantic node must expose:
id
path
title
type
semantic_layer
cognitive_role
epistemic_status
concept_terms
actionability
depends_on
enables
tools
risks
tests
The node is incomplete if it cannot answer:
what it is
what it says
what it enables
what can use it
what risk it opens
what readback or test closes it
Every compiled claim must carry one bounded status:
raw
hypothesis
working_model
validated
reproducible
deprecated
contradicted
Claims without status are compiler failures. Contradicted claims may remain in the graph, but they must not silently drive action.
Knowledge becomes operational only when it compiles into explicit capability records:
capability_id
capability_type
source_nodes
tools
file_targets
requires
risks
readback
rollback
tests
Capability types:
informational
procedural
instrumental
regulatory
diagnostic
repair
identity-bearing
Medium or high risk capability records must include permission or approval gates. Every capability must include readback.
The host should not load the whole repository when a compact task pack is enough. The runtime compiler emits context packs for:
bootstrap
operations
epistemic
semantic_task
import
runtime_health
Each pack contains selected nodes, claims, capabilities, and compact text for bounded injection into the host runtime.
The compiler must check for:
claim duplicate
claim conflict
stale instruction marker
missing or broken Markdown link
unsafe operation
identity drift
semantic orphan
The output is:
md-os/ops/runtime/epistemic_health.json
md-os/ops/runtime/semantic_drift_report.md
Knowledge import remains the intake path. Runtime compilation is the promotion readback path. After an import, the repository should rebuild:
markdown graph
semantic graph
self-release index
runtime compiler
global index
health
replay
This is the stable distinction:
knowledge import = custody and structured arrival
runtime compiler = operational cognition readback