Help center
PR to article
Product change becomes a help article. A docs job.
[code to docs]
Code-to-docs turns a pull request into an article. Oppulence turns a role into a reviewable workflow.
Code-to-docs agents draft help articles from merges. Oppulence models prompts, tools, and action boundaries before an agent can write to a customer system.
Free first reportApproval before anything leavesNo invented case studies
[definition]
What “code to docs” actually means
Code to docs is the Ferndesk move: a PR merges, an article is drafted. Oppulence does not watch your repo to write help. This leftover slug is workflow design — roles, MCP, simulations, and the same approval boundary as everything else.
Three jobs that are not the same.
Reviewable
Agent workflow
A definition you can inspect: tools, prompts, who it may write to.
Not a promise
Money-moving MCP
The managed registry can list finance scopes. That is not a production claim.
[for]
This page is for you if
- You already write promises in mail, Slack, and calls, and they disappear.
- You want a register with sources, not another place to type notes.
- Customer-facing sends should wait for a person.
[not for]
This is the wrong page if
- You need a public help center, article CMS, or ticketing inbox. That is a different product.
- You want a bot that sends as you without approval.
- You want a wall of logos and invented time-saved numbers. We will not publish those.
Questions this URL actually answers
The leftover slug is a search path. The answers stay honest about the product.
No. Connect the repo as an MCP tool if you want the desktop agent to call it. That is not a help-center publisher.
