Why this exists

The obvious fix is memory: let the thing remember what you told it. That is what everyone built, and it produces a pile of assertions with nothing behind them — a note from a bad afternoon two years ago carries the same weight as a principle you have held for a decade, because neither one kept the reason it was written down.

This takes the other route. It does not ask you what you are like. It reads what you have already written and done, works out what keeps being true, and refuses to write anything down that it cannot show you the evidence for. A rule seen once waits. Two rules that contradict each other become a question rather than a silent decision. The result is smaller than a memory feature would produce, and every line of it can be argued with.

Then it stays on your machine — because an identity measured this carefully is not something to hand to a server, and because a claim you can verify with lsof beats a promise on a privacy page.

The name

Core — the part that is left when everything circumstantial has been taken away. -ence — the Latin ending that turns a thing into a state of being: patience, confidence, the quality of being something.

Together: the state of having a core, established rather than claimed. The word does not exist in a dictionary — it was made for this — but it is built from two real pieces and it leans deliberately on the two words it sounds like. Credence, which is what you extend to a claim that has earned it, and evidence, which is the only reason this product writes anything down at all.

Who makes it

Akaya Labs, a one-person studio. Every release, its notes and every open question are in one public repository; nothing is decided in a room you cannot see into.

Getting in touch

Issues and questions both belong on the engine’s tracker. Nothing is triaged in private, and there is no support address that goes somewhere different from where the code is.