NEXAH — Research & Framework

This repository preserves the research, framework, Orientation Language, experiments, applications, governance and historical development of the NEXAH Orientation Ecosystem.

Public path: Discover NEXAH · Use the Visitor Guide · Try NEXAHEDRON · Inspect ORION

It is not the public landing page, the ORION repository or the Human-facing Workspace. It is the scientific workshop and long-term record behind those public chapters.

Understanding before action.

NEXAH is an evidence-bound orientation ecosystem for making relationships, limits, and possible transitions between bounded representations inspectable and navigable. It exists because knowledge is distributed across many maps, models, disciplines, and forms—and moving responsibly between them is itself a problem of orientation.

NEXAH does not replace knowledge, domain expertise, or human judgment. It does not claim universal truth or authorize action.

---

Choose Your Entry Point

I want to…	Begin here
Enter the public Experience	nexah.de — the public entrance to NEXAH
Inspect the certified deterministic Core	NEXAH-ORION — structural representation, relations, navigation, orientation map and certified expression
Try one Human-facing Orientation Session	NEXAHEDRON — the reference Workspace
Inspect the Experience source	NEXAH-Experience — public presentation, Library, Living Atlas, Laboratory and Reading Spaces
Understand the purpose and principles	Ecosystem Constitution v1.0 · Governance Index · NEXAH Manifesto
Read the published specification	Orientation Language
Use or develop the software	Orientation Kernel
Inspect research and evidence	Evidence Atlas · Research Portal
Explore Works, journeys, or editorial practice	Begin with THE ATLAS OF ATLASES · Public Library on Are.na · Library Architecture & Registry · Editorial Operating System
Evaluate a domain application	Applications
Inspect Orientation Translation pilots and methodological evidence	Applications / Orientation Translation

For the complete directory-level view, use the Repository Map. Cross-system reader documentation is indexed under Documentation.

---

Repository Organization

The six subsystems coordinate without sharing one authority:

The diagram shows what each subsystem is responsible for. The table records where its authority stops:

Subsystem	Authority boundary
Research	Does not define released semantics or establish universality
Orientation Language	Does not execute implementations or establish domain validity
Implementations	Do not redefine semantics; conformance is explicit, never assumed
Applications	Do not generalize beyond admitted evidence or redefine the language
Living Library	Its Registry governs editorial identity, not OLS semantics
Editorial Operating System	Editorial Governance does not replace Specification Governance

The central distinction is simple: the Orientation Language defines semantics; implementations execute behavior; conformance must be demonstrated.

The detailed responsibility and relationship map lives in Architecture.

The adopted Ecosystem Constitution v1.0 is the highest governance document. The six repository subsystems are concrete responsibility areas beneath that constitutional baseline; they are not additional constitutional Houses. Earlier candidate work remains preserved as non-canonical historical evidence in Constitution Review 01.

---

Current State

• Orientation Language 1.0 is published as the canonical semantic authority.
• Orientation Kernel v0.7 is maintained as the current implementation track.
• Research remains active, scoped, and evidence-bound.
• Reference applications for Network Orientation and IEEE Geometry are maintained.
• Library and Editorial infrastructure operate within documented human-governance boundaries.

These are different maturity statements, not one repository-wide certification. The existing tags, public releases and current package version are explained in Release and Version History; no version in one responsibility area versions the entire ecosystem. The current frozen repository baseline is NEXAH Framework 1.0 with the distinct annotated tag framework-v1.0.0 at commit 87f438d05a8841166ea32719b9fda807acf5cb6b. This identity applies only to the Framework repository and does not synchronize independently versioned artifacts. Later documentation commits do not move or reinterpret the frozen tag.

---

Run NEXAH

Install the current Python implementation:

python -m venv .venv
source .venv/bin/activate
python -m pip install -e .

Run one declared Network Orientation case:

nexah orient-network APPLICATIONS/datasets/supply_chain.json \
  --focus normal_operation \
  --target system_disruption \
  --domain supply-chain \
  --recorded-at 2026-07-13T22:45:00+00:00 \
  --format brief

The result is an inspectable report over the supplied representation—not a real-world risk judgment or authorization to intervene.

Continue with the Kernel Start, browse Applications, or inspect the executable NEXAH Demonstrator.

---

Evidence and Limits

NEXAH keeps the following states separate:

representation
→ orientation
≠ recommendation
≠ authorization
≠ execution
≠ observed outcome

The current repository supports typed orientation contracts, inspectable reference applications, explicit provenance and claim boundaries, deterministic replay, and guarded evidence handling.

It does not currently claim:

• universal transition laws or a closed theory
• automatic OLS conformance for any implementation
• broad real-world validation or calibrated uncertainty across domains
• causal intervention guarantees or autonomous execution authority
• production readiness or one unified runtime for every repository lineage

Complete implementation status and limitations are maintained in System State. Before using sensitive, personal, or operational data, read Safety and Misuse Boundaries.

---

Repository Structure

NEXAH/
├── RESEARCH/                     evidence
├── ORIENTATION_LANGUAGE/         semantics
├── nexah/                        implementations
├── APPLICATIONS/                 domain use
├── LIBRARY/                      editorial communication
├── EDITORIAL_OPERATING_SYSTEM/   governance and controlled execution
└── docs/                         cross-system reader documentation

Supporting architecture, validation, prototype, and historical areas are documented in the full Repository Map. The Governance Index records the authority order from Constitution through Governance and Architecture to implementation and derived artifacts without changing the six-subsystem architecture.

---

Contributing, Citation, and License

Begin with the Contribution Guide and the Code of Conduct. Contributions should enter through the subsystem responsible for the proposed work and preserve its local evidence, ownership, provenance, and review rules. Architectural status belongs in Architecture; normative language work belongs in Orientation Language. Release and tag meanings are recorded in Release and Version History. Current public-launch execution state is recorded once in Launch Status.

Software is released under the Apache License 2.0. Original NEXAH documentation and repository research material are released under CC BY 4.0. Third-party and source-derived material retains its stated license and provenance. See the complete Licensing Scope and CITATION.cff.

---

Thomas K. R. Hofmann

NEXAH Orientation Ecosystem · 2026