A clear path
to your workspace.

Review unused starter additions for removal in Starter setup before removing the frontend. Server checks preserve edited or published workflows and pipelines with jobs or references. The process targets recorded kit additions rather than sweeping account records.

Preserve your local configuration and source edits. Preview frontend removal with node setup.mjs remove "/path/to/seedly" --dry-run. The automatic uninstaller uses a private restoration receipt and refuses to overwrite later edits. Keep that receipt private and out of public hosting or source exports. Removing frontend files does not remove account data or undeploy backend functions.

For an update, follow the documented removal/install process and reapply your preserved changes. A manually merged installation needs its own private change ledger and reviewed source rollback.

A job is a native contact-linked opportunity with a namespaced job type, site address label, crew label, cubic yards reference, mix label, a forms set flag, planned and actual pour dates, recorded cure days, a derived cure complete date, finish label, job notes, an immutable supported currency, inspection records with their result and inspector label, and weather hold records with their dates and reason. The recorded contract reference stays separate from native opportunity value. Other custom fields are preserved.

Every date is one somebody wrote down, and the one derived value is arithmetic on two of them. The recorded pour date is the actual pour when one is recorded and the planned pour otherwise, because the cure starts when the concrete goes down. The cure complete date must equal that date advanced by the recorded cure days and must be blank when either is missing; the editor recomputes it on every edit and the server refuses a stored value that disagrees, so the board can never contradict the sheet. Cure days are calendar days from a specification or a superintendent, never a strength calculation, maturity index or cylinder break. Because nobody pours into ground with no forms around it, a recorded actual pour requires forms recorded as set, and cure days or a crew label require a recorded pour date. A passed or failed inspection requires a recorded date while a pending one may leave it blank, and an inspection date is deliberately not constrained against the pour, because forms inspections happen before it and final inspections after it. A weather hold needs both dates in order plus a reason, and two holds on one job may overlap because rain on Monday and a freeze warning on Tuesday are separate facts. The pass rate excludes pending rows from both halves and reports None recorded rather than an invented zero. There is no weather data, forecast feed or radar, no permit system or municipal inspection scheduling, no ready-mix ordering or delivery ticket, no estimating or takeoff, no crew scheduling engine or dispatch, and no invoicing or payments. Nothing here contacts a client, an inspector or a supplier. Totals are grouped by currency and never added across currencies. The pipeline stage stays your CRM’s own: recording a pour never moves a card, and moving a card never records a pour.

The kit’s original operational screens share the frame with full CRM modules from your own Seedly source. Existing account permissions, feature gates, and configured providers still determine access to those modules.