# The C2 Methodology

**Curiosity and Context for Governed AI Collaboration**

---

## What C2 Is

C2 (Curiosity and Context) is how you practice the Piqued
Manifesto. Not the philosophy — the methodology. The daily habits
that turn seven principles into governed work.

Two forces drive every productive collaboration with AI: the
curiosity to question what you're given and the discipline to carry
context forward for whoever comes next. Curiosity without context
produces brilliant work that nobody can continue. Context without
curiosity produces meticulous records of unexamined output. C2
holds them together.

You don't adopt C2 all at once. You start with one habit. The rest
follow.

---

## The Three Habits

### Habit 1 — Ask Before You Accept

Before you accept any AI output, ask it to explain its reasoning.
Not "are you sure?" — that gets you a confident yes. Ask *why*.
"Why this approach? What alternatives did you consider? What are
you uncertain about?"

If the AI can't explain why it produced what it produced, don't
use it.

That's Curiosity. That's Principle 1 (Understanding). That's your
entry into the compact.

### Habit 2 — Say It Out Loud

When you make a decision during an AI conversation — any decision —
state it explicitly. "We decided X because Y. Locked." Not in your
head. In the conversation. In writing. Where the next person can
find it.

Decisions that exist only in your memory die with the session.
Decisions that are stated, recorded, and linked to their reasoning
travel with the work.

That's Context. That's Principle 7 (Continuity) in its simplest
form.

### Habit 3 — Read Back Before You Commit

Before you finalize anything, pause. Read back through the
conversation. Ask yourself: "What did I accept without actually
thinking about it?"

You will find something. Everyone does. The AI was confident, you
were in flow, and something slipped past your judgment. The read-
back catches it. Not always. But often enough to matter.

That's Diligence. That's Principle 2 — earning your confidence
instead of borrowing it.

---

## Curiosity Best Practices

**Ask for reasoning, not confirmation.** "Why did you choose this
approach?" produces useful information. "Is this correct?" produces
false confidence.

**Ask what's missing.** AI optimizes for what you asked. It rarely
volunteers what you didn't ask. "What am I not considering?" is
the single highest-value question you can ask.

**Ask about uncertainty.** "Where are you least confident in this
output?" surfaces the places where borrowed confidence is most
dangerous.

**Challenge the first answer.** The first output is a draft, not a
deliverable. Treat it like a colleague's first attempt: what
assumptions did they make? What constraints did they miss?

## Curiosity Anti-Patterns

**Accepting because it sounds right.** Fluency is not accuracy. AI
produces confident, articulate output regardless of correctness.
"It sounds right" is not a verification method.

**Asking "are you sure?" and accepting the yes.** AI will almost
always confirm. The question teaches you nothing. Ask *why* instead.

**Skipping verification because you're in flow.** Momentum is the
enemy of diligence. The moment you stop questioning because you're
making progress is the moment borrowed confidence enters the work.

**Trusting authority over evidence.** "The AI said so" is not a
justification. Neither is "the senior person agreed." Evidence
justifies. Authority doesn't.

---

## Context Best Practices

**Name your decisions when you make them.** "We decided X because
Y" takes five seconds and saves the next person five hours.

**Record what you rejected and why.** The decision you didn't make
is as important as the one you did. Without the alternatives,
your successor will re-evaluate options you already eliminated.

**Close every working session with a handoff.** One sentence: what
should the next session do first? That sentence is the most
valuable artifact of the session. Everything else supports it.

**Link, don't duplicate.** Point to where the reasoning lives.
Don't copy it into every downstream document. One source of truth,
many references.

## Context Anti-Patterns

**Closing the conversation and walking away.** The session ends.
The decisions die. The next person starts from zero. This is the
most common failure mode and the most expensive.

**Recording what happened but not why.** A log of actions without
reasoning is a history without lessons. "We chose X" is incomplete.
"We chose X because Y, after considering Z" is context.

**Assuming you'll remember.** You won't. Not in a week. Not when
you're three projects deep and someone asks why this decision was
made. Write it down now.

**Carrying context in your head instead of in the work.** If the
context doesn't survive your departure — from the session, from the
project, from the organization — it wasn't context. It was memory.
Memory is fragile. Records endure.

---

## Start With One Habit

If the full methodology feels like too much, it is too much — for
now.

Start with Habit 1. Just Habit 1. Before you accept the next AI
output, ask it to explain its reasoning. Do that for a week.

You will notice two things. First, you catch errors you would have
missed. Second, you start understanding the work at a level you
didn't before — because curiosity compounds. The questions you ask
today give you the knowledge to ask better questions tomorrow.

When Habit 1 feels natural, add Habit 2. Then Habit 3.

That's C2. Not a framework you adopt on a Monday morning. A set of
habits you build one at a time until governed work is how you work.

*Curiosity asks. Context remembers.*

---

*The C2 Methodology*
*Curiosity and Context for Governed AI Collaboration*
*Standard: pqdx/2.0.0*


---
The C2 Methodology by Piqued X — CC-BY-ND 4.0 — piqued.dev/c2
Version: 1.0.0