Skip to content

YuCe 0.1.7

Choose a tag to compare

@OrganeticSphere OrganeticSphere released this 07 Nov 22:52
· 60 commits to main since this release

YuCe 0.1.7: a repair names what fell, and the audit server takes your own text files.

The blind grading of the second run on four makers found the gap: after a withdrawal the kernel kept a conclusion on a page that still
stands, but its request for a repair did not say which row had fallen, and the model wrote the whole answer again without it.

Fixed

  • A repair after a withdrawal names what fell. It names each fallen row by id, with the quotes under it that stand, and keeps the
    row's own text out, as it may state what was withdrawn. A repair takes a few lines, and the rows that stand stay as they are.
  • Copies of the kept rows stay out of a repaired answer. A line that says what a kept row says, on the same grounds, is left out
    and counted (dropped_copies). The same words with another date or on another quote are another claim.
  • A new quote looks for withdrawn text near itself, not through the whole document, with the same decision.
  • yuce --version says yuce.

New

  • sbgk audit-serve --docs <folder> runs on your own text files: contracts, policies, logs, code, any UTF-8 text, with no manifest
    and no repository. A document is named by its path inside the folder and bound by its bytes. Hidden files, service folders, links and
    the server's own files stay out, and the server prints what it took and what it left. A file that is not text stops the start, by
    name. --select names the files instead of walking the folder.
  • audit-verify checks the file set of such a journal (sources), and says whether the documents are the set the run started on.
  • examples/findings-gate/ puts a security review's findings through the kernel: a made-up finding is refused by its bytes, a lost
    reader does not hang the work, and a file that changes takes the findings on it until each is checked again.

The journal format does not change: the release before verifies a journal of this one to the same roots.

The control run

benchmarks/PREREGISTRATION_0.1.7.md fixed it before it
ran: side K alone, from this tree before the tag, with the four readers of run 2. The repair took one new claim for each answer, no copy,
and the conclusion of run 2 stood. The grader marked the second withdrawal kept in one label order and partly in the other, for an
earlier state written as current that the answer held before the withdrawals. Results, with T and L of run 2 graded again:
BENCHMARKS.md.

Full list: CHANGELOG.md. What it does not do: LIMITATIONS.md.

Assets

  • Binaries: yuce-v0.1.7-<target> for Linux x86_64, Windows x86_64 and macOS (arm64, x86_64), each with sbgk, its alias
    yuce, LICENSE, NOTICE, THIRD_PARTY_LICENSES.md and README; SHA256SUMS-<platform>.txt.
  • The Python client: organetic-yuce on PyPI.
  • The control run: control017-K and control017-grading-opus, with a manifest each and SHA256SUMS-runs.txt. The runs on four
    makers stay in the v0.1.6 release, the earlier ones in
    v0.1.0.

Check a download with sha256sum -c SHA256SUMS-<platform>.txt.