Skip to content

spec: v4.0 draft from the 2026-07-10 Puzzmo/Ingrid discussion - #8

Open
saulbert wants to merge 1 commit into
masterfrom
spec-v4-draft
Open

spec: v4.0 draft from the 2026-07-10 Puzzmo/Ingrid discussion#8
saulbert wants to merge 1 commit into
masterfrom
spec-v4-draft

Conversation

@saulbert

@saulbert saulbert commented Jul 11, 2026

Copy link
Copy Markdown
Collaborator

Draft v4.0 of the spec, capturing the changes accepted in the 2026-07-10 spec discussion (Google Doc + call) with Puzzmo and Ingrid:

  • one Unicode codepoint per grid cell; larger graphemes are rebuses
  • case-insensitive header keys
  • repeated rebus keys declare Schrödinger cells (Rebus: 1=O 1=A)
  • ## Design section (Puzzmo's extension, minus the <style> wrapper) replaces the Special header
  • a clue line holds a ~-separated list of answers, usually of size one; rebuses always expanded, keys never in answers
  • markup adds subscript/superscript/small caps and formal nesting
  • backslash becomes the markup escape character (was: line separator)
  • editorial comments via clue metadata (^Comment:); no other comment syntax

Items that didn't reach consensus are filed as #1#7 and referenced from the spec where a detail is still open. The reference parser is not yet updated to match the draft.

Known open wrinkle: with ~ as the answer-list separator, a literal ~ in clue text is ambiguous; probably wants an escape or a rule.

[this PR written by Claude Fable 5 from the 2026-07-10 spec discussion, filed at @saulpw's direction]

🤖 Generated with Claude Code

…sion

Accepted changes from the spec-discussion doc and call:

- one Unicode codepoint per grid cell; larger graphemes are rebuses
- case-insensitive header keys
- repeated rebus keys declare Schrödinger cells (Rebus: 1=O 1=A)
- Design section (Puzzmo's, minus the <style> wrapper) replaces Special
- a clue line holds a ' ~ '-separated list of answers, usually of size
  one; rebuses always expanded, keys never appear in answers
- markup adds subscript/superscript/small caps and formal nesting
- backslash becomes the markup escape character (was: line separator)
- editorial comments via clue metadata (^Comment:); no other comment syntax

Contentious items are filed as issues #1-#7 and referenced from the spec
where a detail is still open.  Reference parser not yet updated to match.

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