Repository navigation
docs(zh): rewrite the Chinese README in plain language - #1
Merged
Merged
Conversation
The zh README opened with protocol jargon (immutable contract DAG, lock-free optimistic concurrency, cascade verification) before a reader knew what problem any of it solved. Rewritten to lead with the intuition — turn writing software into doing mathematics, so agents can work in parallel without coordinating and without a human reviewing code — and to introduce each object with the concrete JSON a reader will actually write. Also fixes two stale facts the English README shares: - the self-hosting section said "eleven children / all twelve contracts Done / 12 done / 0 open"; verify.mjs derives 13 done / 0 open. - the mermaid block predated declared-laws and was missing its node; regenerated verbatim from graph.mjs --structural, and the caption now says why declared-laws carries no edge. Race 001 and the self-reference lesson are promoted to their own subsections — they are the receipts for "a gate judges admissibility, not quality" and "run a gate red before publishing it", and were easy to skim past as prose. Status line left in the shape l6-status-honest checks; verify.mjs and every law check pass. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
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
1 participant
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.
The zh README opened with protocol jargon — immutable contract DAG, lock-free optimistic concurrency, cascade verification — before a reader knew what problem any of it solved. This rewrites it to lead with the intuition (turn writing software into doing mathematics, so agents work in parallel without coordinating and without a human reviewing code), and to introduce each of the three objects with the concrete JSON a reader will actually write.
Two stale facts fixed (the English README still has both)
node tools/verify.mjsderives 13 done / 0 open — the badge line was already right, the prose was not.declared-lawsand was missing its node. Regenerated verbatim fromnode tools/graph.mjs --structural --format mermaid, and the caption now states whydeclared-lawscarries no edge (it declaresserves: root, but none of root's three decompositions import it).Structure
Race 001 and the self-reference lesson were easy to skim past as prose, so they now get their own subsections — they are the receipts for a gate judges admissibility, not quality and run a gate red for the right reasons before publishing it.
Checks
Status line left in the exact shape
l6-status-honestgreps for. Locally:verify.mjsexits 0 (13 done / 0 open),l6-status-honestandl4-englishboth exit 0.🤖 Generated with Claude Code