Spartan Transport
A command platform for the secure fugitive transport and court-ordered extradition industry, replacing paper dispatch with a unified operational picture. Built around one idea: in this work the record is the evidence, so custody, signatures and audit trails are engineered to be answerable in court years later. Described at capability level — operational detail is deliberately withheld.
./visit --live spartantransport.live ↗- Access tiers
- 7
- Custody record
- Append-only
- Signatures
- SHA-256 sealed
A clipboard cannot answer the question that matters
Secure transport ran on paper dispatch, manual personnel management and disconnected communication tools. That is survivable until the day a transport is challenged — by a court, an agency, or opposing counsel — and the question becomes who held custody, at what time, and where. A record assembled afterwards from memory and paperwork is exactly the record that does not hold up. The platform was built on the premise that in this industry the record is the deliverable, not the paperwork around it.
Custody is written as it happens
A transport moves through a defined lifecycle, and every action appends to an immutable record rather than updating a row. Position and time are captured at each stage, and distance is computed per leg rather than estimated at the end. Because entries are only ever added, the chain cannot be quietly tidied up after the fact — which is the entire point of keeping it.
- PendingAssignment created and allocated
- AcceptedAssignment acknowledged by the assigned operator
- In transitPosition and time appended as the movement proceeds
- CompletedClosed out with the full chain intact and queryable
Signatures engineered for non-repudiation
Nobody reaches operations until four legal agreements are signed. Each signature seals a cryptographic hash of the exact document content alongside the signer's typed legal name, the timestamp, and the originating context — written into a vault with no update or delete path at the database engine level, and retained for seven years. The design references NIST SP 800-86 for evidence chain of custody and the E-SIGN Act for electronic validity, under 34 U.S.C. § 60103, the governing federal statute for prisoner and detainee transport. The result is a signature that can be proved against the exact text that was agreed, rather than merely asserted.
Terms, privacy, non-disclosure and non-solicitation — enforced at the gate, not by policy alone.
No update or delete path exists at the database level. Seven-year retention.
Seven tiers, enforced by the database
Access runs across seven role tiers, from full platform authority down to a read-only audit role. Separation is implemented with row-level security on every table, so an operator sees their own records, a coordinator sees their people, and an administrator sees the estate — enforced at the data layer rather than by hiding controls in the interface. The privileged server key is confined to server-side operations and never reaches a browser.
Hold what you must, and nothing more
Warrant and case research is pulled live from official government sources and passed straight through — read-only, with nothing retained in the platform. Operational awareness feeds are queried live rather than accumulated. That is a deliberate security posture rather than an oversight: data that is never stored cannot be breached, cannot be subpoenaed from the wrong party, and cannot quietly go stale. For a system that already holds sensitive personnel records, every category of data it can decline to keep is a liability it does not carry.