Generated docs

Invince reads the connected repository (code, routes, structure) and writes documentation grounded in that, not generic filler.

Each built-in page has two layers:

• Confirmed: tables and lists extracted from the repo (routes, HTTP methods, env var names, package scripts, schema, handler excerpts). This is not invented.
• Inferred: a handbook-style write-up from those facts only. If a command, host, or endpoint is not in the facts, the model is told to say it is missing instead of guessing.

Connect GitHub, sync the project, then open Documentation.

Software document pack

Open Software documents in the project sidebar. You get a checklist of 20 already-written full guides (overview, getting started, architecture, API, data model, auth, env, runbook, and so on).

• Generating does not call Gemini and does not spend shared AI quota.
• Invince fills the template from the connected GitHub repo and the project live URL / public Check, so you do not have to piece the code and the site together yourself.
• Missing evidence stays “not in the extracted evidence.”
• Usage for Ask AI and investigations is on Workspace settings (you do not have to open AI Provider just to see the count).
• Free keeps 4 of these per app, Pro 12, Business 20. Export as PDF or Word from the generated page.

Edit the inferred prose when you know something the extractors cannot see. Sparse repos get short docs. That is preferable to a fluent page about a feature you never shipped.

Drift

When a commit changes facts those pages were generated from, Invince flags the pages. Drift can make the launch gate say Fix first. Regenerating or accepting the new facts clears it.

Your coding agent

Invince can file a GitHub issue with a doccraft:fix-me label. Your Cursor, Claude Code, or Copilot agent then fixes your repo with your credentials. See MCP.