Production pilot · authorized data only

Personal Exposure Defense

Discover exposure. Verify evidence. Score risk. Create and track remediation work. Get human approval before external action. Prove progress.

Operating system

One case loop, visible proof, guarded action

Cloak Harbor turns authorized identifiers into evidence, risk, work, approvals, reports, and recurring review. No external action is taken unless a protected server route and a human approval allow it.

Capabilities

32

Human gates

18

External action

false

Capability loop

Catalog coverage by operating stage.

No external action

Intake

4

Confirm who is protected, what is in scope, and what the system is allowed to touch.

Discover

2

Plan bounded exposure discovery against authorized identifiers.

Verify

2

Review evidence before anything becomes a risk or action item.

Score

1

Translate exposure into a clear StealthScore and explain what would improve it.

Queue

1

Turn validated findings into accountable work with owners and due dates.

Operate

10

Run the work through Kanban, service setup, partner handoffs, and communications drafts.

Cadence

1

Keep the 30-day remediation rhythm visible for clients and operators.

Draft

1

Draft opt-out, correction, partner, and client packets without sending them.

Approve

4

Require a person to approve sensitive work before any outside-world touch.

Prove

6

Package the before/after story into reports, screenshots, and audit evidence.

Monitor

0

Watch for re-exposure after cleanup without pretending live monitoring is active.

Support modes

Postgres and Vercel support are explicit. Missing infrastructure degrades honestly.

Postgres

8

Vercel

8

Redacted public baseline

Connected

Public-safe baseline only; saved client records replace it as soon as a real authorized case is selected.

PED OS capability catalog

Connected

Catalog remains readable even when persistence is unavailable.

Postgres capability support flags

Configured

Vercel reports redacted/degraded mode only until DATABASE_URL is configured.

Local audit event persistence

Configured

Deployments without DATABASE_URL show public-safe trace summaries and do not claim durable audit persistence.

Protected capability bootstrap API

Server-authorized

Without Postgres, the route returns postgres_not_configured instead of fake success.

MCP capability introspection

Connected

MCP reports public-safe degraded runtime when Postgres is absent.

Sensitive action matrix

Actions stay explainable, gated, and auditable.

Client onboarding

Human review

Authorized or redacted data only

externalActionTaken:false

Customer onboarding

Waiting client

No document upload success is claimed

externalActionTaken:false

Management onboarding

Planned

No team changes are saved

externalActionTaken:false

Discovery planning

Planned

No live scan has been performed

externalActionTaken:false

Calendar cadence

Server-authorized

No real calendar event is created

externalActionTaken:false

Human review center

Human review

No auto-submit

externalActionTaken:false

Action packet studio

Dry-run

AI drafted, human approval required

externalActionTaken:false

Communications hub

Planned

No sending without protected server action

externalActionTaken:false

Defense loop ledger

Evidence-to-action proof chain

Every stage declares what is real, what is gated, and whether anything touched the outside world. Checkpoint persistence can be recorded through POST /api/v1/loop when Postgres and server authorization are configured on Vercel or local Docker.

Stages

10

Findings

12

Actions

0

Evidence Risk Approval ReportexternalActionTaken:falseCheckpoint persistence: PostgresVercel-ready protected routePOST /api/v1/loop