01FLIGHT PATH
One tagged release at a time.
Each milestone ships a tagged release and has clear acceptance criteria, so you always know when it's truly done. Hive v1.0.0 is shipped; the next work is the v1.0.x release train.
M10Building nowv1.0.1
Plugin App Store
0 of 0 named packages exist on main
ACCEPTANCEa user can discover a plugin on the Hive website, inspect its
Read M10 in ROADMAP.md ↗MILESTONE WORK08 ITEMS
- 01Extend Hive. Make it yours.
- 02Store experienceBuild a searchable plugin catalog with categories, featured collections, · Provide dedicated plugin detail pages with descriptions, screenshots, · Add filters for agent integrations, workflow automation, developer tools, · Show compatibility badges for Hive versions, supported operating systems, · Clearly identify verified maintainers, official plugins, deprecated · Link directly to source repositories, documentation, issue trackers, · Integrate the responsive discovery experience into the Hive website.
- 03Registry and plugin recordsDefine a versioned registry schema for plugin metadata, releases, · Surface plugin ID, version, author or organization, license, repository, · Record minimum and maximum supported Hive versions where applicable. · Keep release metadata, source revisions, checksums, and publication · Support multiple maintainers and explicit ownership-transfer workflows. · Preserve historical release metadata when new versions are published. · Validate registry records before publication and reject malformed or
- 04Hive CLI integrationAdd
hive plugin search,hive plugin info, andhive plugin install. · Supporthive plugin update [id],hive plugin remove, and · Keephive plugin installandhive plugin linkavailable for · Resolve plugin IDs to registry releases without confusing registry · Display installation progress, compatibility warnings, and actionable · Support non-interactive installation for scripts, with explicit security · Keep the existing CLI usable when the registry is unavailable. - 05Package and manifest contractFinalize the versioned
hive-plugin.tomlmanifest and package format. · Define immutable release references, checksums, supported platforms, and · Validate declared commands, actions, events, startup hooks, and required · Define compatibility and migration rules for manifest changes. · Reject releases whose manifest ID does not match the registry listing. · Specify package size limits, download limits, and extraction safeguards. · Document how plugins declare configuration, data directories, and runtime - 06Installation, updates, and rollbackPreview plugin identity, source, version, requested capabilities, and · Verify package integrity before installing or updating a plugin. · Install atomically so an interrupted operation cannot leave a partially · Preserve the last known-good version during upgrades. · Support rollback after a failed upgrade or explicit user request. · Never delete plugin data without explicit confirmation. · Detect interrupted downloads, corrupted archives, missing dependencies, · Maintain a local installation record with version, source, checksum, and
- 07Open-source submissions and governanceEstablish a documented submission process for public plugin repositories. · Require valid manifests, license information, maintainer metadata, · Introduce submission states: draft, submitted, changes requested, approved, · Maintain an auditable review history for listing changes and release · Automate manifest validation, compatibility checks, license checks, · Require human review for official or verified listings. · Publish moderation policies, reporting procedures, and an appeals process. · Allow maintainers to withdraw or archive plugins without silently rewriting
- 08Initial catalog and developer experiencePublish official example plugins covering PR status, reviewer orchestration, · Introduce
hive plugin initto scaffold a valid plugin. · Document local linking, development mode, test fixtures, event and action · Provide a sample repository and automated validation workflow. · Document ownership transfer, maintainer retirement, security disclosures, · Add a registry contribution guide for community maintainers.
PULSE
The hive, this year.
COMMITS PER WEEK · 2652 WEEKS—
GitHub is computing activity stats…
CONTRIBUTORS · 2
BEE LOG · MAINchecked every 5 min
d278db3fix(ci):linting issuesadmirsaheta · 1h ago→ M101c27900fix(ci):linting issuesadmirsaheta · 1h ago→ M10f9ec32efeat(plugins):app store prepadmirsaheta · 2h ago→ M10a51b7c6chore(roadmap): updateadmirsaheta · 4h ago→ M10ef9ddf1chore(docs):move-to-docs-repoadmirsaheta · 4h ago→ M103e38451fix(linux):runtime-ciadmirsaheta · 4h ago→ M10fdca149ci(release.yml): remove tag hyphen filter for homebrew publishadmirsaheta · 7h ago→ M105f4b872feat: add interactive install flow and Homebrew toolingadmirsaheta · 8h ago→ M1005SYNC
Autosynced with ROADMAP.md.
There's no second roadmap to keep in step. The server reads ROADMAP.md from main three times a day and serves this page from cache in between. Commits, stats and the source tree come through the same server, so your browser never talks to GitHub directly.
Item signals come from the source tree: when a package an item names exists on main, it gets a mark. A mark means code exists, not that the item is done. Acceptance criteria decide that.
- source
- admirable-oss/hive · main · ROADMAP.md
- file changed
- 4h ago · a51b7c6
- last read
- just now
- status
- Read from main on the server, three times a day.
- in production
- Served from Vercel's edge cache and regenerated every eight hours. A server action refreshes commits and stats every few minutes from one shared, token-authenticated cache.