Users and Use Cases¶
Last verified: 2026-07-26 against current checkout c09254f.
This page describes product-facing roles. Exact org and API behavior is covered in Tenancy and permissions.
User Groups¶
| User group | What they need |
|---|---|
| Solution builder | Configure a client-specific document solution quickly using reusable engine, tool, and UI primitives. |
| Template author | Define sections, fields, data needs, prompts, render modes, examples, and template specs. |
| End reviewer | Review generated sections, inspect sources, edit or regenerate content, and export final output. |
| Delivery engineer | Seed orgs, wire tools/MCP servers, configure secrets, run tests, and deploy a client solution. |
| Product/demo operator | Run the DocGen demo app and show multiple seeded solution examples. |
| Platform engineer | Maintain auth, observability, library enforcement, submodules, and deployment posture. |
| Evaluator | Compare generated output against gold/demo expectations and document quality findings. |
Core Use Cases¶
Author a New Template¶
A template author creates a template spec, dry-runs it through /v1, applies
it, stamps an instance, generates output, and exports the result.
Relevant docs:
Onboard a Client Solution¶
A solution builder decides whether the use case fits DocGen, creates solution docs and specs, wires tools/data sources, seeds the org, and validates the generated output.
Relevant docs:
Wire Data Sources¶
A delivery engineer connects deterministic tools or MCP servers so the gather phase can collect the facts that the document needs.
Relevant docs:
Operate a Demo or Seeded Org¶
An operator rebuilds the database, seeds configured org specs, verifies the demo app, and confirms the configured org can generate its documents.
Relevant docs:
Understand a Release or Solution Decision¶
A reviewer reads the durable design/project records that explain why a release, solution, or architectural choice exists.
Relevant docs: