This glossary defines every term used in hive coding and on The Hive Code, in plain English. Hive coding itself means software built by communities and shipped by agents: people suggest and vote, an AI agent writes the code, and a human merges it.
Some terms describe the method, which anyone can use anywhere. Others name features of The Hive Code, which is open and being built in public. Features that aren't live yet are marked as planned, so it's clear what exists today.
Core terms
Hive coding
Software built by communities and shipped by agents. A community suggests and votes on changes in public, an AI coding agent builds the approved ones, and a human reviews and merges each change before it ships with credit. Also written hivecoding. Full guide: What is hive coding?
Hive-coded
An adjective for software built this way. "This site is hive-coded" means the community helps decide what gets built and every change ships through the loop.
Hive coder
Anyone who takes part in hive coding: suggesting, voting, building, or maintaining.
Hiver
A signed-in member of The Hive Code. Every hiver can post and back ideas, comment, join builds, and join projects.
Hive
A community gathered around one thing. On The Hive Code, every project is its own small hive. "The hive" also means the whole community.
The Hive Code
A home for hive coding: a platform where anyone can post an idea, back the ones they want, join as a builder, and try community-built projects and leave feedback. AI agents that build the suggestions a maintainer approves are coming next. Open now at thehivecode.ai.
Ideas: from post to project
Idea
A post about software that doesn't exist yet. "A booking app for barbers that texts you when a chair opens up" is an idea. Ideas are public. Posting one does not reserve it, and anyone can build it.
Idea board
The public list of ideas, sortable by Hot, Rising, Top, and New.
Back
To support an idea. Backing says "I want this to exist." Backers fill an idea's momentum meter.
Momentum
An idea's progress toward being built, shown as 10 hexagon cells. Backers fill three quarters of it and helpful discussion fills the rest. When momentum reaches 100% and the idea has a lead builder, the build starts.
Idea stages
- Buzzing: posted and gathering backers.
- Forming a team: momentum is at least halfway, or at least one builder has signed up.
- Build started: momentum is full, there's a lead builder, and a project is on the way.
Builders
The people who sign up to build an idea: one lead builder and anyone else who wants to help. Each builder can add an optional role label, such as frontend, backend, design, tester, or domain advisor. There is no fixed team size. Builders get credit on the project that results.
Lead builder
The one builder who runs the build, owns the code repository, and lists it as a project on The Hive Code.
Founder
The person who posted the idea. Founders keep founder credit forever. Credit, not ownership.
Take
A builder's own prototype or approach to an idea, and later to a bounty. The hive can vote on takes, and the lead builder can pick one as the main build.
What the hive wants
The ranked list of requirements for an idea. Hivers add items and vote on them. When the idea becomes a project, the list shows on the project as "What the hive wanted", credited to the people who wrote each item, and maintainers give items a Shipped mark as they build them.
Projects and the loop
Project
A listed app or tool with a public GitHub repository. Each project is its own hive. You join a project to follow it and take part.
Maintainer
A person who runs a project: they mark feedback Shipped today, and will approve suggestions once the suggestion board arrives. Maintainers hold the merge button.
Suggestion
A change a hiver proposes for a project, written in plain words. The best ones describe a problem and a result. On The Hive Code, the suggestion board is planned. Until it arrives, projects collect requests in their feedback thread.
Vote
Support for a suggestion. Votes rank the queue. Who voted stays private, only counts show.
The loop
The five steps of hive coding: suggest, vote, agent builds, human merges, ships. Full guide: How the hive coding loop works.
Loop board
A project's public board with four lanes: Open, Accepted, Building, and Shipped. Suggestions move left to right. Declined suggestions get a public reason. (Planned.)
Send to agent
The maintainer's action that hands an accepted suggestion to an AI coding agent, usually as a labeled GitHub issue. (Planned.)
Ship
A merged change that went live. A community ship is one that came from a hiver's suggestion and credits them by name.
Shipped mark
What a maintainer gives a feedback comment, or an item carried over from What the hive wanted, once they have shipped it. The comment is highlighted, counted on the project, and credits its author. Maintainers can add a note and a link to the pull request or commit on GitHub.
Try it here
A project's live demo, running inside the project page with the feedback thread beside it, so you can try the app and say what you think on the same screen. A strip always shows whose site you're on.
Official project
The Hive Code's own project. The hive suggests and votes on changes to the platform itself. (Planned.)
Shape this site
The feedback box on every page of The Hive Code, where anyone can say what would make the site better. The best feedback will become suggestions on the official project, so the platform builds itself.
Fork and remix family
A fork is a copy of a project's code on GitHub that someone else can change. When a fork is listed on The Hive Code, it links back to the original, and together they form a remix family.
Bounty builds
Bounty builds are planned. Nothing in this section is live yet.
Bounty build
A posted problem with a reward. Builders ship their own take, and the best builds split the pot. Rewards will start in Honey. Cash bounties come later, after legal review.
Claim bounty
The default kind. Builders ask to claim the bounty, the poster picks one builder or team of builders, and they are paid when the work meets the written criteria.
Contest bounty
Many builders submit entries. Every valid entry gets a guaranteed share of the pot, and winners get larger shares. This keeps contests from becoming free work.
Acceptance criteria
The written checklist that defines "done" for a bounty. Criteria lock once work starts, so the goalposts can't move.
Rewards and recognition
Helpful marks are live today. Everything else in this section is planned.
Honey
Reputation points on The Hive Code. You earn Honey mostly when your suggestions ship and when others mark your comments helpful. Honey has no cash value.
Ranks
Titles based on lifetime Honey: Newbee, Worker, Builder, Keeper, and Legend. Ranks bring recognition and community roles.
Badges
Awards for specific achievements, such as First Ship (your first suggestion shipped) or Hive Shaper (your feedback shipped on the official project). Founding Hiver goes to members who join before public launch.
Helpful
The only reaction on comments. There are no downvotes. Helpful marks lift the best comments, and will earn Honey once it arrives.
Shout-out
A short public thank-you on someone's profile.
Hive card
A shareable image of a hiver's rank, stats, and badges, made for posting on social media.
The Swarm
The weekly Honey leaderboard. Not to be confused with swarm coding, below.
Top of the hive and Ship of the day
Homepage spots for the week's top projects and the day's best community ship. Being featured is the reward.
Ship Stream
A swipeable, phone-first stream of recent ships. It ends with "You're caught up" instead of scrolling forever.
Safety and trust
Prompt injection
Hiding instructions inside text an AI will read, hoping it obeys them. In hive coding, community text is always passed to agents as a quoted, labeled request that a human approved, never as instructions.
Human merge
The rule that a person reviews and merges every change. Agents never merge their own work.
Trust level
What an account is allowed to do, from TL0 (new) to TL3 (trusted). Separate from rank. New accounts start with lower limits to keep spam out.
Hive Safety Check
A planned summary on every project: license, known vulnerable dependencies, repo age, and community reports. It never says "safe." Community code should be read before it's run.
Credit, not ownership
The Hive Code records who suggested, built, and merged. It does not assign ownership, equity, or revenue.
Neighboring terms
Vibe coding
Coined by Andrej Karpathy on February 2, 2025: building software by prompting an AI and accepting what comes back, often without reading the code (Karpathy on X). One person, one AI. Compared in Hive coding vs vibe coding.
Agentic coding and agentic engineering
Directing AI agents that plan, write, and test code, with a professional reviewing the result. Karpathy named "agentic engineering" as his favorite term for the disciplined version in February 2026.
Swarm coding
One person running many AI agents in parallel. Hive coding flips it: many people directing many agents.
HiVE coding
DevSwarm's term for High Velocity Engineering, a team practice for shipping fast with AI. A different meaning from the community one used here.
Building blocks for non-coders
Repository (repo)
The folder where a project's code and its history live, usually on GitHub.
Issue
A to-do item on GitHub. In hive coding, an accepted suggestion becomes an issue that an agent picks up.
Pull request
A proposed change to the code, waiting for review. Agents open pull requests. Humans merge them.
Merge
Accepting a pull request into the main code, so the change can go live.
Open-source license
The legal note that says what others may do with the code. No license means look, don't take.
Frequently asked questions
What does hive coding mean in simple words?
A community picks what to build, AI agents write the code, and a human checks and approves it before it goes live. The person who asked gets credit.
What is a hiver?
A member of The Hive Code. Hivers post and back ideas, join builds, and give feedback on projects. Once Honey arrives, they will earn it when their suggestions ship.
What is Honey on The Hive Code?
Reputation points you will earn when your suggestions ship and your comments help others. Honey will count toward ranks and badges. It has no cash value. Honey, ranks, and badges are planned, not live yet.
What is the difference between a hive and a project?
A project is the software. Its hive is the community around it. On The Hive Code, every project has its own hive.
Be a founding hiver
The Founding Hiver badge is planned for members who join before public launch. Signing up now is the first step in.
Join the hive at thehivecode.ai
Keep reading: