Files read in place,
never copied.
Every file enters through a single gate. Format control runs in quarantine before any passage reaches an index. Nothing moves. Nothing is converted. The file you cite is the file that was sealed.
LLX-ARCH-ING · R1
A single gate. No file bypasses it.
The ingestion gate is the only path into the corpus. A file that has not passed format control does not exist in the index. The gate is not a scanner — it is a proof-of-format check.
Format declaration
The handler declares the file format before reading begins. If the declaration cannot be made, the file is held in quarantine.
Zero execution
No file is executed, rendered or previewed during ingestion. The handler reads structure and text only. Macros, scripts and embedded objects are never run.
Quarantine on failure
A file that fails format control is isolated and logged. The operator is notified. The corpus index is never written with an unverified file.
Audit trail at the gate
Every file that passes or fails is logged with a timestamp, the handler version, the declared format and the outcome. The log is append-only.
No file is trusted until the handler clears it.
Zero Trust ingestion means no implicit authority. A file named .docx is not a Word document until the handler has read the binary structure and confirmed it. Name, extension and MIME type are discarded until the format proof succeeds.
Extension ignored
The file extension is not used to select a handler. The handler is selected by reading the file's binary header. A .pdf that is actually an image is handled as an image.
No rendering path
The engine has no rendering surface. There is no display, no preview, no font engine. A file that requires rendering to extract text cannot inject anything.
Isolated handler process
Each handler runs in an isolated process. A malformed file that crashes the handler does not reach the index. The gate logs the failure and moves on.
Read-only mount
The corpus storage is mounted read-only during ingestion. The engine cannot write to, rename or delete a source file under any condition.
The engine reads the NVMe it sits on.
Files are never copied before indexing. The handler reads the file from the NVMe it occupies, passes the extracted text to the indexer, and is done. The source file does not move and is not altered. What is indexed is what exists.
No staging copy
There is no staging area and no temporary copy. The handler opens the file in place, reads it, and closes it. Disk usage for ingestion is zero beyond the index itself.
No format conversion
The file is never converted to an intermediate format. A .docx is read as a .docx. A .dwg is read as a .dwg. Conversion introduces loss. PARALLAX RC® introduces none.
Sub-second per document
In-place NVMe reads at native speed. A 500-page disclosure set ingests in the time it takes a competing system to copy the first file to staging.
Source integrity maintained
The file's last-modified timestamp is not changed. The file's access permissions are not changed. The file is exactly as the custodian held it.
The passage is sealed to its source.
Every passage extracted by a handler is sealed with a SHA-512 hash of its source position in the source file. The seal proves the finding came from that byte range, in that file, at the moment of ingestion. The seal is stored in the custody record and cannot be rewritten.
SHA-512 seal
Each passage carries a SHA-512 hash derived from its byte offset, length and the file's own hash. A passage that has been altered does not match its seal.
Custody record
The custody record logs the file path, file hash, handler version, ingestion timestamp and the seal for every extracted passage. The record is append-only and signed.
Chain of custody
The seal chain links each passage to its file, each file to its ingestion event, and each ingestion event to the operator who authorised it. The chain is auditable at any point in the chain.
VERBATIM compliance
A finding produced from a sealed passage can be presented as verbatim evidence: the passage is as it was in the file, the file is as it was on the NVMe, the NVMe is as it was at ingestion.
The corpus is sealed before the first query.
Ingestion is not a preprocessing step. It is the forensic act. Everything that follows — retrieval, chronology, register, finding — rests on what the gate passed and the handler sealed.
Request access