Module
Knowledge Base Turn a facility's folder of technical reports — stability studies, monitoring, closure plans, manuals, protocols, TARPs — into something you can ask, and that answers citing the page.
"It's in the stability report" is not an answer. "Page 47, revision C" is.
The problem
What happens today at a facility
A facility's knowledge sits in documents nobody opens again. Not because they don't matter: because finding the answer requires knowing which report it is in, and the person who wrote it is the one who knows. When that person moves to another project, the document stays in the folder and the knowledge does not.
And there is a quieter problem underneath: nobody knows which version rules. The same folder holds the report at revision B, the same one at C, and the approved one. A TARP pointing at the wrong revision is a correct procedure executed against a threshold that no longer exists.
Twin Mining TMS ingests the corpus once — conversion to PDF, the original archived, metadata transcribed from the cover page — and from then on it is indexable, searchable and citable. The assistant proposes an answer, cites the document and page, and signs it; the person decides what to do with it.
What it does
Capabilities, with their nuance.
-
The citation carries the page
Ask in plain language and the answer cites the document and the page it came from, not just the file name. That is the difference between an answer and a hint, and it is verified in one click.
The sources panel has a fixed place: it is not an appendix to the answer, it is half the product. -
Three advisors, one engine
Protocols advisor, technical advisor and GISTM compliance are three configurations of the same query engine over the corpus, not three products. Each proposes, cites the document and page, and signs; the person decides.
Six different ways into the same corpus, because looking up a value and auditing a requirement are not the same task.
-
Revision control from the trade
A document runs through the letters A, B, C while under review and reaches 0 when the client signs and validates it. Zero is terminal: a later change is a new document that starts at A and points at the one it replaces. That is how tailings engineering actually works.
-
Nothing is derived
No metadata is invented. Title, date and type are transcribed from the document's cover page, not from the file name, and a field nobody wrote shows up empty rather than filled with a plausible value. In a module whose output is used as evidence, an invented metadata field is worse than none.
-
Figures come out of the PDF and stay objects
Figures and charts are extracted from the documents and become addressable: they can be opened, combined with one another and used as the basis for a new chart.
-
A graph you can walk
A knowledge graph links documents, studies and people by their declared relationships, and lets you walk from a report to what replaced it or what cites it.
Your folder holds the same report at revision B, at C and approved. Which one rules?
Scope
What it decides and what it does not
What it works out on its own
It answers and cites. Every statement from the assistant carries the document and page it came from, and the interface shows the sources beside the answer, not underneath in small print. The sources panel has a permanent place of its own, even when empty.
What it never decides
It does not decide what is true, approves nothing and changes no state. And it does not derive: a field nobody wrote shows up empty. An earlier version fabricated plausible metadata from an identifier; the screen looked complete and it was fiction.
Honesty
What it does not do yet, on purpose.
We would rather say it before the first meeting.
- In the demo the corpus is a simulated catalogue, byte-for-byte reproducible and with no network calls. That is a presentation choice, not a product limitation — but no capture shows a client's documents. A technical report identifies the facility on its cover page.
- "Three advisors" are three configurations of the same engine. They are not three specialized artificial intelligences.
- The assistant answers and cites. It does not decide, approve, or change any state. Models get things wrong; that is why the page-level citation is verified in one click and the module prefers an empty field to a plausible one.
- The search and assistant captures show the layout, not an answer in progress: they are taken right after opening.
Who it is for
Who comes in through here
- RTFE — Responsible Tailings Facility Engineer Something crosses a threshold and they find out late.
- Engineer of Record Something that compromises their design gets changed without anyone asking them.
- Corporate compliance lead Having to explain where a green came from in front of the reviewer.
- Geotechnical engineer A value they know is written down in some report.
- Independent reviewer / auditor That the trail does not exist.
Frequently asked questions
What people usually ask about this module
Short answers with no overclaiming. If something is not built yet, we say so.
Which documents does the Knowledge Base accept, and how does it handle revisions?
The documents a tailings facility lives with: stability studies, monitoring reports, closure plans, operating and instrument manuals, emergency protocols and TARPs. Ingestion converts each document to PDF, archives the original and transcribes title, date and type from the cover page, not from the file name; deriving them produced invented titles that later contaminated the citations.
Revision control follows the trade: a document runs through the letters A, B, C while under review and reaches 0 when the client signs and validates it. Zero is terminal. A later change is a new document that starts at A and points at the one it replaces, so it is always clear which version rules.
Language models make things up. How do I know a Knowledge Base answer is true?
That is exactly the right objection, and the answer is built into the module. The assistant proposes an answer and cites the document and the page it came from, not just the file name; the citation is verified in one click, and the sources panel has its own permanent place beside the answer, even when empty. A person decides what to do with it.
And one rule governs the whole module: nothing is derived. A field nobody wrote shows up empty instead of being filled with a plausible value. The assistant does not decide what is true, approves nothing and changes no state.
Does Twin Mining's artificial intelligence make decisions on its own?
No. Agents propose and cite; people decide. This is not a stated policy: it is in the data model. An agent suggestion enters a state that blocks until a person confirms it, and that confirmation is a second event with its own author and timestamp.
An agent never takes part in evaluating state transitions, and every verdict is signed with the model and prompt version that produced it, so an external reviewer can reconstruct where it came from.
Nothing is inferred from nothing either: every edge of the impact graph corresponds to a real relationship in the data model and declares whether it is stated or derived. Deterministic computation first, model narration second — inverting that order would let the model invent the pattern with no way to check it.
Other modules
What connects with this module.
- Management of Change We know who signed. We don't know what they had in front of them when they signed. That is the problem. See the module →
- GISTM Your GISTM self-assessment is green. When did anyone last open the document that supports it? See the module →
- Agents It's three in the morning and the ground just shook. Where is the TARP? See the module →
- Operations Your facility's water balance lives in a spreadsheet that only one person understands. See the module →
- Physical Stability The engineer thinks about the dam in section. Monitoring software shows it in plan. See the module →
- Twin Model Fleet in one system, works in the contractor's drawings, facility in another. Where do you see them together? See the module →
Request a demonstration
Let's talk about your facility.
Tell us which facility you manage and what keeps you up at night. We will walk you through the demonstration environment with someone from the team, module by module, and tell you frankly what is built and what is not.
- We reply within 24 business hours
- Guided demonstration, tailored to your operation
- No commitment. There is no public price: we talk