● ADR-0003 · HUMAN SIGN-OFF ENFORCED

Does this build still match what you shipped and what you promised?

Extension bundles drift. Preflight gates every build before it reaches the Chrome Web Store: deterministic evidence, versioned policy packs, and a human decision when it matters.

● Harbor Node · isolated per tenant SOC2 · no JS execution

VERDICTS3 types

AGENTS5 deterministic

RUNTIME0 JS exec

preflight · harbor-node@1.4.2zsh

$ preflight review ./build.zip --claims ./claims.json

AGENT 01 artifact.rs — sha256:9f3c…a1d2 · 127 files, manifest v3

AGENT 02 extract.rs — manifest v3 ok, permissions parsed [storage, tabs, *://*.analytics.io/*]

AGENT 03 diff.rs — new host detected vs baseline: *.analytics.io (not in v1.4.1)

AGENT 04 rules.rs — host not in claims.json → BLOCK · CWS-07 / PRIV-01

AGENT 05 review.rs — verdict: BLOCK · needs human sign-off · 2 evidence chains

● key provenancepf_live_••••••••

PIPELINE

Five deterministic agents

Out-of-process Rust binary · Zero runtime execution

Artifact Hasher

artifact.rs

Evidence Extractor

extract.rs

Baseline Diff

diff.rs

Policy Auditor

rules.rs

Arbiter

review.rs

✓ Explainable chains — every verdict cites rule + diff▣ Baseline-locked — compares to last shipped + claims.json▣ Human sign-off required for BLOCK & NEEDS_HUMAN

Policy packs versioned like dependencies

Pin to cws-2026.1. Extend with your own claims.json. Rules are pure Rust, auditable, and deterministic.

audit --pack cws-2026.1 · deterministic

cws-2026.1CHROME WEB STORE

CWS-01 MV3 required BLOCKER

CWS-03 No broad host patterns HIGH

CWS-05 No eval / WASM without… BLOCKER

CWS-07 Declared hosts must match… BLOCKER

node-client-2026.1CUSTOM CLAIMS

PRIV-01 Host list pinned per tenant BLOCKER

PRIV-02 Permissions require justification HIGH

NODE-03 No websocket to non-allowlisted host BLOCKER

CLAIM-01 claims.json version and shape BLOCKER

Isolation model

TeamsIndie

WORKSPACE ISOLATION

harbor-prod
key: pf_live_••••harbor-staging
key: pf_live_••••relay-dev
key: pf_live_••••

admin
can create keys, projectsreviewer
can sign-off BLOCKci
can push, cannot sign

AUDIT TRAIL

09:42:11 review created — drifted-host.zip → BLOCK
09:43:05 requested changes — justify host or remove
09:47:22 new build — clean-relay.zip → SHIP WITH CONDITIONS
09:47:40 signed-off — SHIP

One key, everywhere

pf_live scoped to project, not user

LOCAL REVIEW

$ preflight review ./build.zip \
  --claims ./claims.json \
  --pack cws-2026.1 \
  --key $PREFLIGHT_KEY

  ✓ artifact sha256:9f3c…
  ✓ 5 agents ok
  → verdict: BLOCK (CWS-07)

PUSH TO CONTROL PLANE

$ preflight push ./build.zip \
  --project harbor-node \
  --key $PREFLIGHT_KEY

  → review: r/9f3c…
  → https://preflight.aetherhost.com.ng
  → awaiting sign-off

POST /v1/signupPOST /v1/sandbox/evaluateGET /v1/mePOST /v1/projects/:id/reviewsPOST /v1/reviews/:id/sign-off

Try without signup

Deterministic evaluation in the browser view · no workspace required● SANDBOX LIVE — no data leaves this tab

claims.json · editable ADR-0003

{
  "version": "1.4.2",
  "hosts": ["api.harbor.run", "cdn.harbor.run"],
  "permissions": ["storage", "activeTab"],
  "privacy": "strict",
  "justifications": {
    "storage": "session state for isolated tenant"
  }
}

CONSOLE

› loading drifted-host.zip …
› parsing manifest.json — ok
› checking claims.json — hosts match

evidence:

host: *.analytics.io (new)
permission: storage
manifest: v3

VERDICT — BLOCKpack: cws-2026.1

New host *.analytics.io not in claims.json · CWS-07

HUMAN SIGN-OFF — THE LAST GATE

Ship only what you meant to ship.

Preflight runs in CI, blocks drift, and forces a reviewer when policy fails. Rust, deterministic. No JS execution. Same binary locally and in your pipeline.

Free for personal · team plans available

Preflight Documentation & Reference

OpenAPI / Swagger UI (/docs) →

How to use Preflight across the Web Console, the Rust CLI in your terminal, and CI/CD pipelines.

1. Using Your API Key with the Rust CLI in Terminal

Every Organization member and Individual user gets a pf_live_<prefix>_<secret> key. You can use that exact same key in the browser console OR in your terminal:

Local static scan with key provenance or push directly to your web project:

# 1. Run deterministic local scan with your API key:
cargo run -- review fixtures/harbor-node/clean-relay \
  --claims fixtures/harbor-node/claims.json \
  --key pf_live_yourprefix_yoursecret \
  --out reviews/clean

# 2. Push local build + claims from terminal straight to your Web Console project:
cargo run -- push fixtures/harbor-node/clean-relay.zip \
  --project <YOUR_PROJECT_ID> \
  --claims fixtures/harbor-node/claims.json \
  --key pf_live_yourprefix_yoursecret \
  --api http://localhost:3080

2. Structured Scanner Agents & Policy Packs (cws-2026.1 & node-client-2026.1)

The scanner evaluates two built-in rule packs against your extension artifact and claims.json:

Control	Pack	Severity	What It Verifies
CWS-01	cws-2026.1	blocker	`manifest_version` must be `3`.
CWS-02	cws-2026.1	high	Every file referenced in `manifest.json` exists in the archive.
CWS-03 / CWS-07	cws-2026.1	high	Blocks broad host patterns (`:///*`, `<all_urls>`) and cleartext `http://` or `ws://` endpoints.
CWS-05 / CWS-06	cws-2026.1	high	Requires an `https://` privacy URL and a declared purpose for every manifest permission.
CWS-08	cws-2026.1	blocker	Blocks `eval()`, `new Function()`, remote script imports, and `unsafe-eval` CSP.
NODE-01 / NODE-02	node-client-2026.1	blocker	Every manifest host permission and JS network destination must match `claims.allowed_hosts`.
NODE-03 / NODE-04	node-client-2026.1	blocker/high	Networked extensions must enforce an explicit consent check and a runtime kill switch.
NODE-06 / NODE-07	node-client-2026.1	high	Blocks private/loopback network targets (`127.0.0.1`, `192.168.x.x`) and third-party `update_url` hosts.

3. Account Types (Organization vs. Individual) & RBAC Roles

Preflight isolates every workspace at the database, API key, and filesystem levels:

Organizations (accountType: "organization"): Designed for teams. Admins create a one-time, seven-day invitation link at POST /v1/members/invite. A member accepts it with the invited WorkOS email; CI always receives a separately minted restricted key.
Individuals (accountType: "individual"): Designed for solo developers. Creates a personal workspace with zero team-management overhead while still supporting additional personal CLI/CI keys.
Separation of Duties (ADR-0003): Keys with the ci role can upload builds and poll verdicts, but are cryptographically blocked from signing off human release decisions.

4. HTTP REST API Endpoints

Method	Endpoint	Auth	Description
POST	`/v1/signup`	Public	Create an `organization` or `individual` workspace and mint initial admin key.
POST	`/v1/sandbox/evaluate`	Public	Run ephemeral sandbox scan on Harbor Node fixtures with live agent console logs.
GET	`/v1/me`	Bearer `pf_live_…`	Retrieve active workspace, account type, current key role, and projects.
POST	`/v1/members/invite`	Admin Key	Create a seven-day, one-time WorkOS invitation link for an `admin` or `reviewer`.
POST	`/v1/projects/:id/reviews`	Any Key	Upload `artifact` (.zip/.crx) and optional `claims` JSON for review.
POST	`/v1/reviews/:id/sign-off`	Admin / Reviewer	Record mandatory human release decision (`ship`, `hold`, `reject`).

ORG key: —

Latest Project Verdict

—

Gate: auto_ship = false

Isolated Projects

Active: —

Project Reviews

0 cleared · 0 blocked

Scanner Engine & Packs

5 Agents

cws-2026.1 · node-client-2026.1

Release Build Submission

POST /v1/projects/:id/reviews

Simulate Harbor Node Drops in Active Project

Scanner Agent Console Logs & CLI Bridge

no review selected

Upload an extension build or trigger a simulation to stream the 5 structured scanner agent logs.

Use Your API Key in Terminal (Rust CLI)

cargo run -- push ./build.zip --project <project-id> --claims ./claims.json --key <pf_live_key>

Review Verdict, Findings & Mandatory Human Sign-Off

ADR-0003: Human Sign-Off Required

Select or run a review to inspect findings and sign off.

Project Review History

scoped to active project

No reviews for this project yet.

Team Members & API Keys

RBAC + Zero-Downtime Rotation

Invite a Browser Member (One-Time WorkOS Link)

Preflight creates a seven-day invitation link. Copy it to the intended email address; no API key is sent or displayed.

Member Name

Member Email

Member Role

reviewer — can submit builds, edit claims & sign off releases admin — full organization, project & member management