Resolve inheritance between identified records
This commit is contained in:
@@ -1,6 +1,6 @@
|
||||
# Sequence Identity And Combination Implementation Plan
|
||||
|
||||
Status: implementation in progress; Stages 1–20 complete.
|
||||
Status: implementation in progress; Stages 1–21 complete.
|
||||
|
||||
Audience: a Luna coding agent implementing one numbered stage per prompt, in
|
||||
order. This plan starts at commit
|
||||
@@ -732,6 +732,11 @@ expansion phase, with values and inspection working together.
|
||||
Validation: all inheritance and cross-feature inspection tests,
|
||||
`go test -race ./internal/engine`, and the everyday check.
|
||||
|
||||
**Completion:** Activated identified-record inheritance after tier assembly,
|
||||
including nested collection relationships, ownership and inspection evidence.
|
||||
Verified inheritance/inspection regressions, `go test -race ./internal/engine`,
|
||||
and `./scripts/check.sh`.
|
||||
|
||||
## Stage 22 — Expose The Root-Owned Registration API
|
||||
|
||||
Scope: the settled facade surface and migration of in-repository callers.
|
||||
|
||||
Reference in New Issue
Block a user