Comprehensive documentation for Paprwork V2 - AI-powered desktop assistant.
System architecture, design decisions, and technical specifications.
Files:
SYSTEM_OVERVIEW.md- High-level system architectureCORE_LIBRARY.md- Shared core library designGATEWAY_ARCHITECTURE.md- Gateway process architectureIPC_PROTOCOL.md- Inter-process communication designDATA_FLOW.md- How data flows through the system
User and developer guides for getting started and working with the system.
Files:
GETTING_STARTED.md- Quick start guideDEVELOPMENT_SETUP.md- Dev environment setupBUILDING_TOOLS.md- How to create custom toolsTESTING_GUIDE.md- How to write and run testsDEPLOYMENT.md- How to build and distribute
API references and specifications.
Files:
CORE_API.md- Core library API referenceIPC_API.md- IPC methods and channelsTOOL_API.md- Tool creation APISTREAMING_API.md- Streaming protocol
Implementation details for completed features.
Files:
- Will be added as features are implemented
- One file per major feature
- Includes rationale, approach, and lessons learned
Ideas for future improvements and enhancements.
Files:
- Will be added as we identify improvement opportunities
- Tracks potential optimizations and new features
- Read GETTING_STARTED.md
- Review SYSTEM_OVERVIEW.md
- Check DEVELOPMENT_SETUP.md
- See CLAUDE.md for project context
- Read BUILDING_TOOLS.md
- Check TOOL_API.md
- See example tools in
src/core/tools/
- Start with SYSTEM_OVERVIEW.md
- Read CORE_LIBRARY.md
- Understand GATEWAY_ARCHITECTURE.md
- Review DATA_FLOW.md
- Use clear, concise language
- Include code examples where relevant
- Keep files focused on one topic
- Update docs when code changes
- Use UPPERCASE for major docs (README.md, CLAUDE.md)
- Use UPPERCASE_WITH_UNDERSCORES for doc files
- Use clear, descriptive names
- Use proper heading hierarchy (# → ## → ###)
- Include table of contents for long docs
- Use code fences with language tags
- Add images/diagrams where helpful
When to update documentation:
- Adding new features → Update relevant API docs
- Changing architecture → Update architecture docs
- Fixing bugs → Update troubleshooting guides
- Making decisions → Update CLAUDE.md
Who updates docs:
- Developers update API/implementation docs
- Architects update architecture docs
- Project leads update CLAUDE.md and plans
- CLAUDE.md - Project context and learnings
- PLAN.md - Implementation timeline
- README.md - Project overview
- /plans - Detailed feature plans and specifications
- /src/core - Core library with inline documentation
- /src/main - Main process implementation
- /src/gateway - Gateway process implementation
- Write SYSTEM_OVERVIEW.md
- Write CORE_LIBRARY.md
- Write GATEWAY_ARCHITECTURE.md
- Write GETTING_STARTED.md
- Write DEVELOPMENT_SETUP.md
- Write BUILDING_TOOLS.md
- Write IPC_API.md
Last Updated: 2026-02-09