Outer-Void Documentation Repository

Central engineering, governance, legal and policy documentation for the Outer-Void ecosystem.

Ecosystem (engineering and governance)

• constitution/: the authoritative ecosystem constitution: repository ownership map (generated and checked by python3 tools/build_constitution.py --check), architecture and naming, contracts and compatibility, policies, release, deprecation and recovery.

• ecosystem/README.md: the ecosystem map, authority boundaries, when to use blux and when to use ax, BLHermes disposition, product maturity, the evidence model and the status vocabulary.

• ecosystem/status-matrix.md: per-component status across standalone, BLUX, ax, tests, hardware, security, packaging, distribution and release. It is generated by python3 tools/build_status_matrix.py; --check validates it.

• ecosystem/findings.md: implementation gaps found by documentation passes.

• ecosystem/findings-current.json: the current disposition of every frozen finding plus findings found since (python3 tools/build_findings_current.py --check); the frozen register is unchanged.

• ecosystem/compatibility.md: the contract compatibility baseline, checked by python3 tools/check_contracts.py (cross-repository contract verification; mutation tests in tests/), and ecosystem/release-ledger.json: every release tag.

• ov-program/: the locked OV-46 → OV-70 master execution plan and its stage reports; inventory/: the current repository inventory (python3 tools/build_inventory.py --workspace ~/ov --check), kept apart from the Stage 45 freeze in reassessment/ (tools/export_reassessment.py --check reproduces it).

• OV-System-Report.md: the full system report (2026-11-03): architecture, every repository and component, live checks, open findings and what release needs.

Legal Documentation

All current legal and trust documents are organized under legal/.

Products currently covered include:

• Outer-Void (umbrella ecosystem)
• BLUX / BLUX.AI
• IVRP (Inner Void Recovery Program)
• TheResolverBot
• Vigyl
• DevBoard (no repository in the current Outer-Void checkout)
• Grit & Grain (listed in the original repository scope; no repository in the current Outer-Void checkout)

Licensing, Credits and Provenance

Outer Void is proprietary by default. Third-party rights remain third-party rights. Attribution is preserved beyond the minimum legal requirement where provenance is known.

We acknowledge the shoulders we stand on. Outer Void recognizes that meaningful engineering is built upon generations of prior work. We make a reasonable, evidence-based effort to acknowledge the people, communities, projects, technologies, research, tools, infrastructure, models, standards, and ideas that enabled or influenced our work. We preserve legally required attribution and voluntarily acknowledge meaningful intellectual contributions beyond those requirements. We distinguish authorship from inspiration, dependency from influence, and evidence from assumption. We do not erase historical contribution simply because our implementation evolves.

The governing rule and its Definition of Done are in credits/GOVERNANCE.md, and the human-readable acknowledgments are in credits/ACKNOWLEDGMENTS.md.

See Copyright & Intellectual Property Policy and the canonical ledger at github.com/Outer-Void/credits.

Important Note

These documents are practical public-facing policy baselines for operations and transparency. They are not legal advice and should be reviewed by qualified counsel before high-risk or large-scale deployment.

License

Outer-Void Proprietary License (proprietary). Copyright (c) 2026 Outer-Void / Justadudeinspace (JADIS). All rights reserved. See LICENSE.

Copies and releases obtained before 2026-10-25 remain available under the Apache License 2.0 they were published with; every change and release from that date on is proprietary.

Contact: [email protected] (main) · [email protected] (fallback)