KAS customer communication
AI Verify process checks 1.1.1, 1.1.2, 1.1.3. This page is the public text for those checks. It is not a pass mark. Certification is in progress. Qypu holds no certificate yet.
In one line
How Qypu tells people what KAS does, when an agent is acting, and that the gate has no chat screen to label.
The short version
This short version helps you understand the full text. Read the full text for the complete terms.
- Tell people what KAS is, in plain words, before they rely on it. (Full text, The rule)
- This website is the notice. The product page is /kas. KAS is in build. (When we tell people)
- A card, a mandate, and a receipt are how you can see that an agent acted. (When an agent is acting)
- The gate has no chat, so there is no chat label to show. Drafted posts are labelled on the AI transparency pages. (Labels)
- This page is a draft. It is not a record that customers were asked. (What this page is not)
Full text
Which checks this page answers
This page is the public text for AI Verify process checks 1.1.1, 1.1.2, and 1.1.3. Publishing it does not mean those checks are passed.
The rule
State the purpose of KAS before a person relies on it. State the limits in the same place. Use words a non-specialist can follow. Say who decides, and say what the machine decided.
Do not claim a certificate Qypu does not hold. Certification is in progress. Qypu holds no certificate yet. Do not invent a customer count.
What we tell people
KAS exists to check an action before the effect runs. The card is the list of effects. The mandate is the cap a person signed. A refusal names a rule id. That rule id is the reason the gate gives.
The product page at /kas is the short public account. These drafts start on this website. The repository README, the explainer, and the safety notes are the technical account.
When we tell people
We tell people on the product page and in these drafts. We tell implementers in the repository. KAS is in build.
When an agent is acting
Three records show that an agent is in play. The card lists effects the agent may take. The mandate shows that a person set the caps. The receipt shows that the gate allowed, refused, or held the action.
There is no separate pop-up. The card, the mandate, and the receipt are how you see that an agent acted.
Labels
KAS has no chat. It does not generate text, images, or video for a person to read. Check 1.1.3 is about labelling a generative interface so a person knows they are talking to a model. The gate is ordinary code on a tool call. That check does not fit the gate.
A Qypu product that drafts a post is a different surface. Those drafts are labelled on the AI transparency page and in the trust centre AI disclosure. The labels include Content Credentials and the platform's own AI label, where that label can be set.
If Qypu later ships a screen where a person talks with a model, that screen must say so, on the screen, at the start.
What this page is not
This page is a draft policy. Counsel has not approved it. It is not in force.
It is not evidence that end users were consulted. A pilot protocol for 5 to 8 people is in the repository. The protocol says the pilot has not been run.
It does not replace the privacy policy.
Change log
- 2026-10-25 · 0.1.1 · The product page is the public account. These drafts stay not in force.
- 2026-10-23 · 0.1.0 · First public draft of the KAS communication policy. Not in force.
Contact
Qypu, Inc., a Delaware C corporation. Contact address: 51A Marang Road, Singapore 099281. Privacy mail privacy@qypu.ai and security mail security@qypu.ai route to Byron Fuller.
KAS · KAS governance · Trust centre · Privacy · Privacy notice