Problem
Stage reports accumulate sequentially in the entity body. For an entity that goes through multiple feedback cycles, you can end up with 4+ stage reports appended one after another in a single markdown file. The entity body grows unwieldy:
- Hard to find the "current truth" of the entity
- The original spec gets pushed far down by accumulated history
- Diffs on the entity become dominated by appended report blocks
Workable at small scale (single-digit entities, few feedback cycles). Painful at larger scale.
Proposal
Folder-form opt-in for entities with feedback history:
- Convert `{slug}.md` to `{slug}/index.md` + sibling `reports/{stage}-{cycle}.md` files
- Trigger automatically when an entity is routed back via `feedback-to` more than once
- Or expose a CLI flag: `status --convert-to-folder `
Scale context
- Spacedock version: 0.11.2
- One entity this sprint accumulated 4 stage reports across 2 feedback cycles
Problem
Stage reports accumulate sequentially in the entity body. For an entity that goes through multiple feedback cycles, you can end up with 4+ stage reports appended one after another in a single markdown file. The entity body grows unwieldy:
Workable at small scale (single-digit entities, few feedback cycles). Painful at larger scale.
Proposal
Folder-form opt-in for entities with feedback history:
Scale context