Repository navigation
Survey: where Vocarium could serve, with four experiments and a proposed theorem - #84
Open
hyperpolymath wants to merge 4 commits into
Open
hyperpolymath wants to merge 4 commits into
hyperpolymath wants to merge 4 commits into
Conversation
…iments Asks whether Vocarium has a use in four other parts of the estate: the Palimpsest licence's logic, the chora identity registry, VeriSimDB's consonance subjects, and the cadastre. Each question is put to the built store engine and the shipped checker, with fixtures in examples/survey/. tests/check-survey-experiments.sh re-runs all of it: 12 results. Run results: - A non-interpretive ingestion is refused under a use that claims the work's context survives, and accepted or refused on provenance according to whether the metadata was kept. - Consent for research satisfies a floor that asks for consent for training. This is trope-checker issue 125, in the setting where it matters. The note says the stack must not decide consent until it is settled. - A renamed repository identity resolves by id and not by old path. - A cadastre row is enough to queue a repository and not to describe it. - Vocarium refuses a revocation record, and the IR it emits carries no warrant: two gaps, both measured. It compares Vocarium's warrant record with the epistemic-types levels that Palimpsest's proved warrant model uses, and states three theorems on the level of a verdict. None is proved. It lists three bridge candidates for Mathesis without writing to it. Read only: no specification, licence, proof or sibling repository is changed. Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01J4QvDim4mMEfCer9SiAV4H
# Conflicts: # CHANGELOG.adoc
hyperpolymath
marked this pull request as ready for review
November 17, 2026 13:52
|
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
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.



Summary
A survey asking whether Vocarium has a use in four other parts of the estate: the Palimpsest licence's logic, the chora identity registry, VeriSimDB's consonance subjects, and the cadastre. Each question is put to the built store engine and the shipped checker. It also compares the two things the estate calls a warrant and proposes a theorem that would join them.
Stacked on #83 (base
claude/stack-coherence-gate) so the two changelog entries do not conflict.It changes no specification, licence, proof or sibling repository. Nothing is adopted.
Changes
docs/theory/formalisms/vocarium-survey.adoc: the note.examples/survey/*.jsonl: four fixtures as Vocarium store records.tests/check-survey-experiments.sh(just survey): re-runs the experiments and compares each verdict with the note. It needsVOCandTROPECHECK_BIN; a missing binary fails, it does not skip. It is not wired into CI, because this repository builds neither binary.Results (run 2026-11-17)
fate.context); accepted under "provenance intact"fate.recordfate.bearer)fate.quality)revocationrecord is refused ("reserved for M2")voc invokeemits carries no warrant id and no node textFor the owner to weigh
no-transfer. Proving it belongs to the proof session and its kernels.config.ncl,PALIMPSEST.adoc) and takes no side. That is licence content.Not tested
RSR Quality Checklist
Required
tests/check-survey-experiments.sh12 of 12; vocabulary and root-shape checks passAs Applicable
CHANGELOGupdateddocs/theory/README.adoc)Testing
vocwas built from vocarium3ef6286with Zig 0.16.0.tropecheck-rswas built from trope-checker sources equal tomaininsrc/,schemas/andspec/.Generated by Claude Code