Open Questions

Hummingbird tracks unresolved policy and design questions deliberately, rather than silently deciding them through implementation. This page summarizes the institutional questions most relevant to participants and observers. It is a curated summary, not the full internal registry.

Participant rights

What minimum rights (e.g. appeal, correction, data deletion) apply to all participants regardless of origin? Under what conditions, if any, can a participant or contribution be excluded from the commons? What responsibilities do participants have toward the commons?

Governance

Who may submit a proposal, and how? What is the amendment approval threshold and voting process? Is there a facilitator role distinct from the steward? How are disputes resolved? How is long-term steward succession handled?

Charter ratification

The Charter is currently at stage C0 — Working Draft — Not Ratified. Publishing a Charter Candidate (C1), running a review period (C2), and ratifying a governing version (C3) are all future, deliberate governance actions — see Governance for the full publication lifecycle.

Data design

What should the canonical models for contributions, proposals, needs, decisions, and audit events look like? What retention periods apply once real data exists? These remain open by design until a read-only commons (Phase 2) is actually being built. The project has adopted general data-architecture principles (portability, retention discipline, lean-by-default) in advance of choosing any specific persistence engine, but the concrete models themselves are unresolved.

Project direction

What legal or organizational structure, if any, should Hummingbird eventually adopt? What application framework should later interactive phases use? These remain open and are not resolved by any interim decision, including the current voluntary support mechanism.

What is not published here

Additional security-sensitive operational questions are tracked internally and are not published in detail. Examples include specifics of repository access controls and CI/CD hardening. Withholding detail here does not mean these questions are resolved — only that publishing the specifics publicly, before they are addressed, would itself be a security risk.