Source manifests
A manifest records what entered the investigation and under what rights. Public literature, licensed databases, private repositories, and uploaded data remain distinguishable throughout synthesis and export.
- Stable source identity
- Access and redistribution class
- Content hash when bytes are retained
- Admission decision and investigation scope
Verified artifact storage
Artifacts are uploaded through a lease-scoped service credential, capped per request, hashed before storage, and placed under tenant- and investigation-specific object keys. Metadata is trusted only after the stored object size and hash agree.
- 01Generate inside the isolated executor
- 02Hash and upload under the active lease
- 03Verify object metadata
- 04Commit the ready artifact record
- 05Expose retrieval only to authorized organization members
A connected review package
The review package should let another qualified person follow the work without reconstructing hidden context.
- Methods and protocol revisions
- Results, figures, and source data
- Supporting and conflicting evidence
- Code, dependencies, seeds, and environment receipts
- Decision log and known limitations
- Replication instructions and expected outputs
Publication is a new boundary
Finishing a private investigation does not make it public. Publication creates an explicit intent tied to an exact artifact-set hash, destination, and named approver.
A public paper may include approved findings and reproducible methods while excluding private repositories, licensed source material, and confidential intermediate work.
See the lifecycle in motion.
Pose a question and watch the governed investigation demo advance stage by stage.