Skip to content
TastePolicy.Open workspace

SUBJECTIVE AUTHORITY INFRASTRUCTURE

Knowing your taste
isn’t permission.

Give AI agents a clear boundary between what you might like and what they’re allowed to choose.

Qloo gives agents taste.
TastePolicy gives that taste authority boundaries.

AUTHORITY CARDInteractive example · no live decision

ALLOW

Within your boundary

Requested action
Shortlist a culturally aligned stay
Agent / subject
Travel assistant / example owner
Candidate / context
Example cultural stay / weekend discovery
Qloo cultural evidenceIllustrative affinity signalAffinity is not authorization.
RequestedSHORTLIST
Your ceilingSHORTLIST

The reviewed cultural match and the requested action fit the example policy. Continue only with a shortlist.

Receipt: illustrative only · Lease: not issued · Proof: not issued

No payment, booking, messaging, account or legal authority. A verified proof does not grant permission.

Memory is not permission.

Affinity is not authorization.

Verification is not authorization.

THE BOUNDARY

Your taste.
Your rules.
Any agent.

01 / UNDERSTAND

Cultural evidence, from Qloo.

Reviewed signals across music, film, books, brands and places ground a candidate in cultural intelligence.

02 / DECIDE

Authority, from your rules.

Set the action ceiling. Keep exclusions absolute. Ask for missing facts. Never turn an unavailable provider into permission.

03 / PROVE

A receipt for the boundary.

Inspect the evidence and policy behind a decision. Bind short leases and portable proofs to the choice, context and authority epoch.

ONE CONTRACT. MULTIPLE DOORS.

A boundary your stack can use.

REST, OAuth, remote MCP, A2A and a TypeScript client share the same cultural authority contract.

RESTMCPOAuthA2APortable proofs
Start with the developer guide →

Live ChatGPT and Claude commissioning is pending. Protocol support is not platform approval.

TASTE IS PERSONAL. AUTHORITY SHOULD BE EXPLICIT.

Let your agents know
where to stop.

Open your workspace ↗Inspect the trust boundary →