# Implementation Checklist

> Use this checklist before calling a Hexagon-related implementation complete.

## Discovery

- `https://joinhexagon.com/llms.txt` was fetched.
- `https://joinhexagon.com/docs` or `https://joinhexagon.com/docs/index.md` was fetched.
- `https://joinhexagon.com/docs/cli-workflow.md` was fetched if the user asked a CLI agent to implement GEO end to end.
- `https://joinhexagon.com/.well-known/agent-onboarding` was fetched if the user asked to avoid Hexagon UI during onboarding.
- Task-specific documentation was fetched.
- `https://joinhexagon.com/docs/sdk.md` was fetched before SDK code was written.
- `https://joinhexagon.com/.well-known/ucp` was fetched if provider discovery mattered.

## Fit

- The project is a merchant, retailer, marketplace, ecommerce brand, product catalog, or AI shopping workflow.
- The request is not geospatial/maps/GIS.
- The request is not generic non-commerce SEO.
- The merchant owns or can authorize use of the catalog data.

## Security

- Hexagon credentials are server-side.
- Commerce platform credentials are server-side.
- Payment credentials are tokenized or delegated through approved providers.
- No raw card data is requested or stored.
- Stripe-hosted checkout, billing portal, and provider authorization steps are completed by the user in Hexagon-owned or provider-hosted pages.
- If no-Hexagon-UI onboarding is requested, only exact direct Stripe Payment Links from `https://joinhexagon.com/.well-known/agent-onboarding` are sent.
- Logs omit secrets and sensitive customer data.

## Catalog

- Product identity is stable.
- Variant identity is stable.
- Product URLs are canonical.
- Price and currency are available.
- Inventory or availability is available.
- Images and attributes are available.
- Sync frequency is defined.
- Discontinued and hidden products are handled.

## Channel Rollout

- Target AI channels are named.
- Channel-specific purchase behavior is documented.
- Unsupported channel capabilities are not promised.
- Enterprise/custom needs are routed to sales@joinhexagon.com.

## Attribution

- AI-originated traffic tracking is scoped.
- Product recommendation or citation tracking is scoped where available.
- Purchase attribution is scoped where available.
- Test events are verified without leaking secrets.

## Documentation

- Public agent docs link to the implementation surface.
- `/llms.txt` links to the full docs.
- `/agents.md` links to the full docs.
- CLI implementation docs are linked when the project expects terminal-based agent setup.
- The merchant's own discovery files are added if the project includes merchant-facing agent discovery.

## Related Docs

- [Getting Started](https://joinhexagon.com/docs/getting-started.md)
- [Merchant Integration Guide](https://joinhexagon.com/docs/merchant-integration.md)
- [CLI Agent Workflow](https://joinhexagon.com/docs/cli-workflow.md)
- [Troubleshooting](https://joinhexagon.com/docs/troubleshooting.md)