PaperPAP-2026-0206v0.1

Paper 05 — AI build–attack asymmetry

Phase I paper 05, v0.1, 2026-09-21. An internal research draft; its public replacement is the integrated edition (PAP-2026-0211). A checked summary is on the program site.

Research status: SUPERSEDED replaced by a newer version or theory
Evidence level: E0 Concept only
Data basis: THEORY Theoretical reasoning only; no measurement.
Version: 0.1
Updated: 2026-10-13
Created: 2026-09-21
Domain: Privacy
Program: PRG-2026-0201 AI Agent Publication Boundary and Security Closure (APBSC)
Authors: Neo.K (EveMissLab)
AI collaborators: AI collaboration recorded for the series; the collaborator is not named in the drafts

Record

publication_type: internal research draft (APBSC Phase I, 10 papers); superseded publicly by the integrated edition
authors: Neo.K (EveMissLab)
date: 2026-09-21
doi_or_external_id: APBSC-05

Recorded fields

checksums

draft .md sha256: aa810c9cf1a7f4404987f7fbcebec84c65f09c4d1a144ea26a3ce250036df299

external_sites

https://privacy.evemisslab.com/papers/05/

tags

zh-TW / en titles
paper 05/10
full text internal

Relations

Source	Relation	Target	Status	ID
`PAP-2026-0206` Paper 05 — AI build–attack asymmetry	`reports`	`RES-2026-0201` Why passing checks does not close the publication boundary	`ACTIVE`	`REL-2026-0536`
`PAP-2026-0206` Paper 05 — AI build–attack asymmetry	`formalizes`	`THY-2026-0206` AI build–attack asymmetry (hypothesis)	`ACTIVE`	`REL-2026-0537`
`PAP-2026-0211` AI Agents and the Public Boundary — the APBSC integrated public edition v1.0	`extends`	`PAP-2026-0206` Paper 05 — AI build–attack asymmetry	`ACTIVE`	`REL-2026-0552`

History and provenance

Canonical URL

https://evemisslab.com/ai/papers/PAP-2026-0206/

Machine-readable

/ai/papers/PAP-2026-0206/index.json

Snapshot

AI-SNAPSHOT-v0.1-58e716495670

Provenance

source: EveMissLab research collection: AI Agent Publication Boundary and Security Closure (真本體論14)
extracted_by: Splice (Claude Code), reading the open-source release's own manifests, locks and pooled outputs, and the hashes of the internal drafts
extracted_at: 2026-10-13
generator: tools/extract_all.py
claim_boundary: status, evidence level and result type follow the source artifact's own stated claim boundary; nothing is upgraded beyond what the report supports