Design proposals and ADRs
Find a file
2026-05-15 01:06:51 +00:00
2026-05-13T0922-repair-sg-replication feat: add PPTX slide deck 2026-05-13 09:35:59 +08:00
2026-05-13T1640-task-bus-v2 Close proposal: Hive Task Bus v2 — Design Implemented 2026-05-15 01:06:51 +00:00
adr-build-sequence-opd-clinic.md adr: build sequence — OPD GP clinic as next vertical slice 2026-05-14 19:55:01 +08:00
README.md chore: add task-bus-v2 proposal and repo README 2026-05-13 16:52:02 +08:00

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 .md file directly in proposals/ 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

  1. Does the folder name follow the ISO datetime convention?
  2. Is the proposal ready for review (at least draft status)?
  3. If it references an implementation repo, note it in the document header.

Last updated: 2026-05-13