Outcome Contract
Return the shortages and deltas of the common records that the caller needs. The root of the authoritative package iscore_result. Supported mode: internal.
Reference Routing
- On the first occasion, read
skills/mino-core/references/shared-policies.mdand apply Evidence, approval, and judgment. If already read, do not reread. - If organizing the problem and meaning is necessary, verify the input with the Workflow in
skills/mino-problem-framing/SKILL.md. The public problem definition request is handled by$mino-problem-framing. - For requirements and trace, read
skills/mino-core/references/requirements-and-traceability.md; for terminology discovery, readskills/mino-core/references/domain-discovery.md; for the quality catalog, readskills/mino-core/references/quality.md; and create only this occasion's delta. - For execution of the target system's files/processes/tests and multi-OS requirements, read
skills/mino-core/references/platform-compatibility.md, and record the environment and unexecuted scope. Do not perform additional reading merely to save a record of an answer. - Only when an authoritative package is necessary, read
skills/mino-core/schemas/core.md, and create the necessary records for the Problem Frame, Context Packet, meaning verification, and Selection Gate.
Workflow
- Verify the caller's artifacts, mode, target revision, scope, and approval.
- Reference and reuse existing Evidence, and investigate only the shortages that would change the judgment.
- If the shortages cannot be resolved, leave the identification conditions, verification method, and owner, and return dependent judgments and the current artifact separately.
Hard Gates
- Do not redefine the authority or IDs of specialized artifacts. Return uncreated downstream items to the caller as obligations.
- Do not push missing required content of the current artifact or missing trace onto problems in a later phase and hide them.
Completion
Return the necessary common records, grounds, meaning deltas, undecided choices, and whether the next operation is possible. Distinguish completion of design from completion of verification and adoption.