AEOS / how the pieces connect
Files hold the context.
People hold the authority.
A coordinated workflow from project facts to a bounded task, inspectable results and the next saved action.
The public preview combines local Python commands with explicit operator and assistant actions. The diagrams show those boundaries, including where work must stop for review.
Evidence scope: public.2 source preview · 2026-10-09 · Local CLI behavior; manual assistant transport. Diagram files are documentation, not additional runtime features.
AEOS / how the pieces connect
Files hold the context.
People hold the authority.
A coordinated workflow from project facts to a bounded task, inspectable results and the next saved action.
The public preview combines local Python commands with explicit operator and assistant actions. The diagrams show those boundaries, including where work must stop for review.
Diagram evidence scope: historical public.2 source preview · 2026-10-09 · Local CLI behavior; manual assistant transport. Diagram files are documentation, not additional runtime features.
RESEARCH / EXPLICIT OWNER GATE
From source to trusted knowledge
Bronze stores raw source material with its origin. Silver is a checked draft note proposed from Bronze and remains unapproved. The human owner decision accepts, edits or rejects the exact proposal. Gold is approved knowledge applied only after fresh checks and the required Git checkpoint. Agents can prepare Bronze and Silver; only the owner can authorize Gold. The demo stops at pending Silver.
Two paths. One source of truth.
Project work returns through controller writeback. Knowledge promotion has a separate owner decision and Librarian apply gate.
HOW THE PARTS COOPERATE
One trail from intent
to evidence.
Use it when a project outlasts a conversation: software work, research, prototypes or a series of small improvements.
- 01 / ROUTE
Find current truth
Read the project's index, state and next action. Keep old notes in their historical role.
- 02 / PREPARE
Give context a boundary
Select sources and a task packet. Runner prepares a brief with file hashes.
- 03 / WORK & REVIEW
Keep the result inspectable
Give the brief to your assistant. Return the actual output and run the named checks.
- 04 / CONTINUE
Save the next step
Review before updating project truth. Resume from the files in a fresh session.
Research has its own gate: source → Bronze evidence → Silver proposal → owner decision → Gold knowledge.
THE SETUP PACKAGE
A small foundation.
Room for your own work.
For builders comfortable with folders, Markdown and a terminal who want a repeatable way to work with an assistant.
The downloadable preview starts with a neutral vault and a synthetic project. It contains no personal operating history or account configuration.
Download setup previewHistorical public.2 download. Its bundled FIRST_RUN has a known output-path defect; use the corrected first-run guide. The repaired public.4 candidate remains unpublished. Commercial terms and pricing are not set.
Inside the archive
- Vault and project templatesRouting instructions, current state and next actions.
- Runner handoff toolsPacket builder, context hashes, result checks and read-only continuation.
- Agentic LibrarianSource intake, candidate knowledge, verification and an explicit owner gate.
- A runnable demonstrationSource → task context → checked result, plus missing/stale-source tests.
- Setup and maintenance recordsFirst-run guide, adapter templates, checks, manifest, credits and rollback guidance.
BEFORE YOU START
Simple tools.
Clear responsibilities.
What you need
CPython 3.14.5, a Markdown editor and a place for local files. Librarian uses PyYAML and jsonschema; Git is required for its approved apply/rollback flow. Windows with Python 3.14.5 is the tested setup.
How integrations work
Use a file-capable assistant such as Codex, or manually copy a bounded brief into another app and return its result. Adapter formats are included; provider authentication and live dispatch are not configured or verified.
HOW THE PARTS COOPERATE
One trail from intent
to evidence.
Use it when a project outlasts a conversation: software work, research, prototypes or a series of small improvements.
- 01 / ROUTE
Find current truth
Read the project's index, state and next action. Keep old notes in their historical role.
- 02 / PREPARE
Give context a boundary
Select sources and a task packet. Runner prepares a brief with file hashes.
- 03 / WORK & REVIEW
Keep the result inspectable
Give the brief to your assistant. Return the actual output and run the named checks.
- 04 / CONTINUE
Save the next step
Review before updating project truth. Resume from the files in a fresh session.
Research gate: Bronze keeps raw source material and where it came from. Silver is a checked draft note proposed from Bronze and still unapproved. A human owner accepts, edits or rejects the exact proposal. Only after owner approval and fresh checks may the Librarian apply Gold as trusted project knowledge. Agents can prepare Bronze and Silver; only the owner can authorize Gold.
THE SETUP PACKAGE
A small foundation.
Room for your own work.
For builders comfortable with folders, Markdown and a terminal who want a repeatable way to work with an assistant.
The downloadable preview starts with a neutral vault and a synthetic project. It contains no personal operating history or account configuration.
Download public.4 setup previewPublic source preview. Commercial terms and pricing are not set.
Inside the archive
- Vault and project templatesRouting instructions, current state and next actions.
- Runner handoff toolsPacket builder, context hashes, result checks and read-only continuation.
- Agentic LibrarianSource intake, candidate knowledge, verification and an explicit owner gate.
- A runnable demonstrationSource → task context → checked result, plus missing/stale-source tests.
- Setup and maintenance recordsFirst-run guide, adapter templates, checks, manifest, credits and rollback guidance.
BEFORE YOU START
Simple tools.
Clear responsibilities.
What you need
CPython 3.11 or newer, a Markdown editor and a place for local files. Librarian uses PyYAML and jsonschema; Git is required for its approved apply/rollback flow. Tested on Windows with Python 3.11.15 and 3.14.5.
How integrations work
Use a file-capable assistant such as Codex, or manually copy a bounded brief into another app and return its result. Adapter formats are included; provider authentication and live dispatch are not configured or verified.
QUESTIONS WORTH ANSWERING
Know what you're getting.
Does it run an autonomous team of agents?
No. The portable tools prepare and verify files. You or your assistant invoke the work. No model, paid service, scheduler or general worker sandbox is installed.
Can I use my existing notes and repository?
Yes. Start beside them, run the sample, and bring across only the templates and tools you choose. Keep project code in its existing repository. Never replace an existing vault wholesale.
Does verified mean approved?
No. Mechanical checks, independent review, owner acceptance and release are separate. Librarian proposals remain pending until the owner makes the exact decision.
What happens when context changes?
The handoff freshness check refuses changed or missing source files. Preserve the old evidence, inspect the change, and prepare a fresh authorized packet. A missing result is unknown, not proof nothing ran.
Is it ready to buy or publish?
This is a tested local setup preview. Pricing, commercial license/distribution terms and any support offer still need an owner decision. No customer outcomes, performance guarantees or live integrations are claimed.
START WITH ONE TASK