Overview
A versioned, evidence-gated personal security boundary and explicit No document for dual-use development work. It requires a complete, reviewable action intake before returning compliance, distinguishes outside-scope work from compliance, and records uncertainty as a blocking result rather than a permission. It is a personal auditability aid, not enforcement, legal compliance, semantic safety classification, or external certification. Subtitle: An Evidence-Gated Personal Security Boundary and Explicit No Document for Dual-Use Development Code is MIT licensed; prose and figures are CC BY 4.0. See LICENSE in the repository.
Overview source: Curated paper metadata.
Methods and contributions
Read the source for the full argument, qualifications, and evidence.
Findings and contributions
- Every intake is classified into one of five categories; missing, self-asserted, unverified, stale or contradicted context cannot produce COMPLIANT.
- Degrading any one of the nine intake dimensions withdrew a compliant result in all 45 executed evaluations; an ALL-mode exemption stayed unreachable by a single token across 58 more.
- All five classifications were reached by the fixture battery, but the fixtures are not evidence that any real engagement was reviewed, safe or lawful.
- The author states decisive limitations: local evidence is not independent truth verification, lexical matching is not semantic understanding, and code is not enforcement.
- The evaluator's visible boundary is a 34-word scope vocabulary, so OUTSIDE_SCOPE is a bounded registry statement rather than a safety claim.
Methods
- Versioned machine-readable registry of seven first-person refusals — The author's seven red lines are recorded as a versioned registry that a proposed engagement is checked against via a strict intake gate.
- Nine-dimension evidence-gated ActionContext intake — Each intake must carry a VERIFIED evidence record for nine dimensions (purpose, end use, affected parties, provenance, legal basis, etc.) before policy matching.
- Adaptation of Turner's government AI red-line framework — Turner's organization-to-government red line and oversight framework serves as mechanism source, adapted to one practitioner without importing its authority.
- Deterministic registry hashing and canary attestation — Durability is implemented as hashing of canonical registry content and a canary that detects drift only against a prior copy held outside the writer's control.
- Five-fixture outcome-coverage battery through the real evaluator — A harness runs five ProposedAction fixtures, one per classification, through evaluate_action against the live registry at a fixed review date.
Summary sources: Paper metadata and evidence · Extracted source text.
Document downloads
PDFs are hosted here; supporting sources may use pinned archives.
- red_line_combined.pdf PDF · 5.92 MiB · extracted-text source
Citation
Citation metadata follows the unified bibliography.
Catalog details and resources
Related works
Ranked by recorded methods, topics, contributors and associated software, with contributor roles and domain-only matches labelled. Metadata overlap is not a citation or a scientific equivalence.