Maintain the collection-owned analysis method

Type: types/instruction.md

Keep analysis method edits executable and update every affected consumer.

Consumption and authority

The method author loads this instruction before an applicable edit, together with the owning collection and selected instruction/type-spec contract. The collection contract supplies this mandatory route to method authors. Before changing analysis code, worker instructions, report contracts or publication design, read the analysis design brief for the operator's goals and evaluation priorities. Treat it as design intent, not a replacement for adopted execution contracts.

Analyst job packets load neither this instruction nor the design brief. This instruction grants no mutation authority beyond the commissioned edit.

Composition

Use executability and precision as the quality goal. State goal, authority, inputs, result, acceptance and stop conditions. Keep the goal first and retain reasons only when an edge case needs them. Put transferable explanations in notes. Use imperative instruction titles and trigger descriptions. Plain procedures use the instruction type; shared definition contracts may use the note type.

An instruction is complete for its declared consumption path. Inherit doctrine, collection/type contracts and skills only when the runtime supplies them with binding force. Carry exceptions explicitly. Give delegated packets purpose, consequential choices, authority, inputs, owned output, coordination, acceptance and return conditions beyond the verified baseline. Delegation grants no extra authority; scheduling, integration and recovery remain with the parent. Unstated consequential choices follow an inherited default, deliberately delegated judgment from evidence, or return as a gap. Use clean context for a named benefit.

Editing and verification

Name each consumer and its loading channel before changing a rule. Search this collection and generic instructions for exact filenames, skill names and result literals. Read direct callers, callees, conditional loads and argument/result consumers. Update affected interfaces together or report the unresolved mismatch. A changed inherited rule reopens the packets commissioned against that baseline.

Execution does not depend on incidental link following. Instruction links provide context transfer, conditional deviations or maintainer context; keep chains shallow and never add reciprocal links only to mirror an edge. Search local method/types and generic instructions, notes, reference and tags as needed. Workflow execution inputs enter through declared dependencies. Do not make reviews, archives or workshops execution inputs.

For run evidence records and failed-run retention, follow the collection contract. Do not make audit files workflow execution inputs.

State each rule once, in its owner (ADR 117): a member type owns its member's content, the record contract the shared record grammar and evidence rules, the worker rules execution, and a mission what its job establishes. Keep a second statement only when it adds an obligation, a specialization or a delivery path the first lacks; an interface stated from both sides, grammar beside its procedure, a prompt binding beside its definition, and a template's headings are not duplicates. Before moving a clause, confirm every consumer receives its new home; the instruction composition tests check that each worker reading a type that defers to the record contract receives it.

Edit canonical instructions. Inspect projection, promotion and stub generation when names, skill metadata or promotion status change. Test the affected loading, authority, validation and result paths. Commit method changes before a new run; never rewrite the opening method commit of an existing run.

Vocabulary dependencies

When a registered definition changes, recheck that the supplied record contract still gives workers what they need without following background links:

• Theory builder: localized content, consumption, criticism and iteration remain independently evidenced.
• Addressable theory: individual inspection and revision are graded and boundary-relative.
• Representational form: encoding and consumer rules remain separate from substrate and prompt supply.
• Explanatory-reach: explained transfer remains accountable to fit and premise variation.