Repository navigation
YuCe 0.2.1
YuCe 0.2.1: a table of what each part of the documents came to, strict signed notes, and answers that list each record once.
The reviews of 0.2.0 and a second corpus for the gap pass found what this release fixes. The journal format and the rules of the
kernel do not change: journals of 0.2.0 replay and verify as before.
Fixed
- An answer lists each of its records once. After a repair in several attempts, an answer of 0.2.0 could name a record twice
(control run 1 of 0.2: 11 of 54), and the report of what fell counted its standing grounds too high. Journals of 0.2.0 replay as
written; LIMITATIONS.md says how to count them. audit-proofandaudit-signnever write over what they read. In 0.2.0audit-proof --outpointed at the journal wrote the
quittance over the run. Both now refuse such a path in any spelling and write a new file before renaming it into place.- Signatures are checked strictly, and a weak verifier key is refused. Under the check used before, a "signature" made for a key
of small order verified any text. Keys made bysbgk keygenare never weak; no signature written so far changes. - Signed checkpoints hold to the reference implementation of C2SP signed-note, with vectors written by the code of its authors.
Five places where the kernel read a note more leniently than the reference now read it as the reference does. - The journal of a running server is read by other processes, on Windows too. Beside a live server,
audit-verify,
audit-read,audit-indexandaudit-prooffailed on Windows (os error 33); they now read up to the last complete entry and
say so. One writer still, on every system. - A repair after a withdrawal is told what the withdrawal took: only the quoted bytes it names, not their document or revision;
a point the records no longer establish is named in the done text as a gap. The kernel checks form, not meaning, and no run with a
model has measured this. - A question about what changed takes the claims that say something was removed or renamed. Measured by replaying journals
without a model, not by a run with one. - The coverage of the gap pass is complete only when no second reading is owed, and the library writes no seal right after
another.
New
- A coverage table drawn from the journal:
sbgk audit-read coverage --wal <run.wal>, andaudit_coverageon the live server,
give a row for every list item, paragraph and table row of every document with what it came to: quoted and by which records,
answered empty, left by the reading budget, withdrawn, or unread. The index isyuce-index/2; build an index of
yuce-index/1again withsbgk audit-index --rebuild. audit_seal: the owner seals the journal on request, for example right before a withdrawal;seal()in the Python client.verifier/: the code ofyuce-verify, an independent verifier of 0.2 journals: a standalone implementation in TypeScript from
the open specification of the format, sharing no code and no dependencies with the kernel, 391 tests. It passed both control runs
of 0.2.scripts/verify_published_runs.pychecks the runs of 0.2 too.
A second corpus for the gap pass
benchmarks/PREREGISTRATION_0.2.1_A2A.md
fixed it before any run: the A2A specification of v0.2.5, v0.3.0 and v1.0.1 with its changelog, an oracle of 14 facts that ended by
v1.0.1, two runs with the gap pass and two without, graded blind by Gemini 4 Argon.
- By the pre-registered rule this counts against the gap pass: both runs with it stated more ended facts as current (8 and 6 at
stage 1) than both runs without it (2 and 1). - The journals show a defect in the kernel, in the claims it chose for a question about what changed. 0.2.1 fixes it (above).
The comparison does not separate the defect from the pass, and no run with a model has measured the fix. - The gap pass stays an option, off by default. "Nothing skipped in silence" is now carried by the coverage table, which shows
every part left unread, row by row.
The four runs are summarized in BENCHMARKS.md; their journals are not attached to this release.
Results and caveats: BENCHMARKS.md.
Full list: CHANGELOG.md. What it does not do: LIMITATIONS.md.
Assets
- Binaries:
yuce-v0.2.1-<target>for Linux x86_64, Windows x86_64 and macOS (arm64, x86_64), each withsbgk, its alias
yuce, LICENSE, NOTICE, THIRD_PARTY_LICENSES.md and README;SHA256SUMS-<platform>.txt. - The Python client: organetic-yuce on PyPI.
- The recorded runs stay in v0.2.0,
v0.1.7, v0.1.6
and v0.1.0.
Check a download with sha256sum -c SHA256SUMS-<platform>.txt.