What teams build with capsules and Sage.
Thyme RAG Capsules + Sage Cloud
Support and internal knowledge
Put manuals, policies and past tickets in a capsule. Your team asks Sage Cloud in the dashboard, and Claude or ChatGPT connect through an authenticated, read-only MCP key. Every answer cites its sources.
About Thyme RAG Capsules →Thyme RAG Capsules over MCP
Memory for AI agents and loops
Agents read and write a capsule between runs. Writes carry provenance and can be reverted, and a model-written memory is never treated as an approved company fact.
For loops →Sage AI · early access
Proposals and solicitations: the eligibility ledger
Track a solicitation and its amendments as versioned sources, confirm a complete requirement registry, record hard gates with evidence, and keep overrides as an append-only history. Only a person can record GO or NO-GO, and drafting starts only from a current GO and approved inputs. AI may recommend; it never approves.
Open the ledger (sign in first) →How the eligibility ledger keeps a bid honest
- The requirement registry covers the whole solicitation and its attachments, not a top-k search result. A person confirms it is complete for the current version, and an amendment reopens it.
- Hard gates are pass, fail, unknown or reviewed-not-applicable. Unknown is never a pass, and missing evidence never becomes a confident one.
- An override can't waive a mandatory obligation. Overrides and corrections are appended, never edited in place.
- Confirming (or reconfirming) the plan invalidates any earlier GO. A change to the solicitation, registry, company facts or approved deal inputs does too.
- Eligibility, evidence, fit, capacity, bid cost, risk and win probability stay separate numbers with units and sources. A model's confidence is never used as a win probability.
- A draft is written only from the approved snapshot. If anything changes while it is being written, the draft is marked stale and blocked from use.