ACOS quickstart and harness routing
How the six-harness managed-block architecture, ACOS slash commands, and maker-checker PR gates operate across the FrankX estate.
frankxai/frankx.ai-vercel-website/AGENTS.md, frankxai/claude-code-config/CLAUDE.md, Starlight-Intelligence/starlight-agent-config/core/doctrine/SYSTEM-SPINE.mdThe Agentic Creator OS (ACOS) coordinates six coding harnesses against a single doctrine spine (starlight-agent-config/core/doctrine/SYSTEM-SPINE.md) and shared skill source (starlight-agent-config/core/skills/). Each harness receives marker-bounded instruction blocks while preserving its native safety and configuration semantics.
Six-harness managed-block matrix (SYSTEM-SPINE.md §5)
Shared rules are compiled into each harness target using marker-bounded injection (<!-- STARLIGHT-SPINE:START --> to <!-- STARLIGHT-SPINE:END -->). Content outside the markers is untouched, a .bak backup is written before every update, and compilation aborts non-zero if rendered output matches a secret pattern.
| Harness | Instruction target | Config target | Injection strategy | Skills vector |
|---|---|---|---|---|
| Claude Code | ~/.claude/CLAUDE.md | ~/.claude/settings.json | markdown-block / json-merge | Directory junction to core/skills |
| Codex | ~/.codex/AGENTS.md | ~/.codex/config.toml | markdown-block / toml-block | Directory junction to core/skills |
| Antigravity / Gemini | ~/.gemini/config/AGENTS.md + ~/.gemini/GEMINI.md | ~/.gemini/antigravity/mcp_config.json | markdown-block | acos-frankx plugin junction |
| Grok CLI | ~/.grok/AGENTS.md | ~/.grok/config.toml | markdown-block / toml-block | [paths].extra_skill_dirs + junction |
| Hermes | profiles/<name>/SOUL.md (spine header) | profiles/<name>/config.yaml | markdown-block (header only) | Per-profile skills/ directory |
| OpenCode | ~/.config/opencode/AGENTS.md (discovery target) | ~/.config/opencode/opencode.json | Disabled until adapter tests pass | Repository AGENTS.md |
In frankxai/claude-code-config, CLAUDE.md and AGENTS.md enforce that global hooks remain telemetry-only, short-timeout, and non-blocking. Heavy checks run in explicit CLI commands, daemons, or CI workflows rather than session-start or stop hooks.
Command routing: /acos, /si, /council, and /factory
ACOS commands route work by task complexity and artifact type rather than running a single prompt template for every job:
| Command | Primary routing role | Execution flow |
|---|---|---|
/acos | Top-level router across the creator operating system | Inspects intent, selects the matching domain skill pack from the skills catalog, and loads local repo contracts (AGENTS.md, design.md, taste.md). |
/si | Starlight Intelligence router | Queries the semantic memory vaults and dispatches cross-repo architecture or research synthesis tasks. |
/council | Multi-perspective deliberation | Convenes specialist seats (Strategist, Architect, Continuity, Verification) with Starlight Orchestrator synthesis before irreversible architecture or canon decisions. |
/factory | Content and product publishing pipeline | Sequences research, drafting, voice and editorial gates, visual asset verification, and staging for human release sign-off. |
Branch isolation and pr-gate.mjs discipline
Multiple harnesses operate across the estate concurrently. Git branches, worktrees, and cross-provider verification prevent write collisions:
- One agent, one branch, one worktree. Never push directly to
main. Codex usescodex/<scope>; other harnesses useagent/<harness>/<scope>(for exampleagent/claude/blog-fixoragent/antigravity/docs-brand-depth). Risky or parallel work runs inside an isolated git worktree. - Draft-first pull requests. Open every pull request as a draft (
gh pr create --draft), batch commits to avoid redundant CI runs, and mark ready (gh pr ready) only after local verification passes. - Maker-checker separation (
pr-gate.mjs). The maker harness owns the write lane; an independent verifier from a different model family or harness reviews the exact head commit SHA with zero overlapping write access. - Native Vercel git deployment.
frankxai/frankx.ai-vercel-websitedeploysmaindirectly tohttps://frankx.aivia Vercel's git integration. Do not add GitHub Actions deploy jobs.
Verifying a local checkout (frankx.ai-vercel-website)
Run these exact commands from frankx.ai-vercel-website before pushing a branch or requesting independent review:
# 1. Install dependencies (pnpm-lock.yaml is authoritative)
pnpm install
# 2. Run the four required CI gates (.github/workflows/ci.yml)
pnpm run type-check
pnpm run lint
pnpm run ai-slop:audit:strict
pnpm run build
# 3. Run the broader pre-merge gate (contract tests, claims/language audits, link checks)
pnpm run merge:gate
# 4. Optional repository integrity and workstation health checks
pnpm run ci:check
pnpm run healthFor local web server inspection across any harness, check sds status -IncludeUnmanaged before starting a dev server so agents do not collide on occupied ports.
FrankX overview
The founder domain — frankx.ai, the 124-skill catalog, @frankxai/mcp-doctor, the AI Architect newsletter, and the creator operating system.
Skills library & MCP doctor
How the 124 installable skills in claude-skills-library and the @frankxai/mcp-doctor CLI are structured, resolved, and installed.