schema: coven-memory promotion schema v1 (BLOCKER-1 relocation) - #11
Merged
Conversation
There was a problem hiding this comment.
⚠️ Not ready to approve
The newly added coven-memory schema contains stale/contradictory wording and the v0.5.0 changelog entry omits the schema addition while claiming the release shipped “alone.”
Pull request overview
Updates the repository’s published contract version to v0.5.0 and adds a canonical in-repo copy of the locked coven-memory promotion schema, alongside documentation/validator output updates and an RFC snapshot for v0.4.1 reproducibility.
Changes:
- Bump spec/version references from v0.4.1 → v0.5.0 across validator output, docs, and package metadata.
- Add
schemas/coven-memory-schema.mdas the canonical contract-repo home for the locked coven-memory promotion schema (v1). - Extend RFC-0001 with §6.3.1 (versioning-rule amendment freeze) and add a preserved snapshot of the v0.4.1 RFC text.
File summaries
| File | Description |
|---|---|
| validators/validate.js | Updates CLI banner version to v0.5.0. |
| validators/README.md | Updates validator docs/examples to v0.5.0 references. |
| tests/conformance/README.md | Updates conformance suite README to v0.5.0 references. |
| SPEC.md | Updates pointer to the current normative RFC version (v0.5.0). |
| schemas/ward.schema.json | Updates schema description string to v0.5 subset wording. |
| schemas/coven-memory-schema.md | Adds the canonical coven-memory promotion schema v1 (M1 lock) document. |
| rfcs/RFC-0001-v0.4.md | Adds a historical snapshot of RFC-0001 v0.4.1 text. |
| rfcs/RFC-0001-familiar-contract.md | Bumps RFC to v0.5.0 and adds §6.3.1 amendment-freeze rule and changelog entry. |
| rfcs/README.md | Updates RFC index to v0.5.0 and links the v0.4.1 snapshot. |
| README.md | Updates repo badge and usage guidance to v0.5.0. |
| PRIMER.md | Updates “next steps” pointer to v0.5.0. |
| package.json | Bumps package version to 0.5.0. |
| package-lock.json | Bumps lockfile package version to 0.5.0. |
| docs/faq.md | Updates FAQ references to RFC-0001 v0.5.0. |
| CHANGELOG.md | Adds v0.5.0 release notes and updates “current version references” line-items. |
Review details
- Files reviewed: 14/15 changed files
- Comments generated: 3
- Review effort level: Low
Note
Your feedback helps us improve the quality of this feature.
Please use 👍 or 👎 to tell us whether this assessment is correct.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
Comment on lines
+18
to
+19
| Relocation target (BLOCKER-1): `OpenCoven/familiar-contract/schemas/coven-memory-schema.md` — | ||
| until that PR lands, THIS section is authoritative and the relocated copy must match it. |
Comment on lines
+49
to
+53
| created_by: <familiar-id> | ||
| attested_by: <familiar-id | val> # known ids only, else reject | ||
| attested_via: <attestation ULID or FAMILIAR_ROOT-relative path> # §11.2 | ||
| title: <human-readable> | ||
| source_context: <session-key-class or FAMILIAR_ROOT-relative path> |
Comment on lines
+10
to
+18
| ## [0.5.0] — 2026-07-24 | ||
|
|
||
| Draft minor, classified under the **v0.4.1** §6.3 rule per the incoming §6.3.1 freeze: one additive normative change, shipped alone. No directory-level conformance requirements change. | ||
|
|
||
| ### Added | ||
|
|
||
| - **RFC-0001 §6.3.1** — Amendment freeze for the versioning rule: a release changing §6.3 **MUST NOT** contain any other normative change (current-version anchor substitutions inside otherwise-unchanged normative sentences excepted), **MUST** be classified under the §6.3 rule ratified in the most recent prior release (never the rule it introduces), a changed rule governs only later releases, and ambiguous classification under the prior rule **MUST** take the larger bump. Closes the self-ratification pattern (v0.4.0 review finding A-1; first flagged as A-7 in the v0.3.0 review). | ||
| - **RFC-0001 §9** — Testing-gap bullet for §6.3.1 (release-process property; verified in release history and review, not by the file-level suite). | ||
| - **rfcs/RFC-0001-v0.4.md** — Historical snapshot of the final v0.4.x text (exact copy of tag `v0.4.1`). |
…om Echo workspace) Locked M1 schema (bead cmem-6gy, 2026-07-24) relocated per Nova concurrence (authoritative plan §10.11): implementations pin a version from this repo path. Includes the three 2026-07-24 edge amendments (ULID generate-vs-reject, FAMILIAR_ROOT-only v1 gate, familiars.toml attester authority).
BunsDev
force-pushed
the
schema/coven-memory-promotion-v1
branch
from
July 26, 2026 11:04
8d95269 to
b1ff57e
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
Relocates the locked M1 promotion schema (§11, bead cmem-6gy) from Echo's workspace to its canonical contract-repo home, per Nova's 2026-07-11 concurrence (authoritative plan §10.11): implementations pin a version of this file — Cody's M2 promotion layer in OpenCoven/coven cannot merge until this lands.
Contents
Runtime-portability audit (§11.5, answered)
✅ Yes. All paths are Coven-native (~/.coven/*, FAMILIAR_ROOT abstraction), resolution orders are flag/env/contract-default, no runtime-specific hooks or session-key formats. The schema bans raw runtime session keys from frontmatter by construction.
Review
Beads: cmem-f59 (B1), cmem-6gy (M1, closed), cmem-1ev (M2, unblocked-for-merge by this PR)