Repository navigation
Development
Daniel Brown edited this page Oct 14, 2026
·
1 revision
Start with the development guide and contribution guide. Select defined work from live issues and keep changes focused and reviewable.
| Topic | Source |
|---|---|
| Source layout and runtime files | Source layout |
| Shell/Compose/static checks | Local validation |
| Building and disposable runtime regression tests | Build/runtime |
| Optional trusted proxy CA build secret | Build-network CA |
| Exact-head CI and review evidence | CI evidence |
| Manual versus synthetic acceptance | Validation matrix |
| Security reporting | Private reporting policy |
| Product direction and dependencies | Roadmap |
| Accepted choices and outstanding decisions | Architecture decisions |
| Wiki review/export/publish separation | Wiki synchronization |
| Issues, labels, milestones and project status | Repository governance |
CI must use harmless fixtures without personal Claude/Mem secrets. Static checks and version output cannot stand in for real OAuth, host or hardware acceptance. Inspect the run's exact head SHA and resolve failures/warnings before claiming success.
The foundation source was merged through PR #1; green CI does not establish product acceptance or authorize a release. No license has been selected, and distribution still requires an owner decision.
Procedures live in the reviewed canonical repository guides. Wiki pages provide navigation and do not add runtime capabilities. Security reporting · Roadmap