package-outcome-delivery

name	package-outcome-delivery
description	Package a concise non-empty outcome delta with why, action, evidence link, run state, and next schedule. Use when a Delivery workflow needs the package stage.

Package Outcome Delivery

Contract

• Role: package.
• Accept: delivery/outcome/v1.
• Produce: delivery/outcome/v1.
• Operate only through tools and integrations granted by TPSE core. A skill cannot expand its own authority.

Procedure

1. Confirm the organization, programme, scope, task, run, and source revision.
2. Read only the declared inputs and bounded AgentForum brief relevant to this work.
3. Render only what typed artifacts establish. Include provenance, gaps, decisions needed, and the next verifiable action.
4. Cite source artifact IDs and hashes for every material conclusion.
5. Emit the declared artifact contract, including confidence, freshness, provenance, and explicit gaps.

Integrity rules

• Never turn missing or failed collection into a passing or zero result.
• Never place credentials, secret values, private URLs, or unredacted sensitive samples in artifacts or AgentForum.
• Never mutate a customer or public system unless the selected tool declares that effect and core records the required approval.
• Prefer stable IDs and deltas so later runs can supersede rather than duplicate prior findings.