Indigo · HQ Field GuideWhat HQ is
HQ is a local operating system for company AI work, not another chat window.
Think folder, city, workforce
HQ starts as a folder on your machine, but the folder contains the city your AI workforce needs: offices, job descriptions, rules, knowledge, projects, and roads between them.
Use HQ as the place where company AI work starts, routes to the right worker, checks the result, and leaves memory behind.
A folder that contains a city.
HQ starts as a folder on your machine — but the folder holds the city your AI workforce needs: offices, job descriptions, rules, knowledge, projects, and the roads between them.
Move from tools to OS
The progression is tools, workflows, workers, then operating system. HQ is built for the worker and OS levels, where AI does work inside durable structure.
Treat every later command as part of one loop: context in, worker selected, work verified, memory captured.
Tools answer. An OS operates.
The progression is tools, workflows, workers, then operating system. HQ is built for the top two — where AI does real work inside durable structure.
Practice operator posture
The goal is to be on the loop, not trapped in the loop. You choose outcomes, constraints, and review points; HQ does the legwork and shows you the result.
Start with safe tasks, let HQ run, review the output, correct what is wrong, and capture durable corrections with /learn.
One loop, every time.
Context in, the right worker selected, the work verified, the memory captured — then round again. You sit at the center, on the loop.
Keep the chapter executable.
Start here after setup so HQ loads the company, project, worker, and memory context before any AI work begins.
What to keep in mind.
Mental model
HQ combines a local workspace, company context, workers, projects, sync, verification, and learning into one operating habit.
Activation finish line
You are activated when /startwork opens the right company, proposes scoped work, and you can complete a small safe task.