Why AOS · How it improves
Every run leaves a record. Every lesson becomes a version. Every version reaches the people who need it. That is how a company on AOS.work keeps improving long after the first week.
The improvement loop
The loop is short on purpose: a run record, a draft, a release. It closes in days rather than quarters, and it runs inside the workplace instead of around it.
- 01
Observe runs
Every task leaves a run record: the tools called, the files read and written, how long each step took. Patterns show up quickly when a whole team works the same way.
- 02
Refine a Skill
The person who knows the job opens the Skill in Resource Hub and changes the instruction. No retraining, no memo. The draft is validated before it can go anywhere.
- 03
Release a version
The draft becomes an immutable version and Explore Management releases it to the roles that need it. Teams follow the latest version or pin a specific one.
- 04
Everyone works the new way
The next run in every workspace loads the new version. Nobody has to remember the change, and the run records show whether it helped.
01Observe runs
02Refine a Skill
03Release a version
04Everyone works the new way
- 01load_skillfinance-reconciliation v7
- 02readledger-2026-08.xlsx
- 03readledger-2026-08.xlsx×2
- 04run.completed6m 40s
Run records in every workspace
One Skill, one week, one improvement applied to every run that follows.
Made once, applied everywhere
Resource Hub and Explore turn a change of practice into something a company can actually ship: drafted, validated, published as an immutable version, released to roles, adopted on the next run.
/finance-reconciliation
SKILL.md · reconcile.py · README.md
Illustrative · Resource Hub draft to Explore release
- 01
Draft
Create the Skill in Resource Hub from Git, an upload or a blank file. The author is the person who knows the job.
- 02
Validate
The draft is checked before it can be published, and its publish policies are set: read-only or writable, overwrite or keep.
- 03
Publish
Publishing creates an immutable version. Once it is out, it never changes underneath anyone.
- 04
Release
Explore Management releases the version to roles, with a display order that makes it easy to find.
- 05
Adopt
Most teams follow the latest version. A regulated process pins a specific one and moves on its own schedule.
Without a version
- A memo that is found once and lost twice
- A training session for the people who attended
- Adopted by some, differently by each
- No way to tell who works the new way
With a version
- One draft in Resource Hub, written by the person who knows the job
- Validated and published as a version that cannot drift
- Released to exactly the roles that need it
- Every run from then on uses it, and the run records prove it
Memory that compounds
Memory on AOS.work is long-term and reviewable. It grows with every correction, gets tidier on a schedule and travels with the task instead of starting from zero.
a.chen · Finance · reports in EUR, thousands
Month-end close on the 3rd working day · close checklist as a table
- rev 14AddedVendor codes follow the ERP listSep 12
- rev 13CorrectedFiscal year starts in AprilSep 05
- rev 12Consolidated3 duplicates mergedAug 28
Illustrative · Memory, Update History and a nightly consolidation task
Revisions, never overwrites
Each edit creates a new Memory Revision. Update History lists every revision, and any one of them can be restored, which itself becomes a new revision.
Consolidation on a schedule
A nightly scheduled task merges duplicates, applies corrections and forget markers and drops expired notes. It never guesses that a fact has gone stale.
Context that travels with the task
A Workspace, attached files, Library documents and Base views become context tags on the task. Credentials never go into Memory; they are asked for in secure forms.
What leaders see
Because work runs through one workplace, the Admin Console shows how the company works and how that changes after each release, without anyone filling in a report.
Task counts by team
Which teams run which Skills and Works, and how that shifts as new roles join.
Cycle times after each release
How long a task takes before and after a Skill version, side by side on the same timeline.
Usage overview
Models, credits and runs per period, so cost follows value instead of surprising anyone.
Run records
Every run is traceable to its tools, files and outputs, with Back to Original Message on every result.
Tasks by team
- Finance128
- Operations96
- Sales74
- People41
Median cycle time
Usage overview
- Credits
- 62% of period limit
- Models
- qwen/deepseek-v4-pro
Run records
Back to Original Message
Illustrative · Admin Console overview with Skill releases marked on the timeline
The people side
Improvement is a habit before it is a feature. AOS Academy gives every role a path, and the roles give the loop its owners.
AOS Academy learning path
- Meeting minutes
- Document summary & translation
- Data analysis
- Presentations & HTML
- Email follow-ups
- Finance reconciliation
- HR recruitment
- Sales prospecting
- E-commerce operations
Foundations
How to start a task, add context and read a Task Output.
Office scenarios
Everyday work with the Skills the company has released.
Role-based Works
A complete kit for a role, loaded together in one task.
Who owns the loop
Users
Start tasks, notice what could be better and say so. The loop begins with the people doing the work.
Administrators
Own Resource Hub and Explore Management: validate drafts, publish versions, release them to roles, keep models and credits in order.
Delivery team
Design the scenarios, author the first Skills and Works, and run the Academy sessions that make the habit stick.
Before and after
Nothing about the people changed. What changed is where knowledge, standards and memory live, and who can see the work.
Knowledge
Before
In heads, inboxes and a shared drive nobody trusts
On AOS.work
In the Library, the source of truth every run reads from
Standards
Before
A memo, a slide and a reminder in the weekly meeting
On AOS.work
A versioned Skill released to the roles that need it
Memory
Before
Every task starts from zero
On AOS.work
Revisions that consolidate nightly and travel with the task
Improvement
Before
Depends on who noticed and who they told
On AOS.work
Observed in run records, shipped as a version, visible to everyone
Visibility
Before
Anecdotes in a quarterly review
On AOS.work
Task counts, cycle times and run records in the Admin Console
Learning
Before
A one-off training when the tool arrived
On AOS.work
Academy paths by role, from foundations to Works
Book a demo and we will set up a workspace with your knowledge, your standards and your guardrails.
Built on Basil Harness · Protected by Shieldon