Name the third ring MemorySmith

[heitorrapcinski]

Summary of changes

SPEC.md uses "vault" on nearly every page for the thing a person keeps — the folder resolution may not cross, the boundary an edge stays inside, the place the attribute vocabulary belongs to. § 2 used the same word for a layer of the specification, and the reader had to tell the two apart from context.

The ring is not a property of anybody's vault. It is the notation this profile declares on top of CommonMark and GFM, and it is the only ring with no source above it. The other two rings are named after the specification that governs them; the one that governs this ring is this document.

• SPEC.md § 2 names the ring MemorySmith, and § 1.1 with it.
• profile.json carries "ring": "memorysmith" on all 29 entries.
• schema/profile.schema.json accepts memorysmith in place of vault.
• README.md names it in the table of three rings.
• The ring:vault label is renamed to ring:memorysmith.

The released entries of CHANGELOG.md are not rewritten. They are dated records of what the ring was called then, and the Changed entry of this cycle is what connects the two names.

Closes #5

What an implementation has to do

Read memorysmith where it read vault in the ring field of profile.json. Nothing else changed: no notation was added, removed or given a different effect, no conformance case changed, and no note written in this profile parses differently.

memorysmithapp/memorysmithapp pins a version of the profile and is unaffected until it moves to the next one. That is a separate issue in that repository, to open after this merges.

The three files

• SPEC.md, because the prose of a notation changed — § 1.1 and § 2, the name of the ring
• profile.json, because an entry was added, changed or removed — 29 entries, the ring field only
• tests/conformance.json, because a case was added or its expectation changed — no case names a ring
• CHANGELOG.md, in the same commit as the change it documents
• None of the above: this pull request changes no notation

npm run check passes locally: yes — 31 notations, 35 cases, version 0.2.0.

Version

Minor. It changes the value of a published field, which is a break for anything reading ring, and in 0.x a break arrives as a minor version. It waits in [Unreleased] under Changed for the cycle to close, per CONTRIBUTING.md § 6.

AI productivity analysis

Metric	Value
Lines of code handled (added + removed)	82 (47 added, 35 removed)
Branch duration	Same day (from 2026-09-06 to 2026-09-06)
Technologies involved	Markdown, JSON, JSON Schema
Estimated human effort (without AI assistance)	see below

Estimated human effort (without AI assistance)

Estimated effort: 2h, roughly 0.3 working days (8h/day) or 0.1 working weeks (40h/week).

The edit is mechanical and the work is not. The cost is separating the two senses of "vault" through a document that uses the word legitimately on nearly every page — ~x~ and ^x^ render in "no vault editor" stays, "within the same vault" stays — and deciding not to rewrite the released changelog entries, which is the difference between a rename and a falsified record.

🤖 Generated with Claude Code

https://claude.ai/code/session_015AqyzSutJgPQiub6mc5AZg