Skip to content

Restore arrow notation in SPEC.md - #30

Merged
markmnl merged 1 commit into
mainfrom
spec/restore-arrow-notation
Aug 25, 2026
Merged

Restore arrow notation in SPEC.md#30
markmnl merged 1 commit into
mainfrom
spec/restore-arrow-notation

Conversation

@markmnl

@markmnl markmnl commented Aug 25, 2026

Copy link
Copy Markdown
Owner

Reverts the arrow → semicolon substitution made during review of #29. The arrows suit SPEC.md's terse condition → outcome style, and the semicolon form read worse in the step lists.

Also restores the three sentences that had been split to avoid producing two semicolons in one clause, e.g.:

...MUST exactly match the corresponding expanded size. Mismatch means invalid; TERMINATE.

back to:

...MUST exactly match the corresponding expanded size; mismatch means invalid → TERMINATE.

Purely notational — 31 arrows restored, no wording or normative change. Verified mechanically: applying the semicolon substitution to this branch's SPEC.md reproduces the merged main version byte-for-byte.

A companion commit syncs the same file into markmnl/fmsgd#33.

🤖 Generated with Claude Code

Reverts the arrow-to-semicolon substitution made during #29 review; the
arrows read better in the terse condition → outcome style SPEC.md uses
throughout. The three sentences that had been split to avoid two
semicolons in one clause are restored to their original single-sentence
form as well.

Content is otherwise untouched: applying the semicolon substitution to
this file reproduces the merged version byte-for-byte.
markmnl added a commit to markmnl/fmsgd that referenced this pull request Aug 25, 2026
@markmnl
markmnl merged commit 244cd47 into main Aug 25, 2026
@markmnl
markmnl deleted the spec/restore-arrow-notation branch August 25, 2026 10:06
markmnl added a commit to markmnl/fmsgd that referenced this pull request Aug 25, 2026
* Sync SPEC.md from fmsg-spec v0.5.0 consistency fixes

Notable for fmsgd: the spec now states what the implementation already
does — stored-message verification includes messages the host sent,
exactly one header-response code, add to may not overlap to, add-to
copies omit topic and set has-pid, unsupported first byte gets code 2.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>

* Sync SPEC.md: add-to batch branch semantics and hash identity

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>

* Sync SPEC.md: batch hash verification by reconstruction

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>

* Sync SPEC.md: terminate on unsupported challenge version

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>

* Sync SPEC.md: name the one notification-only case explicitly

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>

* Sync SPEC.md: simplify code 11 wording

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>

* Sync SPEC.md: code 10 is simply duplicate

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>

* Sync SPEC.md: code 10 row without qualifiers

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>

* Sync SPEC.md: terse code 11 table row

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>

* Re-sync SPEC.md after review changes to fmsg#29

Picks up the review outcome: unsupported versions TERMINATE on both
first-byte branches, code 2 retired from the table (numbering unchanged),
and the notification-only re-iteration trimmed from the sending intro.

* Re-sync SPEC.md: notification-only defined at point of use

* Re-sync SPEC.md: recipients are a set, to/add-to overlap permitted

* Re-sync SPEC.md: one code per recipient entry; semicolons for arrows

* Re-sync SPEC.md: restore arrow notation (markmnl/fmsg#30)

---------

Co-authored-by: Claude Fable 5 <noreply@anthropic.com>
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