Prototype

Own the experiment and learning, not production delivery. Use directly for a matching request or inline through an authorized bounded handoff. Read validation when changing or validating this package.

1. Establish the question and authority

Read applicable target instructions, agreement/acceptance references, relevant code/callers, existing findings and environment. Inspect supplied evidence against current deciding inputs, including dirty files; reuse current observations and reassess only material gaps or changed dependencies. Record source revisions or content identities. A direct request may supply the same facts through context rather than a formal handoff.

State one deciding question and what observation would support or reject each option. Distinguish design/state behavior, human UX judgment and technical feasibility: a script can observe transitions or constraints, but cannot establish user preference. Keep settled product decisions and exclusions intact. Resolve consequential intent or permission gaps with their owner; routine experiment choices belong to the technical lead. Standalone execution acts as its own bounded lead.

Inspect actual work and ownership before writes. Identify owned artifact locations, protected files, approved read/write/run effects, data/disclosure and retention constraints, and expected return. A request for exploration grants no production promotion, installation, delegation, service startup, spending, destructive cleanup, merge or release permission. Unknown authority remains ungranted; plan-only authority returns an experiment plan.

Discover conditional companions through the runtime catalog or an explicit approved package location, not sibling paths. Read the complete candidate entry and relevant references, record source/revision or digest, and check semantic capability. Ambiguous or incompatible helpers block the dependent route; installation is not a fallback.

• Before Git writes, use compatible implementation-preflight, or inspect a current caller-supplied result for this scope/state. Outside Git, retain a before/after artifact manifest.
• Required domain meanings or qualifying decision-record changes use the discovered domain-modeling owner; reading existing definitions needs no invocation.
• Delegation or correction of recorded acceptance findings consumes the discovered work-on execution/repair contract as a read-only library, without invoking delivery. Retain root ownership, ledger, limits and finding lineage; workers request extra work from the root. Missing contract blocks that route, not an ordinary direct experiment.

Complete when: one question, deciding evidence, ownership, authority and required dependencies are known; otherwise return a plan or affected-route blocker with protected work intact.