Mobile
BuiltOn-device Android detection, the four input paths, and the live-capture feasibility measurements.
How a call is checkedDocumentation
Every claim VoxShield makes in public is traceable to a document. This hub points at all of them — the ones published with this website, and the ones that live in the product repositories.
Two kinds of entry below. Links open documents published with this site. Entries shown as repository/path.md live in the Console or Mobile repositories and are not mirrored here — they are named so you can ask for them rather than being sent to a dead link.
What each surface is, and what state it is in.
On-device Android detection, the four input paths, and the live-capture feasibility measurements.
How a call is checkedThe detection core, the decision layer, the console views and the enterprise layer specification.
Console tourNo package and no document of its own yet. The wire contract it would wrap is documented.
Planned shapeGrounded retrieval, citation format, refusal behaviour and the corpus it indexes.
How it answersArchitecture, the detection pipeline, models and the decision layer.
| Topic | Where | Covers |
|---|---|---|
| Architecture | technology.html | One process, one CUDA context, twelve stages. |
| Detection pipeline | technology.html#pipeline | Ingest through audit append, stage by stage. |
| Models | technology.html#models | Six components, licences, weights, devices. |
| Precondition gate | technology.html#gate | Four checks, six reason codes. |
| Language gate | technology.html#language-gate | Which languages are admitted, and why. |
| Risk fusion | technology.html#fusion | Weights, bounds and the disagreement rule. |
| Verdict system | technology.html#verdicts | Five verdicts, three-valued is_fake. |
| Frozen constants | Voxshield_Console/app/core/constants.py | Every threshold the product is built on. |
| Technical requirements | Voxshield_Console/docs/TRD.md | The specification the code is held to. |
Privacy posture, encryption, the audit chain and access control.
Zero raw audio persisted, no transcription, encrypted voiceprints, retention windows and DPDP framing.
Read itSHA-256 chaining, verification that names the first broken entry, and the three tested corruption paths.
Read itFive roles, the permission matrix, session handling and what no API will ever return.
Read itWhy there is exactly one outbound call in the codebase, and how that is tested rather than asserted.
Read itRepository sources: Voxshield_Console/docs/RULES.md, docs/claims/07-engineering-security-privacy.md, this site's own backend note.
Benchmarks, datasets, limitations and how to reproduce them.
| Document | Where | Covers |
|---|---|---|
| Measurements | benchmarks.html | Speed, capacity, cost and test coverage. No accuracy figure. |
| Why no accuracy number | benchmarks.html#why-no-number | What a single percentage hides, and what we do instead. |
| What we do not claim | benchmarks.html#limitations | Accuracy, language coverage, replay, carrier and bank integration. |
| Claim discipline | benchmarks.html#discipline | The never-say / say-instead table this site is held to. |
| Detection test runs | Voxshield_Console/benchmarks/results.md | Kept in the repository with their datasets and caveats, not advertised on the site. |
| Dataset notes | Voxshield_Console/docs/ | Which corpora were used, their licences, and how test sets were built. |
The wire contract that everything else would be built on.
# One object, every endpoint, contract_version 1.0
{
"contract_version": "1.0",
"verdict": "SAFE" | "SUSPICIOUS" | "HIGH_RISK" | "LOW_CONFIDENCE" | "ERROR",
"risk": 0-100 | null,
"risk_range": [ low, high ],
"is_fake": true | false | null, # null is not false
"reason_code": "NO_VALIDATED_SIGNAL" | ... | null,
"latency_ms": 308
}
14 REST endpoints and 3 WebSocket channels, documented in docs/API_CONTRACT.md.
Device tokens and recording upload are specified; metadata and a content hash are stored, never audio.
Not built. The contract above is the part that is already decided.
The documents behind this website, published with it.
Scope, audience, success criteria, and what is deliberately out of scope.
docs/PRD.mdThe locked stack: plain HTML, CSS and vanilla JS, static hosting, no build step.
docs/TRD.mdSection rules, the status-badge rule, and the definition of done.
docs/FRONTEND.mdA deliberate architecture decision, written down so nobody looks for a server folder.
docs/BACKEND_SCHEMA.mdProblem statement framing, demo script and the judge-facing guide.
The UI reference this site is built from: type, colour, status chips, components and motion.
Open the referenceMissing something?
Repository documents are not mirrored here, but they exist and can be shared.