Memory
Maintenance is enforced as a process: observe, extract, review, write and consolidate.
AWOS / At Work OS
Keep the record of ongoing work complete, correct and current.
Every delegated project leaves behind state, decisions, lessons and open actions. AWOS maintains the agreements around that work — memory, scheduling, governance and communication — without requiring a person to stand over every session.
The first contract
AWOS turns project memory into a maintained working system.
Maintain project memory through a governed, repeatable process.
AWOS observes permitted work sources, produces bounded candidates, applies written regulation and commits approved truth to text files under version control. The record stays readable, reviewable and connected to its source.
Scheduling
Work runs with prerequisites, state and explicit conditions for progression.
Governance
Written regulation determines what may change, when it may change and who can approve it.
Communication & IPC
Every handoff keeps its source, destination and propagation authority visible.
Memory architecture
How the memory contract is implemented.
The architecture separates observation, deterministic extraction, semantic evaluation, written policy and the store that carries approved project truth.
Observer
Reads transcripts, repository state, worktrees and diffs without blocking the working session.
Deterministic extraction
Turns raw activity into bounded candidates that can be inspected and tested.
Semantic processing
Evaluates meaning under a simplified governed runtime.
Written regulation
Defines retention, consolidation, refresh, forgetting and authority.
Sovereign store
Writes approved truth to plain text under version control, with reversible changes.
Working example
A simplified memory-maintenance path.
A project decision changes. The canonical record follows under policy.
Instead of relying on a person to remember a later documentation task, AWOS turns the change into a governed candidate and preserves its path to the maintained record.
- 01
Observe
A work session changes a decision, a constraint or the current project state.
- 02
Propose
The observer and extraction pipeline produce a bounded candidate, tied to its source.
- 03
Apply policy
Written regulation determines whether the candidate may proceed, needs review or must stop.
- 04
Write truth
An approved change is written to readable project memory under version control.
Continuity by design
Keep memory, timing, rules and handoffs connected.
AWOS carries approved project knowledge across sessions, keeps scheduled work tied to its prerequisites and preserves the authority behind every change. The result is a working record that remains usable through pauses, handoffs and restarts.
AWOS design conversation
Bring the maintenance failure, not a feature list.
The useful starting point is a real project where memory, timing, rules or handoffs stop being maintained reliably.