Skip to content
Preflight Audit

Methodology

Precision at every stage

A rigorous process combining automated analysis, AI assessment, and senior auditor expertise.

1

Upload

Submit contracts, documentation, whitepapers, and repository access.

2

Analysis

Automated static analysis and architecture mapping across all domains.

3

AI Review

Preflight AI performs initial readiness assessment and risk classification.

4

Human Expert Review

Senior auditors validate findings and apply domain expertise.

5

Risk Scoring

Findings classified as Clear, Hold, or Blocked with severity ratings.

6

Remediation

Actionable recommendations with prioritized fix guidance.

7

Certification

Preflight Certified badge issued upon successful remediation.

8

Launch Ready

Final sign-off with continuous monitoring options available.

Launch Readiness Classification

Every finding receives a launch readiness label — separate from technical severity — indicating whether you can proceed.

ClearNo action required before launch

Pattern reviewed and acceptable for launch context. Monitor during operations but no remediation needed pre-launch.

Action: Document and proceed

HoldReview recommended before launch

Non-blocking concern that should be reviewed by the team. May become blocked under regulatory or integration pressure.

Action: Review within 5 business days

BlockedMust fix before launch

Material launch risk — regulatory exposure, architectural flaw, or disclosure gap that must be resolved before going live.

Action: Remediate before launch sign-off

Severity Classification (5-Tier)

Technical findings are scored 0.1–10.0 and classified into five severity levels with defined response times.

Critical9.0–10.0Direct fund loss, permanent lock, or irreversible launch failure possible.Immediate halt — fix before any public launch activity
High7.0–8.9Serious security or compliance gap with high exploit or regulatory likelihood.Fix within 72 hours or downgrade launch scope
Medium4.0–6.9Meaningful weakness that increases risk under adversarial or scaling conditions.Fix before mainnet or document accepted risk with mitigation
Low1.0–3.9Minor issue, best-practice gap, or informational observation.Address in next sprint or document as accepted
Informational0.1–0.9Suggestion for improvement with no direct security impact.Optional — include in backlog

Readiness Score Matrix

Overall project readiness score (0–100) maps to public status in the audit library.

Launch Ready

85–100

No blocked findings. High/medium items resolved or accepted with documentation.

Assessed

70–84

Assessment complete. Open high-severity items require remediation plan.

In Progress

Assessment ongoing. Score published upon completion.