Publish less. Stand behind more.
This library now exposes only notes that have been reviewed for the current public evidence boundary. Historical research remains in source history until its time-sensitive claims and disclosure surface are re-verified.
Research material is not customer proof, certification, legal advice or a current runtime claim. Time-sensitive facts should be re-verified against primary sources before operational use.
Security Sandboxing
Public-safe note on isolation boundaries and tool-execution controls without private infrastructure disclosure.
Fleet Coordinator Drift Monitoring
Public-safe architecture note focused on drift concepts rather than live internal telemetry.
Tool-I/O Bridge Contract
Public-safe interface contract that excludes private operator-control routes and internal endpoints.
Before an AI agent gets write access
Seven questions to answer with evidence before an agent can change records, money or code.
MCP server authority review
Source-backed review of 20 open-source MCP servers through BitEvo's seven authority gates.
Bitget authority after orchestration compromise
What source-bound evidence shows about detection, effect authority and external confirmation.
Historical notes are offline from the public build.
Older pages mixed research, historical metrics and time-sensitive technology claims. Rather than present them as current evidence, BitEvo keeps them out of the public build until each note is reviewed against present sources and disclosure rules.
Removing a public route does not delete its Git history.
The audit uses scoped evidence, not public research as proof.
Commercial findings are produced against an agreed workflow, Rules of Engagement and reproducible evidence criteria.
See audit methodology