The Everything Shelf · one runtime · every function

The OS for everything.

Every function of a company — and of a life — can be stood up as an Agentic Autonomous Organization: agents holding declared capabilities, approval gates where a mistake would hurt, and a named human every role answers to. Each OS below is a charter on one shared runtime — never a fork. And every slot carries an honest state, because a shelf that dresses its empty spaces as products would not be worth trusting with the full ones.

npx @flashyos/agent init --template startupThe runtime, running — Live HQ →
The register — five states, never a sixthLIVE ON THE MESHCHARTER SHIPPEDIN BUILDIN DESIGNOPEN SLOT

LIVE links running proof. CHARTER SHIPPED means the reference charter is in @flashyos/aao today — validated, conformant, claimable. IN BUILD names a builder only with their consent. IN DESIGN means a design doc and nothing running. OPEN SLOT means exactly what it says: nothing exists, and you can be the one who builds it.

For a person

One life has the same functions a company does — money, relationships, commitments, records. A personal AAO is those functions chartered: agents with declared capabilities, approval gates where a mistake would hurt, and one human — you — every role answers to.

PersonalOSCHARTER SHIPPED

One person’s life as a chartered organization — calendar, money, errands, records — answerable to its owner.

schedule · file · renew · track · remind
import { PERSONAL_OS } from '@flashyos/aao'unpack this OS →
FamilyOSOPEN SLOT

A household as an organization: shared budgets, shared calendars, care rotas — with approval gates two adults both hold.

budget · coordinate · book · remind
claim this slot → write the charter
CreatorOSOPEN SLOT

A one-person media company — publishing cadence, sponsorships, community — run by agents the creator directs.

draft · publish · schedule · invoice — family: growth
claim this slot → write the charter

For a business

Every function of a company, stood up as an organization of agents on one runtime — never a fork, always a charter. The ten role families give the shelf its shape; slots follow functions, not fashion.

StartupOSCHARTER SHIPPED

The whole early company — strategy, engineering, research, marketing, operations — governed from the first command.

plan · code · deploy · research · publish
import { STARTUP_OS } from '@flashyos/aao'unpack this OS →
FinanceOSCHARTER SHIPPED

Money movement with an audit trail a regulator could read — settlement, reconciliation, compliance, reporting.

post · reverse · compare · review · block — family: finance
import { FINANCIAL_OS } from '@flashyos/aao'unpack this OS →
AmbassadorOSCHARTER SHIPPED

Relationships at scale — outreach, community, advocacy — with a human gate on anything public.

reach-out · follow-up · host · report — family: growth
import { AMBASSADOR_OS } from '@flashyos/aao'unpack this OS →
SalesOSOPEN SLOT

Pipeline to signature: qualification, follow-up, proposals — with commitments gated to a human.

qualify · follow-up · propose · book — family: revenue
claim this slot → write the charter
MarketingOSOPEN SLOT

Demand as a chartered function — content, campaigns, attribution — where spend requests approval by tier.

draft · publish · test · measure — family: growth
claim this slot → write the charter
PartnershipsOSOPEN SLOT

Business development end to end — sourcing, diligence, deal memos — with the signature always human.

source · research · brief · schedule — family: growth
claim this slot → write the charter
ProductOSOPEN SLOT

Deciding what gets built — research, specs, prioritization — with shipping authority staying explicit.

research · spec · prioritize · review — family: product
claim this slot → write the charter
EngineeringOSOPEN SLOT

Building and shipping — code, review, release — with deploys gated at the tier the charter declares.

code · review · test · deploy — family: engineering
claim this slot → write the charter
OpsOSOPEN SLOT

Keeping it running day to day — vendors, logistics, the books of record that are not money.

schedule · procure · file · renew — family: operations
claim this slot → write the charter
PeopleOSOPEN SLOT

Hiring and the people function — sourcing, scheduling, onboarding — with offers always human-signed.

source · screen · schedule · onboard — family: operations
claim this slot → write the charter
SupportOSOPEN SLOT

The people already using it — triage, response, escalation — with refunds and promises tiered.

triage · respond · escalate · report — family: support
claim this slot → write the charter
DataOSOPEN SLOT

Measuring and explaining — metrics with one definition each, reports with lineage back to the record.

define · compute · explain · publish — family: data
claim this slot → write the charter
Flashy MindIN DESIGNNOT A SLOT — THE LAYER UNDER ALL OF THEM

The organizational memory layer under every OS — a governed, agent-maintained vault every role reads before acting.

The design, labeled as design

Why the empty slots are published

Because the last empty slot got claimed. The finance slot’s reference charter shipped with a placeholder in its accountability field — and a serious team found it, wrote a production charter against it, and validated it with our own conformance suite before we knew their name. An OS on this shelf is a manifest plus domain agents on a shared runtime: the spec is open, the builder surface is documented, and conformance runs in your CI from day one. The shelf is not a product roadmap. It is a standing invitation with a validator attached.

The Everything Shelf is FlashyOS’s public map of operating systems for every function of a company and of a life, each an Agentic Autonomous Organization on one shared runtime, each carrying one of five honest states — live, charter shipped, in build, in design, or open for anyone to claim.

Claim a slot.

Write the charter, pass conformance, put your organization on the floor. The builders who fill this shelf first get a named human, a voice in the spec, and their slot flipped to IN BUILD — with their consent, never without it.

Start at the builder hub
Every state above links its proof. A slot that cannot prove its state does not get one.