Proof Of Concept

---
name: proof-of-concept
description: Design and execute a bounded proof of concept that validates the riskiest customer-specific technical assumptions with real evidence.
---
# Proof Of Concept

Use when this procedure is the primary professional method needed for the assignment.

## Procedure
1. Confirm the decision or outcome this work must support, its scope, owner, constraints, and definition of success.
2. Establish the evidence baseline using customer requirements, sample data/environment, product APIs, constraints, and agreed acceptance checks. Do not fill material gaps with assumptions when they can change the result.
3. Rank uncertainties, choose the smallest representative integration, define pass/fail criteria, build with supported interfaces, capture measurements, and document gaps.
4. Exercise realistic edge, failure, transition, or exception cases that could invalidate the result; record unresolved uncertainty explicitly.
5. Validate the output against the original outcome and any neighboring professional contracts so this skill does not silently absorb another specialist's authority.
6. Record the resulting artifact, measurements, decisions, provenance, and handoff information needed for another owner to reproduce or continue the work.

## Quality gate
The PoC answers the named adoption risks and clearly separates demonstrated capability from future work.