Skip to content

Project Glowing Heart v2.10 Evidence Map Index Integration

What Changed

Glowing Heart now has a structured discovery index connecting the Difference Packet Index, its Atlas Graph representation, the rendered evidence map, and the visitor gallery. The index records canonical source and output paths, renderer provenance, the graph identity, status counts, and per-exhibit links.

The index is generated by tools/glowing_heart_evidence_map_index.py. Generation cross-checks each exhibit ID, status, rule, and claim boundary between the v2.6 index and v2.8 graph, then confirms that v2.9 contains a matching SVG exhibit card.

Artifact Chain

Difference Packet Index
  -> Atlas Graph
  -> Evidence Map
  -> Difference Packet Gallery
Stage Path
Difference Packet Index reports/glowing_heart_v2_6_difference_packet_index.preview.json
Atlas Graph Docs/Observatory/Observation_Atlas/Atlas_Graph/glowing_heart_difference_packet_exhibits.graph.json
Evidence Map reports/glowing_heart_v2_9_evidence_map.svg
Gallery Docs/xPRIMEray/project_glowing_heart_v2_4_difference_packet_gallery.md

The graph ID is glowing_heart.difference_packet_exhibits. The chain contains five exhibits: two Comparable, two Unknown, and one NotComparable.

What This Demonstrates

The same five recorded comparison decisions can be discovered consistently across structured index data, graph nodes, SVG cards, and gallery sections. A visitor or tool can follow one exhibit without deriving identity or status from prose, color, or topology.

This is discovery and provenance infrastructure. It records existing decisions and the artifacts that present them.

What This Does Not Demonstrate

  • Core-vs-Core only.
  • Not a Godot comparison.
  • Not image or pixel comparison.
  • Not parity.
  • Not physical validation.
  • Not renderer equivalence.
  • Structural consistency does not establish scientific correctness.

Runtime Terminology

The index fixes comparisonMode=core_vs_core, parityClaim=NONE, and runtimeExecuted=false. Here, runtimeExecuted=false means the v2.10 indexing and rendering stage did not execute a runtime. Retained source artifacts may have been produced by earlier Core fixture runs; the field is not a historical statement about their creation.

Index Schema Overview

  • schema: schemas/glowing_heart/evidence_map_index.v0.preview.json
  • structured preview: reports/glowing_heart_v2_10_evidence_map_index.preview.json
  • Markdown preview: reports/glowing_heart_v2_10_evidence_map_index.preview.md
  • generator: tools/glowing_heart_evidence_map_index.py

The schema requires the chain paths, renderer paths, graph ID, exhibit list, status counts, and claim boundaries. It restricts exhibit statuses to Comparable, Unknown, NotComparable, or RequiresTransform and fixes the comparison-stage claim fields.

Generate the index with:

python3 tools/glowing_heart_evidence_map_index.py

The generator validates before an atomic output replacement. Missing artifacts, mismatched graph metadata, unsupported statuses, or mismatched SVG card IDs fail without leaving a partial index.

Verification

Verification parses and schema-validates the JSON, validates the source Atlas Graph, checks the SVG exhibit groups and safety boundary, compiles the generator, builds both .NET projects, and builds the MkDocs site. Claim, path-casing, Core dependency, and protected-file scans complete the milestone check.

Next Milestone

A future milestone can expose this index as the stable discovery input for a broader Observatory landing page while retaining the same claim boundaries and source-of-truth chain.