Rig, BOSS, and FlowCraft are not a SaaS trap or an advisory deck. They are the working architecture I use to turn transformation into governed, inspectable, client-owned operating capability.
I run the model before I bring it to anyone else. Rig is the operator-owned work fabric where the build is specified, routed, and proven. BOSS is the business operating graph clients own. FlowCraft is the runtime that turns the graph into live human-and-agent work. DigOps is the first live FlowCraft instance, running idigdata at practice scale.
Rig, BOSS, and FlowCraft are how I turn a mandate into an owned operating asset: govern the work in a portable build fabric, map the business above the vendor stack, then leave the client with a runnable instance for human and agentic workflows.
The client instance is not the meter. The hard part is making the work visible enough to build, adopted enough to run, and portable enough to own.
BOSS and FlowCraft client instances are delivered as part of the engagement, not sold back by the seat. The paid work is the operator-led design, build, training, transfer, support path, maintenance path, and CI/CD capability that lets the business own what was built. Rig is the proof and construction substrate behind that work, not another dependency for the client to rent.
Much of the software market still tries to convert capability into control: host the code, meter the seats, own the state, and keep the customer attached. That is the wrong lesson from agentics. The power is in building a company's ability to run and improve its own work with trained people and trained agents around a system it owns.
That is the scarce role: an operator who can inspect the technology, own the business system around it, carry the work through finance, compliance, vendors, workflows, and people, then leave behind a living operating capability.
Specify · Route · Prove
Built
The control substrate I use to turn ambiguous work into governed, inspectable progress. Rig holds plans, gates, source, evidence, agent instructions, handoffs, receipts, and versioned decisions.
The point is portability: files hold the working memory, git carries integrity, and markdown keeps the handoff inspectable instead of trapped in chat or vendor state.
The Business Workflow Digital Twin
Owned
The client-owned map of how the business actually runs. BOSS models processes, owners, systems, controls, decisions, handoffs, delivery state, SOP memory, and green/green validation above the vendor stack.
A client BOSS instance makes the operating model explicit enough for people, vendors, and agents to work against the same truth.
Build the flow. Run the work.
Run
The isolated firm runtime that turns the BOSS graph into live workflows. FlowCraft gives a specific firm controlled human-and-agent execution, evidence trails, and support routines around how the work really moves.
DigOps is the first live FlowCraft instance: idigdata's own operating system proving the pattern at practice scale.
Work lives as inspectable files, records, gates, and proof instead of side-channel chat. Human and agent contributions can be routed, checked, remembered, and improved.
BOSS names the processes, owners, controls, decisions, systems, exceptions, and validation states that make the operating model legible above the vendor stack.
FlowCraft turns the owned map into an isolated firm instance with trained client roles, controlled agents, support routines, release discipline, and evidence that survives the engagement.
In the old model, software companies rent the system and services firms rent the people. In this model, the business keeps the asset. BOSS and FlowCraft instances are delivered with the work, and the source, configuration, workflow logic, and operating knowledge are made available for inspection, transfer, support, and extension under the engagement.
What you pay for is the hard part: the senior operator work that designs the target, builds the system, trains the operators, installs the agents, creates the support and maintenance loop, and proves the business can keep improving it.
The new operating model includes your people and controlled agents working around the same asset. It defines who owns decisions, who verifies outputs, where support goes, how change ships, and how the system keeps telling the truth after the project room closes.
At the end you hold the operating system of the transformation: mapped workflows, governed data, validation trails, SOP memory, decision records, the BOSS and FlowCraft instances, and the trained human-and-agent operating model around your work.
Your people run it and extend it. Qualified vendors and internal technologists can work against the source, configuration, and evidence the engagement transfers because the point was never software control. The point is the people who run the work owning the asset they run.
If the mandate is real
Your pilots are outrunning your governance. Your vendors are moving. Your board is asking about AI. If that's the room you're in, and the business is serious about owning the result, I can move the work.
Bring the real situation, and I'll walk you through the systems I would use to build it, train it, transfer it, and keep it alive.
