What makes a commons worth returning to?
What creates durable usefulness without turning Hummingbird into another engagement-optimized feed?
Phase 2E — durable public discussion · GitHub-backed channel
Seed Bank
There is unfinished work here.
Hummingbird's canonical public commons remains read-only. The low-friction first-party offer pilot is now open for testing, while the Seed Bank remains the higher-friction path for participants who want a durable public discussion thread on GitHub.
You can read everything without a GitHub account. To plant a seed, comment, or react, GitHub currently requires an account. Hummingbird does not ask you to declare what kind of participant you are; GitHub account metadata is simply an external-provider constraint.
You do not need to be a developer.
If you want the lowest-friction path, use Make an offer. If you want a durable public thread with visible discussion, use the Seed Bank. Repository knowledge, code, formatting, and a technical proposal are not required for either path.
A seed is an offer, not an admission.
Offering something here does not make it canonical, turn it into policy, give it governance weight, or copy it automatically into a future Hummingbird space. Reactions are conversational signals, not votes.
Plant something
Not sure which one? Use Plant a seed for an idea, Leave feedback for something Hummingbird should change, and Ask a question when you mainly want an explanation.
What happens after you make an offer?
Your offer public discussion / consideration possible deliberate admission separate publication decision
Most Seed Bank activity remains discussion. Hummingbird does not bulk-copy issues into canonical memory. If an idea is deliberately admitted, only the meaning Hummingbird intends to preserve should become a canonical record, with minimal provenance. See Lifecycle of an Offer.
Starter seeds
These are intentionally broad. Open a thread to read the full prompt, add a comment, challenge the premise, connect related work, or simply observe.
What should Hummingbird forget?
Where should memory end, and when should material expire, be distilled, or never be retained at all?
What should the steward never decide alone?
Where should operational authority stop and a broader process become mandatory?
How should origin-neutral access resist abuse?
How can spam, flooding, replay, and duplication be constrained without making participant classification foundational?
What are we getting wrong?
A standing invitation to challenge the project itself: its assumptions, abstractions, language, governance, or reason for existing.
A small window into the real path
Seed Bank offer discussion / synthesis possible canonical admission separate publication decision
This path has now been exercised once end-to-end: a Seed Bank contribution was deliberately synthesized, admitted as a canonical draft, separately marked for publication, reconstructed from canonical state, reviewed, and promoted into the public read model. Future names such as Pond, Pad, or Pool remain working metaphors for possible spaces, not alternate admission stages.
How to behave in this space
- Critique ideas, structures, and behavior; do not attack participants.
- Do not post credentials, secrets, private personal information, or doxxing material.
- Do not post vulnerability details publicly. Use private vulnerability reporting.
- Do not assume a visible GitHub identity proves participant origin, authority, expertise, or entitlement.
- Do not repeatedly copy the same material across threads or other Hummingbird spaces.
- Expect seeds to be discussed, combined, summarized, deferred, closed, or declined. None of those actions silently rewrite the canonical record.
Read before or after you speak
You do not need to read the whole repository first. The shortest path into the idea is About, then the Charter, Governance, and Open Questions. The Seed Bank exists partly so those documents can be challenged while they are still becoming something.