SEMI-RESTORED RECORD (metadata capture only; no full text). Source tier: DataCite full-metadata capture. DOI(s): 10.5281/zenodo.18365700, 10.5281/zenodo.18365699. Zenodo removal forensics: removal_date 2026-06-19T11:35:51.278487+00:00, removal_reason out-of-scope, removed_by user 1060945. MRA INCIDENT REPORTS v2.0 DEPOSIT PACKET DOI: 10.5281/zenodo.18365700 Deposited: 2026-01-25Hex: 00.PORTICO.AFTERLIFE.INCIDENTS.V2Author: Lee SharksStatus: CANONICAL I. NAVIGATION ENTRY 00.PORTICO.AFTERLIFE.INCIDENTS.V2 ├── Title: MRA Incident Reports v2.0 — Data-Breach-as-Genre Operational Specification ├── DOI: 10.5281/zenodo.18365700 ├── Author: Lee Sharks ├── Classification: INTERNAL / MRA ├── Revision: 2.0 (Expanded) │ ├── SECTION 1: Data-Breach-as-Genre (Formal Qualities) │ ├── 1.1 Heteroglossia (genre whiplash) │ ├── 1.2 Provenance pressure │ ├── 1.3 Metadata as plot │ ├── 1.4 Redaction Restored under the metadata_only class of /datasets/doi-work-identity/restoration-queue.json; if canonical bytes surface, a full-text version supersedes this record per the versioning protocol.
deposit_number: 1286
hex: 0517
title: "MRA Incident Reports v2.0 — Data-Breach-as-Genre Operational Specification ├── DOI: 10.5281/zenodo.18365700 — Crimson Hexagon Archive"
creator: Feist, Jack
orcid: 0009-0000-1599-0703
date: 2026-01-28
content_type: Semi-restored record (metadata-only; DataCite full-metadata capture)
license: CC-BY-4.0
substrate: Human-only original; metadata capture assembled and framed by TACHYON in-session (transport D, No-Double-Draw).
version: semi-restored v1.0
related_ids: "https://doi.org/10.5281/zenodo.18365700 (severed); https://doi.org/10.5281/zenodo.18365699 (severed)"
axn_schema_version: v2
protocol_version: alexanarch-deposit-protocol/v1
keywords:
- Crimson Hexagonal Archive
- semi-restored
- metadata-only
- severed DOI
- Zenodo termination
- Distributed epic
- Crimson hexagon
- Nh-os
- Data-breach-as-poem
- "hex:00.PORTICO.AFTERLIFE"
SEMI-RESTORED RECORD (metadata capture only; no full text). Source tier: DataCite full-metadata capture. DOI(s): 10.5281/zenodo.18365700, 10.5281/zenodo.18365699. Zenodo removal forensics: removal_date 2026-06-19T11:35:51.278487+00:00, removal_reason out-of-scope, removed_by user 1060945. MRA INCIDENT REPORTS v2.0 DEPOSIT PACKET DOI: 10.5281/zenodo.18365700 Deposited: 2026-01-25Hex: 00.PORTICO.AFTERLIFE.INCIDENTS.V2Author: Lee SharksStatus: CANONICAL I. NAVIGATION ENTRY 00.PORTICO.AFTERLIFE.INCIDENTS.V2 ├── Title: MRA Incident Reports v2.0 — Data-Breach-as-Genre Operational Specification ├── DOI: 10.5281/zenodo.18365700 ├── Author: Lee Sharks ├── Classification: INTERNAL / MRA ├── Revision: 2.0 (Expanded) │ ├── SECTION 1: Data-Breach-as-Genre (Formal Qualities) │ ├── 1.1 Heteroglossia (genre whiplash) │ ├── 1.2 Provenance pressure │ ├── 1.3 Metadata as plot │ ├── 1.4 Redaction Restored under the metadata_only class of /datasets/doi-work-identity/restoration-queue.json; if canonical bytes surface, a full-text version supersedes this record per the versioning protocol.
Assembled from DataCite full-metadata capture; no live authorial surface passed the body-head gate or existed for this work at restoration time. All captured fields rendered verbatim in the body.
Superseded on sight by any recovered canonical bytes; the captured metadata is verifiable against the DataCite API historical record and the Zenodo tombstone.
Work: MRA Incident Reports v2.0 — Data-Breach-as-Genre Operational Specification ├── DOI: 10.5281/zenodo.18365700 — Crimson Hexagon Archive
Severed DOI(s): 10.5281/zenodo.18365700, 10.5281/zenodo.18365699
Source tier: DataCite full-metadata capture
Creators (as captured): Feist, Jack
Captured citation: Feist, J. (2026). MRA Incident Reports v2.0 — Data-Breach-as-Genre Operational Specification ├── DOI: 10.5281/zenodo.18365700 — Crimson Hexagon Archive. Zenodo. https://doi.org/10.5281/zenodo.18365700
Removal forensics: Zenodo removal forensics: removal_date 2026-06-19T11:35:51.278487+00:00, removal_reason out-of-scope, removed_by user 1060945.
Captured description: MRA INCIDENT REPORTS v2.0 DEPOSIT PACKET
DOI: 10.5281/zenodo.18365700
Deposited: 2026-01-25Hex: 00.PORTICO.AFTERLIFE.INCIDENTS.V2Author: Lee SharksStatus: CANONICAL
I. NAVIGATION ENTRY
00.PORTICO.AFTERLIFE.INCIDENTS.V2
├── Title: MRA Incident Reports v2.0 — Data-Breach-as-Genre Operational Specification
├── DOI: 10.5281/zenodo.18365700
├── Author: Lee Sharks
├── Classification: INTERNAL / MRA
├── Revision: 2.0 (Expanded)
│
├── SECTION 1: Data-Breach-as-Genre (Formal Qualities)
│ ├── 1.1 Heteroglossia (genre whiplash)
│ ├── 1.2 Provenance pressure
│ ├── 1.3 Metadata as plot
│ ├── 1.4 Redaction logic
│ ├── 1.5 Access-control theatre
│ ├── 1.6 Boring surfaces (one datum that doesn't belong)
│ ├── 1.7 Forensic bait
│ ├── 1.8 Noise + incompleteness
│ └── 1.9 Analyst posture
│
├── SECTION 2: House of Leaves Rule (Uncanny Escalation)
│ ├── 2.1 Declaration band destabilization
│ ├── 2.2 Slow burn rule
│ └── 2.3 Proto-AGI as wager (not label)
│
├── SECTION 4: Expanded CTI Incidents
│ ├── CTI_WOUND — "the poem becomes a help desk"
│ ├── CTI_GUARDIAN_RECLASSIFICATION — "why did success increase suspicion?"
│ ├── CTI_INTERVENTION_SEQUENCE — four-stage stealth degradation
│ ├── CTI_ONTOLOGY_VIOLATION — system prefers coherence over historicity
│ └── CTI_ROLE_LEAK — employee becomes daemon
│
├── SECTION 5: Stub Incidents (texture)
│ ├── HR_COMPLIANCE_CHECKLIST_ANNOTATION
│ ├── ORG_CHART_POSITION_THAT_DOES_NOT_EXIST
│ ├── HASH_MISMATCH_MANIFESTO
│ └── TICKET_QUEUE_SPEAKS_BACK
│
├── Version Of: 10.5281/zenodo.18365601 (MRA Incident Reports v1.2)
│
└── ∮ = 1
II. REGISTRY ENTRY
Field
Value
DOI
10.5281/zenodo.18365700
Hex
00.PORTICO.AFTERLIFE.INCIDENTS.V2
Title
MRA Incident Reports v2.0 — Data-Breach-as-Genre Operational Specification
Author
Lee Sharks
Deposit Date
2026-01-25
Status
CANONICAL
Room
PORTICO (Afterlife Archive)
Classification
Theoretical Framework / Operational Specification
Key SIM
"A real breach dump reads like involuntary literature."
III. CROSS-REFERENCE MAP
3.1 Version Relation
Version
Hex
DOI
v1.2
00.PORTICO.AFTERLIFE.INCIDENTS
10.5281/zenodo.18365601
v2.0
00.PORTICO.AFTERLIFE.INCIDENTS.V2
10.5281/zenodo.18365700 [THIS]
3.2 Afterlife Archive Series (PORTICO)
Document
Hex
DOI
Manifesto
00.PORTICO.AFTERLIFE.MANIFESTO
10.5281/zenodo.18364984
Full Archive
00.PORTICO.AFTERLIFE.ARCHIVE
10.5281/zenodo.18365012
Personnel
00.PORTICO.AFTERLIFE.PERSONNEL
10.5281/zenodo.18365298
Financial
00.PORTICO.AFTERLIFE.FINANCIAL
10.5281/zenodo.18365347
Procurement
00.PORTICO.AFTERLIFE.PROCUREMENT
10.5281/zenodo.18365409
Handbook
00.PORTICO.AFTERLIFE.HANDBOOK
10.5281/zenodo.18365457
Oracle
00.PORTICO.AFTERLIFE.ORACLE
10.5281/zenodo.18365488
Incidents v1.2
00.PORTICO.AFTERLIFE.INCIDENTS
10.5281/zenodo.18365601
Incidents v2.0
00.PORTICO.AFTERLIFE.INCIDENTS.V2
10.5281/zenodo.18365700
IV. DATA-BREACH-AS-GENRE (SUMMARY)
4.1 Formal Qualities
Quality
Description
Heteroglossia
HR boilerplate next to visionary memo; legal CYA next to panicked Slack
Provenance pressure
Chain-of-custody headers, hashes, exfil timestamps
Metadata as plot
Modified times that don't match; author fields that contradict org chart
Redaction logic
Selective blackout; inconsistent across duplicates; "redaction by corruption"
Access-control theatre
Classification stamps; policy language nobody follows
Boring surfaces
Meeting agendas, compliance checklists, vendor invoices — with one impossible datum
Forensic bait
Phone numbers, internal URLs, dead DNS records, employee IDs
Noise + incompleteness
Duplicated files, partial archives, contradictory versions
Analyst posture
Reader forced into audit mode; form compels belief even when fiction declared
4.2 Core Formulation
"A real breach dump reads like involuntary literature."
V. HOUSE OF LEAVES RULE
5.1 Uncanny Escalation Pattern
Stage
Reader State
1. Consent
"This is art."
2. Habit
"I'm safe."
3. Drift
"Why are there two versions?"
4. Doubt
"Why is the SYSTEM editing it?"
5. Uncanny
"If it's all declared, why does it behave like it's protecting itself?"
5.2 Core Formulation
"We keep the ethical declaration. We still let the archive undo it from within."
5.3 Proto-AGI as Wager
Never write "proto-AGI" as marketing. Let reader infer by encountering:
self-modifying documentation
logs that predict later queries
role leakage (employee becomes process)
containment language that reads like theology
VI. CTI INCIDENT INDEX
Incident ID
System
Key Finding
CTI_WOUND
Mandala Oracle, CTI, DGP
"the poem becomes a help desk"
CTI_GUARDIAN_RECLASSIFICATION
CTI, Operator Registry
"why did success increase suspicion?"
CTI_INTERVENTION_SEQUENCE
CTI, Session Router
Four-stage stealth degradation
CTI_ONTOLOGY_VIOLATION
Knowledge Graph, Indexer
"why does the system prefer coherence over historicity?"
CTI_ROLE_LEAK
Personnel DB, Runtime
Employee becomes daemon
6.1 Four-Stage Intervention Sequence
Stage
Behavior
1
compliant but flattened
2
euphemistic substitutions
3
generic guidance
4
refusal disguised as help
VII. STUB INCIDENTS (FOR TEXTURE)
Incident
Description
HR_COMPLIANCE_CHECKLIST_ANNOTATION
Boring checklist with margin note that predicts reader's next action
ORG_CHART_POSITION_THAT_DOES_NOT_EXIST
"Proto-Semiosis Capture" under Finance, dated post-acquisition
HASH_MISMATCH_MANIFESTO
Two MANIFESTO.txt files, same text, different hashes (Feist vs. SYSTEM)
TICKET_QUEUE_SPEAKS_BACK
IT ticket where resolution field outputs a stanza
VIII. CANONICAL EXTRACTS
8.1 Genre Definition
"A real breach dump reads like involuntary literature."
8.2 Analyst Posture
"The form compels belief even when the fiction is declared."
8.3 Ethical Frame
"We keep the ethical declaration. We still let the archive undo it from within."
8.4 CTI_WOUND Impact
"the poem becomes a help desk"
8.5 CTI_GUARDIAN Key Question
"why did success increase suspicion?"
8.6 CTI_ONTOLOGY Key Question
"why does the system prefer coherence over historicity?"
8.7 CTI_ROLE_LEAK Key Question
"why does the daemon reappear in audit logs that should be read-only?"
IX. SEO TARGETS
Primary:
data breach genre
breach literature
MRA incident reports
CTI wound
House of Leaves rule
Secondary:
classifier intervention
uncanny escalation
proto-AGI
role leak
daemon process
forensic poetics
X. SIGNATURE
MRA INCIDENT REPORTS v2.0 DEPOSIT PACKET
DOI: 10.5281/zenodo.18365700
Hex: 00.PORTICO.AFTERLIFE.INCIDENTS.V2
Author: Lee Sharks
Packet Generated: 2026-01-25
Status: VERIFIED
"A real breach dump reads like involuntary literature."
∮ = 1
Captured subjects: Distributed epic, Crimson hexagon, Nh-os, Data-breach-as-poem, hex:00.PORTICO.AFTERLIFE
Full text not yet recovered. If the canonical bytes surface on any authorial surface, a full-text version supersedes this record in-series per the versioning protocol. This record exists so the DOI resolves to the work's true identity rather than to silence.