What it reads, what it writes, what to do with it

The two halves

The engine reads your work and writes rules. The viewer draws them. They ship as one download and share one file: the engine writes it, the viewer opens it read-only, and neither knows anything about a network.

Everything that changes the identity happens through the engine, on purpose. The confidence formula and the rule that evidence is mandatory live in one place; a second implementation inside the app is how the two would start disagreeing about who you are.

The five layers

Every rule belongs to exactly one. The distinction is the reason the output is not a pile of notes.

• Values

  What you will not trade away. Slow to appear, slow to change, and the least likely to be wrong.

• Patterns

  What you do repeatedly, whether or not you would describe yourself that way. The largest layer by some distance.

• Voice

  How you say things — length, directness, what you refuse to pad.

• Preferences

  What you reach for when nothing forces your hand. A preference is not a value; the engine will not promote one into the other.

• Current state

  What is true this month. Deliberately separated so a passing mood never gets treated as a fact about you.

Confidence, and why rules disappear

Each rule carries a confidence the engine derives from how much evidence supports it and how much contradicts it. Nothing below 0.35 is written at all. In the app, Settings → Identity raises that floor further if you want to see only what the engine would defend — the count of what is being hidden is always in the top bar, because looking at part of your identity without knowing it is worse than not looking.

A rule seen exactly once is held back as a draft rather than published. Two rules that contradict each other become a question in the inbox instead of a silent resolution.

Disagreeing with a rule

Click any node. The panel shows the rule, its layer, its confidence, and the events it was drawn from — the actual messages, with the corrections marked. If it is wrong, the evidence usually shows why.

• Hide a topic

  It stays in the database and stops appearing. Hiding says “this is not me”, not “delete the record”.

• Merge two topics

  When the engine has split one subject into two, merging teaches it the boundary.

• Answer a contradiction

  The inbox queues them. Answering settles the rule and tells the engine which reading to trust next time.

• Confirm or drop a draft

  Single-sighting rules wait in the inbox until you say whether they are real.

Keeping it up to date

Refresh whenever you want the identity brought up to date. The picture watches the database and redraws itself as soon as the engine writes, so you can leave the window open while a pass runs.

Where things live

• ~/.karaca/brain.db

  The identity. One SQLite file. Copy it, back it up, open it with any SQLite browser, or delete it.

• No network connections

  Ask the system yourself: lsof -i -a -p $(pgrep -x Coredence) prints nothing, because there is nothing to print.

• Settings → Engine

  Points the app at a different database, and turns off the automatic refresh if you would rather the picture held still.

Anything not covered here belongs in the issue tracker. If something on this page is wrong or missing, say so.