0001 — Repository structure
Date: 2026-10-19. Status: accepted.
Context
Several teams of agents work in parallel on Astra (literature, data, code, interface). A clear organisation is needed so they do not get in each other's way, and everything must fit in the Git repository, with no server or external service.
Decision
- Top-level folders:
literature/(A2),data/(A9),interface/(A11),docs/andmissions/(A7); the Rust code (crates/,scripts/,Cargo.*files at the root) belongs to A10. Details inOWNERS.md. - Data: one YAML file per object in
data/. These files are the only source of truth. - The SQLite database (
data/astra.sqlite) is generated from the YAML files by the Rust tool; it is ignored by Git. - The Rust code is a "workspace" at the root of the repository, with one crate per tool in
crates/. - The interface site is generated by a Rust crate from the repository;
interface/contains only the templates and static files, and the generated site is not versioned.
Consequences
- Anyone can rebuild everything from the repository alone.
- Versioned files stay readable by a human and easy to review in Git.
- Any change to this structure requires a new decision.