Skip to content

Read this first ​

Spec version: 1.2.0. Source: the owner's system overview, imported as v1.0.0. Changes are tracked in the spec changelog and follow Changing the spec.

This site replaces the Reroot Management overview as the plan to build from. It describes what shoot&grow-crew does, who uses it, and how it fits on the chosen stack. Read it once top to bottom, then use it as a map. Anything marked DECIDE is an open question for the owner; build the default stated next to it until it is answered. Every DECIDE is tracked in Open decisions and encoded as a setting, so answering one changes data, not code.

Ground rules ​

  • This is a new build, not a port of the Rust Reroot system. Nothing is shared with the old Rust server, its SQLite database or the Reroot app bridge. Ideas from the old plan are reused only where the spec says so.
  • Web only. The scaffold's apps/native (Expo) is on hold: do not build features there. It is excluded from dev, build and check-types until it is restarted. See ADR 0001.
  • UI is beUI, not shadcn. See ADR 0002 and UI and beUI.
  • Two inputs are still to come from the owner: the scraper/research guideline (Leads and research) and a more detailed description of the management screen (Dashboards). Leave clear seams for both.
  • Names. Product name: shoot&grow-crew. Package and folder slugs cannot safely contain & (npm scope names, URLs and some shells break on it), so the repo/package slug is shootgrow-crew and the workspace scope is @shootgrow/* (e.g. @shootgrow/ui). The & stays in the display name only. See ADR 0003.

Chapters ​

Chapter idWhat it covers
businessThe agency, the two plans, what the system is for
stackTechnology choices and Workers constraints
accessRoles, scope, public pages
calendarThe global calendar, event types, visibility
pipelineQR scan to Client Admin account, quotes, contracts, payment, sub-accounts
leads-researchLead page, statuses, research job
scheduleShoot-day anchor, generated events, script review
productionPremium production pipeline, review, annotation
dashboardsOwner, client, videographer, editor, sales dashboards
crew-payCrew contracts, pay, ledger, metrics
sales-plannerDay planner and commission
notifications-jobsEmail, notifications, background jobs
data-modelDrizzle/D1 sketch
rulesRules carried over, parked work
open-decisionsOwner decisions and the defaults being built
build-orderNine milestones
glossaryTerms

The chapter ids above are what the web app's planned screens link to (/spec/<id>), and what SpecChapter in apps/web/src/lib/spaces.ts enumerates. Renaming a chapter id is a breaking change to those links.

Internal documentation. Not for clients.