believe
Assert a belief — something held true about this project (a convention, a constraint, a how-we-do-it).
Beliefs are revisable; memories are not. If the fact might change with evidence, use this. If it just happened and is forever-true, use remember.
Signature
believe({ text: string, confidence?: number }) →
{ id: number, text: string, confidence: number }
| Param | Type | Required | Description |
|---|---|---|---|
text | string | yes | The belief to hold. |
confidence | number 0..1 | no | How sure are you. Default 0.7. |
Example
MCP:
> believe the deploy target is staging.example.com — confidence 0.7
REST:
curl -X POST https://mneva.dev/v1/believe \
-H "x-mneva-key: $MNEVA_KEY" \
-H "content-type: application/json" \
-d '{"text":"the deploy target is staging.example.com","confidence":0.7}'
Response:
{ "id": 1, "text": "the deploy target is staging.example.com", "confidence": 0.7 }
Later, when the deploy target changes, revise it. Or when evidence accumulates, use evidence and let SPRT shift the confidence.
When to use this vs remember
Use believe when... | Use remember when... |
|---|---|
| The fact can change in the future | The fact is a historical event |
| You want recall to only return the current version | History matters; old versions should remain searchable |
| You expect to update or refute it | You're recording what happened, full stop |
| believe — conventions/constraints | remember — events/decisions |
| "we use Tailwind 4" | "we picked Tailwind 4 over CSS Modules in March" |
| "the migration table is partial" | "ran the v2 migration on 2026-05-12, hit a row with NULL email" |