Map before review
Run review-map on the repository to make the value paths, assumptions, and test gaps explicit before a reviewer arrives.
Pre-audit
Prepare a clearer surface before review.
For protocol engineers getting ready for an audit, and reviewers onboarding to an unfamiliar codebase. ArkheionX makes the review surface explicit so the audit time is spent where value moves. It does not replace the audit or prove the protocol is safe.
Builder flow
One workflow, run locally.
arkheionx review-map .
arkheionx value-paths .
arkheionx assumptions .
arkheionx test-gap-map .
arkheionx proof-plan .Inspect money-moving paths
Start with the ranked high-priority value exits and privileged setters. Confirm each path's assumptions are enforced in code.
Close the test gaps
For each gap, open its Source: file:line and write a targeted Foundry test that exercises the path under adversarial inputs.
Document assumptions
Capture the trust conditions as explicit notes: oracle freshness, access control, accounting invariants.
Prepare the handoff
Share the review map, the new tests, and your notes so the reviewer starts from context instead of rebuilding it.
What the reviewer gets
A consistent map of contracts, roles, value paths, and assumptions, plus previously untested value-sensitive functions now covered by tests.
What it does not give
A clean review map does not mean the protocol is safe, and passing the tests you added does not prove the absence of bugs.
Still required
A formal audit and human review. ArkheionX assigns no severity and confirms no vulnerability.
Boundary
Preparation, not a verdict.
ArkheionX does not confirm vulnerabilities, assign final severity, prove safety, or stand
in for a human auditor. Read the full guide in the repository's
docs/PRE_AUDIT_WORKFLOW.md.