Developer preview. Pre-admission. Not for sensitive, proprietary, regulated, or production code. Expect breaking changes and data loss. Read the limits.

Exfiltration control starts with per-use approval

Phase 1 asks the user to approve each use of a credential, configurable through the shared scopes (per use, per run, per conversation, remembered per host and use). Egress hardening (an egress lock or proxy) is deferred to a later phase; the design keeps a clean extension path for it. The approval is the generic approval primitive of UR-04.

The logbook index

Search the record

Type to search the curated record.

↑↓ move Enter open Esc close