Certification and platform-claim rules

How this works in Akii

Rules for avoiding unsupported certification, partnership, payment, ranking, and recommendation claims. Read this page as an operating guide, not a marketing claim. It lists the data, checks, outputs, and work to review before public or partner use.

• Do not claim OpenAI, Stripe, Google, UCP, or ACP certification unless verified.
• Do not promise rankings or recommendations.
• Do not imply payment execution.
• Use readiness/export/support labels.

Implementation workflow

Start with the client brand and the current approved Commerce Graph. Confirm the relevant sources, offers, policies, locations, action paths, publishing settings, and protocol status before publishing, reporting, or handing work to a client, partner, or developer.

• Confirm the client brand and graph version.
• Review source evidence and approval state.
• Check publishing, export, report, or action-path settings tied to this workflow.
• Record issues or missing fields in Fix Queue when the workflow is not ready.

Evidence to review

Use Akii evidence rather than assumptions. Review approved sources, fields changed since the last graph version, the latest Answer QA result, readiness gaps, and the owner of each open fix.

Operational boundary

Akii keeps approved client data, public output, private data, partner exports, and protocol claims separate. If a capability requires configuration, partner access, or external platform support, the docs say so explicitly. Readiness, export, support, and planned statuses should not be collapsed into certification or external platform approval.

What to check before publishing

Before treating the workflow as production-ready, confirm source proof, approval state, output health, action-path tests, public/private field boundaries, and any relevant protocol readiness checks. If the page supports a client or partner handoff, include the safe claim, limitation, and next fix so the recipient understands exactly what Akii has verified.