Protocol surface
The reviewable shape of a protocol: contracts, actors, permissions, dependencies, value movement, assumptions, and evidence.
Concepts
The vocabulary behind a review map.
ArkheionX is built around a simple idea: security review needs reproducible context before it needs conclusions. These concepts define the context the tool is meant to preserve.
Input Local repository
Mapping layer Protocol surface
Artifacts Roles · paths · assumptions · gaps · evidence
Reviewer Human judgment
Role
An actor or authority that can affect protocol behavior, such as owner, admin, keeper, user, oracle, governance, or emergency role.
Value path
A route where assets, shares, rewards, collateral, or accounting value can move through the system.
Assumption
A condition the protocol appears to rely on, such as oracle freshness, access control correctness, accounting invariants, or timing behavior.
Test gap
A review-relevant behavior that appears important but is not clearly covered by tests or deterministic fixture checks.
Evidence link
A reference that connects review context back to source files, fixtures, snapshots, or generated artifacts.
Review package
A structured set of artifacts that helps humans inspect what was reviewed, what changed, and what still needs judgment.
Snapshot drift
A change between expected deterministic output and newly generated output.
Source fingerprint
A deterministic identifier that helps track the source inputs used to generate artifacts.
Important
Concepts are not verdicts.
A role, assumption, value path, or test gap is review context. It is not automatically a vulnerability. Human validation is required before any security conclusion.
Read safety model