feat: UUIDv4 IDs, GTD conventions, backdate ROADMAP

- memory-id-generate now produces UUIDv4 (id-87917806-...)

- GTD Conventions added to programming-standards.org

- ROADMAP.org v0.3.0 tasks have :ID:, :CREATED:, :LOGBOOK:, CLOSED:

org/programming-standards.org

@@ -59,6 +59,31 @@ If a LOADER ERROR or reader-error occurs:
 
 Rationale: The two tracks prevent the two failure modes we have observed. Writing implementation code directly in Org (without REPL prototyping) produces syntax errors that require external tools to debug. Skipping Org-first test writing produces code without verified success criteria. The split is not bureaucratic — it is the mechanism by which both failures are prevented.
 
+** GTD Conventions
+
+Every task headline in the project's ROADMAP.org and gtd.org follows these rules:
+
+1. **:ID:** — generated by ~memory-id-generate~ (UUIDv4 with ~id-~ prefix), never written manually. Use ~(memory-id-generate)~ in the REPL to produce one.
+2. **:CREATED:** — ISO-8601 timestamp: ~[2026-05-02 Sat 14:30]~. Set when the headline is first created, never changed.
+3. **:LOGBOOK:** — each state transition is logged: ~- State "DONE" from "TODO" [2026-05-02 Sat 15:00]~.
+4. **CLOSED:** — set when the task reaches DONE: ~CLOSED: [2026-05-02 Sat 15:00]~.
+5. **TODO keywords** follow the standard sequence: ~TODO~ → ~NEXT~ → ~IN-PROGRESS~ → ~DONE~ / ~BLOCKED~ / ~CANCELLED~.
+6. **The Agent** updates these automatically during Phase E of the lifecycle. The human never needs to write a UUID or timestamp manually — the agent generates and inserts them.
+
+Example:
+
+#+begin_src org
+*** DONE Event Orchestrator
+:PROPERTIES:
+:ID:       id-4a2b9c8f-3d7e-4f12-a9b0-1c2d3e4f5a6b
+:CREATED:  [2026-05-02 Sat]
+:END:
+:LOGBOOK:
+- State "DONE" from "TODO" [2026-05-02 Sat 18:00]
+:END:
+CLOSED: [2026-05-02 Sat 18:00]
+#+end_src
+
 * Implementation
 
 ** Standards Enforcement