Your company already runs on scattered folders, docs, and tools. ACOS turns that sprawl into one coherent context surface any AI agent can read, orient itself in, and act on — without you re-explaining your business every single time.
LLM-agnostic · tool-agnostic · bring your own folders
You've wired up assistants, agents, and copilots across your business. But each one lands in your files blind — no idea where things live, what to skip, or how your company actually works. So it guesses, or you spend the first ten minutes of every task re-explaining context you've explained a hundred times.
Context lives in your head. The rules for how your business runs aren't written anywhere an agent can read them.
Every tool reinvents the wheel. Multiple agents across multiple folders each build their own understanding, inconsistently.
No shared conventions. Where files go, how documents reference each other, which folders are even in play — nothing is codified.
It doesn't compound. What you teach one tool today is lost the moment you switch models or open a new session.
ACOS is a small, opinionated set of conventions that make your company legible to AI. Point any tool at your folder tree, have it read the top-level README, and it can find the right context, follow your house rules, and get to work. Written once, honored by every agent, on every model, forever.
Agents orient themselves top-down — instance root, to the folder in scope, to the specific item — so they always have the right context and never guess.
Ready-made scaffolds for the artifacts every company has — company brief, client & stakeholder briefs, client manifest, dashboards. Copy in, fill out, done.
Reusable agent capabilities — brief processing, brand capture, dashboard refresh, integrity checks — that work against any ACOS instance out of the box.
Which folders are in scope, markdown style, frontmatter, who to escalate to — codified once so every agent behaves consistently instead of improvising.
Configure any skill for your business — account names, folder paths, routing quirks — without forking it. Your specifics, the framework's logic.
A single state record — what's active, what's slipping, what needs you this week — refreshed automatically each morning from across your business.
Copy a handful of ACOS templates into the one or two folders where agents will actually work — Google Drive, OneDrive, Dropbox, a repo, it doesn't matter. You list those folders in one map; everything else in your tree stays exactly as it is. No migration, no instrumenting your whole company.
Fill in one company brief — your voice, your defaults, who agents escalate to. That's the judgment only you can supply; you don't pre-load every client and project. Your business-specific content lives in your instance; the reusable framework stays clean underneath it.
Any LLM or AI platform reads your root README first, cascades into the folder in scope, and follows your house rules. From there the instance grows itself — agents add the briefs, manifests, and records as real work reveals the need. Improve the framework once and every agent, on every model, inherits it.
Most agents are either under-briefed or overloaded with everything you know. ACOS lets them discover context in layers: system rules first, then the relevant client, project, brand, and exceptions.
One task, one relevant path
Task: Prepare a client proposal
Progressive disclosure: the agent carries what matters for the job while the rest stays available but out of the way.
Two interactive explainers walk through how ACOS is built and how an agent actually orients itself inside an instance.
The layered view: the reusable ACOS framework, the company instance on top, the operating folders that hold your work, and the rendered views over them — plus the promotion path that feeds proven patterns back into the framework.
A worked example of how an agent dropped into a client folder climbs to the company root, then descends through the right client, project, brand, and routing instructions — and writes durable knowledge back when it's done.
ACOS gives you the connective tissue and nothing you don't need. It's deliberately not a platform you're locked into.
An opt-in membership model — you list the folders ACOS governs; the rest of your tree stays exactly as it is.
A set of four folder README patterns — root, container, item, asset.
A template library for company and client briefs, stakeholder briefs, client manifests, and dashboards.
A skill library of reusable agent capabilities that run on any instance.
An overlay convention so each business configures skills without forking them.
House rules for naming, markdown, frontmatter, and escalation.
Storage. Bring your own folder tree. ACOS rides on whatever you already use.
Tooling. Any LLM or platform that can read markdown and walk a folder tree works.
Content. Briefs are templates, not filled-in identities — your business fills them in.
The payoff: no lock-in. Switch models or tools freely; your operating layer stays put.
Open source. Yours to adopt, extend, and keep.
ACOS was extracted from tPPOS — the operating system theProductPath itself runs on every day. The framework isn't a whiteboard idea; it's the generalized, battle-tested core of a real company's daily operations. Patterns get proven inside a live business first, then promoted into the framework so you inherit only what already works.
You wear every hat and lean on AI to keep up. ACOS gets the context out of your head and into a place every tool can use — so you stop being the bottleneck.
Client work spans folders, briefs, and brand rules. ACOS keeps every engagement consistent and every agent on-brand, whichever client you're in.
You'd rather encode how the company works than repeat it. ACOS makes your operating knowledge a shared, versioned asset that compounds over time.
ACOS is open source and free to adopt. Start with the adoption guide, scaffold your first instance from the templates, and point your agents at the root.
Open source · actively developed