1. Purpose and Scope
The Factory is a set of authoring instruments designed to manufacture structured evidential artefacts from user-supplied inputs, without embedding interpretation, outcome, or advocacy into the production process.
Its purpose is not to analyse events, determine liability, or persuade a reader. Its purpose is to enforce discipline at the point of creation, so that downstream artefacts remain inspectable, reproducible, and resistant to narrative distortion.
The Factory operates entirely offline, without external dependencies, network access, or backend services. The markup panels in each Authoring system displays the canonical system output. It is read-only within the platform. Any modification outside the platform falls outside governed continuity and should be independently validated.
2. Definition of “Factory”
Within this system, a factory is defined as:
A factory:
- does not contain case-specific knowledge
- does not inspect or depend on existing artefacts
- does not infer meaning beyond what the user explicitly supplies
It applies structure, not interpretation.
3. Core Design Principles
3.1 Separation of Authoring and Artefact
The Factory exists only to construct artefacts. The artefacts it produces are standalone documents, readable without the Factory present.
This separation is deliberate and mandatory.
- The Factory is a toolchain component
- The artefacts are release components
- The Factory must be removed prior to distribution
This prevents post-hoc modification, silent revision, or adaptive rewriting after release.
3.2 Determinism and Reproducibility
Given the same inputs, the Factory will always produce the same output.
- No stochastic behaviour
- No auto-completion
- No heuristic rewriting
- No content inference
This allows third parties to audit how an artefact was constructed rather than being asked to trust what it asserts.
3.3 Structural Constraint Over Narrative Control
The Factory enforces structural rules, not correctness.
- Chronology entries must be bound to dates
- Claims cannot introduce facts not present in the chronology
- Claims Heads cannot introduce law not tested in the Claims Matrix
- Appendices cannot function as evidence or timelines
The Factory does not judge whether content is true. It ensures content is placed where it is allowed to exist.
4. Artefact Families Produced by the Factory
4.1 Chronology and Contextual Search
The chronology factory produces a time-ordered chronology artefact and a contextual search artefact built over the same chronological corpus.
Chronology constrains sequence. Search constrains association.
Together, they prevent both temporal distortion and decontextualised extraction.
4.2 Claims Matrix
The Claims Matrix provides a structured testing surface where facts from the chronology are mapped against potential legal provisions.
It records arguability. It does not assert outcomes.
4.3 Claims Heads
Claims Heads are synthesised only after the chronology and claims matrix exist. They enforce downward-only linkage and may not expand the evidential universe.
4.4 Appendices
Appendices are non-temporal explanatory artefacts. They explain patterns or structures that cannot be expressed as dated events.
5. State Handling and Backup Discipline
The Factory maintains local working state solely to protect the user during construction.
- State persistence is explicit
- Backups are user-controlled
- JSON outputs are inspectable
The Factory does not silently alter committed content.
6. Intended and Prohibited Uses
Intended Use
- Construction of disciplined evidential artefacts
- Support for oversight, legal review, or scrutiny
- Preservation of authorial agency without narrative inflation
Prohibited Use
- Advocacy masquerading as structure
- Outcome-driven drafting
- Retrofitting facts to conclusions
- Shipping the Factory with released artefacts
7. Release Boundary
- The
/toolchain/directory must be removed - Only emitted artefacts remain
- No authoring interfaces are exposed
Release is an irreversible boundary.
8. Conclusion
The Factory is not an editor, advisor, or judge.
It is an instrument for manufacturing constraint.
It does not make arguments stronger. It makes them harder to evade.