Xtreme Ops Layer · systems online

Control
Hub

The command centre for every The Calls Warehouse tool, workflow, automation, customer journey and suspiciously-powerful spreadsheet you have somehow built while pretending this is normal behaviour.

AI workflows Customer journeys Quote engines Ops dashboards

Enter the command deck Show next domination moves

0systems and prototypes

0customer-facing routes

0active tools

∞parked genius / chaos

System galaxy

active map

TCW

AI🧠

Mail📨

Ops📊

Launch🚀

Do not forget

priority brain

✨

Customer-facing = The Calls WarehouseUse the full name externally unless told otherwise.

Locked

🧩

Demo-ready beats perfectStabilise flows before beautifying everything.

Rule

🛡️

No code chaosPatch surgically, duplicate-check, avoid risky reshuffles.

Rule

Tool stack

The empire, but organised.

Every serious build gets a home: what it does, whether it works, where it lives, what still needs fixing, and why it matters commercially.

Priority queue

What actually needs doing next.

The short list, so the mothership stays useful and does not become another beautiful swamp.

Equipment Inventory / Scanner Ops

Load existing stock, add customer 4G routers, link the 4G order sheet, check handset route with Frank, and finish scanner-chat outstanding items.

Redeploy the live Hub

Push the latest HTML to Cloudflare so the live page shows the updated scanner/inventory and legacy scanner changes.

Customer journey pages

Finalise Cloudflare route for customer-facing pages and update FLG notes with social/new-lead creation rules.

Hub wiring cleanup

Add custom drawer buttons later so tools can have Dashboard, Scanner, Sheet, Worker, Notes and Source links separately.

Featured route

The lead-to-report machine.

This is the customer-facing workflow that makes the Hub feel like a real system rather than a folder full of clever bits.

Health Check pathway

Social / landing page visitCustomer sees a campaign asset, guide or health check invitation and lands on the mini-site.

Identity capturedExternal form or FLG capture route creates/identifies the lead before the assessment starts.

Journey completedAnswers are stored in FLG fields and sent through the webhook to the workflow processor.

AI report generatedScore, category, colour values and human-readable summaries are calculated and pushed back to FLG.

Follow-up triggeredOnly the explicit Health Report Ready status should trigger the final customer report email.

Next domination moves

1. Add real links

Replace every “Add link” button with actual Apps Script, Cloudflare, Sheet or Drive links.

2. Add owner/status notes

Track whether each system is live, demo-ready, internal-only, customer-facing or parked.

3. Add setup guides

Each tool should have a plain-English “what it does / how to use it / what can break” page.

4. Parked end goal

Make the Hub pull tool data from a Google Sheet or JSON config so cards can be updated without editing HTML.

Link health

What still needs wiring.

This panel updates automatically from the tool database, so missing links stop living in your head.

0missing tool URLs

0missing sheet URLs

0missing notes URLs

Still to find

checking

Mothership admin

Command Centre config.

Update live URLs, labels, statuses and notes from inside the Mothership. The data saves to Cloudflare KV through /api/config, so you do not have to edit HTML for routine link changes.

Loading config...

Use it as a launchpad

One page where Frank or internal users can find the right tool without knowing the messy backstory.

Use it as a memory bank

Every build gets a purpose, location, status, next action and “done looks like” so nothing gets lost.

Use it as proof

This makes the whole automation estate look intentional, valuable and slightly terrifying in the best possible way.