This endpoint exists to answer one question: why did recall not return that?
A read surface that silently applies three filters and reports one boolean makes
that question unanswerable, so every row carries
recallable and the three
filters behind it.List beliefs
recallable and the three filters
recallable is the AND of three checks, each reported separately so a false can
be diagnosed without guessing:
Each filter carries a
*_measures string saying what it actually tested, because
the obvious reading is wrong in one case — see below.
🔴 not_expired does not measure retention
valid_to is the temporal validity of the assertion: this was true until
then. It is not a retention deadline.
There is no retention column on any brain table, so:
expires_atis absent from the response entirely, andexpires_at_unavailable_becauseexplains why. Reporting it even asnullwould imply a lifecycle that does not exist.- A belief in this build never lapses. Nothing ages out.
GET /v1/brain/retentionanswers501for the same reason.
Fields that are null everywhere
One belief
404 not_found if the belief does not belong to your
company.
The four that refuse
These share the/v1/brain prefix and answer 501 not_configured.
Reaffirm
POST /v1/brain/beliefs/{id}/reaffirm
A reaffirmation is an event — this was checked again, on this date, by this
actor. No table records one, and no recall-count column exists. The only way to
implement it today would be to bump observed_at, which would silently rewrite
when the claim was first observed and destroy the column that orders belief
history.
Lessons
GET /v1/brain/lessons · POST /v1/brain/lessons
A lesson is not a belief with a different label. Serving lessons out of the claims
table would make one row mean two things — the two-vocabulary collision the brain
exists to end.
Retention
GET /v1/brain/retention
Decisions
GET /v1/brain/decisions
A read view over the policy decision ledger filtered to brain resources —
explicitly not a second ledger. There is no first ledger to view. See
GET /v1/policy/decisions.
Availability
These operations exist at the company prefix only. There is no/v1/users/{user_id}/brain/beliefs. Company-scoped and tenant-scoped brain
operations are listed in the Brain overview.
Like every /v1/brain route, they require the brain primitive to be enabled on
the AccountKit and are metered against the plan quota.