setup

# aigent-OS setup and reconfiguration `/start` owns the day-one onboarding arc. `/setup` is the deeper configuration flow and may also be used later to revise one section. ## Entry behavior Read `.aigent/state.json` first. - If state is missing or not `ready`, route through `/start` unless the operator explicitly requested advanced setup. - If state is `ready`, ask which configuration area needs revision rather than replaying the entire interview. - Never detect setup state by searching for placeholder prose in a Markdown file. Before writing, set `status: setup-in-progress` while preserving any prior `completedAt`. On interruption, the next `/start` or `/setup` should resume from the last durably completed section. ## Interview Ask one question at a time and write each completed section immediately. ### 1. Identity Ask for the operator's role, responsibilities, preferred collaboration style, and risk posture. Update `system/00_identity.md` without replacing framework-owned doctrine. ### 2. Priorities Ask for the top two or three active priorities, the most urgent outcome, operating mode, and blockers. Update `vault/memory/ACTIVE_PRIORITIES.md`. ### 3. Authority boundaries Ask what the AI may handle autonomously, what needs confirmation, what is human-only, and whether spending has an escalation threshold. Update `system/12_authority_matrix.md`. ### 4. Decision logic Ask what makes the operator accept or reject opportunities, their active-work limit, and their ...