Alex's AI Operating System

One home. Right context. Clear ownership.

Turn diverse inputs into stakeholder-specific output, learn from the response, and compound judgment on a model-neutral foundation.

Direction & governance
Command surface

Workbench

Mission, high-level thinking, cross-system priorities, approvals, and what is owed to each stakeholder.

Live coordination

Buzz

Human-agent rooms, presence, handoffs, and an attributable activity trail.

Priorities and approvals↓source-grounded work↓visible outcomes
Context & judgment
Shared record

Context Library

People, organizations, projects, concepts, source pointers, and authorized exact raw-record retrieval.

Individual intelligence

Agent G-Brains in Obsidian

Tom, Barb, and every specialist keep their own working contract, scoped judgment, and approved lessons.

Repeatable method

Skills /wayfinder

Start by shaping an open question into a decision, then invoke the trusted procedure for the work.

Workbench says what matters→G-Brain decides how to think→Skills make execution repeatable
Hands-on work
Operating layer

Orca

The real hands-on environment. Authorized agents open terminals, inspect evidence, build, test, and produce VIP work here.

Execution record

GitHub Issues

One discrete, repo-bound deliverable with acceptance criteria, blockers, technical history, and completion.

Code truth

Repositories & Worktrees

Source code and isolated changes. Worktrees exist for outcomes, not people or permanent categories.

Build and verify→deliver to the right person→capture the response
Output & learning loop
Stakeholder output

Decisions & Deliverables

The useful thing someone receives, not another summary of the work.

Feedback loop

Use → Response → Learning

What happened in the real world becomes evidence. Approved lessons improve the relevant G-Brain and workflow.

Return to the record

Source-Linked Receipt

The outcome links to authorized source evidence so the right agent can check the record instead of trusting metadata.

Use GitHub when…the outcome can be delivered and verified inside one repository or codebase.
Use Workbench when…the item sets priority, crosses systems, needs Alex's approval, or represents a stakeholder commitment.
When both apply…Workbench holds one outcome line and the Issue link. GitHub holds the detailed checklist. Never duplicate both.