Internal draft

KarpatiLaw image review + systems notes

Kept simple on purpose: a presentable image carousel first, then the operating notes underneath.

Build stamp: HTML 2026-06-27 23:46:24 UTC · styles 2026-06-27 23:42:32 UTC · carousel CSS 2026-06-27 23:43:39 UTC · JS 2026-06-27 23:33:06 UTC

Carousel

Images to review

Accounts

Google account direction

  • Services should center on one primary Google account.
  • Nathalie account: nathalie@karpati.com.
  • Second seat is currently believed to be help@karpatilaw.com.
  • That shared seat should be usable by Marvin.

Access

Auth / recovery risk

  • MFA and recovery may currently depend on Nathalie's phone, Marvin's phone, or both.
  • This needs to be mapped before account cleanup work.

Infrastructure

Office systems direction

  • Shared-records planning is still open.
  • Possible office NAS in Nathalie's office.
  • Possible dedicated node in the office as well.
  • Longer term, app writes may need to flow into the same target the Google Form uses today.

Next steps

What to pin down next

  1. Confirm the actual shared-seat email and account owner.
  2. Write down which phones are tied to MFA and recovery.
  3. Decide whether Marvin should use the shared account directly or through a cleaner admin setup.
  4. Decide whether shared records should live first in Google, on the future NAS, or in both.