Operated in the client environment
The engine is a CLI application a senior architect operates inside your environment. The source code does not need to leave your network to be analyzed.
Security & Data Handling
Deterministic evidence first. Client-controlled AI, if approved.
Evincia separates initial evidence generation from any later AI-assisted synthesis. The diagnostic starts inside the client's environment, and the client controls whether AI is used and where approved outputs may be processed.
The initial evidence boundary
Evincia's diagnostic engine is deterministic and does not use AI to scan source code or generate the initial evidence set.
No required external network calls
Nothing phones home while the evidence is generated. A run on a network-isolated machine produces the same evidence set.
Rules before inference
The initial outputs come from a fixed rules engine, so the same code in yields the same evidence out -- every run, reproducible on request.
A defined handoff
Any AI involvement begins only after the deterministic outputs exist -- a boundary you can see in the run artifacts, not a policy you have to take on faith.
AI is a later, optional step
AI-assisted synthesis is optional. The engine can run with it turned off entirely -- the run stops at the deterministic evidence set.
When AI is off
The deterministic evidence set is complete on its own. A senior architect carries the analysis through to the report without AI touching the work.
When AI-assisted synthesis is approved
The client decides where and how outputs are processed: inside the client environment, against the client's designated model, or with client-approved external tooling.
The no-required-external-network claim applies to generating and gathering the initial evidence; everything after that boundary is governed by the client's rules.
The handling claims, in one place
These are the operating claims Evincia uses when describing the diagnostic and its optional AI-assisted synthesis.
- Evincia's diagnostic engine is deterministic and does not use AI to scan source code or generate the initial evidence set.
- The diagnostic engine is a CLI application operated by a senior architect in the client's environment.
- No external network calls outside the client's network are required to generate and gather the initial evidence.
- Initial outputs are created by the deterministic rules engine, not AI inference.
- AI never generates a finding. When AI drafts the narrative, a machine grounding gate fails any run whose narrative cites evidence the deterministic output does not contain.
- AI-assisted synthesis is optional, happens only after deterministic outputs exist, and can be turned off entirely.
- If AI-assisted synthesis is approved, Evincia follows the client's rules for where and how outputs may be processed -- inside the client environment, against the client's designated model, or with client-approved external tooling.
For the full diagnostic sequence, see How Evincia Works. For information collected through this website and related communications, see the Privacy Policy.
Put the client's rules on the table before the work starts.
The evidence boundary is not a policy promise -- it is how the tool works. Bring your rules for AI and data handling to the scoping conversation and the engagement is shaped around them.