Skip to content

chore: surgical realization→implementation rename (system sense only) — implements #104 - #106

Merged
croadfeldt merged 1 commit into
mainfrom
chore/rename-realization-to-implementation
Aug 3, 2026
Merged

croadfeldt merged 1 commit into
mainfrom
chore/rename-realization-to-implementation

Conversation

@croadfeldt

Copy link
Copy Markdown
Owner

Implements the rename proposed in #104 (DCM foundations legibility). Not for merge without engineering sign-off — this is the concrete proposal to review against #104.

What it does — surgical, context-sensitive

Renames only the overloaded sense — "a system that implements UDLM" → implementation — so it stops colliding with the realize/Realized lifecycle. Same discipline as udlm #301. 67 replacements / 35 files, markdown-only.

Renamed (system sense): DCM/peer/conformant/valid/assessment/second/reference realization, realization-neutral, "DCM is one realization", "the realization owns/exposes/drives", realization-declared.

Kept (act/state — ~600 uses, untouched): request-realization (70), realize/Realized (613), vm/resource/db/class/native/partial/ordinary realization, during/before/post/mid-realization, PRV-003 (Realization), "IP Address Realization", "Provider Contract and Realization", and ADR filenames 025-scoped-class-realization / 027-policy-firewall-realization.

Left for your judgment (flagged, not renamed)

  • realization-layer — recurring; "a decision at the implementation layer." Likely → implementation-layer, but it's your control-plane vocabulary to rule.
  • "realization engines DCM already has" and "realization honors the disposition" — genuinely act-ish; left alone.

Verification

check_links 0 broken · check_estate_tokens 0 hits · act-sense preserved (request-realization 70→70, realize/Realized 613→613, ADR filenames intact).

Ties to the broader #104 proposal (prior-art positioning + legibility on-ramps) — this PR is just the rename half.

🤖 Generated with Claude Code

https://claude.ai/code/session_015GJFtLoW43JTABs3gGS6mR

… — implements #104

Implements the ADR-056-equivalent rename proposed in #104. Renames ONLY the
overloaded sense — 'a system that implements UDLM' → 'implementation' — so it
no longer collides with the realize/Realized lifecycle. Context-sensitive, the
same discipline as udlm #301. 67 replacements / 35 files. Markdown-only.

RENAMED (system sense): DCM/peer/conformant/valid/assessment/second/reference
realization, realization-neutral, 'DCM is one realization', 'the realization
owns/exposes/drives', realization-declared.

KEPT (act/state — ~600 uses, untouched): request-realization (70), realize/Realized
(613), vm/resource/db/class/native/partial/ordinary realization, during/before/post/
mid-realization, PRV-003 (Realization), 'IP Address Realization', 'Provider Contract
and Realization', ADR filenames 025-scoped-class-realization / 027-policy-firewall-
realization + their titles.

LEFT for engineering judgment (flagged, not renamed): 'realization-layer' (recurring —
a decision at the implementation layer; likely → implementation-layer, but it is the
control plane's vocabulary to rule); 'realization engines DCM already has';
'realization honors the disposition'.

Gates: check_links, check_estate_tokens — green. Not for merge without engineering
sign-off (#104).

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Signed-off-by: Chris Roadfeldt <chris@roadfeldt.com>
@croadfeldt
croadfeldt merged commit 68a394b into main Aug 3, 2026
4 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant