# Document an API or codebase — acceptance checklist

Record evidence for every checked item. Unchecked or untested is not a pass. This checklist does not execute an integration or authorise external actions.

## Required inputs

- [ ] A fixed source revision and the intended reader.

- [ ] The API or library versions used by the project.

## Output checks

- [ ] Every endpoint, option and default maps to the chosen source revision.

- [ ] External references match the installed library version or name the mismatch.

- [ ] Examples are run with an authorised runner or explicitly marked untested.

- [ ] A fresh reader can identify prerequisites, expected output and recovery from an error.

## Deliverables

- [ ] Versioned API inventory

- [ ] Task-oriented documentation draft

- [ ] Example execution receipts

- [ ] Unverified-claim ledger

## Evidence and decision

Evidence links: [fill in]
Untested paths: [fill in]
Unresolved findings: [fill in]
Reviewer: [fill in]
Decision and scope: [fill in]

## Boundaries

- Choose a host for each stage and verify its tool mapping. Pass evidence explicitly between stages; the listed resources do not automatically configure or invoke one another.

- Context7 supplies reference material; it does not establish what your own application actually implements.

- The agent definition may need host-tool adaptation. Review the upstream skill’s current licence and terms before redistribution.

Workflow: https://undominated.ai/workflows/#document-an-api