Your Continuity File.
The running file on your own situation: what you sell, what you run it on, who collects your money and what has already gone wrong. Every tool reads it and updates it, so a diagnosis in January still counts in June.
What to sell.What to charge. What to run. What to say.
The layerThe information layer for running an ecommerce business.Something other than advice, because it is wired to the other three layers.
Wired inThe SKU it picks is the SKU the factory quotes.The price it sets is the price the checkout charges.The spend it plans is read against the rail that collected the money.
✦ Twelve freezes handled✦ Twelve migrations completed✦ All twelve still trading✦ Our own sourcing and China freight✦ We run this stack on our own stores first
✦ Twelve freezes handled✦ Twelve migrations completed✦ All twelve still trading✦ Our own sourcing and China freight✦ We run this stack on our own stores first
01 / Where you areCurrent layer / Intelligence
One loop. Current layer marked.Select any node to move through the operating system.
01 / How an answer gets madeQuestion in, plan out
Ask once.
Leave with a plan.
Your question goes in, the system reads the material that applies to your situation, and what comes back is a document you can act on, kept on your file so the next answer knows about the last one.
Five stages. One written record.Kept on your file, so the next answer knows about the last one.
02 / The eight toolsWhat you get / when to use it
Eight ways
to operate.
Each one hands back something finished rather than a conversation. All eight read your file before they answer, and write to it afterwards.
| Tool | What you get | Use it when |
|---|---|---|
| Diagnose stack risk | A map of the five companies that can switch you off, each one rated, and the single worst one to fix first. | You want to know where you are actually exposed before something breaks. |
| Draft processor appeal | A finished appeal ready to send, the documents to attach, who to send it to, and what never to say. | An account is under review or already frozen. |
| Design redundancy | An ordered build plan, each step with a test for when it is done. | You are on one rail and know it. |
| Crisis walkthrough | The actions for the phase you are in right now, plus how many weeks of runway you have. | A freeze is happening today. |
| Restructure plan | The root cause of what happened, and the plan so it cannot happen the same way twice. | You survived one and do not want a second. |
| Plan migration | The rail assessment and the cutover plan. | You are moving off your current processor. |
| Source second supplier | A second-source plan and a vetting protocol. | One factory is a single point of failure. |
| Generate creative | Concepts and copy against your brief. | You need angles to test. |
03 / What it reads57 entries / 11 domains
The material
behind the answer.
Nothing is invented on the spot. Every answer is read out of written operating material, and only the part of it that applies to your situation.
| Domain | Entries | Coverage |
|---|---|---|
| Strategy | 10 | Operating posture, sequencing and owned-stack decisions. |
| Multi-processor | 9 | Rail redundancy, routing and continuity. |
| Processor migration | 8 | Dual-rail planning, descriptor and cutover. |
| Appeal templates | 5 | Evidence-led processor appeals. |
| Entity banking | 4 | Account structure and banking exposure. |
| Reserve math | 4 | Runway and reserve exposure. |
| Escalation rolodex | 4 | Correct function, channel and routing. |
| Store host | 4 | Host dependence and exit paths. |
| Supplier | 3 | Second-source design and vetting. |
| Fulfillment and 3PL | 3 | Fulfillment exposure and continuity. |
| Ad account | 3 | Ad-platform landlord exposure. |
| Total | 57 | The material behind every answer. |
04 / What it keepsFile, Room, handoff
Your file.
Not a chat log.
The Room.
Cases from other operators, with the replies, what was decided and how it ended. Real episodes rather than opinions, and the resolved ones become material the tools read.
It goes somewhere.
The plan can move straight into supply, the store, the rails or creative production, or be handed to our team to run. Nothing gets re-explained on another call.
05 / Honesty boundaryIt tells you
It tells you
what it read.
Every answer names the material behind it and stays on your file. It does not turn a missing fact into confident prose. Where the material does not cover your situation, it says so instead of filling the gap.
06 / DelegationPlan to operator
Our own teamRun it
Any plan it writes can be handed to our team to run.
They pick the work up off your file, with the brief and the decisions already on it. Nobody rebuilds the context from another call.
INTELLIGENCE / HANDOFF
SUPPLY
The chosen product now has to exist. The next layer answers a physical question: can it be made, and moved, at a cost that works?
Open SUPPLY↗Ask. Get a plan. It stays on your file.
Eight tools. Fifty-seven entries. One file that remembers.
Start a processing review↗