DocuSign

Build me a focused PDF editing, document workflows and electronic signatures workflow for the personal core of DocuSign. Requirements:

- Use Next.js 15, TypeScript, Python 3.12, FastAPI, pikepdf, LibreOffice headless, and PostgreSQL. Model source documents, editable pages or notes, internal links, revisions, and exports; retain source IDs and timestamps.
- Paid product context: Request a low-stakes signature with a transparent audit log and no legal-assurance claim. Build only this DIY scope: Request a low-stakes signature with a transparent audit log, preserve originals, generate auditable outputs, and keep files in a user-owned store without any legal-assurance claim.
- Keep every original immutable and write each operation to a versioned output file.
- Support merge, split, reorder, rotate, compress, watermark, redact, OCR, and Office-to-PDF conversion.
- Render page previews and warn when fonts, forms, signatures, or encryption may be altered. Add file expiry, download, deletion, backup, and a prominent low-stakes-use warning.
- Use a local web page with input, progress, review, and export views. Required input or access: Docker; LibreOffice headless.
- Recovery: On invalid input or interrupted processing, keep the original record, show the failed step, and permit a safe retry.
- Acceptance: with one labelled sample, show the input, saved intermediate state, and exported result; verify this invariant: An unsupported format must not be marked converted; the exported file must reopen and the original hash must remain unchanged.
- Out of scope: brand trust, identity options, global legal framework, integrations, and compliance; pixel-perfect proprietary PDF engine. Keep this a personal, inspectable workflow.
- Include a README with setup, a sample input, required keys or permissions, data location, and the supported scope.

# AGENTS.md — Build guide for DocuSign

## Project scope
Request a low-stakes signature with a transparent audit log, preserve originals, generate auditable outputs, and keep files in a user-owned store without any legal-assurance claim.

Catalogue verdict: no. A consolation build is possible, but the paid product's decisive value sits outside a solo rebuild. For DocuSign, request a low-stakes signature with a transparent audit log and no legal-assurance claim. The hard boundary is brand trust, identity options, global legal framework, integrations, and compliance, plus document fidelity, identity, and compliance.
Use the implementation prompt below to define the deliverable. Complete each phase's acceptance checks before extending the scope.

## Working agreement
- Inspect the repository and its existing instructions before choosing paths, dependencies or commands. Keep one coherent stack and explain changes to the proposed architecture.
- Plan a vertical slice that accepts a real input and produces the useful output described below. Persist only the state the prompt calls for; respect memory-only and upstream-managed workflows. Use fixtures only when they are clearly labelled.
- After scaffolding, document the actual install, development, check and build commands in README and keep them synchronized with the package or project manifest. Do not report commands as successful unless they ran.
- Work in small steps. At handoff, list implemented flows, checks actually performed, remaining blockers, and any credentials or provider setup the owner must supply.
- Do not publish, spend money, contact customers, delete source data or run irreversible migrations without the project owner's authorization.

## Prerequisites
- Docker
- PostgreSQL
- LibreOffice headless
- local or S3-compatible storage
- public HTTPS for signature links

## Stack and architecture
- Use Next.js 15, TypeScript, Python 3.12, FastAPI, pikepdf, LibreOffice headless, and PostgreSQL.
- Model source documents, editable pages or notes, internal links, revisions, and exports; retain source IDs and timestamps.
- Interface for this PDF editing, document workflows and electronic signatures workflow: a local web page with input, progress, review, and export views.

## Security and data integrity
- On invalid input or interrupted processing, keep the original record, show the failed step, and permit a safe retry.
- Validate imported records and file paths; keep user data within the storage location named in the prompt.
- State the practical limit: brand trust, identity options, global legal framework, integrations, and compliance.

## Agent implementation rules
- Project rule, data: Model source documents, editable pages or notes, internal links, revisions, and exports; retain source IDs and timestamps.
- Project rule, behavior: Keep every original immutable and write each operation to a versioned output file.
- Project rule, recovery: On invalid input or interrupted processing, keep the original record, show the failed step, and permit a safe retry.

## Optional agent skills and references
No installable skill is listed for this guide; use the project rules and the stack documentation.

Read the linked SKILL.md and its dependencies before adding a skill. Select only the skills matching this project's runtime and task; their documentation does not supply API access, credentials or approval to perform external actions. Pin the reviewed revision where the tool supports it. Follow the chosen agent's documented project-level installation mechanism.

## Distribution ideas
These are optional planning notes. Obtain the owner's approval before publishing or contacting anyone.
- Demonstrate this PDF editing, document workflows and electronic signatures operation with sample or user-owned data: Keep every original immutable and write each operation to a versioned output file.
- Show a concrete result or export: Keep every original immutable and write each operation to a versioned output file.
- State the practical limit: brand trust, identity options, global legal framework, integrations, and compliance.

## Engineering roadmap
1. Phase 1, architecture and data: Use Next.js 15, TypeScript, Python 3.12, FastAPI, pikepdf, LibreOffice headless, and PostgreSQL. Model source documents, editable pages or notes, internal links, revisions, and exports; retain source IDs and timestamps.
2. Phase 2, implement: Keep every original immutable and write each operation to a versioned output file.
3. Phase 3, implement: Support merge, split, reorder, rotate, compress, watermark, redact, OCR, and Office-to-PDF conversion.
4. Phase 4, review and output: Render page previews and warn when fonts, forms, signatures, or encryption may be altered. Keep every original immutable and write each operation to a versioned output file.
5. Phase 5, recovery and acceptance: On invalid input or interrupted processing, keep the original record, show the failed step, and permit a safe retry. Verify this invariant with a saved fixture: An unsupported format must not be marked converted; the exported file must reopen and the original hash must remain unchanged. State the practical limit: brand trust, identity options, global legal framework, integrations, and compliance.

## Paid-product capabilities outside this build
- brand trust, identity options, global legal framework, integrations, and compliance
- pixel-perfect proprietary PDF engine
- identity verification
- qualified trust services
- large template and integration ecosystem

## Implementation prompt
Build me a focused PDF editing, document workflows and electronic signatures workflow for the personal core of DocuSign. Requirements:

- Use Next.js 15, TypeScript, Python 3.12, FastAPI, pikepdf, LibreOffice headless, and PostgreSQL. Model source documents, editable pages or notes, internal links, revisions, and exports; retain source IDs and timestamps.
- Paid product context: Request a low-stakes signature with a transparent audit log and no legal-assurance claim. Build only this DIY scope: Request a low-stakes signature with a transparent audit log, preserve originals, generate auditable outputs, and keep files in a user-owned store without any legal-assurance claim.
- Keep every original immutable and write each operation to a versioned output file.
- Support merge, split, reorder, rotate, compress, watermark, redact, OCR, and Office-to-PDF conversion.
- Render page previews and warn when fonts, forms, signatures, or encryption may be altered. Add file expiry, download, deletion, backup, and a prominent low-stakes-use warning.
- Use a local web page with input, progress, review, and export views. Required input or access: Docker; LibreOffice headless.
- Recovery: On invalid input or interrupted processing, keep the original record, show the failed step, and permit a safe retry.
- Acceptance: with one labelled sample, show the input, saved intermediate state, and exported result; verify this invariant: An unsupported format must not be marked converted; the exported file must reopen and the original hash must remain unchanged.
- Out of scope: brand trust, identity options, global legal framework, integrations, and compliance; pixel-perfect proprietary PDF engine. Keep this a personal, inspectable workflow.
- Include a README with setup, a sample input, required keys or permissions, data location, and the supported scope.

## Completion evidence
Demonstrate the prompt's acceptance scenarios against the scoped workflow. Include setup from a clean checkout and failure recovery. Check persistence across restart and export/restore only for the state the prompt says to store; for memory-only tools, confirm that temporary content is discarded as specified. Record actual results and remaining limitations. A detailed plan alone does not establish a working replacement.