Repositories
Where the code and the specifications actually live.
Alexandria is three repositories.
| Repository | What it holds |
|---|---|
| alexandria-api | The Rust workspace: alexandria-core (the domain), alexandria-http (the axum REST/JSON server), and alexandria-ffi (the C ABI). |
| alexandria-ui | The Flutter desktop front-end, and the release pipeline that packages it together with the core for Windows and Ubuntu. |
| alexandria-docs | This site. |
One more repository sits next to those three without being part of Alexandria:
| Repository | What it holds |
|---|---|
| heimdall-api | The identity API Alexandria validates tokens against in external mode. Its documentation site covers its overview, architecture, API reference, and requirements. |
The specifications
Alexandria is specified before it is built, and both code repositories carry
the same two-tier document set: informal initial/ documents for context, and
formal requirements/ documents for the normative detail.
Core — alexandria-api
| Document | What’s in it |
|---|---|
| Brainstorm | The original free-form notes. |
| Project Overview | What the project is, who it is for, and how success is measured. |
| Technology Stack | The informal stack decisions. |
| Workflow | How one use case is delivered, step by step. |
| Business Rules | Domain entities, relationships, and the BR-xx rules. |
| Vision Document | Stakeholders, positioning, and the F-xx features. |
| System Requirements Document | The FR-<AREA>-xx and NFR-xx requirements, the data model, and traceability. |
| Use Case Specification Document | The UC-xx use cases, their flows, and their AF-xx alternatives. |
| Development Workflow Document | The branch pattern, issue lifecycle, and Definition of Done. |
| Testing Specification Document | How tests are written, named, and run. |
| Technology Stack Document | The single source of truth for every technology and version. |
| Operations & Infrastructure Document | Layout, configuration, logging, startup checks, and the IR-xx platform requirements. |
Front-end — alexandria-ui
The front-end repository carries the same set, scoped to the desktop application.
| Document | What’s in it |
|---|---|
| Brainstorm | The original free-form notes. |
| Project Overview | What the application is and who it is for. |
| Technology Stack | The informal stack decisions. |
| Workflow | How one use case is delivered, step by step. |
| Business Rules | Domain entities, relationships, and the BR-xx rules. |
| Vision Document | Stakeholders, positioning, and the F-xx features. |
| System Requirements Document | The requirements, the data model, and traceability. |
| Use Case Specification Document | The UC-xx use cases and their flows. |
| Development Workflow Document | The branch pattern, issue lifecycle, and Definition of Done. |
| Testing Specification Document | How tests are written, named, and run. |
| Technology Stack Document | Every technology and version. |
| Operations & Infrastructure Document | Layout, configuration, logging, and the IR-xx platform requirements. |
Tracking progress
Work is tracked on the Alexandria API project board, grouped into milestones that mirror the feature groups in the System Requirements Document. Each repository’s README carries a live backlog table whose issue references render their own open or closed state.