Deadbolt is a research prototype. It is not a production security boundary, a sandboxing replacement, a compliance system, a certification system, or a production trust system. Do not rely on it to protect real systems.

The current repository is reviewed as a local deterministic governed execution harness. The current real mutation routes are the two narrow Hyprland primitives documented in the authority boundary: Phase 29F decoration:rounding -> 0 and Phase 31J general:border_size -> 3. MCP is status/review-only.

Please report security-sensitive issues privately if possible. Use GitHub private vulnerability reporting if it is enabled for the repository. If no private channel is available, contact the maintainer privately before sharing sensitive details in public.

No response SLA, coordinated disclosure timeline, production support, or bug bounty is promised unless explicitly stated.

Good reports are concise and sanitized. Please include:

• affected command, document, route, or boundary;
• reproduction steps using synthetic or minimized examples;
• expected behavior and actual behavior;
• why the issue may affect Deadbolt's reviewed authority boundary;
• short excerpts only when needed, with sensitive material removed.

Do not include secrets, raw logs, raw host context, screenshots, environment variables, .env files, private keys, signing keys, local paths, usernames, hostnames, customer or user data, clipboard/browser/window/process state, raw Home Manager or Nix output, raw MCP output, terminal transcripts, or private run artifacts in reports.

The following are usually out of scope for this policy:

• dependency vulnerabilities that should be reported upstream;
• social engineering, spam, or denial-of-service against public services;
• claims that require broad host compromise outside Deadbolt's reviewed boundary;
• findings based only on missing production hardening, since this repository does not claim production security;
• reports that require collecting or sharing raw private host material.

The model may suggest. The harness compiles. The kernel decides. The witness trace proves.

In this project, "decides" currently means: on the real mutation routes, the accept/refuse decision is made by cog-leases lease verification plus typed route handlers inside the CLI process; cog-kernel evaluates synthetic noop/replay decision bundles only and is not on the live mutation path. See docs/audits/mythos-hostile-architecture-audit.md.

In this project, "proves" means local deterministic inclusion, recomputation under named local profiles, and internal artifact consistency. It does not mean real-world occurrence, independent host behavior, authorization, production trust, compliance, conformance, certification, attestation, or permission to disclose sensitive material.

Cloud, provider, Hermes, or MCP output is untrusted planner/status material only. It does not authorize execution, disclosure, adapter routing, mutation, or trust in reported host state.

CI success, build success, test success, preflight success, workflow success, verifier output, witness output, DSSE output, reports, receipts, leases, governance files, SECURITY.md text, CONTRIBUTING.md text, pull request templates, docs, and release-readiness checklists authorize nothing by existence.