# Portable contribution and knowledge contract

This is a plain-file record shape; it creates no runtime authority or sending permission.

## Contribution

- outcome and accountable owner
- source locator/revision and approved inputs
- allowed actions/resources and explicit restrictions
- performer, intended recipient, request basis, and deadline if real
- current state: drafted, requested, accepted/declined, executing, result supplied, verified
- transport receipt separate from explicit acceptance and result evidence
- dependency, blocker cause, recovery, and next authorized action

## Attributed claim

- exact quote or faithful paraphrase and speaker/source revision
- basis: observation, report, inference, or proposal
- every material qualifier and scope restriction
- confidence as self-report; verification state separately
- limitations and evidence locators exactly as supplied
- status: proposed, accepted, rejected, superseded; authority and revision of any adoption

Do not turn “I think X; not tested” into “X is approved.” A transport acceptance status is not task acceptance. Preserve old text when correcting: append the proposed replacement, reason, evidence, reviewer decision, and version links.

The retained collaboration source docs describe transport/provider interfaces, not a new obligation to install them. Provider implementations belong to the separately routed Team Access tool. Good Teammate supplies judgment and carries the same contract over an already authorized transport or local file.