One front door for the Dixieland system.

OS keeps the module map, shared theme, and handoffs together while each app stays cleanly owned by its own repository.

Front door

Routes users into the right source module.

Lee binder workflow

Scheduler

Links schedule items to Jobflow job packets.

System of record

JobFlow

Receives scheduled work and returns packet/billing status.

Modules

The launch cards are backed by the OS module registry, so hostname, repo, and ownership stay in one place.

Secure launch point, module registry, shared navigation, and cross-module status.

StatusActive shell

BoundaryFront door

Hostnameos.dixieland.ctsolutions.dev

Lee's Binder, scheduling queue, crew staging, Scheduled, Print & Email, and intake.

StatusPrototype ready

BoundaryLee binder workflow

Hostnamescheduler.dixieland.ctsolutions.dev

Jobs, customers, materials, POs, invoices, inspections, daily records, billing, and migration.

StatusFoundation branch

BoundarySystem of record

Hostnamejobflow.dixieland.ctsolutions.dev

Start in OS

OS carries the suite map, shared theme, and module entry points.

Schedule the work

Scheduler owns Lee's binder, queue, crew staging, and print/email workflow.

Run the job packet

JobFlow owns the durable job record, billing, purchasing, inspections, and audit trail.

Theme source

OS owns base tokens. Modules specialize only module accents and domain colors.

Module boundary

Scheduler keeps scheduling. JobFlow keeps durable job records.

Module	Owns
OSShared operating layer	Identity context, navigation, module health, theme tokens
SchedulerScheduling module	Queue placement, work-type colors, crew schedule staging
JobFlowJob lifecycle module	Master Job Sheet, billing, purchasing, inspections, audit trail
PublicPublic web presence	Public content, public visual precedent, customer-facing brand