PDF generation and distribution

Access boundary: Current capability and authority required.

Implemented; generation, preparation, approval and delivery remain separate.

Surfaces: Web, REST and MCP; generation is separate from distribution and delivery.

Read the engineering guide · All features

Capabilities

1. Single PDF from a business form
2. PDF batch from a validated mapping
3. Progress, per-record results and source-cell provenance
4. Generation cancellation and retry of failed records only
5. PDF selection and separate distribution-plan preparation
6. The first plan permanently freezes the full batch, including excluded failed records; prepare_distribution declares destructiveHint true
7. Common recipient or frozen columns with an explicit channel per record
8. Resume remaining entries without duplication
9. Entry-linked postal preflight with separate review and sending
10. Known assistant-excluded content is never generated, previewed, shared or distributed; request a person-redacted version and never treat scanning as proof of absence

REST operations

• GET /api/generation-jobs
• POST /api/generation-jobs
• GET /api/generation-jobs/{id}
• GET /api/generation-jobs/{id}/results
• GET /api/generation-jobs/{id}/provenance
• POST /api/generation-jobs/{id}/cancel
• POST /api/generation-jobs/{id}/retry
• POST /api/distribution-plans
• POST /api/distribution-plans/{id}/resume
• POST /api/distribution-plans/{id}/entries/{entryId}/postal-preflight
• GET /api/distribution-plans/{id}

Read the REST integration guide for authentication, errors and contract discovery.

MCP tools

• cancel_generation_job
• create_distribution_postal_preflight
• generate_documents
• get_distribution_plan
• get_generation_job
• get_generation_provenance
• get_generation_results
• list_generation_jobs
• prepare_distribution
• resume_distribution
• retry_generation_records

Read the MCP integration guide for scope, approval and host boundaries.