PROMISE · NEW CLAIM
“We can waive the implementation fee.”
● CHECKING AGAINST REFERENCE POLICY
A pledged word · a promise you can be held to.
Remember.
Verify.
Commit.
Troth is the sales/client copilot that remembers what was actually promised — and refuses to repeat a promise it hasn't verified.
Try it yourself — paste a transcript, break the policy, watch the promise get flagged.
WARMCLIENT FACT
HOTACTIVE DEAL
FLAGGEDUNVERIFIED
COLDCALL · 14:32
TROTH
MEMORY WITH RECEIPTS
01 · The trust gate
A promise is only useful when you know why you believe it.
CRM notes remember the conversation. Troth remembers the commitment, the evidence behind it, and whether policy allows it to become a fact.
WARMCLIENT TERMS
REFERENCE15% MAX
COLDCALL 14:32
FLAGGEDCONFLICT
02 · Five tiers, and one label of our own
Not a database. A living evidence field.
Sibyl Memory ships five tiers. Troth routes each piece of relationship memory into the one where it belongs — then writes a trust label of its own on top of WARM.
SIBYL MEMORY — THE FIVE REAL TIERS
HOT
Active deal, objections, next action.
WARM
Confirmed facts, pricing, signed scope.
COLD
Timestamped calls, emails, decisions.
REFERENCE
Standing pricing and policy rules.
ARCHIVE
Closed relationships and proof.
TROTH — A STATUS WE WRITE ONTO WARM
FLAGGED
Not a sixth tier. Sibyl’s entities carry a native status field, and Troth writes flagged into it when a promise breaks standing policy, hedges, or can’t be checked at all.
Sibyl stores the word. Deciding what it means — and refusing to repeat the promise until a human resolves it — is Troth’s logic.
set_entity("promise", id, body,
status="flagged")
status="flagged")
03 · Why Sibyl
Memory you can hold in your hand.
Troth needed a memory that outlives the session, separates a standing rule from a passing fact, and can be deleted to prove it was load-bearing. Sibyl Memory does all three in a single file.
01
A file, not a service.
No vector database, no embedding bill, no network hop before an agent can remember. Sibyl is SQLite with FTS5 — it starts instantly and it is yours.
02
Tiers that mean something.
A pricing policy and a passing remark are not the same kind of memory. REFERENCE outlives the deal; HOT changes hourly. Most stores flatten that distinction — Sibyl keeps it.
03
Status is native.
Entities carry a real status field, so the trust label rides on the record itself and list_entities(status="flagged") is one indexed read — not a scan.
04
Deletable, therefore provable.
Because memory is one file, you can remove it and watch Troth refuse to answer. That failure is the proof the memory was load-bearing rather than decorative.
Who it is for
NOT ONLY CLIENT-FACING WORK
Freelancers & solo reps
One person, many conversations. Troth is the memory you would keep if you had time to keep one.
Sales teams
A shared policy in REFERENCE and a shared flag queue. What one rep promised does not leave with them.
Companies, internally
The same gate works on any commitment against any standing rule — procurement limits, SLA terms, hiring offers, vendor scope. A promise is a promise whether the other party is a client or a colleague.
Nothing in Troth assumes a customer. It assumes a rule and a commitment. Change what is in REFERENCE and the same machinery guards a different kind of promise.
04 · The loop
Ingest once. Verify every commitment.
A transcript, email thread or notes dump becomes structured memory. Nothing bypasses the same audit trail used by manual entries.
01 / INGEST
Drop the conversation.
Troth extracts client facts, policies, timeline entries and promises from the raw material.
02 / CHECK
Test the promise.
Every commitment is checked live against REFERENCE rules before it can become confirmed memory.
03 / RESOLVE
Let a human decide.
Approve, retract or archive a FLAGGED promise. Every resolution is written to COLD.
04 / PROVE
Keep the receipt.
Archive is a state change, not disappearance. Troth can prove who was retired, when, and why.