AN ORGANIZING COLLECTIVE // OPEN SOURCE & SOVEREIGN

The Collective.

The Collective brings together the enterprise agentic systems I am building and an invitation to develop them with other practitioners.

Every human operator can now be their own software factory. The Rig couples an experienced operator with agentic build harnesses to map, fabricate, and run systems that match how an enterprise actually functions.

Software is not a static purchase or a rented seat. It is an org-instance structure with a continuous learning loop. Authoritative orgs map domain truth and execute operations, while firm instances run the daily work.

What works today: deterministic developer harnesses running on local iron, structured schema boundaries that isolate sensitive ledgers, and verified workflow blocks.

What we are developing: open pattern sharing across sovereign orgs, composable multi-seat collaboration, and severable enterprise architectures that reduce recurring vendor lock-in.

We are not claiming we have it all figured out. This is the seed. We are pulling the pieces together, and we are looking for passionate builders to join the collective. I am sharing the architecture, the runtimes, and the harnesses so we can collaborate, build open patterns, and create something durable together.

ARCHITECTURE SPECIFICATION // SPEC-COL-01
SOVEREIGN NODE • PATTERN COMMONS
SOVEREIGN HUMAN FACTORY // PRIVATE IRONPrivate Iron • Sovereign & SeverableSPEC // SPEC-COL-01SCHEMAS ↙INTENT ↓VERIFIED →→ RUNTIME↖ FEEDBACKB.O.S.S.01 // DOMAIN TRUTHUnwritten Operating RealityFrontline heuristics codified into deterministic schemasTHE RIG02 // SOFTWARE FACTORYAutonomous Build & ProofDeterministic fabrication verified against caller test gatesFLOWCRAFT03 // AGENTIC RUNTIMELive Execution & StateHuman + agent workflows orchestrating existing ledgersIntent = OutcomeSHIPPEDDeterministic ProofVERIFIED RUNTIMESHARE PATTERNS ↓Zero Private Data↑ PULL PATTERNSPre-Verified Blocks & HarnessesTHE COLLECTIVE PATTERN COMMONS // PEER BUILDER EXCHANGE (OPEN SOURCE)OPEN SOURCE • ANONYMIZED PATTERNS • ZEROS AND ONES01 // DOMAIN SCHEMASOperational InvariantsTolerances, price limits & inventory balance rulesSPEC // B.O.S.S.02 // WORKFLOW BLOCKSComposable WFBsQuickBooks, ERP connectors & dispatch state machinesRUNTIME // FLOWCRAFT03 // TEST HARNESSESCaller FixturesMulti-agent verification suites & edge-case test gatesFACTORY // THE RIG
Org-Instance Sovereignty & Built-In Factory: The Rig creates the org-instance structure. B.O.S.S. and FlowCraft each hold an authoritative org and spawn as many firm instances as needed. Each org is designed with built-in development harnesses—architected to be severable and runnable on private iron to minimize vendor dependencies.
The Workflow Block Network Effect: The patterns are driven through composable workflow blocks (WFBs). When connected to The Collective, workflow blocks updated in one org flow through to the other, through The Rig. The collective library compounds while private data and ledgers remain within your operational boundary.

THE WORKING CONTRAPTION // THREE INTERLOCKING SYSTEMS

How the systems work together.

To make a collective work in practice, you need a deterministic stack. Three systems designed to work together, grounding twenty years of plant-floor operating experience into modern agentic runtimes.

DOMAIN TRUTH • SPECIFICATION (ORG)

B.O.S.S.

Business Operating System Specification

Every business runs on unwritten plant-floor judgment, Mary’s edge-case scheduling spreadsheet, and thirty years of experience that never made it into the software manual. B.O.S.S. is the authoritative specification org that maps and digitally twins that domain truth—capturing business rules, exception boundaries, and operational invariants into clear, machine-actionable schemas. An enterprise can take a B.O.S.S. org and run it entirely on their own private iron; it carries its own built-in factory inside.

HOW IT IS USED

Domain mapping & specification. Turns tacit human heuristics into unambiguous schemas so agents understand real operating constraints before touching anything.

OPERATIONAL RUNTIME • ORG & INSTANCES

FlowCraft

Workflow Operating System

The live operational runtime. FlowCraft structures execution across an authoritative org and as many running firm instances as the business requires. It bridges existing systems, databases, and autonomous agent swarms—composing named workflow blocks into isolated, severable companies that actually run, with shared Master Data (MDM), live permissions, state machines, and complete audit trails.

HOW IT IS USED

Live execution across instances. Runs composable workflow blocks around ledgers like QuickBooks or ERPs, keeping humans in authorization command.

SOFTWARE FACTORY • BUILDS THE MACHINES

The Rig

The Machine That Builds The Machines

The Rig creates living assets of value. It is the machine that builds the machines that build assets—and builds the machines that can build themselves. The Rig provisions the org-instance structure for B.O.S.S. and FlowCraft, runs multi-seat synthesis, deterministic caller gates, and verified test harnesses. When workflow blocks are updated in one org, they flow through to the other, through The Rig.

HOW IT IS USED

Asset fabrication & cross-org flow. Builds, tests, and verifies custom operational blocks on local developer iron, and distributes updated workflow blocks across the collective.

THE ARCHITECTURAL FLYWHEEL // ORG-INSTANCE & WORKFLOW BLOCK FLOW

Machines that build themselves. Patterns that flow.

Two foundational principles govern the architecture: complete sovereignty on private iron through the org-instance model, and compound capability through workflow block flow across The Collective.

01 // ORG-INSTANCE STRUCTURE

The Machine That Builds the Machines

The Rig does not just generate scripts; it creates living assets of value. It is the machine that builds the machines that build assets—and builds the machines that can build themselves. The Rig designs and provisions the org-instance structure: both B.O.S.S. and FlowCraft each maintain an authoritative org, and spin up as many running firm instances as needed.

Every org carries its own built-in software factory. It is completely sovereign and severable from day one: an enterprise can take a B.O.S.S. or FlowCraft org and run it entirely on their own private iron, operating autonomously with its own internal build capability.

BUILT-IN FACTORY // PRIVATE IRON

Each org is self-contained. Take an org and run it yourself on private iron—it has its own built-in factory, zero cloud locks, and zero per-seat rent.

02 // THE PATTERN COMMONS

Workflow Blocks Flow Through The Rig

The collective’s patterns are mainly driven through Workflow Blocks (WFBs)—modular, verified operational building blocks for accounting connectors, inventory state machines, and frontline dispatch.

When an org stays a part of The Collective, the network effect ignites: workflow blocks that get updated in one org, flow through to the other, through The Rig. When one builder solves an edge-case ERP reconciliation or refines a receiving state machine, that verified pattern flows to every rig in the collective.

COMPOUND CAPABILITY // OPEN COMMONS

Patterns compound across all rigs while your accounting ledgers, transactions, and customer relationships remain 100% private and sovereign.

OPERATIONAL BLUEPRINTS // INTENT = OUTCOME

Tested on operational patterns. Practical proof.

The Collective is an applied operational lab. When you combine domain mapping (B.O.S.S.), code fabrication (The Rig), and runtime execution (FlowCraft), working sovereign systems take shape:

REFERENCE ARCHETYPE // FRONTLINE OPERATIONS

Frontline Billing & Work-Order State Machine

An automotive shop or specialty service business runs accounting on QuickBooks, but job tracking, mechanic schedules, parts ordering, and customer sign-offs live on whiteboards and text messages.

  • B.O.S.S. maps the shop’s pricing tiers, labor rules, and bay scheduling invariants in days.
  • The Rig fabricates and verifies custom QuickBooks connectors and mobile work-order state machines.
  • FlowCraft executes the runtime—tracking bay throughput, notifying technicians, and updating QuickBooks.
  • Outcome: A working operational blueprint Dave's shop can own and evolve. Zero per-seat rent.
REFERENCE ARCHETYPE // MANUFACTURING & SUPPLY

Sovereign Purchasing & Receiving System

A multi-facility producer struggles with purchase order exception loops, invoice variances, and slow dock handoffs, facing multi-million-dollar ERP consulting quotes to fix it.

  • B.O.S.S. codifies the unwritten receiving rules, freight variance tolerances, and 3-way match logic.
  • The Rig tests automated reconciliation agents against historical edge-case ledger records.
  • FlowCraft orchestrates human approvals and autonomous PO matching across warehouse and finance.
  • Outcome: A sovereign purchasing architecture with full audit trails, owned by the enterprise.

TWO DOORS // ENTERING THE SEAM

How to take part.

Whether you are a builder who wants to run a Rig and collaborate in the collective, or an enterprise looking for a working sovereign system.

PATH 01 // OPEN SOURCE & PEER COLLABORATION

Join the Collective. Build with us.

For software builders, systems architects, and technical operators who want to build real enterprise agentics. Run a Rig on your own iron, explore open schemas, test local developer harnesses, and collaborate with us on verified, severable workflow blocks. We are looking for passionate builders to pull the pieces together, share our zeros and ones, and create something special.

PATH 02 // SOVEREIGN ENTERPRISE BUILD

Commission a sovereign system for your enterprise.

Have an operational bottleneck, an unyielding legacy ERP, or a mission-critical workflow trapped on whiteboards? We use B.O.S.S. to map domain truth, The Rig to fabricate and verify the code, and FlowCraft to deploy a living, sovereign system around how your team actually works. Zero per-seat rent. You own the code.

Explore Delivery Blocks →

DIRECT CORRESPONDENCE // ROB PADDOCK

Start the conversation.

Direct to my desk. Tell me what you are building, an operational problem you are trying to solve, or why you want to collaborate in the collective.