Integrations
A public read of the roadmap
29 supporters520 influence
10 comments · 10 people in the discussion
- Idea→
- Discussing→
- Gaining support→
- Proposal→
- Voting→
- Approved→
- Building→
- In experiment→
- Shipped→
- Measured
Problem
People building on top of Hive can't ask, in a stable way, what is being explored, decided, built, tested, or shipped. They scrape the page.
Why it matters
If the story of the product can't be read by other tools, it will be retold incorrectly.
Potential solutions
A read-only feed of roadmap items with their idea, stage, influence, and decision link. No write access.
Proposal #30
A public read of the roadmap
- Problem
- People building on top of Hive can't ask, in a stable way, what is being explored, decided, built, tested, or shipped. They scrape the page.
- Evidence
- Two community scripts broke in a week because they were reading HTML. Both were trying to show 'what shipped because of us.'
- Proposed change
- Publish a read-only roadmap feed. Writes stay inside Hive, behind a member.
- Expected impact
- The evolution can be shown elsewhere without being reinvented.
- Alternatives
- The embed alone. An embed is visual. Some tools need data.
- Risks
- A feed can expose a vote's lean. Publish stages and links, not live option totals.
- Open questions
- Do unpublished drafts ever appear? They should not.
- Complexity
- small
- Success metrics
- The known scrapers switch to the feed, and idea-page referrals continue.
The draft is open for discussion before a vote begins.
Hive Intelligence · community synthesis
Synthesis
Drawn from the discussion. Not a decision.
People building on top of Hive can't ask, in a stable way, what is being explored, decided, built, tested, or shipped. They scrape the page.
Evidence
- The part I would spend influence on is specific: other tools were scraping the roadmap and inventing statuses.
- I don't want another feature. I want fewer people stuck with other tools were scraping the roadmap and inventing statuses.
- I keep running into this around other tools were scraping the roadmap and inventing statuses. “A public read of the roadmap” is the name I would have used.
Community sentiment
- Demand is specific. Supporters keep returning to the same broken moment, not a vague wish list.
- The objection is about scope. Concerns are less “never do this” and more “don’t do it in a way that drowns the problem.”
- People brought proof. Evidence comments describe real sessions, not hypothetical users.
Arguments for
- Read-only is the whole proposal. The moment a script can vote, we have built the wrong door.
- Before we build “A public read of the roadmap”, write the success metric in the proposal itself.
- A smaller version of “A public read of the roadmap” could tell us if we even framed the problem correctly.
Arguments against
- Even stages can leak a strategy. I still think the roadmap is public on purpose, and the feed should match the page, not exceed it.
Alternatives
- Ship the embed first. Add the feed when someone has a real consumer besides a scraper.
Open questions
- Will the feed include the transcript URL once a decision closes?
Treat “A public read of the roadmap” as a problem statement: People building on top of Hive can't ask, in a stable way, what is being explored, decided, built, tested, or shipped. The leading suggestion is: A read-only feed of roadmap items with their idea, stage, influence, and decision link. Why it matters here: If the story of the product can't be read by other tools, it will be retold incorrectly.
Community discussion
Read-only is the whole proposal. The moment a script can vote, we have built the wrong door.
Even stages can leak a strategy. I still think the roadmap is public on purpose, and the feed should match the page, not exceed it.
Will the feed include the transcript URL once a decision closes?
Ship the embed first. Add the feed when someone has a real consumer besides a scraper.
Before we build “A public read of the roadmap”, write the success metric in the proposal itself.
The part I would spend influence on is specific: other tools were scraping the roadmap and inventing statuses.
A smaller version of “A public read of the roadmap” could tell us if we even framed the problem correctly.
I don't want another feature. I want fewer people stuck with other tools were scraping the roadmap and inventing statuses.
Whatever we do with “A public read of the roadmap”, the decision has to stay attached to this thread.
I keep running into this around other tools were scraping the roadmap and inventing statuses. “A public read of the roadmap” is the name I would have used.
Join the hive to add to this thread.