Private Vault

Public front. Private control room.

Git is the version history for the app, public pages, templates, prompt packs, and sanitized research. The vault is where private records, client files, approvals, and audit logs live behind owner login and scoped permissions.

Git Layer

Best for public site code, pages, templates, playbooks, sanitized notes, rollback history, and reviewable diffs.

D1 / SQL Layer

Best for accounts, staff, settings, bookings, watch rules, approval cards, audit rows, and searchable private metadata.

Private Files

Best for uploads, discovery files, contracts, PDFs, intake packets, photos, exports, and anything too sensitive for public content.

Lawyer Safe Pattern

Do use GitWebsite text, non-confidential templates, standard operating procedures, prompt packs, public research pages, and sanitized examples.

Do not use GitRaw client facts, privileged communications, IDs, medical records, evidence, discovery, private strategy, or passwords.

Use the vaultStore private item records in SQL, put large/private documents in protected storage, require login, and write an audit row for every create, view, update, export, or delete.

Git Recall

Use Git for recallArticles, public case studies, showcases, SEO pages, FAQs, templates, prompt packs, training notes, and code snippets can be stored in Git so AI can pull them fast.

Ask in plain text

pull the article about spring cycles
show the case where rank dropped
find my NAP checklist
commit this FAQ update

Keep vault separateGit is for public or sanitized memory. Private files stay behind login in D1/R2/private storage with audit logs.

API Shape

GET  /api/bookitnow/vault/items
POST /api/bookitnow/vault/items

{
  "title": "Matter timeline notes",
  "item_type": "case_note",
  "visibility": "private",
  "storage_ref": "r2://client-vault/...",
  "notes": "Sanitized summary only"
}

The live API is gated by the BookITnow session cookie. Owners only see their business. Admin can select a business. This gives Git-style history plus a real private data boundary.