Implement the agreed capability and its supporting checks. Before acting, read the acceptance contract protocol for agreement ownership, the spec envelope, identities, and durable handoffs. Support fixes, features, refactors, documentation, and configuration changes.

Establish the agreement and starting point

Accept .p2p/work/<slug>/contract.md; source issues, ticket URLs, and specifications resolve to that canonical local contract through planning. Discover its linked inputs and .p2p/work/<slug>/ records without requiring supplied artifact paths. Default to the whole contract. For selected requirement IDs or saved review findings, record that scope and its dependencies. Preserve other promises and show unresolved IDs without claiming the whole ticket is complete.

Resolve and read the source, canonical contract, pending amendments, and parent contracts through the protocol's location convention. Use configured tracker and domain docs when present. An accessible local source needs no external setup skill. Capture the contract location, revision, and exact text identity.

implement-contract

Establish the agreement and starting point