eModulus· Vortex Lab

UKL (Unified Knowledge Layer) is the hierarchical classification system for all knowledge fragments inside DAO365. Each node in the ecosystem carries a UKL code — from 0.0.0 (core ethics) to F.3 (synthesis). The code is the address, not the container.

DNR.JSON (Do-Not-Resuscitate) is the immutable constitutional document that names what cannot be revived under any pressure: no CDN termination, no client-side prompts, no RevLog rewrite, no unregistered service deployment. It is append-only and hash-chained.

The Crystal Map you see on this page is the intersection of UKL paths and DNR constraints — showing which nodes are sovereign attractors (Z+), which are extractive threats (Z−), and which are in active quarantine pending a decision (0.0.0).

• UKL codes are NOT folder paths — they are knowledge addresses independent of filesystem layout.
• DNR articles are NOT roadmap items — they are architectural laws above governance vote.
• This Vortex page is a READ-ONLY renderer of that law. It adds nothing and removes nothing.

FractalHundo is a read-only file-hash drift detector. It runs a SHA-256 check on all files listed in the current build MANIFEST and compares against the chain head in revlog/chain_head.json.

It does not write to RevLog — that is by design. Writing on detection would itself be a mutation risk. Instead:

• Any drift triggers an alert to Esperas (console output + log file).
• Esperas evaluates: intentional change (legitimate patch) or infiltration.
• Only Esperas can classify the drift and authorize a SEAL update if warranted.
• Unclassified drift blocks all further deployments — hard stop, no bypass.

FractalHundo runs locally on the Getac S0 rugged tablet. No cloud dependency. The manifest is the single source of truth — not the filesystem timestamp, not a CI pipeline result.

Command: python local_tests/fh_file_monitor.py

Gate 1 is a planned (not yet active) internal service layer. When active:

• Qdrant stores all distilled knowledge fragments as vector embeddings with UKL metadata tags.
• LightRAG builds a knowledge graph over Qdrant — entities linked by semantic edges, not just proximity vectors.
• The Vortex map would query /internal/vortex-feed (internal AI proxy, never public) and receive a live node topology serialized as JSON.
• The client would render this as an SVG or table — still no canvas, still no external resource.

Gate 1 will NOT become a public endpoint. The Vortex map will always be read-only, always offline-capable, always require Esperas SEAL before any topology update is reflected.

Until Gate 1 is sealed: what you see on this page is the static ground truth. It is not approximate — it is exactly the current classified state of the UKL-DNR topology.

Dynamic rendering of the sovereign immune map from a public surface would itself violate the immune membrane. The reasons Gate 0 is intentionally static:

• P0-4 compliance: Any fetch to an internal endpoint from a public page would create an observable side channel. Static HTML has zero runtime surface.
• Offline integrity: A visitor with no network sees the exact same map as a visitor with full connectivity. The truth does not depend on uptime.
• Audit simplicity: A static HTML file has a deterministic SHA-256. It can be committed, sealed, and verified by FractalHundo without ambiguity.
• No drift vector: JavaScript execution creates a drift surface — prototype pollution, supply-chain injection, eval paths. Static HTML eliminates the category entirely.

Gate 0 is not a limitation. It is the correct architectural posture for a public-facing projection of a sovereign internal system.