A document leaves a partner's desk. It cites a rule that was current last Tuesday, in a jurisdiction whose regulator updated guidance overnight. The first reading is rarely the last.
Evidence accrues — KYC files, attestations, a screenshot from a counterparty's portal at 03:14 in São Paulo. The middle is where most journeys lose their footing. Tread carefully; keep the field notes.
A request arrives from a subsidiary on a different DMS, a different IdP, a different jurisdiction of disclosure. Some of what you know can be shared. Most of it cannot. The pass is wide enough only for what is permitted.
A regulator, an opposing counsel, or simply the next associate to inherit the file asks: how did you get here? The far shore is where the path becomes evidence. The path is the work.
An eight-pass pipeline reads a regulated document the way a careful first-pass reviewer would — structural, semantic, consistency, style, legal pack, synthesis — with jurisdiction-aware rules across 127 jurisdictions. Each finding records the rule it fired on. Review · Sentinel · Ledger.
A self-contained file — a ZIP wrapping a SQLite database, a hash-chained oplog and audit log, and the documents it speaks of. Made for compliance-sensitive workflows like Client Due Diligence. Offline-first. Syncs without a server. AES-256-GCM.
For enterprises whose subsidiaries, JVs and acquired practice groups run on different DMSes and IdPs. Sits above the silos rather than replacing them. Source binaries stay in the home DMS; a seven-level ladder (L0 – L6) governs what each requester sees.
Compliance has been treated as the residue of work — paperwork generated after the fact, by people who weren't there.
We think this is backwards. The artefacts — the redline, the field note, the citation — are the work. Anything else is reconstruction.
Parelion is a careful crossing: three tools that move with you, and a record clear enough that the next traveller can read the way you came.
Parelion · Glasgow · MMXXVI