Indigo · HQ Field GuideCompany creation and isolation
Create a company as a strict boundary for projects, workers, knowledge, policies, settings, credentials, and future sync.
Company boundary
Each company is a self-contained operating context.
Create the company
The company folder and manifest entry are the source of truth for company-scoped work, like a building in the HQ city.
Create the company with a stable slug, verify the generated folders, and describe the company purpose in plain language.
Verify isolation
Company isolation applies to credentials, issue trackers, deploy targets, knowledge, outputs, and the assumptions a worker carries into a task.
Confirm the active company name before any settings, invites, deploy targets, secrets, or project files are created.
Prepare for teammates
A teammate should sync into a company that already has a recognizable name, purpose, starting point, and garden of truth: current, useful knowledge the company actually wants HQ to use.
Add only the minimum current, useful, decision-shaping context, then sync and invite from the same active company.
Keep the chapter executable.
Creates the isolated company structure used by projects, workers, knowledge, and sync.
Use startwork to verify the active company before deeper work begins.
What to keep in mind.
Isolation rule
Never use another company's credentials, settings, policies, or deploy targets as a fallback.
Company readiness
A company is invite-ready when it has a stable slug, a manifest entry, clean sync, a clear starting point, and no stale knowledge pretending to be truth.