Profiles
A profile is a reusable authorization template. It defines what an agent is allowed to do — which actions, through which execution paths, under which domain authority — before any attestation is issued. Profiles turn authorization policy into structured, machine-verifiable configuration.
Calendar authority — governs calendar access: reading, drafting, and booking events
Records authority — governs accessing and managing personal structured data
Publishing authority — governs posting public content to social media, blogs, and other platforms
Authority to make an already-built version live. Successor to deploy@0.6, which gated 'build and deploy this commit'; this gates the act of putting something in front of real users, because building is not consequential and going live is. The action is a RELEASE: it activates bytes that already exist, so the human can look at the artifact before approving and no rebuild can diverge from what was approved. Host-agnostic — the artifact identifier is a Vercel deployment id, a container image digest, an Azure slot — named by the connector manifest, never here.
Charge authority — governs charging customers: payments, refunds, subscriptions
Customer authority — governs CRM operations: contacts, activities, deals, tasks
Email authority — governs sending, drafting, and reading email via Gmail
Sales authority — governs quote-to-order in an ERP: draft quotes, send quotes to customers, convert quotes to orders. No invoicing, delivery, payments or master data.
Purchase authority — governs spending company money: subscriptions, supplies, services, advertising
Delegation authority — lets an agent propose changes to its own setup: the agent brief and new mandates. Every proposal waits for a person's approval; nothing takes effect before it. Also lets the agent read the setup guides.
Reporting authority — lets an agent read the evidence a gateway holds (tickets, approvals, mandates, records in the systems it connects) and write one report stored on that machine. Changes no system.
Email authority — governs sending, drafting, and reading email via Gmail
Purchase authority — governs spending company money: subscriptions, supplies, services, advertising
Authority to make an already-built version live. Successor to deploy@0.6, which gated 'build and deploy this commit'; this gates the act of putting something in front of real users, because building is not consequential and going live is. The action is a RELEASE: it activates bytes that already exist, so the human can look at the artifact before approving and no rebuild can diverge from what was approved. Host-agnostic — the artifact identifier is a Vercel deployment id, a container image digest, an Azure slot — named by the connector manifest, never here.
Customer authority — governs CRM operations: contacts, activities, deals, tasks
Customer authority — governs CRM operations: contacts, activities, deals, tasks
Charge authority — governs charging customers: payments, refunds, subscriptions
Publishing authority — governs posting public content to social media, blogs, and other platforms
Customer authority — governs CRM operations: contacts, activities, deals, tasks
Sales authority — governs quote-to-order in an ERP: draft quotes, send quotes to customers, convert quotes to orders. No invoicing, delivery, payments or master data.
Authority to make an already-built version live. Successor to deploy@0.6, which gated 'build and deploy this commit'; this gates the act of putting something in front of real users, because building is not consequential and going live is. The action is a RELEASE: it activates bytes that already exist, so the human can look at the artifact before approving and no rebuild can diverge from what was approved. Host-agnostic — the artifact identifier is a Vercel deployment id, a container image digest, an Azure slot — named by the connector manifest, never here.
Reporting authority — lets an agent read the evidence a gateway holds (tickets, approvals, mandates, records in the systems it connects) and write one report stored on that machine. Changes no system.
Customer authority — governs CRM operations: contacts, activities, deals, tasks
Purchase authority — governs spending company money: subscriptions, supplies, services, advertising
Email authority — governs sending, drafting, and reading email via Gmail
Authority to put software live. Successor to deploy-gate@0.2, HAP's first profile — renamed because the old id is bound to a structure (flat frame, disclosure_hash) that no longer exists. Deliberately host-agnostic: every deployment system has something to deploy, somewhere to put it, a rate worth capping and a notion of undo. Provider vocabulary (GitHub 'environment', Vercel 'target', Netlify 'context') lives in the connector manifest, never here.
Email authority — governs sending, drafting, and reading email via Gmail
Authority to make an already-built version live. Successor to deploy@0.6, which gated 'build and deploy this commit'; this gates the act of putting something in front of real users, because building is not consequential and going live is. The action is a RELEASE: it activates bytes that already exist, so the human can look at the artifact before approving and no rebuild can diverge from what was approved. Host-agnostic — the artifact identifier is a Vercel deployment id, a container image digest, an Azure slot — named by the connector manifest, never here.
Calendar authority — governs calendar access: reading, drafting, and booking events
Sales authority — governs quote-to-order in an ERP: draft quotes, send quotes to customers, convert quotes to orders. No invoicing, delivery, payments or master data.
Records authority — governs accessing and managing personal structured data