The session determines the workspace for each request, and access validates the investigation within that context. Fine-grained object policies are not presented as complete.
ARCHITECTURE AND ISOLATION
Sensitive material needs to stay within the right context.
Sessions, workspaces, and investigations form the implemented access boundaries. Originals remain separate from derived artifacts, and the deployment design defines where processing occurs.
Request a demoCENTRAL QUESTION
How do we keep context, access, and processing separate across investigations?
01Workspace
02Investigation
03Object
04Permission
05Processing
Workspace
Investigation
OriginalsImmutable, versioned, with a fingerprint.
DerivativesTranscripts, extractions, and projections.
ObjectsRecords, actors, contexts, and evidence.
ReviewsStates, human decisions, and authorship.
PublicationsReleased dossiers, with version and responsible person.
The current layer defines workspace and investigation boundaries. Fine-grained object authorization within an investigation remains an explicit future evolution, not a published guarantee.
Original material remains separate from derivatives, with SHA-256 and a recorded custody chain.
Hash-linked events preserve authorship, state, and sequence. History does not depend on the team’s memory.
Roles are resolved in the database. States and human decisions record who reviewed, confirmed, or rejected a reading.
An external call enters a ledger with provider, model, purpose, and sent objects. Material kept local stays local.
Period, policy basis, exceptions, and deletion are deployment decisions—declared, not assumed.
01 · WORKSPACE
The session bounds access and operation.
An opaque cookie identifies the session; workspace and role are resolved in the database; every investigation is validated within that context. Fine-grained object policies are not presented as complete.
- RLS by workspace
- Validation by investigation
- Role resolved in the database
02 · SOURCES
Originals and derivatives play different roles.
Received files remain immutable and versioned. Transcripts, extractions, and derived records are tracked separately.
- Preserved originals
- Identified derivatives
- Fingerprints
03 · PROCESSING
Deployment determines where each flow may run.
External providers, local processing, and retention policies are explicit choices, not generic promises for every situation.
- Local or external flows
- Explicit providers
- Policies by deployment
WHAT THIS LAYER DELIVERS
The result takes reviewable forms.
01Opaque, revocable session
02RLS by workspace
03Originals separate from derivatives
04Declared processing boundaries