Bearer Token Policy

The token is portable. Authorization is conditional.

CREATE SOMETHING .agency issues one managed bearer token per authenticated user for approved hosts, local tools, and background agents. A valid token does not guarantee access unless current policy and entitlement checks pass.

Token
One active token per authenticated user

The token is personal to one user and governed by .agency.

Boundary
Not a raw identity token

The managed bearer token is not a replacement for portal identity or organization checks.

Check
Live entitlement at request time

Membership, policy acceptance, contract status, billing status, and service entitlement are checked before access.

Audit
Issuance and revocation logs

Issuance, regeneration, revocation, and request-time authorization are recorded.

Effective March 6, 2026

User responsibilities are part of the control model.

Bearer tokens are useful because they are managed, revocable, and auditable. They become risky when treated as shared credentials or bypass paths.

Do not share
No shared team tokens

Do not share a personal token with another person, team, repository, or uncontrolled environment.

Store
Use a secret manager

Store tokens in a secure secret manager or equivalent controlled runtime environment.

Rotate
Regenerate on suspected compromise

Regeneration invalidates the prior token immediately unless a managed transition is explicitly provided.

Expect stops
Access can end immediately

Access may stop when a user, organization, contract, billing state, or policy state is no longer in good standing.

Enforcement

Revocation terminates token usability at once.

CREATE SOMETHING may revoke or suspend bearer-token access immediately where compromise, misuse, billing delinquency, contract failure, policy violation, or other legal, operational, or security risk is detected.

Performance system

Make the handoff faster without losing the judgment.

Start with one workflow that still needs manual rescue. We make the owner, allowed actions, approval pauses, and proof record visible before a build expands what automation can do.

Outcome Routine work moves. Judgment stays with the operator.

Evidence can be prepared before review while approval, rejection, and consequential action remain with a named person.

Worked example Marketplace template review

The system prepared 49 of 50 selected evidence packets before a human reviewed the templates.

  1. Map the frictionSee the systems, handoffs, and decision owner.
  2. Test one pathLet routine work move while consequential work pauses.
  3. Keep the proofReview what ran, what stopped, and what needs recovery.