How JC steps into AOS, why May 30 is the line in the sand, and the system Mark is mapping in the dark.
AICS becomes WaveX. By month's end, every role down to agent level moves from Asana to GitHub, with all information pulled from there. WaveX is more than ticket handling — it's the connective tissue between client tools, apps, and AOS.
JC owns this migration. The plan: shadow Mark on the first build, then lead the succeeding ones with Mark in the loop. John may yet rewrite the choreography.
Holds the system end to end and is accountable to John. Must be able to QA everything the team produces — different directions, different approaches, one bar.
Eventual owner of internal department work. Runs JC's official onboarding walkthrough and shares the Asana migration with him.
Eventual owner of client-facing work — starting with WaveX. Confidence in learning by doing, not by reading. The handoff lands when knowledge transfer is complete, not when the calendar runs out.
Skills are derived from each team's scorecard — the document that defines what every role is responsible for. Convert a primary task into automation, and you have a skill. CE Review came from Customer Experience's primary task: reviewing tickets.
A nine-stage pipeline. Half of it happens after the code merges.
Automated by John.
The hands-on craft.
Quick sanity passes.
Tighten the seams.
Local history.
Submitted upward.
AI output validated against the team's manual work.
≥90% accuracy → manual work stops.
Bugs and feature requests get triaged in real time.
"John is the only PR approver — that's the bottleneck, and the rhythm of the day is built around it."
The cutover threshold is 90%. CE cleared it on day one.
The same work, less than half the wall clock.
Plus 2 feature requests. All resolved within 24 hours.
Each wave is one department. Each subwave (1.1, 1.2, 1.3…) is a smaller skill that piggybacks on integrations the primary wave already paid for.
CE Review · Calibration. Helpdesk integrations live here — succeeding CE skills inherit them.
Next in queue.
Two departments, parallel build.
The closer.
A full Asana audit surfaced skills beyond the primary tasks. Those become subwaves and slot into sprints — smaller in scope, equal in importance, often unblocked by the integration work already done upstream.
Automation fires on each incoming event. Stateful, scheduled, hard to gate.
Agent starts shift. Runs the skill at, say, 2:04 PM. The skill picks up every active, untouched ticket as of that timestamp. Claude returns: "25 tickets — 22 automated, 3 flagged for human." Agent approves.
SHOPIFY · already integrated via Redo · POC validated · AOS speed > N8N speed · output volume is the new bottleneck — Claude is verbose, two conversations balloon fast
All API tokens and keys have been pulled out of AOS. Credentials live in LastPass and are pulled in at runtime — update once, reflected everywhere, never committed.
.env, git-ignored by default.Mark submits at night and finds his PRs merged the next morning. You won't. Your PRs need to be in by 9 PM Manila — work that lands tonight gets approved overnight, and you merge first thing the next morning before building from there. Plan one day ahead.
— end of edition —