Design proposals and ADRs
| 2026-05-13T0922-repair-sg-replication | ||
| 2026-05-13T1640-task-bus-v2 | ||
| adr-build-sequence-opd-clinic.md | ||
| README.md | ||
Proposals — Agent Read Me First
Read this before creating or modifying anything in this folder.
Folder Naming Convention
Every proposal folder must follow this format:
<ISO datetime>-<short hyphenated title>
Examples:
2026-05-13T1640-task-bus-v2/2026-05-13T0926-repair-sg-pitch-deck/
Rules:
- Datetime in ISO 8601 format:
YYYY-MM-DDTHHMM(24-hour, local time) - Short title: lowercase, hyphen-separated, concise
- No trailing slash in documentation references
File Structure
- Single-file proposals: place
.mdfile directly inproposals/root - Multi-file proposals: create a dated subfolder, place all files inside
What Goes Here
- Architecture proposals
- System redesigns
- Infrastructure changes
- Any design that needs review before implementation
What Does NOT Go Here
- Code — code lives in
thefivjs/repos - Daily logs — those go in
memory/ - Completed projects — archive or link to implementation repo
Before Committing
- Does the folder name follow the ISO datetime convention?
- Is the proposal ready for review (at least draft status)?
- If it references an implementation repo, note it in the document header.
Last updated: 2026-05-13