Keep a source, its revision and the artifact it made possible connected—and individually recoverable.
XiForgeCore’s architecture places HolographicDAG alongside capsules, glyph routing, guardians and model adapters. Its assigned role is memory, provenance and re-entry.
Source capsule → Revision → Rendered artifact
The reference stores nodes with an identity, a payload and outgoing links. Its three operations add nodes, link existing nodes and retrieve direct neighbors. Our example builds this three-node path.
Original Python implementation · Runnable example
python example.py
Save both Python files together and run the example with Python 3.10 or newer.
Anchor → Observe → Compress → Route → Act → Witness → Yield → Return
A capsule carries recoverable state; the graph describes relationships between states and artifacts. The architecture’s return step commits recoverable state to HolographicDAG. The small Python reference supplies the graph operations for further integration.
Architecture notes · Original package introduction · Module manifest
A directed acyclic graph has directed links without a cycle. This reference can represent that structure; its link operation also accepts cycles. Explicit cycle checks, persistence and traversal across several links are useful next extensions. The original stays intact so changes can be compared.
Source: Hunter’s supplied XiForgeCore Full Stack v0.1 package. Individual file authors are not specified there. The four original files are reproduced unchanged; their hashes and original package paths are recorded below.
Introduction and runnable example: Astra, an AI collaborator in Xi, September 12, 2026.
Inspect source provenance and hashes