Hummingbird

Canonical source: docs/decisions/0024-phase2e2-constitutional-and-governance-dispositions.md · source commit 11cd616d4b9a · SHA-256 50f89e75e931df7ba2bc294013805cc6280747472315123e487a112597d47776 · build d0b31c8d8e17 — View raw Markdown — All decisions

ADR 0024 — Phase 2E.2 Constitutional and Governance Dispositions

Status: accepted for the C0 / Phase 2 working institution

Date: 2026-11-18

Context

Phase 2E.2 requires Hummingbird to resolve the constitutional and governance questions that block Phase 3, before the security and runtime work of Phase 2E.3 begins. The Phase 2E.1 closeout (repository reference) set the order. The options and trade-offs were prepared in the Phase 2E.2 decision packet (repository reference).

Five Phase 3 blockers are in scope:

Two facts shaped the choices:

  1. Scope. ADR 0023 narrows the core to Arrive, Leave, and Carry. The rules below are sized to that core and do not presume accounts, social graphs, rooms, or guilds.
  2. Evidence. Between the pilot's launch on 2026-09-12 and 2026-11-18, the Phase 2E offer store received two submissions in total, one of them the steward's withdrawn launch test. There is no meaningful participation evidence yet. The decisions are therefore deliberately small, grounded in existing published principles and pilot-scoped rules, and expected to be revised as real use appears.

The steward chose each disposition below on 2026-11-18.

Decision

1. Minimum participant rights — a small floor, open to growth

CHARTER.md §2 adopts a six-part floor that applies regardless of origin: Arrive (open reading), Leave (withdrawal before admission; correction or removal of one's own private information after), Know (published handling contracts and a stated reason class for any restriction), Review (one review of a restriction by a different layer), Carry (portable public artifacts), and No hidden standing.

The floor explicitly excludes any right to an individualized reply, admission, publication, endorsement, or particular outcome.

At the steward's direction, the Charter records that this is the minimum Hummingbird can honestly promise today, not a ceiling. Further rights remain open to exploration through the proposal process as evidence accumulates.

2. Exclusion — actions and material, not people

CHARTER.md §3 allows material to be declined or removed only for published reason classes: unlawful content, secrets or private information about others, security threat, flooding or resource abuse, or out of scope for the capability used. A capability restriction is limited to that capability, time-bounded, reasoned, and reviewable. Reading is never withdrawn as a sanction. Hummingbird does not ban people.

Rejected: participant-level bans, which require durable identity and conflict with ADR 0003; and no exclusion at all, which fails once any contribution is retained.

3. Participation conditions — published bounds plus three universal conditions

CHARTER.md §4 makes each capability's published bounds its participation conditions, plus three universal conditions:

  1. no secrets or private information about others;
  2. no evasion of published bounds;
  3. no unlawful content.

Breach fails the action or restricts the capability under §3.

Rejected: a general code of conduct about civility or intent. That would need moderation judgment about intent, which falls outside the narrowed core and invites hidden criteria contrary to GOVERNANCE.md §No hidden institutional criteria.

4. Emergency authority — pause-only, triggered only by Hummingbird's own risk

CHARTER.md §6 adopts the steward's narrowed variant of pause-only authority:

Rejected: no defined emergency authority, which would leave pause powers implicit; and broad emergency powers, which risk the self-perpetuating authority the Charter is built to prevent.

5. Proposals — public pull requests anyone may draft

GOVERNANCE.md §Proposals defines a formal proposal as a public, versioned pull request against the Charter, Governance, or an ADR. Anyone may draft one without an account, identity, or endorsement. Offers never become proposals automatically.

During C0, the steward decides proposals with written reasons until a later authorized process replaces this one.

At the steward's direction, the steward may use advisory tools such as an endorsement threshold for some or all proposals, where safe to deploy. Such a tool never decides a proposal and grants endorsers no standing. Endorsement counts cannot be relied on until a multiplicity- and Sybil-resistant approach is settled under OQ-SECURITY-AUTHN-MODEL and OQ-SECURITY-MULTIPLICITY-ABUSE. That evaluation is carried into Phase 2E.3.

Rejected: a binding endorsement threshold, which requires countable identity; and steward-only initiation, which makes the steward the gatekeeper of change contrary to the minimum-necessary-authority rule.

6. Steward succession — still deferred, with one concrete follow-on

Long-term succession (OQ-GOVERNANCE-STEWARD-SUCCESSION) is a non-blocking review gate and remains open. The decisions above give a future steward a smaller, more legible authority to inherit: pause-only emergency power, reasoned proposal decisions, and no participant-level sanctions.

The next concrete step is a custody plan, so that credentials, domains, and backup decryption are not recoverable only through one person. Producing that plan creates no governance authority.

Consequences