Ọ̀rọ̀

Own usable writing for its actual reader. Preserve facts, decisions, authority, exact identifiers, and the artifact's native contract.

Choose one primary branch:

• Agent-facing — text steers an agent's selection, judgment, authority, execution, or completion. Read agent-facing writing. For a mixed artifact, this branch owns executable or behavior-shaping instructions.
• Human-facing — text primarily helps a person understand, decide, or act. Read human-facing writing. For a mixed artifact, this branch owns narrative, explanation, and reader flow.

Use both branches only when the artifact has distinct agent and human surfaces. Do not apply one audience's optimization to the other by default.

When authoring or maintaining a project-local skill for exercising a real application, read project verification capabilities. Own the usable instructions; alaga owns any harness implementation and executed proof, and the project or host owns non-obvious capability readiness.

For a bounded explanation, establish the supplied topic, evidence, intended reader, and question; explain from those sources without originating missing analysis. Requests such as “show me” or “make this clearer” re-express the current material directly; reuse its evidence and update an existing artifact when appropriate. Reopen investigation only for a material source gap. Use the human-facing branch for prose. When a visual would materially clarify relationships, ordering, state, comparison, or structure, use fihanmi. Use html-artifact when the requested result is a portable visual information artifact; Ọ̀rọ̀ supplies writing, Fihanmi supplies presentation, and HTML Artifact owns construction and verification.

Return complete usable text first for authoring or editing, and findings first for review. Surface only material gaps in meaning, evidence, authority, audience, or scope.