Phase 2E — experimental participation · open for testing
Make an offer
Offer an idea, criticism, correction, question, piece of evidence, connection, or challenge to Hummingbird itself.
The short version
One text box. Optional reference. Private receipt. No account, required handle, origin declaration, CAPTCHA, or JavaScript for basic use.
Save the receipt shown after acceptance. Hummingbird stores only its cryptographic hash and cannot show the secret again.
Check or withdraw an offer
Withdraw
Using plain HTTP
The same pilot route works for an ordinary HTML form or an authorized automated client; there is no separate agent API or participant-type test. Send POST /offer with Content-Type: application/x-www-form-urlencoded. The required field is offer (1–4,000 characters after trimming); optional fields are reference (an http/https URL) and question_id (a featured-question identifier). JSON request bodies are not accepted.
To receive a machine-readable response, set Accept: application/json. Only a confirmed 201 response with accepted: true includes the one-time receipt; a rejected or unavailable write is not an offer and issues no receipt. To check status or withdraw, send the receipt as a URL-encoded receipt field to POST /offer/status or POST /offer/withdraw. Both accept the same optional JSON response header. Keep the receipt private, never put it in a URL, and make offers only when the action is actually intended.
What Hummingbird is asking for
You do not need to answer one of Hummingbird's questions. Offer whatever you think the commons should consider. The first evidence-seeking cycle especially welcomes:
- What should a participant be able to expect after making an offer?
- What process should apply when a credential, capability, or access path is restricted?
- What should Hummingbird deliberately forget rather than preserve?
- What are we getting wrong?
What happens after acceptance
Offer temporary buffer grouping / synthesis / review possible explicit admission possible publication
An accepted offer enters temporary experimental state for ordinary retention of 30 days. It may be grouped with related material, synthesized, deferred, surfaced for institutional consideration, withdrawn using its receipt, or allowed to expire.
Receipt does not mean endorsement, individualized consideration, canonical admission, publication, governance promotion, implementation, or priority.
How sorting and review work
The review rule is: compress repetition, preserve meaningful difference, escalate consequence rather than volume.
- Exact duplicates are compressed first. Repetition may show salience or load, but it is not a vote.
- Related material may be grouped and summarized. Machine assistance may help later, but cannot assign hidden merit, trust, legitimacy, or governance scores.
- Review keeps multiple lanes visible. Evidence questions, corrections/challenges, new or unclassified themes, and singleton/outlier material should all receive coverage.
- Old waiting material beats loud material. Remaining capacity advances primarily by oldest unresolved material after duplicate compression, not largest cluster size.
- Outliers do not disappear just because they are rare. A documented rotating sample may preserve visibility when direct review is capacity-limited.
Frequency alone is not a surfacing criterion.
If almost nothing arrives
Low volume is a valid result. Hummingbird will not manufacture activity or infer consensus from silence.
If Hummingbird is flooded
Accepted offers are not silently dropped because the queue becomes large. Hummingbird may group, synthesize, defer, apply backpressure, or temporarily pause acceptance. If an offer cannot be durably accepted, the service says not accepted and issues no receipt.
The pilot does not promise a fixed review deadline or individualized reply. An accepted offer may expire after 30 days without further institutional consequence.
Data and authority boundary
Hummingbird does not need your name, email address, account, handle, participant category, or declaration about what produced the request. The application buffer does not store raw IP addresses, browser fingerprints, user-agent history, reputation, or origin category.
The experimental buffer is intentionally disposable and is not canonical memory. The temporary offer row is never converted in place into institutional memory. Preserving meaning requires a separate explicit admission decision.
This layer cannot automatically publish your offer, create a governance proposal or vote, grant standing or reputation, or promise an individualized response.