Chengdu Kangyasi Heng E-commerce Co., Ltd.

Six services, one bench

Chengdu Kangyasi Heng E-commerce Co., Ltd. keeps its integrated systems work on a quiet spring bench at No. 102 Unit 1 Building 11 No. 88 Niusha Back Street, Jinjiang District, Chengdu - 610000, China (CN). Each service below is a working part of that bench, and together they carry a system from the first cut to the long watering that keeps it alive.

Bench service one

Twig Desk

The Twig Desk is where every engagement begins, and it is the service we treat with the most care. We sit down with your operations leads, your system owners and anyone else who will touch the finished system, and we draw the boundary of the work on a single sheet. What is inside, what is outside, what is assumed, what is unknown: all of it gets named while the twig is still green and easy to bend. A weak Twig Desk session produces a scope that drifts within weeks, so we refuse to hurry this step.

The output of a Twig Desk session is short and practical. It includes a one-page scope, a list of systems to be joined, a named contact for each system and a plain statement of what the bench will and will not deliver. We also record the questions we could not answer yet, because those questions become the first agenda items for the Sap Bay Rounds. Nothing at this stage is written for the archive; every line is meant to be read by the people doing the work.

Twig Desk sessions usually take half a day and can be held at our Chengdu bench room or over a screen share. We prefer to have at least one person present who will actually operate the system after handover, because their daily friction is the most reliable source of scope we have found.

Bench service two

Sap Bay Rounds

Sap Bay Rounds are scheduled architecture walk-throughs carried out while integration work is in motion. We trace the data sap from source to sink, junction by junction, and we write down every place where the flow narrows, splits or loses pressure. Each round produces a route map that shows the real path of an order, a shipment or an invoice through your systems, not the path the diagram promised. Over two or three rounds the map becomes the single most useful document on the bench.

We hold rounds twice a week during active build windows and once a week during quieter phases. Each round is short, usually sixty to ninety minutes, and each ends with three items: what we learned, what we will change and what we will re-check on the next round. The discipline of re-checking is what separates a Sap Bay Round from a status meeting, because a route map that is not verified against live traffic slowly becomes fiction.

Rounds are led by the same engineer who will later write the Leaf Week evidence, which means the person testing the joins is the person who documented them. Clients often tell us this continuity is the reason they trust the route map, and we consider that a fair judgement.

Bench service three

Leaf Weeks

A Leaf Week is a fixed build window in which one leaf of the system is finished end to end. We choose a leaf that can stand on its own, such as a single order handoff or a single reporting feed, and we push it all the way to a working surface inside the week. The point is not speed for its own sake; the point is that each week leaves behind something you can actually use and inspect, rather than another layer of half-built scaffolding.

Each Leaf Week opens with a short written brief and closes with a short written evidence pack. The brief states the one leaf under construction and the definition of finished. The evidence pack shows what was built, what was tested, what was deliberately left out and what the next leaf will be. We keep both documents in plain language so your team can review them without a translator or a slide deck.

Most engagements run three to six Leaf Weeks. We deliberately keep the window short because long build blocks hide slippage, while short windows surface it early enough to correct without drama. When a leaf cannot be finished in its week, we say so on the closing day and re-plan the next window rather than quietly carrying unfinished work forward.

Bench service four

Potting Days

Potting Day is the handover. After the last leaf is finished, we move the system into your soil and make sure it can live there without us standing beside it. That means checking credentials, environment settings, monitoring, backups and the runbook against the real production ground, not against a happy test fixture. We tighten the rim, confirm root contact and only then consider the system planted.

The day itself is run by your operators. Our engineer sits beside them while they drive the system through a full working shift, answering questions and note-taking rather than taking the keyboard. Any gap in the runbook discovered during that shift is fixed on the spot. A Potting Day that ends with our team still holding the controls has failed, no matter how green the test results looked.

Every Potting Day closes with a potting note: what was planted, what was changed in the final days, which accounts exist, which schedules run and what needs attention in the first month. The note is written for the person who inherits the system twelve months from now, because that person is the real audience for every handover we do.

Bench service five

Bud Check Sessions

Three weeks after potting, we return for a Bud Check Session. By then the system has met real traffic and small signals have started to appear: a queue that creeps, a timeout that fires once a day, an operator workaround that has quietly become load-bearing. The session is a calm inspection of those buds before any of them harden into a problem. We look at latency drift, error budgets, retry behaviour, disk growth and the human side of operations, including the questions your team has started asking.

We do not arrive with a long list of improvements. We arrive with a short list of the smallest corrections that will keep the system healthy through the next season, and we agree on them with your team in the room. Anything larger is written into a separate proposal so that it competes for attention honestly rather than smuggling itself into a maintenance session.

Sessions are deliberately short, usually two hours, and deliberately honest. If the system is healthy, we say so and close the session early. If it is not, we say that too, plainly and with evidence, because a Bud Check Session that only ever delivers good news is not a check at all.

Bench service six

Watering Run Evenings

Once a quarter we hold a Watering Run Evening for the teams whose systems we have potted. It is a working evening in the bench room or on a call, and it exists because healthy systems still need water. We update the dependency map, retire stale accounts and integrations, rehearse the rollback under supervision and refresh the runbook against anything that changed in your business since the last watering.

The evening ends with a printed card of the watering dates for the coming quarter, so the habit does not depend on anyone remembering it. Teams that keep the watering rhythm tend to find that their Bud Check Sessions become shorter year over year, which is exactly the direction we want the bench to push.

Watering Run Evenings are included in our retained engagements and can be booked as a standalone service for systems built elsewhere, provided we are given enough access to read the real configuration. We will not water a garden we cannot see.

How the bench runs a season

Step one

Cut

The Twig Desk session trims the scope to one clear twig and names every system at the join.

Step two

Feed

Sap Bay Rounds trace the real data routes and keep the route map honest against live traffic.

Step three

Grow

Leaf Weeks finish one working surface at a time, each with a brief and an evidence pack.

Step four

Pot

Potting Days hand the system to your operators, then Bud Checks and Watering Runs keep it alive.

Tell us which leaf of your system is holding you back, and we will tell you honestly whether the spring bench can grow it. Write to admin@springli.lol or call +12247865443 to reserve a Twig Desk slot.