russell@unturf.com
44b38c55da
Two related changes: #000042 — Term-aliases table (vocabulary-mismatch bridge) ========================================================= Sibling design to #000041 citation-aliases. Maps a (term, domain) pair to an alternate term used in older / foreign / pre-modern translations of the same concept. Triggered by the Hilbert "incidence" vs "connection" gap surfaced in #000040 §6 — claim-pack records use modern post-1950s names, the 1902 Townsend Hilbert translation uses the original "Verknüpfung" / "connection". Resolver wiring: each FTS5-query token gets OR-expanded with its registered aliases when --use-aliases is set. So '"line incidence"' becomes '"line incidence" OR "line connection"' once fox approves the (incidence, connection, geometry) alias. Decision audit: each row carries decision_at + decision_by + decision_rationale. Same audit discipline as #000041; same opt-in via --use-aliases; same distinct process_id ("warrant-resolver-v1+alias") on alias-resolved derivations rows. A single decision unlocks 7 stuck Hilbert pillar IV records: arborist alias term add incidence connection \\ --domain geometry --by "fox YYYY-MM-DD" \\ --rationale "Hilbert 1902 Townsend uses 'connection' for what modern texts call 'incidence'" Implementation deferred until that decision triggers it. `arborist sweep` CLI — Target B warrant-resolver fragment ========================================================= Implements the schema-no-change increment of #000037 §3.1 Target B (documents that bypassed meta-cognition at ingest time). arborist sweep --shards-dir X --target warrants [--write] `--target warrants` walks every claim-pack record and re-runs warrant_resolve. Same code path as `arborist warrant-resolve` but framed as the unconscious sweep — operators can run on a cron / systemd timer; the target name reserves namespace for the full bicameral sweep landing later (canonical-projection probe, freshness probe, document-content witness fan-out). `--target all` reports "deferred" with an honest message: the full sweep needs #000037 §12 phase trigger + documents.last_swept_at schema migration. Idempotent: re-running on the same shards is a no-op at the DB layer (PK collision on (core_root, src_root, process_id) in the existing derivations table). Operators can run the sweep on a recurring schedule without row proliferation — exactly the property #000037 §3.1 needs from the unconscious sweep. Test suite stays at 1605 passed / 28 skipped — pure CLI + new ticket; no source-code changes outside cli.py. |
||
|---|---|---|
| .. | ||
| _source | ||
| diagrams | ||
| tickets | ||
| bench-maxing.md | ||
| benchmarks.md | ||
| cti-architecture.md | ||
| dav1dprometheus-update-2026-05-09.md | ||
| mesh.md | ||
| pi-star-composition.md | ||
| qa-modes-bench.md | ||
| seven-point-program.md | ||
| soft-hash-channel-analysis.md | ||
| spec-methodology.md | ||
| TICKETS.md | ||
| tool-action-dag-design.md | ||
| v7w-frontier-catalog.md | ||
| v8-fork-score.md | ||
| zk-frontier-bench.md | ||
| zk-wire-protocol.md | ||