Sabel Customer Success · internal SALES PIPELINE →

Sabel OS. system map

The business operating system: sources flow in hourly, land in one folder structure, get routed through four function pillars, and automation loops turn them into deliverables. Click any node for detail; click a model step to highlight its layer.
BASEfolder structure
UPLOADmanual intake
INFLOWauto data feeds
LOOPscheduled agents
DRIVEdeliverables out
01 · INFLOWSourceswhat the OS reads, mostly on its own schedule
▼ ▼ ▼
02 · BASEThe store — ~/sabel/raw is untouched truth; wiki points at raw
▼ ▼ ▼
03 · ROUTERFour pillarsCLAUDE.md routes every task by intent → pillar page → skill
▼ ▼ ▼
04 · LOOPAutomation loopsgreen = running on a schedule now · amber = built, you schedule it
▼ ▼ ▼
05 · DRIVEOutputswhat actually leaves the system — always human-gated when client-facing
hover a loop → its sources and outputs light up · click → detail