AI Disclosures and Agent Registration

This standard governs how the Company discloses its use of AI to the people who rely on it, and how automated agents: the Company's and sellers': are registered before they act on the Platform. It is used by the AI Operations Lead, who maintains the disclosure list; by Product and Support staff, who present disclosures in the services customers and sellers use; and by the Seller Operations function, which registers seller agents and records seller acknowledgements. The governing duties are stated in the Automated Access and Agent Disclosure and the AI Disclosure Policy; this standard states how they are carried out, and does not restate them differently.

Roles and duties

• AI Operations Lead: maintains the authoritative disclosure list and confirms every AI feature appears on it before the feature serves customers or sellers.
• Seller Operations: registers seller agents, verifies enumerated scopes, records acknowledgements, and operates revocation.
• Support: answers "where do you use AI and what do you tell people" enquiries from the disclosure list only, and routes gaps it finds to the AI Operations Lead.

The disclosure list

The disclosure list is the single authoritative answer to where the Company uses AI and what it tells people. Each entry states the feature, what it discloses, where the person sees it, and when the wording last changed. The AI Operations Lead shall maintain the list under the same change control as policy, because it is policy made visible. No AI feature serves customers or sellers until its entry exists. The Pawzly features: conversational reply, product selection, grounding rewrite, and triage: and the classroom tutor are the standing entries, and the disclosures they carry in the product are

1. Identity. The assistant presents as Pawzly, the pet-care helper. It does not present as a veterinarian or as a human staff member, and its governing instructions state its identity and its limits in the same breath.
2. Limits. Every triage-shaped conversation carries the no-diagnosis boundary and the emergency direction: the fixed list of emergency signs: trouble breathing, collapse, seizures, poisoning, bloat, repeated vomiting, blood, inability to urinate: is answered with direction to contact an emergency veterinarian immediately. The customer is told what the service cannot do, not only what it can, in accordance with the Teletriage Disclosure Policy.
3. Accuracy of product statements. The grounding step exists so the assistant never names a product the Company does not sell. Presenting generated output as Company fact where it is not is a disclosure failure, and is filed under AI Incident Handling.

Seller AI agents: registration before operation

An unregistered agent acting for a seller is indistinguishable from fraud tooling, and the standard is applied accordingly, under the Automated Access and Agent Disclosure

1. Registration before operation. No AI agent acts on the Platform: listing tools, pricing agents, buyer-messaging tools: until it is registered and approved. Registration states the operator, the agent's capabilities, its scope (which resources, and which sellers or buyers it acts for), the data it touches, and its level of decision autonomy.
2. Enumerated scopes, least privilege. Anything not enumerated at registration is denied. An agent approved for listing content does not receive pricing. An agent acting for a seller shall not exceed what that seller authorised.
3. Revocable within 60 seconds. Every registration carries a revocation mechanism that the Company, the operator, or the affected seller or buyer can trigger. Stale or unused registrations are revoked on review. Revocation is a protective act, not a penalty; repeated revocations are reviewed under the enforcement provisions of the governing policy.
4. Identification as automated. A buyer-facing agent identifies itself as automated at the start of every interaction. Impersonation of a human is prohibited without exception.

Registration is a written record held by Seller Operations where it can be produced in an incident. The absence of a registration system entry is not a defence: a seller deploying an agent notifies the Company in writing what the agent is, what it touches, and who operates it, before it acts, and Seller Operations keeps that record.

Seller acknowledgements

The acknowledgement record: seller, feature, time acknowledged: is the audit trail of who was told what, and when. Before any seller-facing AI feature is enabled for a seller

1. Present the disclosure text at the point where the seller first uses the AI feature, not buried in onboarding.
2. Require explicit acknowledgement before the feature activates, and record it: seller, feature, timestamp.
3. Acknowledgement is per seller and per feature. Acknowledgement for listing assistance is not acknowledgement for pricing automation.
4. Check the record before enabling the feature. No record for that seller and feature means the feature stays off. This is a gate, not a reminder.
5. Where disclosure wording changes materially, present it again and record a new acknowledgement. The history of what each seller acknowledged, and when, is the evidence of informed agreement.

Automated connections to the Platform

Every connection by which an automated system outside the Company's own services invokes Platform functions or reads Platform data is registered with its scope, its credentials, and its owner: or it does not operate. The Company's own AI services are reached only through the Company's own gateway under Model Inventory and Lifecycle; a credential that cannot be rotated on demand is a connection the Company does not control, and is treated as a defect until corrected.

Controls

The AI Operations Lead shall confirm, before any AI feature launches or changes its disclosure wording, that the disclosure list entry, the in-product disclosure, and the governing policy agree. Seller Operations shall verify quarterly that every operating seller agent has a current registration matching its actual scope, and revoke registrations that do not.

Records

This standard produces the disclosure list with its change history, agent registration records, revocation records, and seller acknowledgement records. Acknowledgement and registration records are retained permanently.

Escalation

An unregistered agent found operating on the Platform is revoked immediately and reported to support@aapawz.com the same day. A disclosure failure served to customers is filed under AI Incident Handling. Questions about the Company's disclosure duties to regulators or partners go to legal@aapawz.com.

Review cadence

The disclosure list is reviewed monthly by the AI Operations Lead, registrations quarterly by Seller Operations, and both are reviewed whenever a new AI feature is proposed.