The Conditional Barbell Hypothesis predicts that AI's hollowing of middle-tier cognitive labor shifts economic premium toward performative humanity and constitutive human presence. Process provenance — cryptographically verifiable records of a document's analytical trajectory — becomes the mechanism by which scholars defend claims to both poles. The integration of Karpathy's LLM Wiki pattern and Condrey's Witnessd framework provides the execution engine.
AI hollows middle-tier cognitive work, driving premium toward uniquely human attributes and the irreplaceable fact of human presence.
Append-only chronological log (log.md) creates grep-able audit trail of every ingest, query, and synthesis — preventing long-context "context rot."
Jitter seal (HMAC-SHA-256 over session_secret + keystroke_ordinal + cumulative_document_hash) cryptographically binds human keystroke entropy to document evolution.
Forces skeptics to make simultaneous, falsifiable allegations across Telemetry, Cryptographic, and Temporal layers rather than expressing vague doubt.
AI automates routine, structured cognitive tasks — including literature summarization and citation formatting — hollowing out the middle of the cognitive labor market and forcing workers toward either end of the barbell.
Performative Humanity: Creativity, critical thinking, emotional intelligence, contextual nuance, and authentic expression — attributes AI cannot replicate.
Constitutive Human Presence: The inherent and irreplaceable value of being human — lived experience, conscious intent, and personal values AI lacks as a statistical model.
Jitter seal demonstrates real human keystrokes produced intermediate document states. Append-only log.md records a human was there throughout the knowledge-building process.
"I wrote this" shifts from an unverifiable assertion into a falsifiable claim — backed by cryptographic proof and chronological audit trail.
| Layer | Focus | Answers | Gap |
|---|---|---|---|
| Data Provenance | Dataset lineage & transformations | "Where did this data come from?" | Doesn't answer who wrote the analysis |
| Content Provenance | C2PA cryptographic signing | "Who signed these pixels?" | Signs custody, not creation — post-hoc reconstruction problem |
| Process Provenance | Chronological analytical trajectory | "How was this produced?" | Missing layer — the critical gap for academic integrity |
Key insight: Digital signatures prove key possession, not authorship. An author who generates text with AI, constructs intermediate states post-hoc, and signs each hash produces a chain indistinguishable from genuine composition. Only Process Provenance closes this gap.
The LLM Wiki solves context rot — the degradation of LLM output quality as conversation length grows. Each turn appends to wiki/log.md, creating a structured, grep-able audit trail that externalizes state.
Raw source data — PDFs, HTML dumps, transcripts. Immutable once ingested. Prevents source drift.
One markdown page per source. LLM extracts title, authors, abstract, key claims. Human reviews.
Cross-cutting concept pages linking related sources. The emergent value of the knowledge graph.
Append-only chronological record. Every operation logged with timestamp: ingest, query, lint, synthesize. Prevents "what did we already do?" loops.
The jitter seal is computed as: HMAC-SHA-256(session_secret, keystroke_ordinal || cumulative_document_hash) — generated by the physjitter user-mode daemon capturing keystroke timing delays at microsecond precision.
| Tier | Attestation | Threat Model |
|---|---|---|
| T1 | OS-level keystroke logging | Application-level adversary |
| T2 | OS-level + validation | User-level adversary |
| T3 | Hardware-Bound (TPM) | OS-level adversary |
| T4 | Hardware-Hardened (Secure Enclave) | Kernel-level adversary |
Claim: Keystroke timing was fabricated by kernel-level adversary.
Defense: At Tier T3/T4, keystroke validation is dual-source — OS events AND hardware signal (TPM/Secure Enclave) must agree.
Claim: HMAC-SHA-256 was tampered with or session secret extracted from Secure Enclave.
Defense: TPM/Secure Enclaves are independently audited hardware — claiming compromise is a specific, testable allegation.
Claim: System clock was rolled back to fabricate temporal sequence.
Defense: External NTP/blockchain anchors + Verifiable Delay Functions (VDFs) independently record state hashes at wall-clock times.
Explicitly: Kernel-level adversaries can defeat the system. Typing AI-generated content produces valid evidence. The contribution is converting vague doubt into falsifiable allegations.
| Dimension | LLM Wiki | Witnessd |
|---|---|---|
| Layer | Process Provenance (analytical trajectory) | Cryptographic Attestation (keystroke proof) |
| Records | What was done (ingest, query, lint) | How it was done (human keystrokes) |
| Granularity | Operation-level | Keystroke-level (microseconds) |
| Immutability | Append-only (convention) | Cryptographically enforced (HMAC chain) |
| Verification | Human-auditable (grep log.md) | Machine-verifiable (jitter seal validation) |
| Privacy | Full content visible | ZK-PoP: content hidden, process verifiable |
Verification Protocol: 1. Audit log.md for complete source ingestion + query trail. 2. Validate .pop packet via Adversarial Collapse Principle. 3. Check VDF timestamp anchors against external clocks. 4. Verify CLAUDE.md/AGENTS.md schema compliance.
For Academic Authors — Initialize Witnessd session + LLM Wiki structure before writing. Package .pop Evidence Packet alongside log.md as a supplementary attestation bundle upon journal submission.
For Publishers & Editors — Shift from trust-based AI disclosure to verifiable .pop packet audit in peer review. Adopt tiered ZK-PoP attestation for privacy-preserving human authorship verification.
For EU AI Act Compliance — Extend Article 50 beyond binary disclosure. Log.md enables granular compliance: "31% human-authored, 69% AI-assisted with human direction" — enforceable August 2026.
For Research Integrity (ORI) — Shift enforcement from "prove the author used AI" (currently impossible) to "author has not provided a valid process provenance bundle" — making undeclared AI use technically detectable.
Tier guide: Tier 1 = Primary source (academic paper, official specification, or original framework) · Tier 2 = Policy analysis, trade publication, or multi-source synthesis · Tier 3 = Single-source reporting — verify independently before citing
Generated May 26, 2026 · DeepSeek V4 Pro · research-to-vault v1.0 · Gambit / brief-to-slides v2.0