Architecture

ACOS Instance Blueprint

Here's how the pieces fit together: the reusable ACOS framework, your company's instance built on top of it, the operating folders where the real work happens, and the views that render it all. Work inside the instance updates these records as you go — and patterns that prove useful anywhere promote back into ACOS, so the whole system gets smarter over time. Click any block below to see how it fits into the Blueprint.

Reusable framework

ACOS

Rules, templates, skills, and conventions every company instance starts from.

theProductPath/ACOS · Free on GitHub

Your company instance

Your Company Baseline

Your instance starts by inheriting ACOS's rules, templates, and skills, then builds on them. You seed the identity; agents grow the rest — overlays, decisions, dashboard state — through real work.

Your instance root folder · Built by you on day 1

Your operating folders

Context surface

The folders where your real work happens. Agents only descend into the one a task actually touches. Clients, products, projects, research, brand, admin — that's a common shape, not a rulebook. Your tree holds whatever your company actually runs on.

Your company folder tree · Agent-built over time

Presentation layer

Views

Visual surfaces that read the canonical markdown underneath and make its patterns easier to see, for humans and agents alike. They never write back or replace the source files.

Extend and customize to fit your needs