Repo Boundaries
The MAC ecosystem uses an explicit source-of-truth split.
mac
mac owns:
- shared governance doctrine
- the product registry
- reusable ecosystem and process skills
- curated prompts, templates, and examples
mac does not own product runtime implementation.
mac-docs
mac-docs owns:
- published product docs
- the curated public-safe subset of MAC governance docs
- published release logs for documented products
- published changelogs until the planned
MAC Logproduct becomes the dedicated changelog surface
mac-docs is the documentation hub, not the canonical authoring source for governance doctrine.
mac-mcp
mac-mcp is the runtime and integration layer for MCP-facing capabilities.
In this first pass, it is scaffolded and documented, but not yet built out as a full runtime product.
mac-codex
mac-codex is the planned Codex client and plugin layer.
Its job is to package Codex-facing skills, context composition, and client behavior on top of the shared governance in mac and the runtime/tool layer in mac-mcp.
mac-neo
mac-neo is the project-facing AI instruction layer for client and delivery work.
It owns reusable guidance for website builds, redesigns, rebuilds, SEO, marketing, copywriting, HTML, design examples, components, icons, image direction, and output consistency.
It may feed selected instruction packs into mac-codex and may use runtime capabilities from mac-mcp, but it does not govern MAC products or replace product repo .codex context.
mac-figma
mac-figma is the planned Figma standards and project workflow repo.
It owns Figma file conventions, design asset organization, component naming guidance, and Figma-to-implementation handoff guidance. It can feed design workflow inputs into mac-neo and mac-codex, but it does not own product governance.
Product Repos
Product repos such as mac-cli and mac-core own:
- implementation
- repo-specific quick docs
- repo-specific local
.codexcontext - local operational skills
They should not duplicate the full governance layer from mac.
Client Repos
Client repos do not use the mac- prefix and do not receive full parity governance in this first pass.
They follow the integration rules and orchestration defaults defined by the MAC governance layer when they depend on MAC products.
Decision-Pending Areas
The current governance model also tracks a few adjacent questions or early products without treating them as fully built out in this pass:
mac-canvas- early-stage products such as
mac-clover,mac-figma,mac-bricks-hub, andmac-etch-hub