1
Codify knowledge
Structure what you know with taxonomy, links, and agent-oriented metadata—online editor or Obsidian vault.
Simple, transparent pricing
No pricing plans available. Please try again later.
TPS Report — codify SOPs and procedural knowledge for your team and your AI agents
Procedural knowledge for teams & AI agents
Write your SOPs once. Your team reads them. Your agents run them.
TPS Report is where you codify SOPs, runbooks, and how-tos into one structured knowledge base—readable by people, executable by agents, and sharpened by what every run teaches you. Authored anywhere, wired into every agent ecosystem.
Your agents are brilliant strangers.
They reason well—but they don't know your playbooks, your decisions, or what worked last time. And throwing your company's junk drawer at them—docs, emails, wikis, PDFs—doesn't fix it. That's not knowledge; it's noise with an index. TPS Report is where you codify SOPs, how-tos, runbooks, and tutorials into structured knowledge bases—one source of truth your team reads and your agents execute.
How it works
2
Index into a graph
Scoped Graph RAG collections combine embeddings with codified graph signals and the Retrieval Contract.
3
Agents execute
Chat and agent workflows retrieve from your corpus—not the open web—routed to the right doc, every time.
4
Distill & improve
Runs capture what worked and what broke; you distill it back into the SOPs. The playbook compounds with use.
Why it beats generic RAG
Generic RAG embeds text and hopes for the best. TPS Report codifies knowledge so retrieval can route, defer, refuse, and respect access. One knowledge base, structured for both audiences: the reader and the agent.
Reasoning-grade retrieval
Hybrid graph + vector, prerequisite chains ("read this first"), and multi-hop traversal—not naive chunk search.
The Retrieval Contract
Every doc declares what it's for—and what it's not for. Enforced at authoring and sync, so agents never misfire.
Access control built in
RBAC on every report, section, and page—and agent retrieval obeys the same rules as readers. Monetize with it if you want.
A playbook that compounds
Runs write back raw learnings; a distillation pass promotes the keepers into your SOPs—reviewed, not accreted.
Structured & codified SOPs One source · two audiences The Retrieval Contract RBAC for humans & agents MCP native 100% online or Obsidian sync By Augmentable
Reachable wherever you work—browser-native, Obsidian sync, and MCP-native for any agent. See all features →
Proof, not promises
Retrieval you can audit — grounded, not guessed.
Every answer cites its source document, and the Retrieval Contract makes each doc's scope explicit—so you can see exactly why an agent retrieved what it did. Built on Augmentable's own stack: dogfooded, not demoed. No marquee-logo cosplay—real customer stories land here as we launch.
Who sees what is yours to control — RBAC on every report, section, and page, enforced for readers and agent retrieval. Want to monetize? The same access rules power a membership portal: public teasers, member unlocks, built-in signup. Browse sample reports →
Loading FAQs...
Go deeper
See exactly how it works
Features
Every capability, in detail
Reasoning-grade retrieval, the Retrieval Contract, MCP & Obsidian — and the full comparison.
Explore features → Use casesWho builds on TPS Report
Consultants, research teams, and KB builders — find the playbook that fits you.
Browse use cases → Reach it anywhereObsidian sync + MCP server
Author in your vault, expose your corpus to any MCP agent, and clip from the browser.
Get the plugins →Write it once. Read it. Run it.
Codify your SOPs, run agentic workflows on metadata-rich retrieval, and distill what every run teaches back into the playbook—online today, Obsidian when you want it.
SOPs humans read, agents run The Retrieval Contract MCP native · Obsidian optional
Prefer done-for-you? KnowOps builds it for you → Augmentable