Security boundary

A deliberately small authority surface.

The local product constrains what can be inspected, executed, persisted, and applied. AI output does not gain direct shell, patch, answer, or repository authority, and every unsupported condition fails closed.

Local by default

Runrail Desktop binds only to 127.0.0.1. Repository content and generated review artifacts stay on the operator's machine.

Base-owned rules

An optional .runrail/review-contract.json is read from the selected base commit. Candidate changes cannot weaken its budgets or required evidence.

Non-executing checks

Runrail uses fixed Python, JavaScript, JSON, TypeScript, TSX, and JSX syntax or parse checks. Unsupported changed source types block the preflight; package scripts, project code, and arbitrary shell instructions are never run.

Human-controlled apply

The product exports a patch for review and does not apply it automatically.

Portable evidence

The path-free passport binds checks, contract fingerprint, relation, and review outcome to the audit checksum. It does not authenticate who created the evidence.

Conservative hunk continuity

Review Coverage carries attention only for an exact unique hunk in a related revision. Changed, shifted, split, duplicated, ambiguous, and new hunks reset to unreviewed; attention never becomes approval.

Local revision evidence

The free browser workspace compares related audit files without opening either repository or sending files to Veyact. Licensed CLI comparison is available in Pro.

Model-independent core

Offline deterministic recommendations require no model. Optional DeepSeek advice receives no source or diff and may return only fixed candidate IDs or ABSTAIN, with authority none.

Disclosure and support

Security reports are accepted at the published support address. The current Runrail 2.x security-support period runs through 28 July 2031, with fixes delivered through the current supported release channel.

Path traversalRejected
Arbitrary shellRejected
Automatic source mutationDisabled
External model providerNot required; separate BYOK metadata-only advisory is opt-in
Operating-system sandboxNot provided; trusted local operator machine required
Artifact originChecksummed, not identity-authenticated

Security detail

Review the full boundary and current limitations.