Team & Process¶
The project runs as a multi-agent team. Each agent has a name and a narrow role. Stefan talks to Nora; Nora dispatches the right specialist.
Roster¶
| Name | Role | Profile |
|---|---|---|
| Nora | Chief of staff / orchestrator | — |
| Cleo | HR — defines roles & writes profiles | — |
| Iris | Business Analyst — runs requirements discovery | team/business_analyst.md |
| Theo | Solution Architect — designs the stack | team/solution_architect.md |
| Kit | DevOps / Platform — git, CI, docs site, infra | team/devops_engineer.md |
New roles are added as needed; Cleo drafts the profile before each new hire.
Backlog¶
Project work is tracked in GitLab Issues on the project's source repo (the public mirror disables Issues). Issues use type::*, priority::*, status::*, area::* label scopes.
Documentation¶
This MkDocs site is published to GitLab Pages on every push to main via .gitlab-ci.yml. Edit any page via the pencil icon — links route to the GitLab editor on the main branch.
Operations¶
- Deploy pipeline verification (2026-05-04) — what runs in CI, where it runs, how to debug a red pipeline.
- V1 → V2 upload spec — the cutover flow Stefan runs at V2 cutover: upload XLSX → reconciliation report → sign-off → re-run if needed. Operator-facing companion to the M15 ETL.
- V2 launch readiness — explicit go/no-go checklist Stefan ticks off before flipping from V1 to V2. Owners and verification steps per item; final sign-off line at the bottom.
- V2 smoke-test plan — step-by-step plan Stefan runs in the test environment before flipping V1, with ten test cases (Add Stringjob, mark Strung + email, mark Paid, catalogue moderation, reports, export, V1 upload, DE locale, tenancy, FADP DSAR), sign-off section, and failure-triage path.
- CHANGELOG generation — how to regenerate
CHANGELOG.mdfrom conventional-commits history with git-cliff before each release.