The organization profile introduces the Arbora ecosystem.
The product family is Overstory (browser UI), Tuig (terminal UI / CLI),
Scion SDK (connector contracts), Meristem (in-run agent harness), and
Axil (desktop GUI), alongside Arbora and Medulla.
Repository links use the canonical product names; package/import identifiers and spec
prefixes stay unchanged. The Tuig command remains tuig.
The Arbora Architecture Explorer is the canonical, always-current
architecture view: every spec row of every organization repository with specs/,
with its status, on the part it builds. It is generated by the pipelines
scripts/architecture_explorer generator and stamps its build time and each
repository's head commit.
The repositories and skills map links the public owners,
universal-skills kit, and canonical arbora-development instructions.
The specification status report is generated from committed
specs/*/status.json in the public owner repositories and this organization hub. It shows, per
repository and per specification, how many requirements are delivered and which are still open. The contribution
guide points contributors to the owner-native design, tasks,
tests, and reusable development skills.
The Pages workflow rebuilds the explorer and the report
from public main branches on every merge to a core repository's main branch, and at least
every 30 minutes, and also on each hub change and on manual dispatch.
The report is a snapshot with source revisions, not a live CI feed. SPECIFIED
is the build queue; LANDED and ACCEPTED require separate public evidence.
Each requirement ID is defined in its owner spec's requirements.md and carries its own
delivery state in status.json. A requirement counts toward the completion percentage only
when its entry cites an implementing commit on the owner repository's default branch.
To render locally, clone the public owner repositories under one directory and run
python scripts/public_spec_report.py --checkouts-root <directory> --repo .github=. --output site/spec-status.html.
See python scripts/public_spec_report.py --help for explicit checkout paths.
The runtime diagram is one file, maintained in Medulla, and referenced by URL. Every page that shows it links the explorer: Explore the live architecture.
