Deterministic boundary model
DVS separates source, authority, policy, review, replay, and receipt checks before downstream movement.
Public-safe technical review start
Current proof floor for DVS, without exposing internal mechanics.
This page is the public-safe summary of what is reviewable now. It keeps the claim ceiling explicit, states what is real today, and separates public disclosures from deeper scoped technical review.
This page is a bounded disclosure surface. It is not a public code release, not a production claim, and not an unrestricted proof repository.
Current proof floor
What is real today
The current public-safe ceiling is a bounded proof floor: deterministic boundary logic, local-alpha review evidence, and adversarial review results that can be described honestly without publishing the full internal engine.
Recorded baseline reproduction
A reproduced five-scenario demo and a documented ten-scenario release-gate packet exist as local review evidence, with structured receipts and metrics.
Adversarial red-team expansion
Twenty-two payloads were run through the real Governor decision path with zero downstream propagations, zero crashes, and zero true false-passes in that run set.
Trust-layer hardening review
A surgical self-attestation fix was reviewed and re-run without introducing new breaks; the deeper propagation-veto follow-up is still a separate item, not a completed claim.
Claim-boundary discipline
Public copy is intentionally capped at local-alpha / prepilot / patent-pending unless stronger source-backed evidence is separately promoted.
Scoped next step
Deeper repository and code walkthroughs remain available by scoped technical review, not by an unrestricted public proof-repo claim.
Why this page exists
A public-safe summary should not outrun the evidence.
The public website needs to show the strongest safe version of current progress without exposing internal mechanics, customer data, private review scaffolding, or unsupported maturity claims.
The active GitHub repository is not being presented here as a public proof repository. Deeper repository review is scoped and human-routed so the disclosure path stays aligned with the current claim boundary.
This keeps the public surface useful for research, diligence, and application routing while preserving the internal engine boundary.
Non-claims
What this page does not claim
- Not production-ready.
- Not externally validated or customer validated.
- Not security certified, compliance certified, or legally certified.
- Not a durable production ledger claim.
- Not a full public proof repository or unrestricted code disclosure.
- Not a claim that all deeper hardening work is complete.
Deeper review path
What happens after this page
A deeper technical review can include the bounded architecture packet, claim-boundary materials, selected evidence artifacts, and a scoped repository walkthrough.
That deeper path is not assumed public. It is routed through a technical review request so the exact audience, purpose, and disclosure boundary are explicit before more material is shown.
This preserves the difference between a public-safe disclosure floor and a scoped technical diligence path.