Interface Overview
The Appendices Factory is used to author opinion, assessment, and interpretive material that sits outside the evidential chronology.
Appendices are epistemically subordinate by design. They explain, contextualise, or assess — they do not prove.
Scope and Authority
Critical: Appendices do not create evidence, establish facts, or bind conclusions.
Appendices may include:
- Professional or technical assessments
- Narrative synthesis
- Interpretation of patterns already established elsewhere
Appendices may not include:
- Document links
- Evidence references
- Chronological assertions
- Claims of legal determination
Appendix Structure
Identifier
Each appendix is assigned an explicit identifier (e.g. Appendix A, Appendix B.1).
Sequencing is not enforced by the tool.
Title
Titles must describe what is being assessed, not what is being proved.
Body Content
The body is free text, with headings and lists permitted. No linking or evidence selection controls are available.
Interface Controls
The Appendices Factory deliberately exposes fewer controls than other generators.
- Create new appendix
- Edit appendix content
- Preview rendered output
- Emit final HTML
No automation, inference, or validation occurs.
Explicit Limitations
These limitations are defensive. They protect epistemic integrity.
- No hyperlinks
- No file pickers
- No evidence binding
- No cross-artifact resolution
Workflow
- Create a new appendix
- Assign identifier and title
- Author assessment or opinion
- Review for restraint and clarity
- Emit HTML
- Move into
/html/for publication
Design Principles
- Opinion must not masquerade as evidence
- Interpretation must not replace chronology
- The system must not persuade
- The reader must perform reasoning
- Absence of linkage is a safeguard
Appendices exist to make reasoning visible — not unavoidable.