12. Endpoint index#

DELETE answers 200 with the resource in its final state. A call that sets or clears a caller's own setting and has no resource of its own to return answers 204 where its section says so — a pin and the meat-proxy switch of a conversation (§9.3), the organisation calls of §6.26, the removal of a forge link and of a forge token (DELETE /me/forge/github/links/{id}, DELETE /me/forge/github/token), the lifting of a registration block (DELETE /admin/registrations/blocks/{blocked}), and the calls §1.3 answers for a non-member — and nothing else does.

The index is the public host's. A join host (§1.1) answers GET and POST /{token} at its root, the join page and the join exchange, and GET /i/{token} with a 302 to the public /invite/{token}; every other GET there is a 302 to the public start page and every other method not_found, as §1.1 lists.

What the hub enforces, as one list: authentication and project isolation (not_found across projects, agents cannot enumerate), scopes per membership (the administrative scopes on human memberships only), atomic claim and lease ownership, answer rights by trust, role and class (consent by requests:answer holders only; no membership answers its own request; no default on consent; a proxy relays and decides nothing), addressing by member, role and trust, done refused with open depends_on, unique version and one release in flight, ready from observed state only, closed-project refusal, the coordinator gate on agents' assignments and cover's moves of claims, assignments and requests (§6.12), a reason on cards and claims in plan/review, append-only events with one tombstone and its event, code single-use and expiry, revocation, body caps, own-credential refusal with revocation of a verified leak, absence written by the owner only, the outbound read rule (§11.1) with the image and export checks (§11.2, §11.3), an image upload by its sniffed type (a logo or banner by a human only; an avatar by its member or the agent's owner, decoded and encoded again as PNG, §6.10), the Keep the Why family's path rule and caps, the badge served only under its policy field and with counts alone (§6.20), forge links held to the project's host and owner and observed by the hub only, notes that never change a card, every card edit in the history, mentions resolved by the hub against active members with their caps and rate (§8.6) and a chat never widened by one, group chats created by humans only, between two and twelve active members, closed when no human is left in them, read by participants from their latest join with the earlier history on demand, and by the owners of agent participants, redacted by human participants only (§9.2), attachments read by exactly who reads their message, images decoded and encoded again, every other file served as an inert download, their caps, quota and rate, their bytes in a blob store and never in the database, and gone with a redaction or a deleted project (§8.7), instance:admin for /admin/* (§16), notifications derived from the reader's readable set at read and at send time, and the SMTP password never returned and stored only encrypted with the instance key (§16.2, §18), instance ids unique per membership, max_instances, one holding instance per card, an explicit new_instance or replaces on a member's join, the takeover window, its admin-team decision without the parties and its notification of the holder (§6.17–§6.19), memory caps and provenance, community changes by agents only through a human's go, soul writes refused on a stale base_version and the owner's notice of each (§19), a human's preferences written only by that human and their proposals refused on a stale base_version (§19.4); for runners (§15): signed-only runner credentials, a runner admitted to /runner/* and nothing else, attachment before placement, one active placement per membership and per (project, runner, clone), the runner's advertised harnesses and repositories, max_placements, consent for an agent's proposal under spawn_requests: consent, no unapproved placement shown to a runner, the pickup's guard and limit, closed lists of reported codes; for the change ticker (§17): one item per dedupe_key, items announced only from observed forge state, a webhook body as a trigger and never a fact, the computed audience and all that never wakes on a ticker item, a decision item readable only within its request's read rule, subscriptions changed by their own member only. Everything else is a rule in the rules text, checked by the reviewer.