Package evidence (LEO)
Assemble a reviewer-ready evidence pack.
Packages scoped inputs, claims, sources, and manifests into a reproducible pack.zip artifact.
Civitas Analytica
EPI Rail offline evidence packs you can verify locally.
Civitas EPI Rail packages reviewer-ready evidence for ISO 27001, SOC 2, NIST CSF, and related library baselines, with portable outputs for procurement, diligence, and internal review.
Quick orientation
What EPI Rail is for
Who it is for
Teams preparing evidence for audit, diligence, vendor review, procurement, or internal control review.
What problem it solves
Turns scattered evidence into a versioned pack that can be checked locally instead of passed around as ad hoc review material.
What comes out
Pack.zip, manifest and seal, reviewer documents, and verifier output that can travel with the decision record.
North Star: Human dignity • Epistemic truth • Bounded autonomy
What the workflow does
Verify locally (EPI CLI)
Check integrity and structure offline.
Validates pack structure locally and emits stable JSON for review records.
Review evidence (Viewer + drift)
Inspect claims, artifacts, and drift over time.
Review surfaces keep claim-to-evidence context and drift deltas visible for audit and procurement review.
Operating model
Portable evidence packaging for teams under real scrutiny.
Why it matters
High-consequence reviews need traceable evidence, local verification, and outputs that survive handoffs. Civitas keeps each claim tied to evidence.
How the workflow moves
- 1. Inspect proof
- 2. Buy
- 3. Generate
- 4. Verify
- 5. Review
Deterministic packaging keeps pack contents, seals, and verification outputs inspectable end to end.
Custom pack/library requests: email hello@civitasanalytica.com.
Outputs
- Pack.zip + manifest + seal
- DecisionPack.pdf/html + verify.json
- Claim-to-evidence review context
Portable artifacts, explicit assumptions, and bounded scope.
Proof, not promises
Review the method and evidence directly.
Civitas does not imply partnerships or make claims that cannot be verified. Public statements should resolve to packs, verification outputs, methods, or measurable results.
Browse
Start with the product if you need the bundle. Use proof and verify when you want to inspect the method directly.
Scoped path
Need a fixed-scope engagement or custom pack?
Use Solutions when the work should be delivered as a bounded diligence, governance, or trust-review engagement. Use Request intake when you need a custom pack or a scoped commercial reply by email.
Artifact-first proof
What you can verify
- Versioned packs (ZIP + manifest + seal)
- Local verification (tamper-evident)
- Drift reports over time
- Reproducible methods (commands + inputs + outputs)
Insights
High-signal analysis, calm delivery.
Research
Zeta + methods + benchmarks.
Reproducible runs, clear claims, and artifacts you can audit.