A core that does not change.
Plugins that do.
PARALLAX RC® separates what must stay stable from what must keep moving. The core holds ingestion, the indexes and the custody record. Everything that touches the outside world — formats, models, repositories — is a plugin, versioned and replaceable without re-ingesting a corpus.
Four layers, and only one of them is fixed.
A finding has to be reproducible years later. That is only possible if the layer that records it never changes shape — and if everything volatile sits outside it, behind an interface.
Access layer
Repository connectors reach files where they already live. Nothing is exported, and your access model is inherited as it stands.
Reading layer
Format handlers turn a file into text, structure and metadata — whole, never chunked, with the digest of the bytes read.
Core
Five parallel indexes, the semantic linter and the custody record. Deterministic, versioned, and the same for every domain.
Answering layer
Retrieval, chronologies and drafting assistance. Where a model is used it drafts around cited passages; it never invents one.
Read where they are, in the format they arrived in.
Ingestion does not move your material. Files stay on the NVMe volume they already occupy, and the engine reads them natively, in place. What is produced is an index and a custody record — never a second copy of the corpus.
Nothing is converted, so nothing is altered.
Every conversion is a transformation of the evidence: a re-encoded PDF, a flattened drawing, a re-saved spreadsheet. Each one introduces a difference between what you produce and what was issued. Reading in place removes that step entirely — the file examined is the file received, byte for byte, and the digest proves it.
Files stay in place
The volume is mounted and read. No staging area, no export, no duplicate to secure and then dispose of.
Format identified
The engine identifies what each file actually is from its own bytes, not from the extension it happens to carry.
Handler resolved
The identified format is matched against the installed handlers; where none is installed, the compatible handler is named.
Read and sealed
The handler reads the file entire and records a SHA-512 of the bytes it read, so every later citation is replayable.
A file the engine cannot read is reported as unread, with its format named. It is never partially parsed and never silently skipped — an unread file you know about is a decision; one you do not know about is a hole in the record.
What comes out is what was written.
Extraction is verbatim. A passage leaves the file as the characters it contains — not normalised, not paraphrased, not summarised on the way out. The ingestion engine records the digest of the bytes it read, so the passage and its source stay bound together for the life of the matter.
No rewriting on extraction
Sealed content
Enhanced ingestion
Nothing generated in between
Three registers, read against each other.
Most matters already hold the answer across separate registers that nobody reads together. PARALLAX RC® builds each register from the corpus itself, then cross-checks them — so every drawing revision can be placed against the date it was issued, the date it was transmitted and the date the programme assumed it.
Drawing register
Every sheet and every revision found in the corpus, with the title-block date each one carries.
Correspondence register
Every transmittal, instruction and notice, with the header dates that say when it actually left.
Programme register
Every submitted revision of the schedule, with the activity dates each one assumed.
Every drawing revision, placed against the timeline.
Revisions issued but never transmitted
Revisions transmitted after the programme relied on them
Sheets referenced in correspondence but absent from the register
Revisions matching issue, transmittal and programme
Each line of the cross-check opens on the three documents that produced it: the sheet, the transmittal and the programme revision. The finding is not a judgement about the record — it is the record, put side by side.
What a plugin is allowed to be.
Format handlers
One handler per format family: it knows what the file actually is, and presents it whole.
LLM plugins
A model is an interchangeable component at the edge, never the place where facts are decided.
Repository connectors
Read-only adapters to the systems your organisation already runs, over the Model Context Protocol.
Why a plugin architecture is what makes this scale.
Every regulated domain brings its own formats, its own repositories and its own obligations. A monolith answers that with a rewrite. An interface answers it with a plugin.
Request access