Primacode

The claim record

What the system believes, what happened to that belief, and who said so. An append-only event stream, never a stored verdict.

Live Built and working today on the surface this card describes.

What it does

A claim is something the system believes and has not necessarily checked. A claim event is one attributed, timestamped thing that happened to that belief.

The event stream is the record. Everything a reader sees is folded from it at render time. There is no stored state column, because the moment current state is stored beside the events the two can disagree, and the stored one is what gets rendered.

It is deliberately not a feature of the desktop tool. The desktop and the chat write the same objects into one repository, distinguished only by their source, so nothing in the record may assume a terminal, a diff, or a repository being present.

You can act on it from the pane: check a claim, dispute it, or read its history. Undo and withdraw are typed commands reachable from anywhere.

The undo window is before the append. The record has no update and no delete, so the pane holds the event for five seconds while the confirmation is up and the repository is never told. Past that window the honest act is to withdraw, visibly, in the record.

Inputs and outputs

Store	An append-only file, one event per line.
Event	Attributed and timestamped. Never edited, never deleted.
Rendered as	Four trace sections, folded from the events at render time.
Exports	An 88-column text export, and a self-contained page.
Actions	Check, dispute, history, undo (within five seconds, before the append) and withdraw (after it).

Configuration

Key mode	The pane's keys are live only while its footer is drawn. A pane that offers an action it cannot perform is worse than one that offers none.
Undo	A typed command, deliberately not the usual keyboard shortcut, which is Suspend Terminal in a terminal application.

Limits

One person using both the chat and the desktop tool must resolve to the same actor string, or the audit shows one human as two. That is open, and it corrupts quietly until it is closed.
The actor chain has one link that returns nothing on purpose: the chat gateway client is chat-only and exposes no user.
There is no update and no delete. A correction is a new event, not a rewrite.

Example

what you can do to a claim

c          check
d          dispute
h          history
/undo      within five seconds, before the event is appended
/withdraw  after it, visibly, in the record

Source of truth

philosophers_stone/platform/primacode.md § The claim record (the vocabulary, the fold, the append-only store, the pane, the undo window, the open actor question)

All product cards Primacode