Repository navigation
YuCe 0.1.4
YuCe 0.1.4: a journal checks about five times faster, the limits campaign is in the open, and the runner is ready for a run from this tag.
Roots, journal format and checks are unchanged: journals of earlier versions verify as they did.
Faster
- A journal replays about five times faster. On the recorded runs of about 3,000 records,
audit-verifywent from about 11 s to
2 s, and reopening a journal gains the same. Every entry's outcome and roots are still computed and compared, so a journal that
misreports one is refused as before. The whole state is still hashed at every entry, so the time grows close to the square of the
journal's length.
Fixed
- A refused start of
audit-serveno longer writes to a journal or leaves a new one. Every flag that needs no journal is checked
before the journal is opened, and a new run whose start fails is taken away again. One thing stays: opening a journal cuts a torn
tail, so a start refused by a check against that journal has already cut it. It says so at once and keeps the bytes. audit-verify --at-end. With--expect, the receipt's state must be the journal's last: a journal that went on after a terminal
receipt is a mismatch, and so are bytes after the last complete entry.conerefuses an entity no claim names (exit 2), and a container it cannot read. It printed an empty cone and exited 0.- Tables of records take a key per process, so an agent cannot search for record ids that fall in one bucket and slow every pass.
Measured and repeatable
benchmarks/run_limits.pyrepeats section 4 of BENCHMARKS.md
and says how busy the machine was. The section is taken again on this kernel code, and its memory column is now the peak of the whole
process.- The runner names the tag, the trees of
cratesandbenchmarks, the binary's version and the hash of every runner source in a
run's provenance, and refuses a binary of another version than its tag.benchmarks/revision_outcomes.pycounts what a withdrawal
cost and what it took with it, on every side. benchmarks/PREREGISTRATION_0.1.4.mdfixes what a run from this tag will measure, before it runs: a team of models from different
makers, the withdrawals, the grading rules and the outcomes. That run is not part of this release; its results will be added when it
has been done.
Changed in the texts
README now says what the audit server does: a claim rests on quotes, all of them required, and CURRENT_UNCERTAIN falls on a claim that
rested on an earlier and a later report. LIMITATIONS adds what a withdrawal reaches: in the journal, no claim stays grounded on a withdrawn
quote; the text an agent writes can still repeat it in other words, and that is measured, not prevented. BENCHMARKS section 3 keeps the
check of quotes alone: the comparison of answers with knowledge-graph systems, which have another purpose, is out until the graph work
of a later version.
Full list: CHANGELOG.md.
Assets
- Binaries:
yuce-v0.1.4-<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 recorded runs of BENCHMARKS section 1 stay in the v0.1.0 release.
Check a download with sha256sum -c SHA256SUMS-<platform>.txt.