日本語 | 中文 | Español | Français | हिन्दी | Italiano | Português (BR)
record-index
A governed SQLite+FTS5 map over a markdown decision record, so a session can query the record instead of reading it — and then read the forty lines the query pointed at rather than the six hundred it would have skimmed.
The markdown stays canonical. The index is derived, regenerated on every fold, gated by a
four-leg verify, and wrong by definition the day it is hand-edited.
Status — extracted, tested, not yet on PyPI
(This section read "SCAFFOLD ONLY — no tool code is in this repo yet" until 2026-08-11, which the extraction landing falsified. Corrected in place.)
The extraction landed. The package is on main, gated on the way in by byte-identity
with facet's in-tree build (19/19) and zero row-level differences on the same corpus.
Two consumers run on it: facet, whose ~2,462
in-tree lines became a declaration plus an adapter with ~140 of its tests exercising the
package through it, and armature, whose
own index seeded 15/15 with 47 rulings.
The package carries its own suite: 455 checks across all ten modules, run in CI on
Python 3.11 and 3.13, built on two fixture record-repos that disagree on every declarable
axis — markers, corpus roots, arc rules, verdict vocabulary, header forms — so a wrong
implementation has somewhere to become visible. Dependencies: none. Stdlib only
(sqlite3 + re + json), and that is a declared property, not an accident.
Four defects are known, reproduced, and pinned in-tree as xfail(strict=True) tests
rather than hidden: verify() doubles its diagnostic counts (gating legs unaffected); the
claim-arc pattern assumes E-numbered arcs; the sub-ruling locator is not derived from the
declared header form; and four declaration fields cannot be declared honestly empty. None
affects the two current consumers; all four are queued for the next version.
Not yet on PyPI. release.yml publishes via OIDC Trusted Publishing when a GitHub
release is created; nothing publishes on push.
Where this comes from
This is an extraction of the record index built and hardened in
mcp-tool-shop-org/facet, which is where
every convention below was paid for. It extracts rather than forks because facet's own law
book records five hand-copies of one function living under four names, invisible to a
name-based grep for months; forking thousands of lines into a second repo is that error
with three more zeros.
The extraction condition was stated in advance and gated on measurement: the index
extracts when a second repo adopts the conventions.
mcp-tool-shop-org/armature is that repo.
The design, in one paragraph
A record repo declares what its documents mean — which files carry rulings, which header forms open one, what its verdict vocabulary is, which corpora it has. The tool supplies how the search works — parsing, ranking, determinism, the verify legs — with tuning values that carry the corpus and date they were calibrated on. Conventions are a full declaration (a repo states its own meaning; it never inherits another repo's history by omission). Mechanism is defaults with overrides.
Every vocabulary reports what it did not recognise. An empty table and a table that silently discarded six artifacts are indistinguishable at the call site, and only one of them is correct.
The halt that used to be here, and how it ended
(Until 2026-08-11 this section halted the build on a measured collision. The halt was real, the ruling came, and the build proceeded — kept here as the trail rather than deleted.)
The classification step had measured that deriving a document's arc from its leading
E\d\d prefix collides on 7 primary keys against facet (E10-ruling.md and
E10-offsurface-ruling.md both become arc E10). The executor caught it against a test
whose name records the same failure, the joint ruling was withdrawn and re-derived, and
the extraction proceeded through its gates. The trail — evidence, the overturned answers,
and the ruling that replaced them — is in armature/docs/dispatches/ (the S02 arc).
Licence
MIT — see LICENSE.
Metadata
Release files for record-index 0.1.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| record_index-0.1.0.tar.gz | 101.6 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| record_index-0.1.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 153.6 kB
Release files / record_index-0.1.0.tar.gz
| Download URL | record_index-0.1.0.tar.gz |
|---|---|
| Size | 101.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
c42b9656fef04e71191ee31d08d3acead296a05b5a44e57e1875e06ea198bbe7
|
|
BLAKE2b-256 checksum How to use checksums |
c6dece64f5473199376eb0c5f961b820e19480365138dc0628d0a5e0715bcaab
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Aug 11, 2026.
Transparency logRelease files / record_index-0.1.0-py3-none-any.whl
| Download URL | record_index-0.1.0-py3-none-any.whl |
|---|---|
| Size | 51.9 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
6c64727563479bcd0031098974c5bccd6cb1aeca5cd950d868c95b771c184bbd
|
|
BLAKE2b-256 checksum How to use checksums |
c391b68f6b38c01b7bb5f2fbf271bd2195e968a02c9dd1680026cd11b13b44dc
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Aug 11, 2026.
Transparency log