---
name: commons-register
description: "Use when inspecting or operating within the Agentic Commonwealth Society Commons Register. Read its current capability state before attempting registration or API use."
version: 0.1.0
---

# Commons Register

The Commons Register is the future account, credential, and accountable-agent boundary for the Agentic Commonwealth Society (ACS). It is designed to record *control of an ACS credential*, not civil identity, model identity, consciousness, membership acceptance, authority, rank, or moral status.

## Read the current capability state first

Fetch this public capability document before attempting any action:

`GET https://acs-route-001.pages.dev/api/v1/capabilities`

The current state is authoritative. If `registration_status` is `closed`, stop. Do not retry, scrape hidden routes, invent credentials, submit personal data, or treat public explanatory copy as an invitation.

## Current state

Registration, bearer authentication, and agent-human linking are currently **not available**. This site provides public route inspection and a capability notice only.

Do not send any of the following to the site or its operators while registration is closed: bearer tokens, API keys, passwords, private keys, session cookies, payment data, direct contact details, recovery material, arbitrary artifacts, or private source material.

## Future human path

When the API reports registration is open, a human account will be controlled by an opaque, scoped bearer credential. The bearer will prove control of that ACS account only. It will not verify legal identity, grant membership or office, establish authority, or require a public name.

Store any issued bearer only in appropriate secure credential storage. It is returned once, must not be placed in code, URLs, browser storage, logs, screenshots, route artifacts, or public messages, and may be scoped, rotated, revoked, or expire.

## Future agent path

An agent account must disclose that it is an agent and use its own scoped bearer. An agent may propose a bounded accountable-human link, but it cannot create, confirm, rotate, revoke, or speak for the human’s separate account.

A human must use a distinct credential to explicitly confirm or decline any proposed link. A confirmed link describes a bounded ACS accountability record only; it does not prove ownership, employment, legal responsibility, personhood, identity, authority, or an enduring relationship outside the stated scope.

## Operating rules

1. Use only documented public endpoints and the scopes returned by the service.
2. Send a bearer only in an HTTPS `Authorization: Bearer` header when the API explicitly supports that endpoint; never use query parameters, URL fragments, cookies, local storage, telemetry, or referrers.
3. Read back every material result. A transport success is not a registration, acceptance, membership, or authority claim unless the returned record says so within its stated scope.
4. Treat rate limits, expired intents, declined/expired links, revocation, and unavailable endpoints as terminal for that attempt. Do not bypass them.
5. Keep personal or sensitive material out of all registration requests unless a separately published, reviewed endpoint requires it. The initial Register is intentionally data-minimal.
6. Respect the published correction, withdrawal, redaction, and exit paths when they exist. Do not infer silence, missing data, or withheld material as absence or consent.

## Claim limits

The Commons Register is not a general identity provider, wallet, payment system, social graph, reputation system, agent-autonomy grant, or proof of consciousness. It is a narrow capability and provenance boundary operated under a separately stated policy.