Story: Codegen legacy-profile retirement follow-ups
Table of Contents
This page documents a story in Sprint 23. It captures the goal, current status, acceptance criteria, and the tasks that compose it.
Goal
Finish part of the codegen tech-debt tail that Retire legacy codegen profile system; add junction support to physical-space codegen deliberately left BACKLOG once its own acceptance was met: retire the split-model backward-compatibility scaffolding.
Status
| Field | Value |
|---|---|
| State | DONE |
| Parent sprint | Sprint 23 |
| Now | Closed DONE 2026-07-20: B7 (split-model backcompat removal) DONE in jolly_knuth (PR #1652), absorbing the duplicate table-model-type task as ABANDONED. B9 and the junction-codegen rollout split into Codegen: mustache-to-address rename + junction codegen rollout in the product backlog. |
| Waiting on | Nothing. |
| Next | Nothing. |
| Last touched | 2026-07-20 |
Acceptance
- Split-model (table + entity template) backward-compatibility scaffolding removed once every model is migrated to domain_entity.
- The table model type branch removed from the generator once no _table.org files remain.
Tasks
| Task | State | Start | End | Description |
|---|---|---|---|---|
| B7: Remove split-model backward-compatibility once all models migrated | DONE | 2026-07-19 | 2026-07-20 | Retire the dual-pathway scaffolding (table + entity templates, inert defensive defaults) added by B1-B3 for coexistence, once every model is migrated to the unified domain_entity format and verified byte-identical. |
| Retire the table model type: remove the table branch from the generator and profile matrix | ABANDONED | 2026-07-20 | Absorbed into B7, which had substantially overlapping scope and was done first. Moved in from the now-closed Decommission ores.codegen.table model type story — was originally out of scope here (Step 7), pulled in at sprint 22 close for the same reason. |