Software verification plan
Build a plan, challenge its acceptance checks and inspect the evidence that still remains open.
From intent to evidence
Verification library
Browse the full inventory of verification obligations, domains and frameworks. Published guides and check references are linked; planned entries show the topics still to develop.
327 obligation topics
32 domains
11 frameworks & contracts
31 published guides
01 check references
Planned entries are topic outlines, not completed guidance. A topic becomes a guide link after its content and evidence have been reviewed.
Featured guides
Start with a published guide.
Inspect the procedure, the recorded results and what remains unresolved.
Requirements-based testing
Turn a written rule into an independent expected response and stored effects, verify that the real operation ran, and interpret the observed result.
Negative testing
Check the required rejection and forbidden durable effects. Inspect an executed partial-write failure, rollback correction and reusable rejection record.
Why tests pass while bugs still ship
Find why a green suite can violate an approved rule. Use a free worksheet and a recorded worker-count setting example to assess inputs, assertions and repair limits.
Planned topics, guides and check references
Browse the full inventory.
327 obligations · 32 domains · 11 frameworks.
Published guides and check references are marked below.
402 entries
Publication status per entryNo entries match these filters.
Try a broader search or clear the filters to see the full inventory.
Obligations
Individual behavior, safety and verification topics. A planned title names the property to examine; it is not a recorded result.
- Planned
Access control enforced
- Planned
Access-controlled state mutation
- Planned
Access-denied behavior
- Planned
Account-existence disclosure
- Planned
Accounting delta safety
- Planned
Accounting input verified
- Planned
Accrual snapshots before state updates
- Planned
Accumulation bounded
- Planned
Action sizing from manipulation-resistant state
- Planned
Zero-address inputs checked
- Planned
Hash algorithm chosen deliberately
- Planned
Allowance race reviewed
- Planned
AMM price boundary checked
- Planned
AMM asset orientation reviewed
- Planned
Solidity assembly audited
- Planned
Atomic write
- Planned
Operation atomicity
- Planned
Combined attacker capabilities
- Planned
Authentication precedes expensive work
- Planned
Authentication posture declared
- Planned
Authentication tag verified before plaintext use
- Planned
Authentication attempts throttled
- Planned
Authorization membership graph consistent
- Planned
Bounded backpressure
- Planned
Price bands for quotes and execution
- Planned
Batched request work bounded
- Planned
Binary data preserved
- Planned
Binary framing: length bounds and byte order
- Planned
Block-environment dependence audited
- Planned
Boundary values
- Planned
Bridge migration supply conserved
- Planned
Bridge settlement liveness reviewed
- Planned
Browser embedding policy restrictive
- Planned
Compiler built-in argument domains
- Planned
Cache entries coherent across version boundaries
- Planned
Callback sandboxed
- Planned
Caller-declared type or structure validated
- Planned
Caller-supplied control field honored
- Planned
Cancellation observed
- Planned
Certificate chain validated
- Planned
HTTP client TLS and certificate validation
- Planned
Ciphertext bound to identity
- Planned
Client error detail redacted
- Planned
Commutativity
- Planned
Compiler warning reviewed
- Planned
Compound-operation atomicity under concurrency
- Planned
Concurrency at scale
- Planned
Concurrent operations
- Planned
Concurrent invariant preserved
- Planned
Confused deputy prevented
- Planned
Connection leak free
- Planned
Constant-time comparison
- Planned
Constrained principal scope preserved
- Planned
Container network namespace isolated
- Planned
Container syscall surface minimized
- Planned
Continuation checkpoint context bound
- Planned
Contract caller code-length gate reviewed
- Planned
Contract state lifetime matches semantics
- Planned
Control not silently disabled
- Planned
Coverage exclusions tracked
- Planned
Aligned coverage and slashing timebases
- Planned
Cross-chain oracle freshness reviewed
- Planned
Cross-chain rate-limit symmetry and recovery
- Planned
Cross-chain transition boundary aligned
- Planned
Cross-contract token compatibility reviewed
- Planned
Cross-engine rollout guarded
- Planned
Cross-field and referential validation
- Planned
Cross-module pattern consistent
- Planned
Cross-runtime validation parity reviewed
- Planned
Cross-structure key identity
- Planned
Cryptographic input structure validation
- Planned
Cryptographic randomness sampling domains
- Planned
Cryptographic transcripts bound to all inputs
- Planned
CSRF protection
- Planned
Deadline arithmetic
- Planned
Deadline semantics match economic settlement
- Planned
Deadlock recovery declared
- Planned
Delegatecall audited
- Planned
Delegatecall-only enforced
- Planned
Delegated order execution bound and atomic
- Planned
Delegated session lifecycle controlled
- Planned
Delegated spend authorization lifecycle
- Planned
Parser denial-of-service resistant
- Planned
Deployment and initialization checks
- Planned
Derivative mint requires backing
- Planned
Derived address canonicality validated
- Planned
Derived state consistency
- Planned
Determinism
- Planned
Deterministic signature or randomness documented
- Planned
Disk-quota bounded
- Planned
Documented behavior review
- Planned
Executable witnesses for documented contracts
- Planned
Documented interface semantics consistent
- Planned
Dual-clock guard composition reviewed
- Planned
Dual-path guards equivalent
- Planned
Edge cases
- Planned
Emergency stop effectiveness reviewed
- Planned
Empty input
- Planned
Empty-liquidity reward time reviewed
- Planned
Encoding-aware parsing
- Planned
Encoding safety
- Planned
Enforcement identity consistent
- Planned
Attached-value entrypoint reachable
- Planned
Just-in-time resistance in epoch-vesting rewards
- Planned
ERC1155 batch shape checked
- Planned
ERC20 allowance authorized
- Planned
ERC20 value conserved
- Planned
ERC4626 rounding and inflation reviewed
- Planned
NFT ownership and callback state consistent
- Planned
Error handling
- Planned
Errors propagated
- Planned
ETH value handled
- Planned
Event payload size bounded
- Planned
Expiry and validity-window checks
- Planned
Extension hook selector validation
- Planned
Extension per-pool storage isolation
- Planned
External-call concurrency bounded
- Planned
External-call failure observable
- Planned
External call recovery
- Planned
External-call timeout bounded
- Planned
External interface contract conformance
- Planned
External interface signature compatible
- Planned
External receiver custody reviewed
- Planned
Externally supplied URL scheme allowlisted
- Planned
Failure reason matches condition
- Planned
Filesystem operations use a single handle
- Planned
Net charge consistency for order fills
- Planned
Algorithm compatibility with FIPS mode
- Planned
Fixed-point rounding reviewed
- Planned
Flash-loan callback atomic
- Planned
Format string is a compile-time constant
- Planned
Forward-compatible schema migration
- Planned
Forwarded calldata canonical and authorized
- Planned
WebSocket frame-size bounded
- Planned
Freeze and sanctions checks on token exit paths
- Planned
Collision-free generated symbol names
- Planned
Governance parameter bounds reviewed
- Planned
Governance transition lifecycle reviewed
- Planned
GraphQL introspection policy declared
- Planned
Hash format deterministic
- Planned
Idempotency
- Planned
Idempotency-Key handling
- Planned
Indexed collection removal targets the requested element
- Planned
Input domain
- Planned
Input size bounded
- Planned
Intended interface reachability preserved
- Planned
Intended usage path review
- Planned
Interactive protocol state consistency
- Planned
Interface mutability contract honored
- Planned
Interface selectors collision-free
- Planned
Interface storage type consistent
- Planned
Intrusive collection links preserved
- Planned
Invariant preservation
- Planned
KDF iteration and cost-factor bounds
- Planned
IV and nonce uniqueness
- Planned
Signing-key separation
- Planned
Input domain behind audit-lead closure
- Planned
Known vulnerable component blocked
- Planned
Length-prefix validated against frame
- Planned
Limit-order input and output consistency
- Planned
Local wallet password strength
- Planned
Migration locks bounded
- Planned
Safeguards for external calls inside loops
- Planned
Low-level call checked
- Planned
Low-level call intent reviewed
- Planned
Malformed input
- Planned
Malformed-input recovery and explicit errors
- Planned
Manual memory ownership documentation
- Planned
Message sender origin authenticated
- Planned
Meta-transaction context preserved
- Planned
Mid-callback transient identity
- Planned
Mitigation origin traced
- Planned
Mobile reauthentication on resume
- Planned
Mobile secret store access control
- Planned
Fund movement independent of reward APIs
- Planned
Monotonicity
- Planned
Name resolution before chroot
- Planned
Nil safety
- Planned
No filesystem in trust boundary
- Planned
No selfdestruct without release authority
- Planned
No tx.origin authorization
- Planned
Nominal behavior
- Planned
Operation outcome recorded faithfully
- Planned
Compiler optimization semantics preserved
- Planned
Optional state absence distinguished
- Planned
Oracle bound manipulation reviewed
- Planned
Oracle refusal gates: content and delivery checks
- Planned
Oracle source trustworthy
- Planned
IPC ordering guarantees documented
- Planned
WebSocket Origin check enforced
- Planned
Output encoding correct
- Planned
Overflow safety
- Planned
Package dependency versions pinned
- Planned
Aligned field access in packed layouts
- Planned
Panic-free input handling
- Planned
Parameter boundary safe
- Planned
Parameterized queries (read path)
- Planned
Parameterized writes
- Planned
Parsed references reconciled with notarized set
- Planned
Parser accepts only spec-valid, downstream-consistent instances
- Planned
Path identity canonicalized
- Planned
Path normalization consistent
- Guide available
- Planned
Path traversal prevented
- Planned
Pause does not block debt collection
- Planned
Pause lifecycle safe
- Planned
Periodic state iteration bounded
- Planned
Permission prompt matches grant scope
- Planned
Permissionless state collection liveness reviewed
- Planned
Permissions set at creation
- Planned
Permit nonce and domain checked
- Planned
Persistent state schema initialized
- Planned
Proof-of-concept quality review
- Planned
Pointer arithmetic bounded
- Planned
Policy rule restricted to applicable context
- Planned
Polymorphic-type allowlist
- Planned
Position solvency maintained
- Planned
Prior audit coverage across repositories
- Planned
Priority inversion free
- Planned
Privileged authority scoped by duty
- Planned
Privileged capability not exported
- Planned
Privileged failure observable
- Planned
Production dependency connections
- Planned
Production topology review
- Planned
Protocol abort class matches spec
- Planned
Protocol accounting invariants preserved
- Planned
Protocol interval windows preserved
- Planned
Proxy forwarded host trusted
- Planned
Proxy upgrade authorized
- Planned
Public bundle asset types allowlisted
- Planned
Public domain registration lifecycle reviewed
- Planned
Public namespace claim bound
- Planned
Property tests for pure functions
- Planned
Query timeout bounded
- Planned
Quoted minimum-output enforcement
- Planned
Cryptographically secure random sources
- Planned
Rate limit respected
- Planned
Rate-limit window burst bounded
- Planned
Raw pointer ownership preserved
- Planned
Read isolation: declared level and read-committed minimum
- Planned
Recursion and nesting-depth bounds
- Planned
Redirect policy explicit
- Planned
Regular-expression denial-of-service resistance (ReDoS)
- Planned
Reentrancy protected
- Planned
Reference-cycle handling
- Planned
IPC replay detected
- Planned
HTTP-client request timeout bounded
- Planned
Requested operation fulfillment explicit
- Planned
Required runtime configuration explicit
- Planned
Resource lifetime released
- Planned
HTTP-client retry policy explicit
- Planned
Migration reversal and documented rollback
- Planned
Reward attribution fair
- Planned
Reward schedule liveness reviewed
- Planned
Role transition complete
- Planned
Rounding direction correct
- Planned
Runtime memory regions are disjoint
- Planned
Salt uniqueness
- Planned
Sanctions list coverage complete
- Planned
Secret material not exposed in cleartext
- Planned
Secret zeroization
- Planned
Secrets not logged
- Planned
Security boundary covers derived objects
- Planned
Security decision matches enforcement identity
- Planned
Bounds on semi-trusted values
- Planned
Sensitive response cache control
- Planned
Async-signal-safe signal handling
- Planned
Signature replay and domain separation
- Planned
Signed artifact bound to authenticated intent
- Planned
Signed payload matches user confirmation
- Planned
Signed and unsigned threshold comparisons
- Planned
Claimed protections and actual enforcement
- Planned
Simulation and live-execution differences
- Planned
Slippage covers gross transfer
- Planned
Slippage protection reviewed
- Planned
Snapshot consistency anchor declared
- Planned
Snapshot wire format compatible
- Planned
Solidity compiler version pinned
- Planned
Source fragment validated before composition
- Planned
SQL injection prevention
- Planned
SSRF protection
- Planned
Stale authorization reviewed
- Planned
Starvation bounded
- Planned
State rewrite preserves logical state
- Planned
State transition preconditions reviewed
- Planned
Sticky state cleared on empty transition
- Planned
Storage growth cost charged
- Planned
Storage-narrowing migration and pre-upgrade scans
- Planned
Storage pointer initialized
- Planned
Storage read semantics preserved
- Planned
Stored state type discriminator unique
- Planned
Swap slippage bounds reviewed
- Planned
SwapMath model and live-execution agreement
- Planned
IPC tampering detected
- Planned
Compiler operand bounds
- Planned
Secure temporary-file creation
- Planned
Timelock delay and configured limits
- Planned
TLS required for secrets
- Planned
Totality
- Planned
Transaction isolation level declared
- Planned
Transaction resource estimate matches final payload
- Planned
Transaction work budget bounded
- Planned
Transfer-fee topology reviewed
- Planned
Type and dependency graph cycles
- Planned
Unchecked arithmetic block audited
- Planned
Uninitialized oracle state reviewed
- Planned
Unsafe block documented
- Planned
Unsafe narrow cast reviewed
- Planned
Unsafe trait invariants verified
- Planned
Untrusted-input deserialization bounded
- Planned
Upgrade type invariants preserved
- Planned
Upgrade version state managed
- Planned
Upstream timeout budget coordinated
- Planned
URL query parameters encoded
- Planned
Vault exits: checks-effects-interactions during external divestment
- Planned
View, quote and execution consistency
- Planned
VSS polynomial and threshold binding
- Planned
Wallet backup confirmation required
- Planned
Wallet transaction analysis matches execution
- Planned
WebView executable source trusted
- Planned
Well-known identity metadata edit guarded
- Planned
XSS prevention
- Planned
Zero-address recipient semantics reviewed
- Planned
Zero-amount settlement liveness reviewed
- Planned
Constraints on nondeterministic advice in ZK proofs
Domains
Collections planned around a workload or engineering boundary. Counts refer to obligation topics in this inventory, including those without guides.
- Planned
Audit process
8 obligation topics in this inventory.
- Planned
Compilers & code generation
7 obligation topics in this inventory.
- Planned
Shared-state concurrency
3 obligation topics in this inventory.
- Planned
Cryptographic decryption
3 obligation topics in this inventory.
- Planned
Cryptographic encryption
4 obligation topics in this inventory.
- Planned
Cryptographic hashing
1 obligation topic in this inventory.
- Planned
Key derivation
2 obligation topics in this inventory.
- Planned
Cryptographic signing & protocols
6 obligation topics in this inventory.
- Planned
Cryptographic verification
4 obligation topics in this inventory.
- Planned
Daemons & signal handling
1 obligation topic in this inventory.
- Planned
Data processing
5 obligation topics in this inventory.
- Planned
Database migrations
10 obligation topics in this inventory.
- Planned
Database reads
3 obligation topics in this inventory.
- Planned
Database writes
4 obligation topics in this inventory.
- Planned
Decentralized finance (DeFi)
30 obligation topics in this inventory.
- Planned
Deserialization
4 obligation topics in this inventory.
- Planned
Error handling
5 obligation topics in this inventory.
- Planned
Ethereum & smart-contract safety
68 obligation topics in this inventory.
- Planned
External calls
4 obligation topics in this inventory.
- Planned
Filesystem paths & permissions
4 obligation topics in this inventory.
- Planned
File I/O
4 obligation topics in this inventory.
- Planned
HTTP clients
7 obligation topics in this inventory.
- Planned
HTTP servers
18 obligation topics in this inventory.
- Planned
Input processing
3 obligation topics in this inventory.
- Planned
I/O
1 obligation topic in this inventory.
- Planned
Interprocess communication (IPC)
4 obligation topics in this inventory.
- Planned
Memory safety
5 obligation topics in this inventory.
- Planned
Parsing
7 obligation topics in this inventory.
- Planned
Pure functions
1 obligation topic in this inventory.
- Planned
Scheduling & cancellation
4 obligation topics in this inventory.
- Planned
Security boundaries & policies
68 obligation topics in this inventory.
- Planned
WebSockets
2 obligation topics in this inventory.
Frameworks & contracts
Planned references for standards, control catalogs, weakness taxonomies and interface contracts. Their inclusion does not establish a verified mapping or compliance.
- Planned
OWASP ASVS 4.0.3
- Planned
CWE weakness taxonomy
- Planned
NIST SP 800-53 Rev. 5
- Planned
IEC 62443 · industrial control security
- Planned
IEC 62304 · medical device software
- Planned
RTCA DO-178C · airborne software
- Planned
ISO 26262 · road vehicle functional safety
- Planned
MISRA C:2023
- Planned
AUTOSAR C++14 coding guidelines
- Planned
FIPS 140-3 · cryptographic modules
- Planned
Go standard library interface contracts
Published guides
Worked procedures with inspected evidence, examples and explicit limits.
- Guide available
Software verification plan
Build a plan, challenge its acceptance checks and inspect the evidence that still remains open.
- Guide available
MC/DC coverage
Follow condition-independence pairs, inspectable examples and the limits of structural coverage.
- Guide available
Differential testing
Define an agreement rule, inspect a concealed state change and keep a usable comparison record.
- Guide available
Database/API migration
Define preserved behavior, test consumers across migration phases, inspect a committed-write failure, and plan recovery that preserves post-switch writes.
- Guide available
DO-178C verification
Review one requirement-to-evidence chain: its authority, baseline, failed or missing evidence, reviewer separation, tool reliance and acceptance decision.
- Guide available
IEC 62304 change evidence
Review one software change through its adopted basis, risk-related links, current verification and anomalies. Includes a complete worksheet and recorded correction.
- Guide available
ISO 26262 software evidence
Review one allocated software requirement with a complete worksheet, recorded sequence failures and correction, and explicit timing and safety-decision boundaries.
- Guide available
Property-based testing
Write justified properties for one pure function. Use an inline worksheet and inspect actual generated failures, shrinking, corrected replay and campaign limits.
- Guide available
Negative testing
Check the required rejection and forbidden durable effects. Inspect an executed partial-write failure, rollback correction and reusable rejection record.
- Guide available
Why tests pass while bugs still ship
Find why a green suite can violate an approved rule. Use a free worksheet and a recorded worker-count setting example to assess inputs, assertions and repair limits.
- Guide available
Equivalence partitioning
Define valid and invalid classes, choose representatives and expose an endpoint failure with executed checks. Preserve the exact response contract and limits of sampled evidence.
- Guide available
A crash the suite missed
Preserve a reproducible failure, settle the intended behavior, inspect an implemented correction and record what the regression evidence leaves open.
- Guide available
Requirements-based testing
Turn a written rule into an independent expected response and stored effects, verify that the real operation ran, and interpret the observed result.
- Guide available
GDPR requirements to tests
Translate a resolved privacy decision into named live-store criteria, detect false deletion completion, and retain independent evidence for retries and controlled restores.
- Guide available
Software correctness audit
Agree a bounded correctness audit, retain six inspectable records, and reproduce a teaching failure and correction with complete free worksheets.
- Guide available
Loop invariants
Build a loop invariant from entry through preservation to exit. Copy a complete worksheet and inspect a Go defect, its correction, finite replay and unresolved strong solver claims.
- Guide available
Hazard analysis to code
Carry one hazard from applicability and mitigation policy through implementation evidence, remaining risk and an authorized decision, with a free complete worksheet.
- Guide available
Requirements completeness
Review requirements-set completeness with explicit inventories, denominators and authority, a free worksheet, and a bounded importer failure and correction.
- Guide available
AI4SDLC change record
Apply AI4SDLC guidance to one change with a free assurance worksheet, an observed retry failure and correction, and separate validation and acceptance decisions.
- Guide available
Preserve the older promise
Preserve an older requirement through an agent change: inspect changed acceptance criteria, independent effects and evidence tied to the exact candidate.
- Guide available
SOC 2, pentests and business logic
Decide what existing SOC 2, pentest and engineering evidence says about one business rule. A local booking retry shows why a recorded failure can be useful evidence. Includes complete free scope records.
- Guide available
PoC review checklist
Review what a software proof of concept actually demonstrates. Use the free human checklist, a separate copyable AI prompt and a worked example to choose the next check.
- Guide available
DoWI 8430.01 evidence inspection
Inspect one AI-assisted change or release: confirm its governing basis and identity, bound the supplied results, assign evidence gaps and identify the deciding authority.
- Guide available
MIL-STD-882E: a first review of software safety evidence
Understand MIL-STD-882E and review one hazard, software control and evidence gap with a free worksheet and an illustrative plan that has not been executed.
- Guide available
Preliminary design review (PDR): purpose, checklist and decision record
Review one architecture claim before detailed design: connect requirements, assumptions and evidence, plan the missing check, and distinguish a recommendation from authorized permission to proceed.
- Guide available
Critical design review (CDR): checklist and exit criteria
Review one detailed-design claim against its requirement, failure path and available evidence, with a free CDR worksheet and a filled illustrative record.
- Guide available
Test readiness review (TRR): checklist and exit criteria
Review whether a planned software test can deliver its required condition and record an interpretable response. Includes a free worksheet and filled example.
- Guide available
System requirements review: decide whether the requirements are ready
Review a requirement-set revision, expose unsupported assumptions, and record the next authorized decision with a free worksheet and illustrative example.
- Guide available
NPR 7150.2D: review changed requirements against verification
Review one changed software requirement under an adopted NASA basis. Compare current verification content, available evidence and authority with a free worksheet.
- Guide available
NASA-STD-8739.8B: review a conclusion after a configuration change
Review one prior conclusion against a changed configuration, record justified reuse or missing work, and separate the recommendation from actual disposition.
- Guide available
DO-333: review what a formal result actually supports
Review one formal result through its property, assumptions and implementation relationship. Use a free human record and inspect recorded timestamp-model evidence.
Published check references
Checker contracts, eligibility, result meanings and remediation. A linked reference does not establish that a catalog obligation has been verified.
- Reference available
Documented claim check
Declare documented_behaviors cells, interpret documented_claim_verified results and inspect a separate cancellation witness with complete free evidence records.
This is a publishing inventory. A planned topic does not claim completed guidance, an executed check or compliance with a framework. The published guides retain their own scope, evidence and limitations.
Bring the context
Working through a real change?
Start with the behavior that must hold and the evidence you need to inspect.