Canonical descriptions
Titles, status, taglines, summaries, links, and claim boundaries load from ParallaxArchiveCore. This page cannot silently rewrite project canon.
Parallax guided entry layer
See the whole field.
The Full Constellation helps a first-time visitor understand where to begin, how the systems relate, what evidence exists, who owns the work, and what remains architecture, demonstration, prototype, retained source, or planned proof.
ONE
FIELD
Human authorityVisible evidenceRepairable continuityHonest ownershipFIELD
Relationship ≠ integrationA line explains intended architectural relevance, not a deployed connection.
Presentation ≠ proofEvery node carries evidence and maturity states beside its story.
Discovery ≠ ownershipOnly currently attributed Parallax work enters this guided map.
Mock run ≠ executionThe ecosystem trace is fixed, synthetic, unsigned, and unable to act.
Start here
Five ways into the same field.
Choose the question closest to your interest. Each path highlights a sequence of canonical Archive records and explains the human outcome connecting them.
Choose a journey
The field will organize around your path.
Select one of the five routes to highlight its systems in the living map.
Living relationship map
One body of work. Visible boundaries between its organs.
Click any node to inspect its canonical Archive record, ownership basis, source state, maturity, evidence classes, and project claim boundary. Highlighted lines show the selected journey; every relationship remains descriptive rather than proof of deployed integration.
Loading canonical Archive records…
First ecosystem trace
Full Constellation Mock Proof Run 001.
Follow one bounded public-documentation mission through the intended Parallax chain. Every stage states what evidence exists and what the demonstration cannot establish.
FIXED SYNTHETIC TRACE
Evidence in this fixture
What remains unproven
No response selected.
Choose a bounded response to generate an unsigned demonstration receipt.
Select a response to produce a demonstration-only receipt preview.
Integrity architecture
The map is governed like the projects it describes.
The experience inherits Archive Core records rather than replacing them, keeps ownership metadata separate and inspectable, and carries a dedicated validation gate for journeys, evidence classes, project IDs, proof stages, non-action flags, and external-ownership exclusions.
Curated relationship layer
Journeys, ownership statements, evidence classes, map positions, and relationships live in one reviewable data file with an explicit version.
Front-door validation
CI checks Archive data, collaborator ownership, Constellation boundaries, all project-specific gates, public JavaScript, and the production build before deployment.
Choose the depth you need
The field explains. The Archive preserves.
Use this guided layer to understand the constellation, the Network to browse the wider public universe, or the six-terminal Archive to inspect canonical project records and artifacts.