Repository navigation
docs: restyle the README and add the repository logo - #329
Conversation
The README is reorganized for a reader arriving cold: a centered header with the logo, the one-line value proposition, the document links and the state badges, then Quickstart (container, binary, source, the §29 literal), How LexLean works (pipeline plus the command table with what each command may claim), Why LexLean, When to use LexLean, the capability register table, the examples, the gate, the evidence rules, the documented deviations, the layout and the license. The gate-relevant content is unchanged: the capability table keeps its exact header, its three cells, its `build` level cell and its 35 rows, so every one of the 457 registered IDs is still claimed exactly once by the row that owns it, and the register-size and honesty-level sentences are still stated. No dash is used as punctuation anywhere in the prose, and no list uses a hyphen marker; hyphens remain only where they are part of an identifier, a path, a command or a table separator, because those are machine-checked tokens. assets/lexlean-logo.svg is new: a QED tombstone with a check mark beside a monospace wordmark, in the repository's own purple, legible on light and dark renderings. SPEC.md §7 lists it, so the added file has the defined role §7 requires.
|
Thanks; the shape is right and the gate-relevant invariants you list are the ones RP-11 and RP-03 read. Two things before it can land:
It queues after #305 (H7-audit, in landing) and #247; I land it with the usual regeneration if the gate needs one (a README and an SVG move no identity, so likely none). Mark it ready again once it sits on Generated by Claude Code |
Rewrites README.md for a reader arriving cold, in the shape other projects use: a centered header (logo, one-line value proposition, document links, state badges), then Quickstart (container, binary, source, the SPEC.md §29 literal), How LexLean works (pipeline plus a command table whose third column says what each command may claim), Why LexLean, When to use LexLean, the capability register table, the examples, the gate, the evidence rules, the documented deviations, the layout and the license.
Gate-relevant content is unchanged. The capability table keeps its exact header line, its three cells, its
buildlevel cell and its 35 rows, so every one of the 457 registered IDs is still claimed exactly once, ranges still start and end at the register's first and last ID for their prefix, and the register-size sentence (All 457 registered conformance IDs) and the honesty-level phrase remain as RP-11 reads them.No hyphen is used as punctuation anywhere in the prose and no list uses a hyphen marker; hyphens remain only inside identifiers, paths, commands, code spans and table separator rows, because those tokens are machine-checked (RP-11 parses
RP-01..RP-18) and appear in links.assets/lexlean-logo.svgis new: a QED tombstone with a check mark beside a monospace wordmark, in the repository's purple, legible on both light and dark renderings. SPEC.md §7 gains the two tree rows that give the file the defined role §7 requires; RP-03's §7 parse asserts that every listed path exists, and it does.Verified locally against the gate's own logic, re-implemented from
conformance_rp_11andconformance_rp_03: 35 capability rows, 457 claimed IDs, no duplicate and no unclaimed ID, no range that leaves its prefix or misses the register's first or last ID, 231 §7 tree rows present on disk, no assertive vocabulary on any line naming an authority, no em or en dash.just vvitself is the gate's to run.