Skip to content

Roadmap ​

New ideas go here, not into the change in hand. An idea becomes work when it is moved into the spec (Changing the spec) or into a numbered step below.

Step 1: Foundation, done ​

Everything step 1 asked for is built. How each item was settled, so the next person does not look for the wrong thing:

  • [x] Bootstrap the first owner account. Not a one-off script: the owner seat is created and reconciled from the OWNER_PASSWORD deploy secret on every start (packages/auth/src/admin.ts). There is no HTTP path that creates an owner, no sign-up, and the admin plugin's create-user is owner-only, so nothing can be used once an owner exists. Because the secret is the source of truth, the owner changes their password by changing the secret and redeploying; a password changed in the app would be put back at the next start. The forgot-password flow skips the owner for the same reason.
  • [x] Sign-in policy. user.mustChangePassword is set when the owner creates a login or sets its password and cleared when the person chooses their own (/security). Client Admins must set up an authenticator app (setting access.requireClientAdminTwoFactor, on by default) before the client area opens. The server refuses every procedure but v1.me.policy until both are done (packages/api/src/sign-in-policy.ts). /login has the code and backup-code challenge, and /forgot emails a single-use link (reset_password) that reuses /p/pw.
  • [x] Settings service. v1.settings (owner only) reads through resolveEffective, writes a revision and an audit_log row in one batch; the Settings screen is under /owner/settings.
  • [x] Template service. Create draft, edit draft, publish (content_hash), retire, owner only, audited (packages/api/src/template-writes.ts); quotes freeze the published package.
  • [x] Audit helper. packages/api/src/audit.ts holds the one audit row (auditValues) with audit and auditStatement; auditRow (leads-views) and auditInsert (money) build their rows through it.
  • [x] Notifications and email. Tables, the outbox with idempotency keys, templates including reset_password, and the sender. The sender is Cloudflare Email Service, not Resend.
  • [x] Read auth limits from settings at request time. packages/auth/src/limits.ts reads the current value; a hook enforces access.passwordMinLength on change, reset and owner-set passwords, and membershipLimit is a function.
  • [x] Client Admin or member in the procedure. clientScope(db, actor).kind loads it when a procedure needs "is this the Client Admin?" (ADR 0007).
  • [x] Host the docs site. docs is a static site in the Alchemy stack (packages/infra/alchemy.run.ts) and its URL is the web app's VITE_DOCS_URL.
  • [x] Rename the working directory shoot&grow/ to shootgrow-crew/.
  • [x] apps/native. Decided to stay parked (ADR 0001); its files still use the old & names and are restored only when a native app is wanted.

Later steps ​

See Build order. Steps 2 to 8 are built (calendar, sales planner, intake, quotes and contracts with Stripe, content, production, crew pay). Step 9, the management screen refined with the owner's brief, is deferred by decision until the brief exists.

Also deferred by decision: a live deploy of the stack (the docs site hosting is written and type-checked, not yet run against Cloudflare), and restoring apps/native.

Parked ideas ​

From the spec's parked list: native app, Reroot bridge, AI assistant, ads management, comment scraping, business map, automated post metrics, Google sign-in for clients, Google Drive, voice/auto-dialling, bank holidays in date maths.

Additional ideas raised while setting up (not accepted):

  • Per-user iCal feed (the spec lists it as "optional later").
  • Cloudflare Workflows for multi-step jobs (conversion, pay runs) if Queues plus sweeps get awkward.
  • A review/approval state for settings changes, like templates have.
  • Per-environment feature flags if a half-built feature must ship dark.

Research follow-ups ​

  • [ ] Run research automatically on lead creation (step 4) and on client conversion (step 5); today a person presses the button.
  • [ ] Let a salesperson research their own leads (access rule with the lead tables).
  • [ ] Verify the BROWSER binding and the production API-key path on a real deploy (only the dev bridge path has been run end to end).
  • [ ] Re-run on a schedule for active clients; show what changed between briefs.
  • [ ] A metrics source for real follower and view counts, so figures need not be dropped.
  • [ ] Use the brief to prefill the client's content pillars and persona (Reroot did this; the spec does not ask for it yet).

Internal documentation. Not for clients.