Skip to content
This repository was archived by the owner on Jul 29, 2026. It is now read-only.

Add EDCM Canon v2 proposal (three-layer architecture, lensing-as-structure) - #19

Merged
erinepshovel-code merged 1 commit into
mainfrom
claude/add-pagination-AMpmi
May 1, 2026
Merged

erinepshovel-code merged 1 commit into
mainfrom
claude/add-pagination-AMpmi

Conversation

@erinepshovel-code

Copy link
Copy Markdown
Collaborator

Summary

  • Adds canon_eng/canon_v2_proposal.md — the architectural specification for EDCM Canon v2
  • Extends the two-layer system (Operator + Behavioral) with a third Content (flesh) layer, each layer getting exactly the embedding machinery its substrate demands: UCNS for bones, none for markers, ZFAE for flesh
  • Introduces the lensing-as-structure principle: where metric names overlap across layers, each layer produces an independent reading and cross-layer disagreement is a diagnostic signal, not a conflict

What this document contains

  • §0 — Status of prior canon (v1 remains frozen; v2 extends)
  • §1 — Eight locked architectural decisions (three-layer table, lensing principle, 11D Behavioral, three trajectory paths M/B, Content 10D schema, ternary Bridge, zero-dep protocol inversion, C formula repositioning)
  • §2 — Repository layout for edcmbone and interdependent-lib
  • §3 — Eight open questions with provisional defaults (speech-act enum, rating frames, rating range, epistemic overlap, conservation, BoneEmbedder shape, ContentEmbedder shape, marker embedding)
  • §4 — Falsification anchors for iteration
  • §5 — Migration notes (v1 files stay, edcm_metrics.py as seed, interdependent-lib checklist)
  • §6 — Provenance
  • §7 — hmm-tagged deferred items

Status

Proposal, not yet frozen. §3 open questions must resolve before canon_v2_freeze.md is written.


Generated by Claude Code

@erinepshovel-code

Copy link
Copy Markdown
Collaborator Author

@codex[agent] @claude[agent] @claude @grok

@erinepshovel-code
erinepshovel-code marked this pull request as ready for review May 1, 2026 23:56
Copilot AI review requested due to automatic review settings May 1, 2026 23:56
@erinepshovel-code
erinepshovel-code merged commit 4c3e62e into main May 1, 2026
1 of 2 checks passed
@chatgpt-codex-connector

Copy link
Copy Markdown

Thanks — I checked the trigger and PR metadata.

@codex[agent] @claude[agent] @claude @grok appears to be a broad agent mention without a concrete change request, review comment, or CI failure to act on. Given the provided context, there’s no specific follow-up I can safely implement yet.

If you want me to take action, reply with one explicit instruction, for example:

  • “Address reviewer comment X”
  • “Tighten section §3 defaults in canon_v2_proposal.md
  • “Run checks and fix CI failures”
  • “Draft a follow-up PR that resolves open question #N”

View task →

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

Adds a new Canon v2 proposal document describing an expanded EDCM Canon architecture (three-layer measurement model + “lensing-as-structure”) and outlining intended repo/module organization and migration notes.

Changes:

  • Introduces canon_eng/canon_v2_proposal.md as the architectural specification for Canon v2.
  • Defines a three-layer model (Operator/Bones, Behavioral/Markers with trajectory extension, Content/Flesh) and a ternary Bridge concept.
  • Documents proposed repository layout, dependency inversion via Protocols, and a migration/checklist path.

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.


## 0) Status of Prior Canon

Canon v1 (`canon_eng/spec.md`, `canon_eng/spec_hard_freeze_appendix_v1.md`, `canon_eng/behavioral_formulas_v1.md`, all `*_schema_v1.json`, `bones_v1.json`, `affixes_v1.json`, `behavioral_markers_v1.json`) remains frozen and authoritative for the two-layer system it describes. This proposal extends, it does not overwrite. Backward semantic compatibility is preserved per the canon's own evolution constraint (EDCM metrics §"Evolution constraint": old definitions are archived, not overwritten).
- One path dominates → use it; archive others as falsified-but-preserved
- Multiple paths complement → keep two or three, emit all readings, the disagreement becomes a coupling-layer signal in itself

**Path (a) — Curated markers.** Two new marker sets in `behavioral_markers_v1.json` (or `_v2.json`): `motion_markers`, `basin_markers`. Same architecture as the existing 26 markers. Marker-pure, transcript-deterministic.

### 2.1 The-Interdependency/edcmbone (this canon repo)

The library code lives at `edcmbone/edcmbone/` (the nested subpackage path that already exists). Application surface (`frontend/`, `backend/`, `engine.py`) imports the library; library never imports the application.
- `negated_utterance` — the claim is denied / the negation is what was uttered
- `hypothetical` — claim is offered conditionally / as supposition

**Provisional default:** `uttered | referenced | quoted | implied | negated | hypothetical` (6 values). Override before freeze.
Comment on lines +285 to +287
### 5.2 The GPT-generated edcm_metrics.py module

Treat as seed material, not as canonical code. Its C formula migrates to marker-domain (Behavioral C); its Progress/Basin formulas migrate to trajectory path (b). The module itself does not land in the library; it is referenced as a research artifact.

## 4) Falsification Anchors for Iteration

Per EDCM metrics §"Validation criteria" and §"Falsification pathways", v2 additions must remain falsifiable. Specifically:
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants