Skip to content

docs: sync README to OpenDEAM v0.5.0 + CR-001..004 downstream status - #9

Merged
emmanuel-a-otchere merged 1 commit into
mainfrom
docs/readme-v0.5.0-sync
Aug 16, 2026
Merged

emmanuel-a-otchere merged 1 commit into
mainfrom
docs/readme-v0.5.0-sync

Conversation

@emmanuel-a-otchere

Copy link
Copy Markdown
Contributor

What

README had drifted from the model it describes (still presented v0.4.0-alpha while VERSION/tag are 0.5.0).

Changes

  • Version badge → v0.5.0-alpha
  • Layer entity counts corrected to actual model allocation (L2 12, L3 16, L4 10; 53 first-level entities, 2 dimension)
  • Consumption-contract example pins @v0.5.0
  • New Downstream sync status section: v0.5.0/ADR-0005 content summary, dea-metamodel CR-001..004 (v0.6.0–v0.9.0) consumption, v0.6.0 candidate note (CR-004's 10 new core anchors), and the T2 metamodel-pointer.yaml v0.2.1 pin drift documented as pending fan-out regen (not hand-edits)
  • ADR index now lists 0001–0005

Verification

  • scripts/validate_model.py → OK (5 layers, 27 BBs, 53 entities, 70 rels, v0.5.0)
  • Entity names in README cross-checked against model/opendeam-model.yaml (Resource kinds: Financial/Physical/Intangible; L4: Information Asset, Knowledge Asset; dimension: Concept, Performance Metric)

Docs-only; no model change.

…01..004 downstream status

- badge v0.4.0-alpha -> v0.5.0-alpha (VERSION=0.5.0, tag v0.5.0)
- layer entity counts corrected to model reality (L2 12, L3 16, L4 10; 53 total, 2 dimension)
- consumption contract example pins @v0.5.0
- add Downstream sync status: dea-metamodel v0.6.0-v0.9.0 (CR-001..004),
  v0.6.0 candidate (10 new core anchors upstream), documented pointer-pin drift
- ADR index 0001-0005
@bolt-new-by-stackblitz

Copy link
Copy Markdown

Review PR in StackBlitz Codeflow Run & review this pull request in StackBlitz Codeflow.

@emmanuel-a-otchere
emmanuel-a-otchere merged commit 0d7ec86 into main Aug 16, 2026
1 check passed
@emmanuel-a-otchere
emmanuel-a-otchere deleted the docs/readme-v0.5.0-sync branch August 16, 2026 13:21
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