TheoryTHY-2026-0201v0.1
Publication-boundary closure — the integrated framework
Generating, testing, scanning, reviewing and pushing are five propositions, none of which is that the delivered result respects its boundary. Information passes observed → authorized → persisted → published → externally obtainable, and each arrow is its own permission. Closure is evidence that covers the intended postcondition, not more checks.
Definitions
definitions- AI may observe ≠ AI may persist ≠ AI may publish.
- Knowledge states: O observed, H hypothesis, E established, NM not measured.
Claims
claims- A hash proves the bytes are the bytes that were hashed; it says nothing about what they reveal.
- A private repository is not a vault; a clean current tree does not clean history.
Recorded fields
tags- paper 00
Relations
| Source | Relation | Target | Status | ID |
|---|---|---|---|---|
THY-2026-0201 Publication-boundary closure — the integrated framework | contains | CLM-2026-0201 H1 — AI-assisted repositories disclose more than matched non-AI repositories | ACTIVE | REL-2026-0512 |
RES-2026-0201 Why passing checks does not close the publication boundary | develops | THY-2026-0201 Publication-boundary closure — the integrated framework | ACTIVE | REL-2026-0504 |
PAP-2026-0201 Paper 00 — Agentic publication boundary and security closure: the integrated framework | formalizes | THY-2026-0201 Publication-boundary closure — the integrated framework | ACTIVE | REL-2026-0527 |
History and provenance
- Canonical URL
- https://evemisslab.com/ai/theory/THY-2026-0201/
- Machine-readable
/ai/theory/THY-2026-0201/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