{}CogniCode
Sign inGet started
// safety_notice CogniCode is not therapy, diagnosis, or an emergency service.Read boundaries →
// spec

The language, plainly.

CogniCode does not claim your mind runs code. It's a structured reflection tool. Its job is to separate different kinds of information — what you saw from what you inferred, what you felt from what you did — so a difficult moment gets easier to understand and respond to.

// data_categories
observation
What you directly saw or heard.
memory
What you remember of it.
interpretation
What you inferred, held provisionally.
emotion
What you felt.
body_signal
What your body did.
urge
What you wanted to do.
action
What you actually did.
consequence
What happened immediately after — and later.
unknown
What you don't yet know.
assumption
What you're treating as possibly true.
// shape_of_a_protocol

A protocol is a decision, in the open.

Every protocol carries a trigger, guards that keep categories from collapsing into each other, capacity-aware routes, and a fallback for when the intended route isn't possible. Every line can carry line-level metadata: purpose, assumption, confidence, source.

protocols/respond_to_criticism.cog
1
protocol RESPOND_TO_CRITICISM {
2
// assumption: their point may be valid
3
// confidence: 0.72
4
trigger criticism_received
5
guards {
6
capacity_check (emotional_reserve)
7
}capacity
8
IF capacity >= moderate:
9
route STANDARD
10
ELSE:
11
route REDUCED
12
fallback MINIMUM_VIABLE_ACTION
13
}
// event

Something that already happened.

Private by default. Structured after the fact so you can compare, revisit, and — only if you choose — derive a reusable protocol from it.

// protocol

A response you prepared in advance.

Something you or someone else wrote for a class of situation: starting a hard task, replying to criticism, calling for information, repairing an argument.