Part 1: Use OPCC with your data | Install | Key concepts | Normalize postal codes | Look up a single postal code | Join OPCC geographies to your own data | Download and cache artifacts | Verify a release | Offline and air-gapped use | Source-qualified point lookups | Import your own open evidence locally | Part 2: Reproduce and verify artifacts | Verify published artifacts | Reproduce the DA artifact from the DB artifact | Reproduce offline | Rebuild all artifacts from raw sources

The promise | The privacy gating ladder | 1. Entry attestation: direct identifiers | 2. Upload | 3. Early soft fail-safe | 4. Objective | 5. Configure: two questions per column | 6. Synthesis enforcement | 7. Compare plus privacy report | 8. Export | What the two questions reinforce | Short glossary | Worked k-anonymity examples from the built-in samples | individual_sample (200 x 7) | temporal_sample (365 x 5) | geographic_sample (50 x 5) | Using it with AI | Hand off the synthetic bundle | Trusted reruns and new variants | The no-network guarantee | Lock 1: no network code | Lock 2: nothing is persisted | How it is proven | Verify it yourself offline | Supply-chain note

Installation | Step 1 — Discover Your R Installations | Platform detection | CLI Workflow | Step 2 — Scan a library with manifest() | Step 3 — Compare two libraries with inventory() | Step 4 — Migrate with ship() | Always dry-run first | Include version upgrades | Check results | Migrate GitHub and Bioconductor packages | Transfer modes | Why copy modes need the same R x.y series | Common Recipes | One-way migration (old R → new R) | Mirror two same-version installs | Inspect before migrating | Save a manifest to disk | Dashboard | Bulk Dispatch | Custom Dispatch | Tips

Test suite overview | Running tests | 1. Unit + integration tests (standard) | 2. E2E browser tests | 3. Manual Shiny UI checklist | Bulk Dispatch | Custom Dispatch | Error reporter | CLI | Platform test status | Windows notes | Linux notes | macOS notes | Adding tests