Close EDCM skill and msdmd compliance repair - #22
Conversation
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: d8088b0858
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
|
|
||
| - [ ] Reconcile remaining MODULE_BUILD, DOCS, CAPABILITIES, BOUNDARIES, CONTRACTS, DEPENDENCIES, OWNERS, and skill-lib declarations. | ||
| - [ ] Install repo-local skill-lib and add real drift/msdmd gates; EDCM currently has no `.agents/skills/` tree or callable local runner. | ||
| All required stack-repair items are implemented in the current tree. No runtime architecture repair remains open. The package remains `0.1.0` and Alpha; release promotion requires empirical evidence and an explicit release decision rather than additional repository-compliance claims. |
There was a problem hiding this comment.
When contributors follow the repo's required read-first docs, this closure statement now conflicts with still-current instructions: CLAUDE.md:240 says not to claim repo-local skill drift or msdmd success, CLAUDE.md:247, README.md:283, and docs/integrity-gates.md:78 still list those gates as unfinished. Marking all stack-repair items complete here without updating those canonical docs leaves compliance/release decisions dependent on which required document was read, so either the ledger should stay unresolved or the other docs should be updated in the same change.
Useful? React with 👍 / 👎.
| `meta-module-build` is an application of [msdmd](../msdmd/SKILL.md). It uses self-declared metadata to keep a proposed module's purpose, surfaces, dependencies, boundaries, tests, and rollout notes visible beside the files that implement it. | ||
|
|
||
| ## Required principle | ||
| Read `msdmd/SKILL.md` first. This skill inherits the block syntax, parser contract, and visible gap-reporting requirement. |
There was a problem hiding this comment.
When an agent uses this repo-local meta-module-build skill for EDCM-native module work, these lines require reading ../msdmd/SKILL.md / msdmd/SKILL.md, but the repo-local skill subset only contains meta-module-build and the-interdependency and has no .agents/skills/msdmd directory. Because this commit replaces a self-contained local skill with one that inherits an unavailable prerequisite, contributors cannot follow the required parser/block contract from a normal checkout unless they already have a separate canonical skill-lib checkout, so either vendor the msdmd skill dependency or keep this local copy self-contained.
Useful? React with 👍 / 👎.
| | `requires` | Comma-separated MODULE_BUILD ids this one depends on. | | ||
| | `since` | Date/version added. | | ||
| | `unresolved` | Comma-separated unresolved items. | |
There was a problem hiding this comment.
When a new EDCM-native module is scaffolded from this repo-local skill, it now says requires, since, and unresolved are optional, but the EDCM native metadata gate still treats them as REQUIRED_FIELDS and fails non-hmmm operational fields in tools/check_metadata_contracts.py:36-56. Following the skill in a normal contribution can therefore produce metadata that fails CI; keep these fields in the required schema or document the EDCM-specific override next to the skill.
Useful? React with 👍 / 👎.
1 participant
What changed
Completes the required post-PR-#21 compliance closure in the ordered repair sequence.
meta-module-buildskill with the exact complete directory from pinnedThe-Interdependency/skill-lib@d0036c6c3a449f5a1213e3289dceb1c43263cb52.edcm_msdmd.tscollection point expected by the permanent byte-for-byte comparison gate.codex-handoff/2026-07-12-stack-repair/IMPLEMENTATION_STATUS.mdso merged PRs Consume canonical UCNS bridge and certification evidence #20 and Install pinned skill-lib subset and metadata compliance gates #21, the actual compliance closure, the preserved empirical frontier, and the cryptographic-authenticationhmmmare accurately recorded.No runtime implementation, measurement formula, canon file, result schema, UCNS adapter, METAPAT adapter, or dependency pin changes.
Root cause
PR #21 intentionally introduced the permanent compliance workflow before committing its generated collection artifact. It also vendored a locally expanded
meta-module-buildspecification rather than the byte-identical pinned canonical file. Consequently:edcm_msdmd.tsdid not exist;.agents/skills/meta-module-build/SKILL.mddiffered from the pinned source.Validation
The branch was produced only after the following completed successfully:
check_consumer_drift.pywith strict SHA and vendored-subset enforcement;python tools/check_metadata_contracts.py;python -m edcm.integrity;pytestsuite;twine check dist/*.The permanent GitHub Actions CI and skill-compliance workflows are the merge evidence gate.
Boundaries preserved
Contact convergence, DA geometry correlation, cadence admission from text, and semantic-label-to-operating-state inference remain non-operational. UCNS evidence does not transfer proof status into EDCM empirical validity.
NA != 0remains enforced.hmmm
UCNS evidence digests establish canonical content identity but not cryptographic producer signatures or authenticated transport. After this repository-compliance closure, the substantive unfinished phase is empirical validation against fixed corpora and declared falsifiers.