Guides, practice, literature, and leads#
Original material |
Replacement and preservation decision |
|---|---|
Getting started, input, models, sessions |
The four user guides retain shared executable fixtures and expected outputs, with links to current implementation chapters. |
Current status |
Capabilities owns admission and limits; previous run counts remain in dated evidence. |
CLI/tactics/backend/statistics |
The reference now contains the full captured CLI inventory, typed tactic inventory, effective policies, statistics and backend procedures. Historical tuning candidate lists are not current defaults. |
Debugging and experiments |
Debugging, experiments, validation, and tuning separate operational procedures from historical incidents. |
Finite-domain and arithmetic fuzz coverage |
Fuzzing preserves mechanism activation, seed staging, grammar settings, bounded mutation coverage and classified outcomes. Valid model checks remain separate from verdict comparisons. |
Run log and storage design |
Evidence storage describes the active ledger; results storage remains an agreed future design. |
Documentation authoring, rewrite, publication plans |
Authoring and replacement preparation own current instructions. The old public-migration plan retains repository/license/deployment decisions; this rewrite does not publish or change repository visibility. |
Literature and paper notes |
Literature mapping accounts for each reading note and every supplied thesis’s role. Detailed comparisons and old intake checklists remain linked at exact source sections in the inventory. |
Open leads |
Research register reconciles numbered entries and the newer dedicated leads. Completed, rejected, and corrected entries stay visible without being listed as unimplemented features. |
Retrospective, profiles, negative results |
Evidence archive provides dated source locations and current destinations. Retrospective use never authorizes copying an older solver’s implementation. |
Supporting files#
The examples, expected responses and case manifest are retained, together with
the bibliography, requirements, build wrapper, diagram sources and original
logo assets. The supporting-file inventory preserves the treatment decisions
made before the move; its old paths and pending-movement labels are historical.
The editable books now live in docs/ and docs-history/. The generated SQLite
index and a results repository are not dependencies of the documentation site.