Story: Codegen: mustache-to-address rename + junction codegen rollout

Table of Contents

This page documents a story in Product backlog — next. It captures the goal, current status, acceptance criteria, and the tasks that compose it.

Goal

Finish the codegen tech-debt tail left by Sprint 23's Retire legacy codegen profile system story and its follow-up's B7 task, both DONE: rename templates to MASD address form, and roll junction codegen out beyond its single proven pilot (tenor_convention_resolution).

Status

Field Value
State BACKLOG
Parent sprint None (product backlog)
Now Not yet started. Split out once the parent stories closed so this tail didn't keep them open.
Waiting on Nothing.
Next Either task is independently startable when pulled into a sprint.
Last touched 2026-07-20

Acceptance

  • The 50 entity-facet .mustache templates renamed to MASD address form, byte-identical generation preserved.
  • Junction codegen (domain/generator/repository) rolled out to the other has_tenant_id junctions beyond tenor_convention_resolution, hand-authored equivalents retired.

Tasks

Task State Start End Description
B9: Rename .mustache template files to MASD address form BACKLOG     Rename the 50 entity-facet .mustache templates to address form (ores_cpp_domain_class_header.mustache) atomically with their :tangle targets, core.py get_schema_template_mappings, and doc-string references; verify byte-identical generation across the graph path and the legacy schema path.
Migrate remaining junctions to generated C++ (roll out beyond tenor_convention_resolution) BACKLOG     Regenerate the other has_tenant_id junctions' domain/generator/repository via the now-working junction codegen path, retiring their hand-authored equivalents – proven only against tenor_convention_resolution so far.

Decisions

Out of scope

Emacs 29.3 (Org mode 9.6.15)