EVIDENCE & PROOF
Match every claim to the evidence that can support it.
Public pages describe Cortrova and the work it is designed to address. A buying or production decision should rely on dated, release-specific, environment-specific, and contract-specific evidence.
EVIDENCE LADDER
From a public statement to accepted behavior.
The stronger the decision, the closer the evidence should be to the exact release, configuration, environment, data, and responsible owner.
Public identity
Cortrova is the product brand; Trunnion AI, LLC is the operator; Duskbridge, Inc. is the parent holding company.
Product scope
A written proposal identifies included, configurable, custom, planned, excluded, or unavailable items for the proposed release.
Architecture and controls
Dated diagrams, responsibility mappings, configuration, provider details, and test results support environment-specific review.
Security and AI
Security and AI claims are evaluated against the proposed data, deployment, providers, human controls, and evidence.
Workflow acceptance
Representative and failure scenarios are tested with owners from the departments that create, approve, change, and consume the records.
What is public today
The website provides operator identity, high-level product positioning, evaluation guides, policy notices, clearly labeled concept illustrations, and hypothetical workflow scenarios. The verified public facts page and citation guide summarize the boundaries.
What is not represented as proof
Cortrova does not currently publish a named customer deployment or quantified customer outcome on this site. The illustrative scenarios are not testimonials. The site also does not use a product page as evidence of certification, guaranteed compliance, universal feature or integration availability, a fixed implementation timeline, or a universal price.
What to request during diligence
- A dated scope and capability matrix for the proposed release.
- Architecture, data-flow, identity, provider, integration, and responsibility records.
- Demonstrations using approved representative and failure scenarios.
- Configuration, test, exception, accessibility, security, privacy, AI, recovery, and acceptance evidence appropriate to the scope.
- Written commercial, implementation, support, renewal, export, and exit terms.
How customer proof will appear
A named customer story should be published only with permission, the relevant scope and time period, a clear source for any result, and limitations needed to prevent a single deployment from becoming a universal claim.
Your next step
Ask for evidence that matches the decision.
Tell us the workflow, release, environment, integration, control, or commercial term you need to evaluate.