Rules your agents follow. Pull requests that prove it.

01 / Pull request gate

Every pull request is checked against your business rules.

Before a change ships, Doclific reads the pull request and compares it to the rules that govern that code. It reports directly on the PR, in plain language. Silence is never the answer.

• Three clear outcomes

  The docs still match this change, they need your answer, or they look out of date. You always get one of those — never silence.

• Asks instead of assuming

  When code and policy disagree, Doclific asks on the pull request. It does not rewrite the rule, and it does not guess.

• One reply updates the record

  Answer in the thread and the rule updates in place, attributed to you and the pull request it came from.

• Only what you connect

  Draft pull requests are left alone. Unconnected repositories are not reviewed. You decide what the gate sees.

02 / Knowledge base

One private source of truth for why your software does what it does.

Business rules, requirements, decisions, exceptions, integrations — written in plain language, private to your organization, and never written into your repos.

• Tied to the code that enforces it

  Every rule points at the exact files — across every connected repository — that implement it. When that code moves, you know.

• You always know who confirmed it

  Each rule records who confirmed it and where — in chat, on a pull request, or from an agent. Authorship stays attached.

• Connected, not scattered

  Rules link to what clarifies them, what supersedes them, and what contradicts them. Related policy lives together.

• Browse it. Never maintain it.

  There is no editor and no wiki to keep current. You read the library and talk to it. The record writes itself.

03 / Coding agents

Agents get the rule, not a dump of your docs.

Cursor, Claude Code, Codex, VS Code — or any MCP-compatible agent — asks Doclific and gets the specific rule that applies, with its reason and who confirmed it.

• The rule, not the library

  Agents ask a question and get the specific rule that applies — with its reason and who confirmed it. Not a dump of your docs.

• Agents contribute what they learn

  When an agent discovers something worth keeping, it files it. Doclific decides where it belongs. The caller never picks the document.

• Access you control

  Each person connects their own tools. Revoke access in one click. When a member leaves, their access ends with them.

04 / Keeping it current

No wiki to maintain. Just say what changed.

There is no editor and no save button. Ask in chat, answer on a pull request, or let your agents file what they learn — the record updates in place, attributed to whoever confirmed it.

05 / Start with a full draft

A first draft of your whole system, in one run.

On Premium, an admin can have Doclific read every connected repository and draft the architecture, flows, and contracts it finds — each tied to the code. It never deletes anything you've written, and re-running it extends the draft instead of duplicating it.

06 / Built for teams

Private, recoverable, and yours.

• Roll back

  Premium keeps a weekly copy of the library for 12 weeks. Admins can restore any of them.

• Private to your organization

  The library is yours. There is no public catalog and no anonymous read.

• Access you can revoke

  Each person connects their own tools. Revoke or rotate access any time. When a member leaves, theirs ends.

• A record of every change

  Writes, members, GitHub, billing, and restores are logged on every plan. Export the audit log on Enterprise.

• Predictable spend

  Included usage each month. Optional overage with a spend cap you set. No surprise bills.

07 / Roadmap

GitHub today. GitLab and Bitbucket next.

After that: the option to block a merge on a rule you've marked non-negotiable, and a visual map of how your rules relate.