The services we keep on the bench

Culm Splitting Desk

Everything begins at the splitting desk, where a single tangled requirement is cut into the parts that can be worked on cleanly. We sit with your team and lay the scope on the bench next to the budget, the hardware inventory, the legacy software and the operational calendar. The goal of the desk is not to produce a glossy proposal but to produce a plan that a working engineer could follow on a Monday morning without a second meeting.

At the desk we separate the must-have from the nice-to-have, we name the assumptions that would change everything if they turned out false, and we mark the places where the grain of the system runs naturally apart. A well split engagement is easier to estimate, easier to review and far easier to hand back to the client when the work is done. The output of this discipline is a written split plan, signed by both sides and kept as the reference point for every change that follows.

Rhizome Run Rounds

Below any working grove there is a mat of runners that decide whether the whole thing lives or dies, and below any working computer estate there is a mat of networks, interfaces, scheduled jobs and data paths that almost nobody has documented. Rhizome run rounds are our way of walking every one of those hidden connections and drawing them out into the open. We trace each dependency from end to end, note where it crosses a boundary, name its owner and record the consequence if it fails.

The rounds produce a runner map: a plain-language picture of how information actually moves through your estate, as distinct from how the org chart imagines it moves. Once that map exists, integration decisions become dramatically more honest. You can see which paths are load bearing, which ones are fragile, and which ones are quietly doing a job that a more robust design would do better. The runner map is refreshed on each subsequent round so it never drifts out of date.

Sheath Band Weeks

A young shoot survives because its sheath protects it while the new wall is still soft, and a newly integrated platform survives its first weeks only if it is wrapped in the right protection. Sheath band weeks are intensive integration sprints held immediately around a go-live, during which we weave monitoring, access control, backup, logging and alerting around the fresh system before real load begins to press on it.

The band is not a passive layer. During each sheath week we run controlled traffic through new paths, confirm that every alarm fires where it should, and rehearse the response to the most likely failures while there is still time to adjust the design. We also record a short sheath checklist so that your operations team knows exactly which protections are in place and which are scheduled for the next revision. When the week closes, the platform is no longer raw material: it has a skin that can take weather.

Node Spacing Days

Bamboo grows in segments, and the distance between the nodes determines whether a culm bends safely or snaps. In a systems program the same is true of milestones: too few reviews and the work grows unchecked, too many and the cadence becomes an obstacle. Node spacing days are our scheduled review points, placed at the interval the specific work actually needs, where we check each completed segment against the plan before allowing the next one to grow.

Each node day has a fixed shape. We walk the segment that has just closed, confirm the evidence that supports it, review any deviation from the split plan and agree the correction if one is needed. The review produces a short set of notes that feed directly into the next segment, so the lessons do not wait in a filing cabinet. Because the spacing is agreed at the start of the engagement, nobody is surprised by a review, and no milestone is allowed to pass on optimism alone.

Grove Walk Sessions

A grove is not understood by reading a plan, and a live system is not understood by reading a test report. Grove walk sessions bring our engineers and your operators together to walk through the running estate in the ordinary reality of daily use. We open the system in your hands, follow the tasks your team actually performs, and log every small friction that never appears in a formal acceptance document.

Each session produces a walk log: a short, honest list of what felt smooth, what felt awkward and what should change before the next season. We prefer this shared walking to a distant survey because friction is easiest to remove while the person who felt it is standing beside us. Sessions are typically held in the first weeks after go-live and then at agreed intervals as the estate grows.

Cure Rack Evenings

Split culm is laid on a rack to cure slowly before it carries weight, and a live platform needs a similar quiet season. Cure rack evenings are our unhurried maintenance windows, normally held in the calm hours when the office is empty. During those windows we apply upgrades, rotate credentials, verify backups and let each change settle before the next one arrives, so the system hardens instead of lurching from one patch to another.

Each evening closes with a short journal entry that records what changed, what was verified and what remains on the rack for next time. The journal is shared with your team so that nobody has to reconstruct the maintenance history later. Over a season, the cure rack evenings are what keep a fresh system from drying out, and they are the discipline that keeps the grove steady long after the launch excitement has faded.