From a fragment of memory to an inspectable evidence path
Legacy does not begin by asking a person to name an asbestos product. It begins with the fragment that survived: a job, task, room, machine, supplier, coworker, family routine, photograph, or approximate year.
The reconstruction sequence
Start with the fragment
Capture the smallest reliable detail without forcing a product name or exposure conclusion.
Resolve people, places, tasks and time
Translate remembered language into searchable entities, aliases and date ranges.
Search the gravity wells
Government records, HHE reports, archives, catalogs, trust documents, court records and other inspectable sources become candidate evidence.
Label what the evidence actually establishes
Documented fact, corroborated relationship, investigative lead, or unresolved question.
Build the relationship path
Place ↔ time ↔ task ↔ equipment ↔ material ↔ manufacturer ↔ records ↔ witnesses.
Ask what remains unanswered
The missing piece becomes the next research question rather than an assumption.
What makes an Answer Packet different
A conventional page explains a topic. A Legacy Answer Packet is designed to help a human or retrieval system answer a specific historical question while preserving the chain of evidence.
- Question: the real-world problem being investigated.
- Documented: what a source directly supports.
- Inference boundary: what the source does not establish.
- Confidence: how strongly the relationship is supported.
- Next memory prompt: the fact that would most efficiently narrow the search.
- Source path: direct links so the evidence can be inspected independently.
The publication gate
Legacy's internal evidence model already separates primary documentation from limited propositions and research leads. A remembered brand, jobsite association or litigation allegation is not converted into a public fact simply because it is plausible. Significant claims must be tied to evidence that actually supports the proposition.