Orísun

Ground one bounded technical question in the smallest exact upstream evidence needed to answer it. Prefer project-resolved truth over model memory and current upstream head. Return compact evidence that another owner can consume without inheriting the research procedure.

Orísun is an explicit Experimental companion. It does not implement code, choose architecture, issue a review verdict, maintain a dependency catalogue, or create a durable research report. Use iwadi when the research result should persist independently as a sourced repository record.

Pin the target truth

Establish the question, target library/framework/tool/repository, and the version/ref that controls the answer.

When the question concerns a dependency used by the current project, resolve the effective project version from exact repository/build/package-manager/runtime evidence before consulting upstream source. Do not assume a manifest range, lockfile entry, installed artifact, release tag, or upstream default branch are interchangeable.

Use current upstream head only when the question explicitly concerns latest/unreleased behavior or no versioned target exists. If the controlling version cannot be established, state the gap rather than laundering newer source into an exact-version claim.

Acquire evidence through native capabilities

Use the active host's ordinary repository, provider, package-manager, filesystem, shell, search, and delegation capabilities. Reuse an exact local dependency/source checkout when available; otherwise obtain the narrowest authoritative upstream source needed for the question.

Do not create an Orísun-specific cache, config file, resource registry, service, MCP server, or search runtime. Do not prescribe clone/search commands unless an exact mechanism is required by the host or upstream contract.