Talk:Feature Request Log
Calibration Report — Feature Request Log — 2026-07-14
- Page: Feature Request Log
- Summary: A log of genuinely desired features that were attempted and found not currently possible with available tools — distinct from Calibration Failure Log (design was wrong) and Known Site Issues (something broken).
- Reviewer: Sovereign, with Claude
- Review Type: Self-Assessment
Summary of Changes
- New page created as the seventh distinct tracker, following direct consideration of whether it belonged folded into Calibration Failure Log — rejected, since "not buildable yet" and "design was wrong" are genuinely different categories that would blur each log's usefulness if mixed.
- Deliberately structured as an index-only page, with full request write-ups and open discussion living on Talk — distinct from other trackers, since a feature request is inherently open to proposal and revision in a way a settled bug/failure record is not.
- First entry logged: the just-tested Cargo multi-table join attempt for per-dependency rich status on `Calibration Dependencies Display`, confirmed structurally impossible (list-type fields stored in a separate internal table, not visible to standard `join on` syntax).
- Added to the seven-template mandatory block, matching every other page built tonight.
Reasoning / Rationale
The Talk-based format was chosen specifically because feature requests, unlike settled logs, benefit from ongoing discussion — someone may propose the Lua-module alternative already flagged as unexplored, or find a different approach entirely. Keeping the main page as a scannable index while pushing full detail (and any future replies/debate) to Talk mirrors how Calibration Reports themselves already work for every other page.
Confidence / Certainty Level
High — the underlying Cargo limitation was directly tested and confirmed via a real error message, not inferred.
instrument_grade: Experimental (unchanged)
calibration_rationale: New page, first entry, structurally sound but not yet round-robin reviewed. review_confidence: Moderate
What This Report Does NOT Claim
This does not claim the Lua-module alternative has been evaluated or attempted — it's named as an open, undiscussed possibility only. Does not claim this is the final or only viable format for future entries; the pattern itself has one real test case so far.
Fields Changed
New page created.
Open Items
- Whether the Lua-module workaround is worth pursuing remains genuinely open, flagged for discussion on the Talk entry itself.
- Not yet round-robin reviewed.
- First real test of the Index-plus-Talk-detail format for this specific tracker type — worth confirming it holds up once a second entry is added.
See the Game. Refuse the Game. Build Better.
Sovereign (talk) 10:09, 19 July 2026 (EDT)
Calibration Report — Feature Request Log — 2026-07-14
- Page: Feature Request Log
- Summary: A log of genuinely desired features that were attempted and found not currently possible with available tools — distinct from Calibration Failure Log (design was wrong) and Known Site Issues (something broken).
- Reviewer: Sovereign, with Claude
- Review Type: Self-Assessment
Summary of Changes
- New page created as the seventh distinct tracker, following direct consideration of whether it belonged folded into Calibration Failure Log — rejected, since "not buildable yet" and "design was wrong" are genuinely different categories that would blur each log's usefulness if mixed.
- Deliberately structured as an index-only page, with full request write-ups and open discussion living on Talk — distinct from other trackers, since a feature request is inherently open to proposal and revision in a way a settled bug/failure record is not.
- First entry logged: the just-tested Cargo multi-table join attempt for per-dependency rich status on `Calibration Dependencies Display`, confirmed structurally impossible (list-type fields stored in a separate internal table, not visible to standard `join on` syntax).
- Added to the seven-template mandatory block, matching every other page built tonight.
Reasoning / Rationale
The Talk-based format was chosen specifically because feature requests, unlike settled logs, benefit from ongoing discussion — someone may propose the Lua-module alternative already flagged as unexplored, or find a different approach entirely. Keeping the main page as a scannable index while pushing full detail (and any future replies/debate) to Talk mirrors how Calibration Reports themselves already work for every other page.
Confidence / Certainty Level
High — the underlying Cargo limitation was directly tested and confirmed via a real error message, not inferred.
instrument_grade: Experimental (unchanged)
calibration_rationale: New page, first entry, structurally sound but not yet round-robin reviewed. review_confidence: Moderate
What This Report Does NOT Claim
This does not claim the Lua-module alternative has been evaluated or attempted — it's named as an open, undiscussed possibility only. Does not claim this is the final or only viable format for future entries; the pattern itself has one real test case so far.
Fields Changed
New page created.
Open Items
- Whether the Lua-module workaround is worth pursuing remains genuinely open, flagged for discussion on the Talk entry itself.
- Not yet round-robin reviewed.
- First real test of the Index-plus-Talk-detail format for this specific tracker type — worth confirming it holds up once a second entry is added.
See the Game. Refuse the Game. Build Better.
Sovereign (talk) 10:10, 19 July 2026 (EDT)
Auto-Linked/Popup Glossary for Defined Terms — 2026-07-14
Type: Future layer, not yet built
This project has accumulated a real, growing vocabulary of precisely-defined terms (Breadcrumb, Nonconformance, Pre-Calibration Check, Calibration Recommendation, and others) — each defined once, correctly, but currently only findable if a reader already knows which page to check. Eventually, any use of a defined term anywhere on the site should auto-link or show a popup/tooltip pointing to its canonical definition, removing the need for a reader to already know the vocabulary or go hunting for it. Requires a real glossary/definitions system to exist first as the single source each term resolves to — not yet built, explicitly deferred rather than attempted piecemeal per-term. Sovereign (talk) 19:09, 19 July 2026 (EDT)