SZLHOLDINGS/szl-estate-graph

SZL Estate Graph v1

This is a deterministic, local publication bundle for SZLHOLDINGS/szl-estate-graph. It turns the two receipted SZL Constellation topology documents into a typed, trinity-connected graph suitable for graph-learning and drift comparison.

Publication target: SZLHOLDINGS/szl-estate-graph. Hub publication and its immutable revision are provider evidence separate from this content bundle; neither publication nor download implies model training, admission, or runtime use.

Honesty and provenance

• MEASURED (2026-09-04 local fetch): the two topology documents and engine source were fetched from immutable Space revision 5e4c2fc59cee618de1e43b18e0c6b2ccd543b498. The exact topology response bodies are preserved under sources/; the immutable app.py byte count and SHA-256 are bound into graph provenance and snapshot_id.
• MEASURED ENGINE PIN: the provider reported that exact revision RUNNING, and its JSON APIs were verified before capture. The generator records ENGINE_PIN_VERIFIED; this does not claim that the separate dataset draft is merged or published.
• DECLARED: both source documents declare generated = 2026-09-04T03:30:00Z.
• METHOD: graph construction mirrors the pinned Constellation Space trust-path engine: estate-to-hub synapses, basename/id vertical matching, one governance edge per vertical, the vertical-by-substrate cartesian product, the fixed three-hub trinity, and the engine's insertion-order BFS tie-break.
• UNSIGNED_HONEST: receipt.json has no signature and supplies integrity, not signer authenticity. Its independently reconstructed canonical payload and SHA256SUMS make every publication file recomputable.
• UNAVAILABLE: the source Space README does not declare a license. This card intentionally omits a license identifier instead of inventing one; publishing the owner-directed snapshot does not supply downstream reuse rights.

Source snapshot	Bytes	SHA-256
sources/estates.json	13,214	50c273b116cf1ce6a4e5dba955e457c2dc3e201755fe54b1d067b286048315c5
sources/verticals.json	7,787	ee50c61c030e1d2a323b509e805297b24d825db9e929c0dcc1b3da5aa766fa73
immutable Space app.py	30,169	2bddb036c2dba69d34c528cd8b15b7187877798e7d1d487edf7dc775ab1d6292

Canonical source URLs:

• https://huggingface.co/spaces/SZLHOLDINGS/szl-constellation/resolve/5e4c2fc59cee618de1e43b18e0c6b2ccd543b498/estates.json
• https://huggingface.co/spaces/SZLHOLDINGS/szl-constellation/resolve/5e4c2fc59cee618de1e43b18e0c6b2ccd543b498/verticals.json
• https://huggingface.co/spaces/SZLHOLDINGS/szl-constellation/resolve/5e4c2fc59cee618de1e43b18e0c6b2ccd543b498/app.py

The mutable /raw/main/ URLs remain recorded only as discovery pointers; they are not the provenance identity for this v1 snapshot.

Reconciled v1 topology

Node type	Count	Source rule
estate	49	every estates.json.estates[] entry
vertical	8	every verticals.json.verticals[] entry
hub	3	every estates.json.hubs entry
substrate_repo	7	verticals.json.shared_substrate.repos only
Total	67

shared_substrate also declares six governance repositories and nine bench-fleet repositories. They remain present in the preserved source snapshot but are not graph nodes in v1 because the live trust-path engine does not insert or connect those two arrays. Expanding that boundary requires a versioned schema/topology decision rather than an unreceipted change.

Edge type	Count	Derivation
synapse	49	each estate to its declared hub
wired-into	10	estate/vertical repo basename, Space basename, exact id, or id-prefix match
governed-by	8	each vertical to hub:second_brain
runs-on	56	8 verticals x 7 shared substrate repos
trinity	3	every pair among the three hubs
Total	126

All 67 nodes form one connected component when edges are traversed as undirected, matching the Space breadth-first trust-path behavior.

Stable identifiers and record schema

Node IDs are namespaced and deterministic:

• estate:{estates[].name}
• vertical:{verticals[].id}
• hub:{hubs object key}
• substrate:{repository basename}

Each node record has id, type, key, label, and type-specific attributes. Each edge record has id, type, source, target, traversal, and derivation; wired-into edges also include match_reasons. Edge IDs are:

edge:{type}:{source}->{target}

source and target retain the semantic direction of the derivation, while traversal is always undirected, as in the Constellation BFS engine. Every edge also carries a unique, contiguous engine_order; consumers sort incident edges by that field before BFS to reproduce the pinned engine's shortest-path tie-break. schema.json is the strict JSON Schema for graph.json.

Files

• nodes.jsonl and edges.jsonl: compact UTF-8 JSON Lines, lexically sorted by ID.
• graph.json: self-contained graph with nodes, edges, counts, semantics, and provenance.
• schema.json: JSON Schema 2020-12 contract for graph.json.
• sources/: exact fetched source bytes.
• generator.py: standard-library-only deterministic builder and fail-closed validator.
• receipt.json: per-file SHA-256/byte manifest plus canonical receipt payload hash.
• SHA256SUMS: hashes all receipted files and receipt.json itself.

The publication tree is exactly the ten files listed by the validator. A local root .incoming/ directory may hold tests or staging material and is explicitly excluded from publication inventory; no other extra file, symlink, junction, or reparse point is accepted.

Build and verify

From this directory in PowerShell, using the bundled Codex Python runtime:

$py = 'C:\Users\steph\.cache\codex-runtimes\codex-primary-runtime\dependencies\python\python.exe'
& $py -I -B .\generator.py build --source-dir .\sources --output-dir .
& $py -I -B .\generator.py validate --dataset-dir .

The builder fails closed if the source counts or derived edge counts drift from this v1 contract. To independently recompute any file hash:

Get-FileHash -Algorithm SHA256 .\graph.json

The validator checks pinned source bytes and field types, strict graph-schema conformance, counts, endpoint integrity, lexical ID ordering, canonical BFS order, graph connectivity, an independently reconstructed receipt and exact receipt file set, Windows-safe path containment, the exact ten-file publication tree, and every SHA256SUMS entry.