SPOTLIGHT REVENUE / DELIVERY + NEXT PHASE

01 / PROJECT CLOSEOUT

Contract deliverables.
All seven complete.

The Locker Operations Agent engagement is complete. This review summarizes the contracted workflows and the supporting tools delivered.

All seven contracted workflows have been delivered.

THE ORIGINAL COMMITMENT

01Reference-ID issuance✓
02Package expiration✓
03Driver unblocking✓
04Pickup & drop-off investigation✓
05Monitoring & incident intake✓
06Remote software remediation✓
07Smartbox deployment orchestration✓

All seven workflows complete.

02 / PROJECT CLOSEOUT

Aero and the
operations team.

Aero gives Mike a direct point of contact for operational questions, investigations and authorized work. Regional agents support the frontline teams.

Executive Aero
Investigations, operational direction and follow-up for Mike.
AeroBVI
BVI team support in approved Slack conversations.
Aero Locker Ops
Regional locker support in approved WhatsApp groups.

Delivered: executive and regional agent support.

Executive Aero

MIKE’S MANAGEMENT PARTNER

Executive Aero

Investigate · Direct · Verify

AeroBVI

AeroBVI

BVI operations
Approved Slack conversations

Aero Locker Ops

Aero Locker Ops

Regional operations
Approved WhatsApp groups

03 / PROJECT CLOSEOUT

Package support
and driver access.

The first three contracted workflows handle reference IDs, package expiration and eligible driver unblocking.

Reference-ID issuance
Retrieve the courier reference for the requested package and location.
Package expiration
Check eligibility, expire the package and confirm its final state.
Driver unblocking
Identify the account, check eligibility and verify restored access.
01Reference ID
02Expiration
03Driver access

Contract workflows 1–3: complete.

a.
a.
a.

PACKAGE SUPPORT

PackageDEMO-042
LocationExample terminal
Courier referenceREF-DEMO-042
Record matched

Package reference located.

Match the package and location, then return its courier reference.

▣

PACKAGE EXPIRATION

Eligible package→Expired
✓ Exact match✓ Eligibility checked✓ State verified

Already in the requested state? No change needed.

Package expiration.

Apply the eligible expiration and confirm the resulting package state.

↗

DRIVER ACCESS

Eligible blocked account→Enabled
✓ Exact match✓ Eligibility checked✓ State verified

Already in the requested state? No change needed.

Driver access restored.

Unblock the eligible account and verify that access is enabled.

04 / PROJECT CLOSEOUT

Pickup and drop-off
investigations.

The fourth workflow brings together package records, compartment readings and incident evidence to investigate a reported problem.

Investigate
Review the package state and available incident records.
Inspect and act
Check door and presence readings; open the specific compartment when authorized.
Report
Return findings, the action taken and any required physical follow-up.
01Records
02Compartment
03Action

Contract workflow 4: complete.

PICKUP / DROP-OFF INVESTIGATION

01

Request

Location + package + error

02

Compare

Package state + locker signals

03

Return

Findings + next action

Review the available evidence.

Connect the reported problem to the package and location.

aeropost SMART LOCKER
a.
Ready for
collection.
A1
A2
A3
B1
B2
B3
C1
C2
C3
D1
D2
D3
Occupancy detected
Door stateClosed

Example B3 · fresh sensor reading · no opening command

Read the compartment state.

Check fresh door and presence signals.

aeropost SMART LOCKER
a.
Ready for
collection.
A1
A2
A3
B1
B2
B3
C1
C2
C3
D1
D2
D3
Opening requestedExample compartment B3

Open the authorized compartment.

Carry out the specific request and check the door state.

05 / PROJECT CLOSEOUT

Monitoring, alerts
and software recovery.

Workflows five and six cover incident detection, regional notification and supported remote software recovery.

Monitoring and incident intake
Observe connected terminal health and route issues to the responsible regional team.
Remote software remediation
Inspect the fault, apply authorized recovery and verify application or service health.
Management visibility
Review the dashboard, incident history and retained diagnostic evidence.
01Monitor
02Notify
03Recover
04Review
Open terminal health monitor ↗

Contract workflows 5–6: complete.

CONNECTED TERMINALObserved health
ApplicationResponsiveness
ServicesAvailability
SystemResource signals
ReportingFreshness

A missing report is not proof of a powered-off locker.

Monitor connected terminals.

Observe application, service, system and reporting signals.

A

ONE INCIDENT

Issue detected

Region AResponsible groupRegion C
“An issue at your location needs attention.”

Illustrative destinations · actual routes follow the approved location map.

Notify the regional team.

Send the location-specific issue to the responsible group.

STEP 03Verify
EvidenceActionOutcome

Supported software recovery. Physical checks remain a human task.

Apply supported software recovery.

Carry out the authorized recovery and verify the outcome.

aero / Health MonitorILLUSTRATION
STATUSReported health
HISTORYIncident timeline
TERMINALOBSERVATIONSTATUS
Example ARecent reportHealthy
Example BFault observedReview
Example COlder reportStale
INCIDENT HISTORY
Open Health Monitor ↗

Review the incident record.

Use the dashboard and retained history to direct follow-up.

06 / PROJECT CLOSEOUT

Smartbox software
deployment.

The seventh workflow provides a controlled process for updating eligible terminals with approved vendor software.

Prepare
Confirm the target, current version, eligibility and required backup.
Install
Apply the approved package within the authorized rollout scope.
Verify and record
Read back the version, check the application and record each target’s outcome.
01Prepare
02Install
03Verify

Contract workflow 7: complete.

SMARTBOX / CONTROLLED DISTRIBUTION

↥SmartboxApproved release
PrepareUpdateVerify
TargetApproved terminal
PackageVendor-supplied release
ReadinessEligibility + backup

Confirm the target and package.

Check the terminal and backup before installation.

SMARTBOX / CONTROLLED DISTRIBUTION

↥SmartboxApproved release
PrepareUpdateVerify
ScopeAuthorized update
ExecutionStaged installation
ProgressRecorded per target

Apply the approved update.

Run the staged installation on the authorized target.

SMARTBOX / CONTROLLED DISTRIBUTION

↥SmartboxApproved release
PrepareUpdateVerify
VersionRead back
ApplicationObserved after update
OutcomeRecorded

Verify and record the outcome.

Check the software version and post-update application state.

07 / PROJECT CLOSEOUT

Documentation
and handoff.

The delivery includes the guidance and operating records needed to use and support these workflows.

Executive handbook
Practical guidance for Mike on requesting work and reviewing results.
Operating runbooks
Documented procedures for investigations, recovery and controlled updates.
Reporting and team guidance
Incident records, outcome reporting and guidance for the operating teams.
Open Aero handbook ↗

This closes the original contracted engagement.

aeropost

THE EXECUTIVE AERO HANDBOOK

Operate.
Understand.
Improve.

MIKE’S PRACTICAL OPERATING GUIDE
01 / Handbook02 / Runbooks03 / Reporting04 / Team guidance

08 / PROPOSED NEXT PHASE

Useful agents.
A wider opportunity.

The locker engagement established what agents can do for AeroPost. The next opportunity is making that capability part of everyday work across the company.

Build on the delivery
Carry the lessons from locker operations into the next phase.
Hydrogen powers the agents
Propose a move from RockOS to Hydrogen as the agent engine.
Water brings the team together
A shared place for people, agents, conversations and work.

A proposed next phase—not a restart of the work already delivered.

BUILT AROUND AEROPOST

Your people+Your agents

WATER / SHARED WORKSPACE

Work together.
Move forward.

LeadershipCustomer serviceOperations
Powered by HydrogenBuilt around AeroPost

09 / PROPOSED NEXT PHASE

Hydrogen.
The engine behind the agents.

Propose moving AeroPost’s agents from RockOS to Hydrogen: the foundation for the next phase, with Water as the shared workspace for the team.

Build on the existing work
Review the agents, knowledge and integrations that need to carry forward.
Validate before moving
Test the agreed workflows and permissions before switching operations.
Keep the transition controlled
Agree the rollout, support and rollback plan around AeroPost’s needs.

An engine transition to plan and validate—not a migration already completed.

Hydrogen agent engine
RockOSCurrent foundation→HydrogenProposed next engine
WaterThe workspace for your people and agents

Review → Validate → Transition

10 / PROPOSED NEXT PHASE

Meet Water.
Your team’s workspace.

AeroPost needs a shared place to work—not another reason to adopt Slack. Water brings people and agents into the same working environment.

Conversations with context
Keep team discussions close to the projects and tasks they concern.
Rooms for your organization
Bring department and country teams together around shared priorities.
People and agents, together
Ask questions, assign work and follow progress in one place.

Hydrogen is the engine. Water is where your people work.

11 / PROPOSED NEXT PHASE

Less chasing.
More follow-through.

In Water, the discussion and the work belong together. Give teams a clearer view of ownership, progress and the next decision.

Clear responsibility
See who owns an item—a person or an agent.
Visible progress
Follow tasks and updates without asking everyone for a status report.
People stay in control
Keep questions, reviews and decisions with the responsible team.

An opportunity for clearer handoffs across AeroPost.

Team prioritiesAgent progressHuman input

12 / PROPOSED NEXT PHASE

A clearer view
of the business.

Bring the updates that matter closer to customer service, country teams and leadership—without making everyone follow every conversation.

Customer service
Connect operational context with the team’s questions and follow-up.
Country teams
Coordinate locally and share relevant updates across the business.
Leadership
See priorities, progress and where the team needs a decision.

One shared environment. The context each team needs.

13 / PROPOSED NEXT PHASE

Configured for AeroPost.
Not a blank platform.

Shape Water around your teams and how they work. Start with useful routines people can adopt, then refine the experience together.

Your organization
Choose the rooms, projects and access each team needs.
Your people and agents
Set clear responsibilities and introduce the workspace with practical guidance.
Your existing tools
Review Aero, Fable 5 and Claude usage to decide what stays and what could connect.

Build on what is useful; validate connections before committing to them.

ConfigureConnectOnboardRefine

14 / PROPOSED NEXT PHASE

Agree the next phase.
Then prove it together.

Choose the business outcomes first. Define a focused Hydrogen transition and Water rollout around the priorities that matter most to AeroPost.

Choose the opportunity
Agree which teams and workflows would benefit most.
Validate the transition
Check existing agent workflows on Hydrogen before any operational cutover.
Pilot, measure, expand
Introduce Water to the agreed group, review adoption and results, then decide what comes next.

Scope, migration, timing and success measures agreed together.

DEFINE THE NEXT PHASE TOGETHER

AeroPostHydrogenWater
01

Choose the outcome.

Focus on the teams and work that matter most.

02

Prove the transition.

Validate workflows and agree the rollout.

03

Learn with the team.

Review adoption and results before expanding.

The next phase starts with your priorities. ↗

Use the corner arrows to explore