Action Catalog

What do you want to authorize?

Software and AI can prepare the work. AtlaSent controls the consequential action: it decides deny, hold or permit before the action executes, and only a permit bound to that exact action can go ahead.

Prepared work, and the action AtlaSent controls.

Actor+Action+Resource+Context+Authority requirements+Evidence→DENYHOLDPERMIT

Work AI or software can prepareConsequential action AtlaSent controlsCanon
Draft an agreementSign agreementCanonical action identity.sign
Complete an applicationSubmit applicationCustom action today
Find availabilitySchedule appointmentCustom action today
Draft correspondenceSend messageCanonical action communication.external.send
Prepare an orderPlace purchaseCanonical action workflow.approve
Reconcile an invoicePay invoiceCanonical action finance.payment.authorize
Prepare a transferMove moneyCanonical action finance.wire.transfer
Analyze a refundIssue refundCanonical action finance.payment.authorize
Prepare a filingSubmit filingNearest canonical action compliance.certify
Generate contentPublish externallyCanonical action content.publish
Evaluate a userGrant accessCanonical action access.grant
Prepare recordsRelease dataCanonical action data.export
Generate or change codeDeploy productionCanonical action production.deploy
Prepare infrastructure changeChange infrastructureCanonical action infrastructure.change
Determine an emergency actionUnblind / overrideCanonical action trial.unblinding.emergency control.override
Anything else your systems or AI prepareCustom actionDefine your own

A listed action is one AtlaSent can govern. It is not a claim that a native connector exists for the system that executes it: your system calls AtlaSent at the commit point, from the GitHub Action, the TypeScript or Python SDK, the REST API or the MCP server. “Canonical action” means a published Canonical Action Record governs it; “nearest” means you confirm the closest record fits; “custom action today” means no record exists yet and you define it.

Six steps from choice to enforcement.

  1. 1Choose an action

    Pick the consequential action AtlaSent should protect.

  2. 2Connect the system that executes it

    Put the AtlaSent check at the commit point: the step, call or tool that actually performs the action.

  3. 3Define who or what has authority

    Who may act, who must approve, which duties stay separate, and under what conditions.

  4. 4Test a denial

    Send a request your rules should refuse and confirm the action does not run.

  5. 5Test authorization

    Send a request your rules should allow and confirm the permit verifies where the action executes.

  6. 6Go live

    Turn on enforcement for that execution path, and keep every other path visible until it is covered.

A denial and an authorization are both tested before go-live. An allow is not proof the action ran; the permit is verified where the action executes, and execution is recorded only when it is observed.

Who acts, on what, under whose authority.

Sign agreement

Affixing a legally binding signature to a contract or regulated record.

Prepared work
Draft an agreement
Actor
A named signatory
Resource
The agreement and its version
Context
Counterparty, value, jurisdiction
Authority
Signing authority for this value; MFA
Evidence
The approved draft and its hash
Commit point
The signing call in your contract or e-signature system.
Canon
identity.sign CANON-000011

Signing is a human act by design. Software or AI can prepare the agreement; a verified person signs it.

Submit application

Submitting a completed application to an outside party on the organization's behalf.

Prepared work
Complete an application
Actor
Applicant, staff member or agent
Resource
The application and its attachments
Context
Recipient, deadline, program
Authority
Who may submit for the organization
Evidence
The reviewed application content
Commit point
The submit call to the receiving portal or API.

No Canonical Action Record yet. A submission action (submission.submit) is proposed to the Canon and not yet decided. Protected as a custom action until then.

Schedule appointment

Booking time that commits a person, patient, customer or resource.

Prepared work
Find availability
Actor
Scheduler or agent
Resource
The calendar, room or clinician
Context
Who is booked, when, for what
Authority
Who may commit this person's or resource's time
Evidence
The request the booking answers
Commit point
The booking call in your scheduling system.

No Canonical Action Record. Scheduling is proposed to the Canon with a recommendation not to make it a Canon action, since the consequence usually belongs to another action. Protected as a custom action.

Send message

Sending a message outside the organization, which cannot be recalled once sent.

Prepared work
Draft correspondence
Actor
Sender or agent
Resource
The message and attachments
Context
External recipients, data classification
Authority
Who may send this content to this recipient
Evidence
The approved message and its hash
Commit point
The send call in your email or messaging system.
Canon
communication.external.send CANON-000047

The permit is bound to the exact recipients and content. Change either and it needs a new decision.

Place purchase

Committing the organization to spend with a supplier. The governed act is the approval that authorizes the order.

Prepared work
Prepare an order
Actor
Buyer or agent
Resource
The order
Context
Supplier, amount, cost center
Authority
Spend limit and required approvers
Evidence
The quote or requisition
Commit point
The order submission in your procurement system.
Canon
workflow.approve CANON-000003 · runs as purchase.approve

Governed as the approval that authorizes the order: the Canon classifies it as workflow.approve, and it runs as its own action, purchase.approve, with its own policy.

Pay invoice

Releasing payment against an invoice.

Prepared work
Reconcile an invoice
Actor
AP clerk, workflow or agent
Resource
The payment
Context
Payee, amount, account
Authority
Two-person approval above your threshold
Evidence
The reconciled invoice and match record
Commit point
The payment release in your ERP or payments system.
Canon
finance.payment.authorize CANON-000021

The person who initiates the payment cannot be the person who approves it.

Move money

Sending funds by wire or equivalent transfer.

Prepared work
Prepare a transfer
Actor
Treasury staff or agent
Resource
The transfer
Context
Beneficiary, amount, currency, account
Authority
Required approvers and separation of duties
Evidence
Beneficiary verification and the approved instruction
Commit point
The transfer instruction to your bank or treasury system.
Canon
finance.wire.transfer CANON-000022

The permit is bound to the amount, beneficiary and account that were authorized.

Issue refund

Returning money to a customer.

Prepared work
Analyze a refund
Actor
Support agent, workflow or AI agent
Resource
The refund
Context
Customer, amount, original charge
Authority
Refund limit and who may approve above it
Evidence
The refund analysis and the original transaction
Commit point
The refund call in your billing or payments system.
Canon
finance.payment.authorize CANON-000021 · runs as customer.refund.issue

The Canon classifies a refund as a payment authorization. It runs as its own action, customer.refund.issue, so its policy is set separately from invoice payments.

Submit filing

Submitting a regulatory, tax or legal filing that carries a certification.

Prepared work
Prepare a filing
Actor
A qualified certifier
Resource
The filing
Context
Agency, period, entity
Authority
Who may certify and submit for this entity
Evidence
The reviewed filing and its supporting records
Commit point
The submission to the regulator's or agency's portal.
Canon
compliance.certify CANON-000017

Nearest Canonical Action Record is compliance certification, which requires a qualified person. A separate submission action (submission.submit) is proposed to the Canon and not yet decided; until then, filings with no certification are protected as a custom action.

Publish externally

Making content public or sending it to an outside audience.

Prepared work
Generate content
Actor
Author, marketer or agent
Resource
The content and its version
Context
Channel, audience, embargo
Authority
Who must approve release on this channel
Evidence
The approved version and its hash
Commit point
The publish call in your CMS, social or campaign tool.
Canon
content.publish CANON-000010

AtlaSent decides whether the release is authorized. It does not review the copy.

Grant access

Giving a person, service or agent access to a system or data.

Prepared work
Evaluate a user
Actor
Admin, workflow or agent
Resource
The role or entitlement
Context
Grantee, scope, duration
Authority
Owner approval for this entitlement
Evidence
The access request and its justification
Commit point
The grant in your identity provider or target system.
Canon
access.grant CANON-000007

The grantee and the approver are kept as separate identities.

Release data

Exporting or sending records outside the system of record.

Prepared work
Prepare records
Actor
Analyst, pipeline or agent
Resource
The dataset
Context
Destination, fields, residency, consent
Authority
Data owner approval for this destination
Evidence
The request and the approved field list
Commit point
The export or transfer job that moves the records.
Canon
data.export CANON-000028

A separate data release action is proposed for the Canon and not yet minted. Data export governs releases today.

Deploy production

Releasing a change to production.

Prepared work
Generate or change code
Actor
Pipeline, engineer or agent
Resource
The service and environment
Context
Repository, commit, change plan
Authority
Required reviews and separation of duties
Evidence
The reviewed change and CI results
Commit point
The deploy step in your pipeline.
Canon
production.deploy CANON-000001

The permit is bound to the repository, commit and environment. Change the commit and it needs a new decision.

Change infrastructure

Applying a change to cloud or on-premises infrastructure.

Prepared work
Prepare infrastructure change
Actor
Pipeline, operator or agent
Resource
The account, cluster or stack
Context
The reviewed plan, change window
Authority
Who may approve changes to this environment
Evidence
The plan artifact and its digest
Commit point
The apply step, for example terraform apply, in your pipeline.
Canon
infrastructure.change CANON-000033

The permit is bound to the reviewed plan. A different plan needs a new decision.

Unblind / override

Breaking a blind or overriding a safety or security control in an emergency.

Prepared work
Determine an emergency action
Actor
Investigator or on-call responder
Resource
The subject's allocation or the control
Context
The emergency and its justification
Authority
Who may break the blind or override this control
Evidence
The justification and the risk assessment at the time
Commit point
The unblinding or override function in the system that holds the control.
Canon
trial.unblinding.emergency CANON-000020
control.override CANON-000009

Two Canonical Action Records: emergency unblinding in a clinical trial, and a control override elsewhere. Both require a verified person.

Custom action

Name the action, point AtlaSent at the system that executes it, and write the authority rules. The same model applies: actor, action, resource, context, authority requirements and evidence, decided as deny, hold or permit.

Start with one action from the catalog.

Authority Launch proves one consequential action in production: we find the commit point with your team, configure your requirements, prove a refusal and a valid run, and prepare a separately authorized production activation. Then expand into an annual Enterprise agreement.