Papers

Coding agents: start with HERMES.md and read it completely before changing Papers or proposing product behavior.

Papers is a personal layer across Windows. Its authoritative product definition is docs/PRODUCT.md; current implementation and historical projects are not substitutes for that definition.

Documentation map

Start here

• Mandatory agent pickup and creator contract

Product authority

• Product definition
• Chronological creator-accepted decisions

Current use, work and acceptance

• User guide
• Acceptance status
• Creator-reported problems

Current implementation, data and releases

• Architecture boundary
• Projects created for Papers use
• Syncthing and evolving data
• How Papers updates itself
• Hermes skin integration and updates
• Hermes skin specification

Historical evidence and engineering fixtures

• Hermes batch implementation handoff
• Legacy program fixture contract
• Hermes batch evidence

Historical material records what happened. It does not define future Backpack contents or authorize the return of superseded product architecture.

Repository checks

npm install
npm run typecheck
npm test
npm run build

Release, installation, termination and restart require separate creator authorization. When a release is explicitly requested, follow How Papers updates itself.

Set PAPERS_ENABLE_FIXTURES=1 only when exercising the historical program and ACP integration suites.