About PRAE
PRAE is the security research practice of Null Ventures LLC in Chicago. We build the PRAE Platform for local security checks through MCP, publish Vigilance advisories and make tools for release reviews.
Why PRAE
PRAE takes its name from the Latin prefix meaning “before,” pronounced roughly “pray.” It names the principle behind the work: security requirements before implementation.
The work
We are developing a security-intent and verification engine for AI-assisted software. The aim is to make intended boundaries explicit, turn approved requirements into independently testable obligations, and keep the evidence current as software changes.
The Four Gaps—Permission, Behavior, Proof and Drift—give that work its method. The Field Kit and its 244-control register provide a practical foundation. Failure Ledger analysis and Vigilance reports contribute research and changing external context.
The integrated Boundary Contract Compiler and evidence-continuity architecture are proposed work, not a finished product or a demonstrated competitive advantage. Read the current status and the validation still required.
PRAE was previously called Null Security. Null Ventures LLC remains the publisher and product provider. Existing purchases, licenses and access links continue to work.
Editorial practice
Publications and research use stable identifiers, named editions or revisions, dated reviews and attributed sources. A source-listed advisory is distinct from an authored Failure Ledger analysis. Neither establishes the state of a reader’s application.
- State what the evidence supports and what remains unknown.
- Distinguish a disclosed vulnerability, a reported incident and a researcher demonstration.
- Keep source dates separate from publication and review dates.
- Record substantive corrections and preserve the context of earlier conclusions.
Read the Failure Ledger’s source and event labels or inspect Vigilance coverage and publication rules.
Corrections
Use the research correction form to identify the page, claim, supporting source and proposed correction. Do not send confidential customer records.
Contact
For publications, billing or access, use the contact page. Security vulnerability reports have a separate disclosure channel.