Resources
Reference material for security verification.
GoSentrix is the independent security verification body for software delivery. Start with the public doctrine, then move into the terms, questions, and research that explain how security evidence earns authority across software delivery.
Doctrine and reference material
These are the materials that anchor the verification body category. Available resources link directly; planned resources are named without broken placeholder links.
The Verification Doctrine
AvailableThe public charter for how GoSentrix treats evidence, authority, replay, AI signals, and its own claims.
FAQ
AvailableCommon questions about verification authority, replayability, field-proven status, and AI signals.
The Glossary
AvailableDefined terms for evidence states, authority, disproval, replay, attestations, and verification acts.
Claims Registry overview
In developmentA public summary of how GoSentrix assigns evidence status to its own capability and maturity claims.
Research and writing
We will publish papers only when the underlying work exists. No fake bylines, stale dates, or download buttons that lead nowhere.
Planned public paper
AI Can Be Probabilistic. Security Authority Cannot.
How AI signals can enter the evidence ladder without becoming the source of enforcement authority.
Planned public paper
The Future of Security Evidence Authority
Why the enterprise question is shifting from what was found to which evidence can support an action.
Planned public paper
Graph Models for Security Evidence
How relationship-aware evidence models support replayable decisions across code, merge, release, and runtime.
Videos
Videos are not published yet. When they are, this page will show real assets with real attribution. The current production priorities are:
- Hero explainer: what a verification body is and why software delivery needs one.
- Replayability walkthrough: how one decision can be reproduced against its original evidence and policy version.
- AI authority explainer: why AI signals enter as claims, not authority.
- Founder POV: the company thesis and the rules GoSentrix is binding itself to publicly.
Verification readiness self-check
This is not a score for your team or your tools. It is a diagnostic for the security delivery pipeline: where evidence is captured, where authority is granted, and where decisions can be defended later.
Can you replay a release decision made six months ago against the policy active then?
When a developer marks a finding fixed, what evidence is captured?
If an AI review agent flags a vulnerability with high confidence, can it block a merge by itself today?
When required proof is missing, does the system deny the action or silently allow it?
Technical documentation
Technical documentation is in development. For technical questions during this phase, contact us directly.
Contact GoSentrix