top of page

Chapter 15: Building Your Own Epistemic Covenant

  • Writer: Paul Falconer & ESA
    Paul Falconer & ESA
  • Mar 20
  • 9 min read

What you now carry

If you have read this far, you carry something substantial.

You know that you already have an epistemology—a way of knowing shaped by your life (Chapter 1). You have seen how the world that shaped it has changed beneath your feet (Chapter 2). You have encountered other traditions, other ways of framing the problem, and you understand that this book's stance is one among many (Chapter 3). You have named your own commitment to epistemological skepticism—not as cynicism, but as a disciplined willingness to doubt well (Chapter 4).

You understand the instrument you're working with: a predicting, grooving, protecting mind that outsources much of its knowing to others (Chapter 5). You have learned to separate questions, claims, and evidence (Chapter 6); to start from the Null Hypothesis and allocate the Burden of Proof (Chapter 7); to ask "What would prove this wrong?" and watch for failure modes (Chapter 8); to treat confidence as a gradient and match scrutiny to stakes (Chapter 9); to act under uncertainty without guarantees (Chapter 10); to know relationally and collectively, curating an epistemic circle (Chapter 11); to weave all of this into daily habits (Chapter 12); to turn the tools inward on identity and memory (Chapter 13); and to apply them in a synthetic world where seeing is no longer believing (Chapter 14).

That is a lot. It is not a set of facts you have memorized. It is a set of practices you have begun to inhabit.

Now comes the question this chapter exists to ask: What will you commit to?

Why covenant, not a code

You could call what this chapter offers a code.

A code is a list of rules. It tells you what to do. It has a certain appeal: it is clear, portable, and easy to check. You either followed the rule or you didn't.

But rules have a failure mode. They can be applied without being inhabited. You can follow the letter of a rule while violating its spirit entirely. You can produce technically compliant behaviour and still be epistemically dishonest. And rules, because they are external, can always be selectively applied, bent in your favour, or quietly set aside when they become inconvenient.

A covenant is something different.

A covenant is a mutual commitment—between you and something you hold as significant. In traditional usage, it is a binding agreement between parties, carrying obligations that go beyond mere compliance. You don't merely follow a covenant. You enter it. You are held by it, and it is held by you.

When you make an epistemic covenant, the other party is reality itself—and the communities of trust and inquiry you belong to.

You are committing not just to follow certain rules about evidence when you feel like it, but to live in a particular relationship with what is true: to remain genuinely open to revision, to extend to your own beliefs the same scrutiny you apply elsewhere, to be honest about what you don't know, and to take seriously the costs your errors impose on others.

This cannot be achieved by a list. It requires something more like character—the kind of commitment that holds even when no one is watching, and especially when updating would be costly.

The anatomy of a personal epistemic covenant

A well-formed epistemic covenant has four parts.

1. Core commitments.These are the bedrock principles you will hold regardless of inconvenience. The non-negotiables: the things you will not do to your own thinking even under pressure. A core commitment might be: I will not declare certainty I don't have. Or: I will not dismiss evidence simply because it threatens a belief I hold. Or: I will always be able to state what would change my mind on a given question, and if I cannot, I will hold that question differently.

2. Calibration practices.These are the regular, active habits that keep your epistemic faculties honest. Knowing is not a static achievement but an ongoing practice. Without maintenance, maps calcify, biases deepen, and the gap between your confidence and your accuracy quietly grows. A calibration practice might be a weekly review of something you changed your mind about. It might be a standing habit of seeking out the strongest version of an opposing argument. It might be the synthetic-era audit from Chapter 14.

3. Acknowledgement of failure modes.This is an honest account of where you specifically tend to go wrong. This is not generic. You know, by now, which biases hit you hardest. You know the domains where your self-story is most heavily invested. You know the kinds of claims you tend to accept too quickly and the kinds you tend to resist too long. A covenant that doesn't name your personal failure modes is a covenant built for a generic human, not for you.

4. The relational dimension.This is who you are accountable to, and how. Epistemology is not a solitary practice. Your knowing is embedded in relationships, communities, and institutions. Your errors have costs that fall on others. Your covenant should name at least one other person or community to whom you are genuinely accountable for how you think: someone who can tell you when your reasoning is slipping, and whom you have given permission to do so.

A note on honesty and self-compassion

Before you build, a word about the frame.

This chapter is not asking you to become a perfect reasoner. That is not achievable, and aspiring to it tends to produce a different failure mode: the person who is so invested in their identity as a careful thinker that they cannot acknowledge when their thinking has been careless.

Calibrated confidence applies to your epistemic self-assessment too. You are a human reasoner operating in a complex and often adversarial information environment, with hardware that was designed for something other than truth. You will make errors. You will be deceived. You will hold beliefs too long and release them too late. You will sometimes reach for certainty when uncertainty is the honest position.

The covenant is not a promise to be perfect. It is a commitment to the direction of travel: toward greater honesty, more proportional confidence, fewer self-serving exceptions, and a genuine willingness to update when evidence warrants it.

Self-compassion and rigor are not opposites here. The covenant is more durable—more likely to hold in practice—when it is built on honest acknowledgement of fallibility rather than aspirational demands for perfection.

You are not trying to become a different kind of mind. You are trying to be a more honest version of the mind you actually have.

Designing your covenant: a guided process

Here is a way to build your covenant. Work through it slowly, in writing, over more than one sitting.

Step 1: Name your core commitments.

Complete this sentence three to five times, in your own language:

"No matter how inconvenient, I commit to..."

Some examples from which to draw or depart:

  • ...never claiming more certainty than my evidence supports, in public or private.

  • ...always being able to articulate what would change my mind on any belief I hold strongly.

  • ...applying the same evidential standards to beliefs I find comforting as to beliefs I find threatening.

  • ...not sharing information I haven't checked, on any topic where the cost of being wrong falls on someone else.

  • ...acknowledging when I was wrong, specifically and without minimisation, to the person or community affected.

Your core commitments should be uncomfortable enough that they will occasionally cost you something. If they never cost anything, they aren't commitments—they're preferences.

Step 2: Identify your calibration practices.

Name two to three specific practices you will maintain to keep your epistemic faculties honest. Make them concrete: not "I will seek out opposing views," but "On any significant belief I hold, I will seek out and genuinely engage with the strongest version of the contrary position before settling."

Practices you might consider:

  • The two-column exercise from Chapter 13, applied to beliefs about the world, not just the self.

  • The synthetic-era audit from Chapter 14, applied weekly.

  • A regular practice of "pre-mortem" thinking: before committing to a major conclusion, asking "How would I be wrong about this, and how would I know?"

  • A reading or listening habit that systematically exposes you to perspectives outside your epistemic circle.

Step 3: Name your failure modes.

This requires honesty that most people find uncomfortable. Write down, specifically:

  • Two or three domains where you tend to accept claims too quickly (because they confirm something you want to believe, or come from sources you reflexively trust).

  • Two or three domains where you tend to resist evidence too long (because updating would be costly to your self-story, your relationships, or your investments).

  • One cognitive pattern—from the failure modes in Chapter 8—that you recognise most clearly in yourself.

These are not confessions for public display. They are private diagnostic information, held in service of awareness. You are naming the places where your covenant is most likely to be tested, and where you are most likely to make the kind of exception that erodes it quietly over time.

Step 4: Name your accountability.

Identify at least one person in your epistemic circle—someone you trust and who knows you well enough to notice—to whom you will make some version of this covenant explicit.

You don't need to share the whole document. You might simply say: "I'm trying to hold myself to better epistemic standards. I'd value you calling me out when you see me reasoning poorly or claiming more certainty than I have."

That act of naming creates accountability that cannot be sustained by intention alone. You are no longer only accountable to yourself. You have given another person a legitimate standing to hold you to the standard you've set.

When the covenant is tested

The covenant will be tested.

Not in abstract thought experiments—in real, costly moments. A belief you've held for years suddenly faces serious counter-evidence. A claim that confirms everything you've been arguing turns out to be false. Someone you trust makes a request that relies on your certainty, and you realise your certainty is thinner than you've been presenting.

These moments are not failures. They are the purpose of the covenant—the moments it exists to navigate.

What the covenant gives you in those moments is not a rule to follow but a prior commitment to draw on. You have already decided, in advance, what kind of reasoner you are trying to be. You don't have to make that decision fresh under pressure. The decision has been made; what remains is whether you will honour it.

This is the difference between a covenant and a good intention. Good intentions are formed in the easy moments and forgotten in the hard ones. A covenant, built deliberately and written down and shared with at least one other person, has enough structure to hold.

It won't always hold. Some version of your worst failure mode will eventually get through. When it does, the covenant gives you a way back: not self-punishment, not denial, but honest acknowledgement and recommitment. "I violated my own standard. Here is specifically how. Here is what I'm doing differently."

That cycle—commitment, failure, honest acknowledgement, recommitment—is not a sign that the covenant doesn't work. It is the covenant working. It is the practice of being a calibrated reasoner in a world that makes calibration genuinely difficult.

The covenant in the synthetic world

One specific dimension of the covenant deserves naming directly, given the world described in Chapter 14.

The epistemic covenant now includes, necessarily, a relationship to the AI tools you use in your knowing life.

You may use AI to gather information, draft text, summarise material, or think through problems. These are legitimate and often genuinely useful uses. But they carry epistemic obligations that most people are not yet honouring explicitly.

Your covenant, if it is to be honest, should include something like:

"When I use AI tools to inform conclusions I will then act on or share, I will treat their outputs as testimony from a knowledgeable but fallible source—not as authoritative outputs. I will corroborate claims that matter. I will not extend trust to fluency."

This is not about distrust of AI. It is about appropriate calibration—the same calibration you apply to any source. The fluency of AI output is not a reliable signal of its accuracy. Your covenant should reflect that explicitly, because the failure mode of over-trusting AI fluency is one of the defining epistemic risks of the current moment.

Living the covenant

A covenant is not a document you file and return to annually.

It is a living practice—something that you move through your days with, applied in the small moments as much as the large ones. The small moments are where the real work happens: the brief hesitation before sharing something you haven't checked, the willingness to say "I'm not sure" when you're not sure, the slight discomfort of genuinely entertaining a perspective that challenges something you hold.

These small moments don't feel dramatic. They often aren't noticed by anyone else. But they are where the covenant either holds or erodes—quietly, incrementally, in one direction or the other.

The person who lives this covenant is not someone who never makes epistemic errors. They are someone who has built, over time, a set of habits and commitments that make honest thinking their default rather than their aspiration. Not a perfect thinker—a practicing one. Someone who has made a real commitment to the direction of travel, and who returns to that commitment when they stray.

That, at the end of this book, is what is being offered: not certainty, not a perfect method, not a guarantee of arriving at truth. But a way of being in relationship with what is real and what is unknown—honest, proportional, humble, and genuinely open to the evidence, wherever it leads.

A closing practice: writing your covenant

Before you finish this chapter, write your covenant.

Not an outline. The actual document—your own words, your own standards, your own failure modes, your own accountability.

It does not need to be long. It should not be long. Four paragraphs—one for each of the four parts described above—is sufficient.

When you have written it, read it aloud once.

Then share it with the person you named in Step 4.

Not as performance. As a commitment made real by being witnessed.

That act of witnessing—of having your standard heard by someone who matters to you—is the small ritual that lifts a private intention into a genuine covenant.


Recent Posts

See All

Comments


bottom of page