Glyph Engine v3

Phase III Execution Layer — v0.3.0

Context

Phase I described seam morphology.

Phase II related seam topology to propagation observables.

Phase III introduces an executable layer: a deterministic interpreter that operates over geometric artifacts.

Version v0.3.0 implements the minimal form of this layer.

It does not expand capability.
It stabilises execution.

---

What v0.3.0 Implements

Glyph Engine v3 is a deterministic script runner embedded inside the lab.

It:

• Executes a minimal DSL
• Loads registered report artifacts
• Consumes pre-computed Q4 comparison outputs
• Renders pairwise distance tables
• Emits a structured decision record
• Exports deterministic JSON results

The canonical script:

seed 1337

load R = report "artifacts/sample/q4_report.json"
let @mode = { strict: true }

compare D = q4(R, config=@mode)

export json("run_outputs/q4_result.json", D)

Execution produces:

• A distance table (cosine, Jaccard, JS divergence)
• A raw JSON result
• A decision record capturing runtime state

---

Execution Guarantees

Each run records:

• Engine version
• Script hash
• Seed
• Loaded artifact path + hash
• Comparability mode
• Timestamp
• Execution notes

The first invariant of Phase III is now explicit:

Same script + same artifact + same seed → identical output.

No hidden state.
No implicit mutation.

---

Report-Only Mode

v0.3.0 operates in report-only mode.

It does not:

• Recompute signatures
• Parse NetCDF layers
• Mutate atlases
• Resimulate parameter space
• Perform anchor-level masking

It consumes pre-computed Q4 artifacts and exposes them through a deterministic execution layer.

This is deliberate.

The objective of v0.3.0 is stability, not expansion.

---

Governance Layer

Every execution emits a Decision Record.

This record is not decorative.
It is structural.

It makes visible:

• What was loaded
• Under what configuration
• Under what mode
• With what hash identity

This converts Q4 comparison from a static report into an auditable computation.

---

Why This Matters

Before v3, the lab produced geometric artifacts.

With v3, the lab executes geometry.

The distinction is subtle but foundational.

A report can be read.

An interpreter can be run.

Execution introduces reproducibility discipline, version identity, and deterministic contracts.

---

Scope Boundary

v0.3.0 is intentionally narrow.

It is the interpreter skeleton.

Future versions will extend computation (signature extraction, atlas-level comparison), but they will not loosen governance constraints.

Phase III begins with stability.

---

Version: v0.3.0
Engine ID: Glyph Engine v3
Mode: Report-Only Execution Layer

---