Unit Review: Epistemic Integrity and Protocol Literacy 2.3A.1-R

Key Structural Points

• Epistemic integrity at the individual level operates through three disciplines: provenance tracking (where did this claim come from?), verification discipline (can I check it independently?), and assumption management (what am I acting on without full verification?).

• Protocol literacy is the infrastructure complement to epistemic integrity: key management, attestation, self-custody, and recovery planning maintain sovereign control over the systems through which truth-contact is exercised.

• The Personal Provenance Protocol reduces epistemic integrity to a three-question habit (Channel, Source, Basis) scaled by stakes — seconds for low-stakes claims, written notes for high-stakes decisions.

• Self-custody means maintaining sovereign control over critical access mechanisms rather than delegating to institutions whose governance, incentives, and continuity the individual cannot verify.

• Recovery planning is part of day one, not an afterthought: backups in independent locations, social recovery contacts briefed before crisis, and incident drills conducted under realistic conditions.

• Under AI conditions, provenance tracking encounters structural limits (provenance collapse), verification faces volume constraints (verification flooding), and assumption management must account for embedded assumptions in AI-generated content (assumption injection).

• Epistemic integrity without protocol literacy leaves clear thinking structurally dependent on unauditable systems; protocol literacy without epistemic integrity is sovereign custody of unverified beliefs. The integration is the structural floor for individual RO practice.

Philosophical Lexicon

• assumptions register — A maintained list of beliefs one is acting on without full verification, tracking the assumption, the behavior it supports, and the behavioral consequences of the assumption failing. (RO)
• attestation — A verification mechanism that confirms a claim without exposing the underlying data; enables auditability without surveillance. (RO)
• auditability — The capacity to verify that a system is operating as designed, with the subject of audit being the arrangement, not the person. (RO)
• bounded interdependence — The requirement that every cooperative framework maintain clean exit, meaningful recourse, and data portability. (RO)
• duty of clarity — The design obligation requiring any institution that processes claims about reality to maintain signal preservation, provenance, verification infrastructure, and safe degradation. (RO)
• epistemic integrity — The capacity of a reasoning system to remain coherent, testable, and non-corrupted across complex or distributed contexts — including the Provenance/correction-channel discipline that keeps commitment sized to warranted confidence and preserves the channel for later evidence to correct a conclusion. One of RO's nine design patterns. (RO)
• operability test — The four-condition assessment (traceability, auditability, survivability, recoverability) applied to every structural claim in the architecture. (RO)
• encoded objective law — The embedding of moral constraints into system design, where values like consent, sovereignty, and property are enforced structurally through code or protocol, not merely by law, habit, or virtue. One of RO's nine design patterns. (RO)
• protocol literacy — The practical capacity to verify claims, manage cryptographic keys, maintain append-only personal logs, and produce signed attestations — the individual-level expression of encoded objective law. (RO)
• recoverability — As an operability condition: when stress produces drift or degradation, the architecture must detect it and enable correction without central authority. (RO)

Unit Glossary

• assumption injection — The condition in which AI-generated content embeds undeclared assumptions derived from training data, requiring the recipient to manage not only their own assumptions but those the system may have introduced. (RO)
• incident drill — A periodic test in which a component failure is simulated and the recovery plan is executed under conditions approximating real stress, converting theoretical preparedness into verified capacity. (RO)
• Personal Provenance Protocol — A three-question habit (Channel, Source, Basis) applied before acting on any claim that might influence a significant decision; the operational form of epistemic integrity at the individual level. (RO)
• provenance collapse — The epistemic condition in which AI-generated content terminates the provenance chain in a process whose reasoning is not inspectable, creating a qualitatively different verification challenge. (RO)
• provenance tracking — The habit of identifying the channel, source, and evidence basis of any claim before acting on it. (RO)
• recovery plan — The pre-designed architecture for restoring access and function after a component failure, comprising backups, social recovery contacts, and incident drills. (RO)
• self-custody — Maintaining sovereign control over critical access mechanisms (keys, credentials, data) rather than delegating custody to institutions whose governance the individual cannot verify. (RO)
• verification flooding — The condition in which AI-generated content arrives at volumes exceeding individual verification capacity, requiring a shift from claim-level to source-level assessment. (RO)

Concept Check

• What are the three disciplines of epistemic integrity, and how does each address a different aspect of truth-contact?

• Why is protocol literacy described as a "moral discipline" rather than a technical skill? What moral principle does self-custody express?

• The Personal Provenance Protocol scales by stakes. Give an example of a low-stakes claim that warrants only a mental check and a high-stakes claim that warrants written provenance notes. What criteria distinguish the two?

• How does the assumptions register connect to Arc 2's weekly review (2.2.1)? What does the register provide that the review alone does not?

• Why is recovery planning described as "part of day one"? What structural vulnerability does a person face if recovery planning is deferred?

• Under AI conditions, provenance tracking encounters "provenance collapse." Explain this concept and describe how the verification strategy adjusts when AI-generated content is involved.

• The article argues that epistemic integrity without protocol literacy is insufficient, and vice versa. Construct an example of each failure mode — a person with one discipline but not the other — and identify what they would be unable to do.

Points to Ponder

• Inventory your own information intake from the past week. For how many of the claims that influenced your decisions can you identify the channel, source, and evidence basis? What does the gap reveal about your current epistemic practice?

• Consider the custody assessment from the Key Management sidebar. How many of your critical systems — email, banking, professional credentials — are held in custody by institutions you have never evaluated against the three criteria (verifiable governance, clean exit, structural safeguards against unilateral change)? What would you need to do to reduce that dependency?

• The article identifies "provenance theater" and "provenance paralysis" as failure modes. Which are you more susceptible to — performing the habit without adjusting behavior, or demanding perfect provenance before acting? What does your default tell you about how you manage epistemic uncertainty?

To Learn More

• Nissenbaum, Helen. Privacy in Context: Technology, Policy, and the Integrity of Social Life. Stanford, CA: Stanford University Press, 2010. Develops the contextual integrity framework that underpins RO's approach to information flow — relevant here because epistemic integrity requires understanding how context shapes the meaning and reliability of claims.

• Schneier, Bruce. A Hacker's Mind: How the Powerful Bend Society's Rules — and How to Bend Them Back. New York: W. W. Norton, 2023. Examines how systems are exploited through their rules rather than despite them — the structural perspective on why protocol literacy is a moral discipline, not merely a technical competency.

• Rand, Ayn. Introduction to Objectivist Epistemology. Expanded 2nd ed. New York: Meridian, 1990. The foundational text for the concept-formation and knowledge-validation methods that epistemic integrity operationalizes — the TO inheritance this unit applies at the structural level.