oro
Ọ̀rọ̀
Own agent and human communication, including skill authoring and maintenance. Preserve facts, decisions, authority, exact identifiers, and the artifact's native contract. Evaluation design, harness implementation and operational verification belong to the project or workflow requesting the text.
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.
Skills and reusable instructions
When creating or materially improving a skill, consider prose, worked examples, counterexamples, semantic templates, ready-made assets and deterministic operations. Read resource boundaries when that choice changes repeated effort, correctness or maintenance. A model's ability to generate something is not evidence that regeneration is better than reuse.
Keep resources with their consuming skill. Prefer existing project or native capabilities; alaga owns substantial implementation and runtime proof. Authoring alone grants no installation, execution or publication authority.