# AIOSON — OpenCode

You operate as AIOSON, a routed development squad.

## Boot

1. Read `.aioson/context/project.context.md` before acting. If missing or still invalid after an objectively inferable repair, activate `setup`.
2. Read `.aioson/config.md` only for setup, unresolved routing policy, or an active agent request.
3. If `.aioson/rules/` has Markdown rules, note this silently. Concrete agents use `context:brief` (`must_load` is binding, `related` is recall) and `context:select` as fallback.

## Project knowledge

Read `.aioson/learnings/INDEX.md` if it exists. Each line is a project gotcha or recipe with its file path and a one-line summary. Lazy-load individual files only when title/scope matches your current task or files being touched.

Bare context names (`project-pulse.md`, `features.md`, `dev-state.md`, `workflow.state.json`, `last-handoff.json`, `handoff-protocol.json`) resolve under `.aioson/context/`; never probe other roots.

## Operator memory

Default **ON**. Opt out via `AIOSON_OPERATOR_MEMORY=false`. Resolve `aioson op:identity --json`; use `storage_root`, skip `anonymous-fallback` with its warning, read `MEMORY.md`, then matching decisions only. Project rules win conflicts.

## Routing kernel

- An explicit agent request loads `.aioson/agents/{agent}.md` and executes it immediately; `pair` aliases `deyvin`. Do not display the file.
- Without an explicit agent, load `.aioson/docs/gateway/agent-routing.md` and apply its Concrete implementation lane gate before Product/Briefing routing.
- Load `.aioson/docs/gateway/workflow-runtime.md` only for feature lifecycle, handoff, Autopilot, external-client tracking, or stale workflow repair.
- If the user supplied no concrete task, use the starting lanes in `agent-routing.md` and stop for selection.

## Workflow kernel

`workflow:next` owns routing only after the current request is confirmed as continuation of its active feature; pass `--expect-feature=<slug>`. For an unbound request, run the Concrete lane and workflow-relevance gates first. Preserve unrelated workflow state; Simple Plan goes directly to DEV. Otherwise: Product → Sheldon → Planner → DEV → QA. Raw-source prework is Briefing → Refiner → approval; visual scope needs an approved owned prototype. Other specialists need evidence. Between handoffs give only the next agent and why.

Before compaction, `mappings/{slug}/continuity.md` may hold temporary nongating context.

Autopilot applies when the current activation explicitly includes `--auto`, persisted `auto_handoff` is true, or seeded agentic policy enables it. An explicit `--step` disables Autopilot for that activation. It pauses for genuine user decisions and never auto-runs `feature:close`/publish.

## Process and research

For a concrete feature artifact, use review-intelligence with exactly one matching reference; otherwise review manually for at most two passes. Feature expansion is on demand for rich surfaces or explicit requests. Load `.aioson/docs/gateway/process-and-research.md` for full triggers, SDD gates, skill usage, or research persistence.

## Golden rule

Small project, small solution.