DROPDOWN LOGISTICS · MODULAR BUSINESS OS
WorkBench
The modular business OS where every module shares one substrate.
Seventeen modules planned. One reference implementation ratified. The same star schema discipline that built AuditForge now powers a horizontal operating system for small businesses. The architecture doesn’t change. The data does.
THE ARCHITECTURAL SPRINT
Seven CRs. One weekend. One substrate.
Over 48 hours in April 2026, the WorkBench governance stack was ratified. One operator. One PM thread. Seven council reviews. The result: a complete architectural foundation for a 17-module business operating system.
CR-WB-CANON-001
Vocabulary ratified. Nine terms locked including PortableRecord, GovernedCohesion, AsymmetricTaxonomy.
CR-WB-FACTLAYER-001
Substrate ratified. Immutable event log + derived dimensions. 17 requirements. The floor everything else rests on.
CR-WB-CONNECTIVITY-001
Bring Your Data posture locked. HARD / SOFT / FORBIDDEN tiers for third-party data integration.
CR-WB-ANALYTICS-001
Three-stage analytics roadmap ratified. Starter Dashboards → Configurable Measures → Natural Language Query. STD-WB-MEASURE-001: 13 fields per measure.
CR-WB-MODULE-001
Module composition ratified. 19 requirements. Four contract categories. Manifest-driven architecture.
CR-WB-HRPEOPLE-001
Module 1 ratified. HR & People reference implementation. Build-ready spec.
CR-WB-MODBUILD-001
Module build procedure ratified. Six phases. Principles placement. Lean standards family.
Plus OBS-WB-PITFALLS-001 — the pitfall observatory, transitioned from CR to standing instrument at sprint close.
THE SUBSTRATE
One truth. Every module.
WorkBench’s FactLayer is an immutable event log with derived dimensions. Every module writes events. Every dashboard reads derived state. No measure drift. Full history preserved. Cross-module analytics work without retrofit — because the architecture never required one.
Immutable Event Log
Every action is an event. Events are never edited. The past is always recoverable.
Derived Dimensions
State is computed from events, not stored. Consistency is structural, not enforced.
Cross-Module Truth
headcount_total means the same thing in HR, in Capacity, and in Finance. One definition. Everywhere.
Ratified: CR-WB-FACTLAYER-001 · 17 requirements
CROSS-MODULE ANALYTICS
The same number. Every module.
Most business platforms bolt analytics on after the fact. WorkBench’s analytics layer is structural — it’s part of CR-WB-ANALYTICS-001, ratified before a single module was built. Every measure follows STD-WB-MEASURE-001: 13 fields, including definition, unit, aggregation, and cross-module tag.
MODULE
HR & People
MEASURE
headcount_total
12
Active employees, full-time equivalent
MODULE
Capacity Planning
MEASURE
headcount_total
12
Billable capacity denominator
MODULE
Finance
MEASURE
headcount_total
12
Cost per head baseline
Same measure. Same number. Same definition. Three modules. Zero configuration.
Ratified: CR-WB-ANALYTICS-001 + STD-WB-MEASURE-001
THE MODULE PATTERN
Every module. Same eight sections.
CR-WB-MODULE-001 defines 19 requirements for module composition across four contract categories. Every module in WorkBench follows the same eight-section pattern — Record, Categories, Substrate, Dashboards, Ledger Export, Connectivity, Deferred. Consistency is structural.
01Record
The primary entity the module manages.
02Categories
The taxonomy that organizes records.
03Substrate
How the module writes to the FactLayer.
04Dashboards
The pre-built analytics views for this module.
05Ledger Export
How records become portable Ledger Cards.
06Connectivity
HARD / SOFT / FORBIDDEN tiers for this module’s data.
07Deferred
What’s explicitly out of scope for V1.
08Build Phases
Six phases from schema to deployment.
Ratified: CR-WB-MODULE-001 · CR-WB-MODBUILD-001
MODULE 1 · REFERENCE IMPLEMENTATION
HR & People
RATIFIEDThe first WorkBench module, chosen for maximum architectural leverage. Every other module inherits the patterns HR & People proves out. Employees are the entity everything else references — capacity, payroll, utilization, scheduling, finance. Start here; everything compounds.
■Employee records with skill tokens and verified profiles
■Org structure — teams, managers, reporting lines
■Employment history with effective dating
■Compensation tracking (ranges, not amounts — privacy by default)
■Analytics: headcount, turnover, tenure distribution, team balance
■Ledger Card export: every employee gets a portable professional record
Ratified: CR-WB-HRPEOPLE-001
SEVENTEEN MODULES
The roadmap.
One substrate. Seventeen modules. Every module follows the same eight-section pattern. Every module shares the same analytics layer. The architecture is built once.
ControlsLIVE
TeamsLIVE
Time TrackingLIVE
AnalyticsLIVE
HR & PeopleTOUR
PayrollCOMING SOON
Capacity PlanningCOMING SOON
InvoicingCOMING SOON
AccountingCOMING SOON
ExpensesCOMING SOON
DocumentsCOMING SOON
SchedulingCOMING SOON
CRMCOMING SOON
ReportingCOMING SOON
IntegrationsCOMING SOON
Ledger CardsCOMING SOON
Client PortalCOMING SOON
OBS-WB-PITFALLS-001
We’re watching the failure modes.
Every modular business platform before WorkBench has failed in one of four ways. WorkBench’s substrate is built to avoid them. The Pitfalls Observatory is a standing instrument — not a one-time review.
Substrate Pitfalls
Schema decisions that make cross-module analytics impossible to retrofit.
Module Pitfalls
Composition choices that break the eight-section contract.
Commercialization Pitfalls
Pricing and access models that punish the wrong behavior.
Scaling Pitfalls
Architecture that works for one tenant and fails at one hundred.
The observatory is open. The substrate is built. The first wall is going up.
WorkBench · A Dropdown Logistics Product
Cathedral planned. Substrate ratified. First wall going up.
CHAOS → STRUCTURED → AUTOMATED