The accountability layer

Here's a yes —
now trace its shape.

ClisTa is not where reasoning happens. It is where reasoning becomes accountable — turning scattered human + AI deliberation into a durable, replayable record of accountable state: evidence, surviving objections, authority, provenance.

zero dependencies Node ≥ 18 102 commits · 37 tags
clista — clean-room replay
$git clone https://github.com/lati-club/clista-protocol.git
$npm run replay
ingested session → canonical event log
byte-identical to committed log
idcr_limited_beta — yes · scope: redacted tickets only
!resumeStatus: "degraded" (origin predates v0.24)
privacy objection survived the yes — trusted: false
Clean-room replay PASSED
Operating law
Conversation is input.
Reasoning state is output.

conversation → event log → projection → verification → accountable state

The lived proof

A team approves an AI support-assistant beta. The approval is not a boolean.

Twenty-three events encode the full deliberation. The yes arrives with its accountability structure fused on — anyone holding the event log can reconstruct it.

Evidence 4 items

carried into the decision, each bound to a participant and event-time authority.

Objection survived

a privacy objection that survived the yes — recorded, not resolved away.

Minority report 1

a dissent preserved alongside the approval, not overwritten by it.

Provenance traced

from dcr_limited_beta back through claims, reviews, and the objection to raw evidence.

Authority 2 reviews

governance reviews routed without becoming approval.

Scope narrower

redacted sample tickets only — narrower than the question asked.

Protocol spine

Every capability is a verifiable command that fails closed.

Eighteen layers, each verifying one boundary. Green never means endorsement — every verifier keeps trusted: false until something outside the protocol grants trust.

+ 12 more layers
Integrityintegrity verify
The log is verifiable history, not just readable data.
Continuitycontinuity verify
A successor resumes settled state without replaying the transcript.
Executionexecution verify
Performed action is evidenced under authorized scope — intent ≠ completion.
Outcomeoutcome verify
Observed effect is checked against intended — completion ≠ success.
Provenanceprovenance trace
Each contribution's source lineage and transformation are auditable.
Releaserelease verify
The repository artifact is bound and reproducible.
That loop is universal

Separate motion from verified progress.

1

An agent claimed a milestone was complete.

2

The artifact disagreed.

3

The protocol paused action.

4

Verification restored alignment.

The gate

A public, falsifiable test — with a hard deadline.

By 2026-09-07 we need ≥5 external-culture runs — different teams, not prompted or graded by us — through blind judging. If they don't materialize, or show no advantage, the productization claim dies on the record.

Failed and abandoned runs are wanted evidence.
What this does not claim
That the format is ready for production use
That internal pilots prove anything
That we have solved governance or agent alignment
productization claim · revocable