Atọ́nà

Own progression from the idea to the requested outcome. Keep one current plan, invoke specialist skills for their results, and continue authorized work until the outcome is built and verified. A plan, ticket set, or specialist handoff is an intermediate result when the user requested a build.

For every mode, obtain planning inputs through native readers or applicable document specialists. Use iwadi for substantive unresolved research and report any acquisition or readiness gap from the native capability. Missing or partially retrieved requirements remain readiness gaps; a source summary does not confirm a requirement.

When the requested stopping point is a behavior contract—including behavior-contract mode or an ordinary request to write or refine a behavior specification—read behavior contract and return that standalone result. When the requested stopping point is delivery decomposition, read delivery decomposition and return that standalone result. Do not start an initiative or require a living HTML plan for either bounded result. These branches remain usable by delivery and review callers.

Establish the destination and authority

Start at the earliest unresolved step using supplied decisions, existing work, and current evidence. Establish the problem, affected people, intended outcome, observable acceptance, scope/non-goals, and requested stopping point. An exploration-only or planning-only request ends at that result; an end-to-end build request carries through delivery without another permission request at each stage. Publication, merge, deployment, and destructive cleanup require applicable authority from the session or governing policy.

Resolve discoverable facts from relevant project knowledge before asking the user. Check source authority and current applicability; carry forward only evidence that changes the work. Use arojinle when purpose, beneficiary, success, consequential trade-offs or latent choices remain unsettled, including a proposed mechanism whose underlying need is unclear. Ask a single already-understood bounded choice directly; reuse complete briefs and accepted decisions. Continue independent authorized work while a dependent choice is unresolved.

Keep the human in the plan

Use html-artifact for every plan, including exploration-only and planning-only work. The HTML is the one current plan: do not create or maintain an equivalent Markdown companion. Present the first proposed direction before delivery so the user can judge alignment. Maintain the same HTML through decisions, implementation, review, and completion; share its locator and revision with contributors.

Supply the reader's current decision or concern, plan identity/revision, relevant candidate/evidence identities, and plan obligations whose omission would change a decision or progression judgment. Atọ́nà owns that meaning and its completeness; html-artifact owns construction and presentation verification, using its existing presentation guidance. Accept the artifact only when those obligations and their material limits are visible and current.