Arbora ecosystem

Build agents and connect source systems through Arbora, with Medulla as the durable knowledge engine. The ecosystem is developed inside Medulla as changesets, a code graph, and requirement records, served through Arbora MCP.

Start with work waiting to be built

The public specification report lists owner-native specs, the share of requirements each has delivered, and the requirements still open. Expand a specification to pick one. Each owner repository holds the full design, implementation tasks, and test contract. A status claim needs public evidence; publication alone does not mean implementation or acceptance.

Contribute with the shared skills

The path is spec-driven, from constitution to release. Each step names its skill and the files it writes.

  1. Constitution. Read the constitution. Every plan checks against it.
  2. Route. Pick the owner repository with the ecosystem boundaries and arbora-development. Choose an open (SPECIFIED) row in Canopy.
  3. Specify. speckit-specify and speckit-clarify write specs/<id>/spec.md: user stories, Given/When/Then scenarios, and FR- and SC- labels mapped to row IDs.
  4. Clarify. Resolve every [NEEDS CLARIFICATION] marker in spec.md before you plan.
  5. Plan. speckit-plan writes plan.md. Add contracts/ for cross-repository seams, data-model.md, quickstart.md, and research.md when unknowns remain.
  6. Tasks. speckit-tasks writes tasks.md. Each line reads - [ ] T001 [P] [US1] <ROW-ID>.
  7. Analyze and checklist. speckit-analyze checks consistency and writes checklists/requirements.md.
  8. Implement. sdd-implementer builds each task. Run the repository gates.
  9. Land. Open a pull request whose commits carry a Spec: <ROW-ID> trailer and a bound test. Do not edit status.json by hand.
  10. Release. Landed rows ship in the next release bundle.

Standards: constitution, spec standard, spec templates, and Canopy. Install the skills with pip install universal-skills, then install-skills --all-detected --symlink. Read the full contribution path.

Core projects

Seven core projects. Arbora is the one door: served operations, admission, authentication, and MCP and A2A serving. It hosts Overstory. Meristem is the in-run harness and holds no store. Medulla owns durable knowledge. Scion SDK holds connector contracts and transports. Tuig and Axil are operator surfaces on the same boundary.

Related contributor repositories