Editorial Recap · Vol. I · № 01 April 29, 2026
Internal Briefing · JC × AOS Onboarding

Onboarding
the Architect.

How JC steps into AOS, why May 30 is the line in the sand, and the system Mark is mapping in the dark.

Featuring · Mark · JC · Bryle Recording ↗
For You
The Deadline
May 30.

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.

Who Builds What

Mark builds. For now.

Primary builder

Mark

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.

Company-side handoff

Bryle

Eventual owner of internal department work. Runs JC's official onboarding walkthrough and shares the Asana migration with him.

Client-side handoff

JC

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.

// AOS_ARCHITECTURE
One repo
per department.
/customer-experience → CE Review · Calibration · …
/operations → Wave 2 skills
/client-success → Wave 3 skills
/workforce → Wave 3 skills
/learning → Wave 4 skills
/recruitment → Wave 4 skills

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.

Skill Lifecycle

From scorecard
to cutover.

A nine-stage pipeline. Half of it happens after the code merges.

01

Plan

Automated by John.

02

Build

The hands-on craft.

03

Smoke test

Quick sanity passes.

04

Finalize

Tighten the seams.

05

Commit

Local history.

06

Pull request

Submitted upward.

07

Shadow run

AI output validated against the team's manual work.

08

Cutover

≥90% accuracy → manual work stops.

09

Parallel ~2 wks

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 Proof of Concept

CE Review
set the bar.

93→97% Accuracy · first run → today

The cutover threshold is 90%. CE cleared it on day one.

5h→2h Runtime, halved and then some

The same work, less than half the wall clock.

14 / 24h Bugs filed in the first day

Plus 2 feature requests. All resolved within 24 hours.

The Roll-out Map

Four waves,
many tributaries.

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.

WAVE 1 · NOW

Customer Experience

CE Review · Calibration. Helpdesk integrations live here — succeeding CE skills inherit them.

WAVE 2

Operations

Next in queue.

WAVE 3

Client Success
+ Workforce

Two departments, parallel build.

WAVE 4

Learning
+ Recruitment

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.

Architecture Decision

From event-triggered
to batch by operator.

Before — AICS

Webhook events

Automation fires on each incoming event. Stateful, scheduled, hard to gate.

→
After — WaveX on AOS

Operator batch

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

Information has leaked.

So we tightened
the perimeter.

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.

For You
Where you stand

Your runway,
checked.

For You
The Daily Rhythm

Your shift overlaps
John's approval window.

01:00–06:00 MNL Mark builds (deep night)
14:00–18:00 MNL Mark's second block · overlap with you
10:00–18:00 MNL JC's shift
21:00 MNL John approves PRs

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.

Closing Ledger

Commitments
on the table.

Owner · ItemDue
JCShadow Mark on the first WaveX buildPRE-MAY 30
JCLead succeeding WaveX builds (Mark in collab; John may restructure)ONGOING
JCAICS → WaveX cutoverMAY 30
JC + BryleAsana → GitHub migration of automationsPRE-MAY 30
MarkDraft handoff plan, assign tasks once JC has GitHub org accessON ACCESS
BryleRun JC's official onboarding walkthroughSOON
TeamOnboard Karim next; QA tester after JC reaches 60–70% capacityFUTURE

— end of edition —