Task: Bind the standard profiles to the configuration entities that carry none
Table of Contents
This page documents a task in the Model the ORE report configuration as entities story. It captures the goal, current status, acceptance, and any notes or results.
1. Goal
Every entity model authored from this environment names a catalogued profile instead of hand-authoring its variability features, and the generated surface follows from that binding.
2. Status
| Field | Value |
|---|---|
| State | DONE |
| Parent story | Model the ORE report configuration as entities |
| Now | Nothing. |
| Waiting on | Nothing. |
| Next | Nothing. |
| Last touched | 2026-10-01 |
3. Acceptance
- check_model_drift.py reports no new contradictions and the eight entities bind a profile
- codegen regenerates the affected components with no drift beyond the intended profile-driven surface
- the build succeeds and the affected component tests pass
4. Plan
(Implementation strategy. Written when work starts; key decisions
are distilled into the parent story's * Decisions at close, but the
plan itself stays — it is the historical record of what we did.)
5. Measurements
Every number this task claims about a tree, with the command that produced it
and the commit it was measured at. A number without both is not a measurement,
because a clean-up record describes a tree and trunk moves under a branch: a
consumer count, a gate's component count and a suite's size all change with no
code changing, and the reader of a bare number cannot tell which tree it came
from. Where the raw output matters, put it in an evidence/ file beside the
task and name that file in the Command column.
| What | Value | Command | Commit |
|---|---|---|---|
6. Notes
7. Test Scenarios
Manual QA scenarios (scaffolded via compass add test_scenario)
that verify this task. Link
new ones here as they're created; the scenario doc itself links back
via its "Verifies task" field.
| Scenario | State | Notes |
|---|---|---|
8. PRs
| PR | Title |
|---|---|
| #2481 | [codegen] Bind the standard profiles to the entities that carried none |
9. Review
| Comment summary | File | Decision | Notes |
|---|---|---|---|
10. Result
Delivered by PR 2481, merged 2026-10-01; this record was left open and is
closed now. Nine entity models authored from this environment bound no
profile: the analytics stress library, scenario and shift, the refdata curve
definition, segment and quote, and the reporting report analytic parameter,
report market binding and risk report config. All nine match one shape and now
bind uuid-identified-lookup, dropping the has_tenant_id the profile
supplies. The binding enabled the shell command and event test facets, so
each gained a command unit, its recipe and an event test, while the domain,
repository, service and SQL output stayed byte-identical. Evidence from the
PR: check_model_drift.py 248 of 411 models bind a profile (was 239);
check_component_drift.py --all clean; affected tests 7/7 passed. Models
owned by other environments were left to their owners.