Overview
A thin reader that declares what a set of small evaluative instruments is, reads whichever sibling packages are installed, and checks one narrow property: that no two of them have given the same spelling to different things. It adds no instrument of its own and computes no aggregate; a legible reading says only that the declared vocabularies did not overlap. Subtitle: A Declaration, a Reader, and a Non-Overlap Contract for a Growing Set of Small Instruments Code is MIT licensed; prose and figures are CC BY 4.0. See LICENSE in the repository.
Overview source: Curated paper metadata.
Methods and contributions
Read the source for the full argument, qualifications, and evidence.
Findings and contributions
- On the review date the four packages yielded 81 line-and-name pairs spanning 80 distinct names, and the only shared name was the already-declared, disambiguated one.
- The single shared name was OUTSIDE_SCOPE, carried by red_line and black_line.
- Appending a fifth line whose package is not installed yielded SET_PARTIAL, which the author argues is the correct answer rather than a shortfall.
- The author stresses that disjoint vocabularies are a necessary, not sufficient, condition: the check cannot detect conceptual overlap between instruments.
- The paper states the set digest is a comparison handle only, not tamper evidence or a record of who changed what.
Methods
- Declarative set registry: four LineEntry records plus one shared token — Declares the set (Red, Black, Golden, White Line) as data, each entry naming its question, job, and what it must not become.
- Five-stage reader with fixed-precedence set statuses — Reads installed sibling packages through resolve, bind, collide, declare and status stages, returning one of four SET_-prefixed readings.
- Enum-member name collision check across sibling package roots — Collects enum member names each line publishes at its package root and flags any name carried by more than one line, unless declared and disambiguated.
- Seven offline structural checks plus a self-application check — Runs seven declaration-only checks and an eighth that applies the package's own collision check to a declaration including itself.
- Executed extensibility example appending a fifth colour at runtime — Appends a hypothetical green_line entry without editing the package and runs the battery and reader on the extended declaration.
Summary sources: Paper metadata and evidence · Extracted source text.
Document downloads
PDFs are hosted here; supporting sources may use pinned archives.
- line_set_combined.pdf PDF · 21.62 MiB · extracted-text source
Citation
Citation metadata follows the unified bibliography.
Catalog details and resources
Related works
Ranked by recorded methods, topics, contributors and associated software, with contributor roles and domain-only matches labelled. Metadata overlap is not a citation or a scientific equivalence.