Evidence model
Evidence is strongest when its source, scope and limitations remain visible.
Advanexus connects supported canonical events and module-specific evidence into a permission-aware investigation model while preserving the difference between a source record, a projection and a human workflow.
Canonical record and projection are not the same object.
A QueryExecution, DatasetVersion, AnalyticsRun, PipelineRun or FileVersion remains owned by its module. Assurance creates normalised events, entities and relations for bounded reading and investigation.
Projection hash has a narrow meaning.
It can show that a normalised Assurance row still matches its stored projection contract. It does not prove that the original source had a cryptographic chain or that the business result was regulator-approved.
Missing is different from unchanged.
Version comparison and reproducibility checks report unavailable, partial, legacy or not-assessed criteria instead of deriving historical values from a hash or current state.
Relations are permission-aware and bounded.
Evidence Graph and Execution Story follow recorded entity, run, correlation and source-event relationships. They do not expose hidden projects, unauthorised counts or a universal global lineage graph.
Package verification is technical, not legal magic.
Manifest member names, sizes and checksums can be verified for a scoped package. Digital signing, WORM controls, legal hold and jurisdictional admissibility remain separate decisions.
Next step
Start with the flow that cannot afford ambiguity.
Bring the systems, owners, rules, delivery obligations and evidence requirements that matter.
Discuss a critical flow