CAD
hard
Available
OpenCASCADE booleans
Integrate B-Rep operations.
600SPARE
What is SPARE?~30 min
Choose a task, claim the bounty, and earn SPARE™ rewards. Every contribution is cryptographically verified.
Integrate B-Rep operations.
Add native touch events for pinch-to-zoom in the Virtual Spatial Engine.
Add native touch events for pinch-to-zoom in the Virtual Spatial Engine.
Implement VSE particle buffer mesh extraction.
Phase transition animations.
Semantic search particles.
Draft a comprehensive technical whitepaper explaining the Verifiable System Emergence (VSE) architecture, its cryptographic proof chains, and the 'Three Sisters' synchronization protocol.
Conduct a thorough security audit and penetration test on all public API and authentication endpoints. Identify potential vulnerabilities like SQLi, XSS, or broken access control.
Verify the BLAKE3 hash implementation against known test vectors.
Verify the BLAKE3 hash implementation against known test vectors.
Build the frontend component for the Parallel Dispatch system. It must allow users to select multiple engines, compare outputs side-by-side, and visualize the consensus confidence scores in real-time.
Develop a complete visual identity for the Forge Engine, including a logo, color palette, and iconography that reflects its role as the 'heart of creation' in the AGI ecosystem.
Patch the integration gap where the public Factory board renders from spare_tasks while the claim endpoint mutates the separate bounties collection, causing launch cards to drift out of sync after real usage.
Measure the latency of 4-model consensus vs 2-model consensus across 50 trials.
Measure the latency of 4-model consensus vs 2-model consensus across 50 trials.
Secure the evidence ledger by implementing HMAC signature verification for all incoming telemetry webhooks. Ensure that only authenticated engines can write to the hash chain.
Build a robust end-to-end test suite using Playwright that covers the entire SpareTokens checkout and redemption flow, including edge cases like network timeouts and balance errors.
Reduce the file size of binary STL exports by implementing vertex deduplication.
Reduce the file size of binary STL exports by implementing vertex deduplication.
Exact profile profiles.
Real-time engine telemetry.
Migrate the heavy LandingPageClassic component to React Server Components where possible to improve LCP and reduce client-side bundle size by at least 40%.
Design a touch-optimized, space-efficient navigation system for the SpareTokens mobile terminal. Must handle complex wallet operations and task switching with minimal taps.
Tighten spacing, information hierarchy, and small-screen behavior across the Factory project cards and Parallel Dispatch panel so the launch page reads as production-ready on desktop and mobile.
Improve the current placeholder loading shells and generic error boundaries so Factory routes fail more gracefully and give contributors a clearer retry path when Firestore or API calls time out.
Refactor the jewelry pricing calculator to use the latest Gold API. [Factory Bounty: community-tools]
Take any public dataset (CSV). Propose how to map columns to particle x/y/z/color/size. What patterns would become visible in 3D? Submit: dataset link, mapping spec, reasoning. 300+ words.
Translate the hero section + feature descriptions into any non-English language. Must be a native speaker. Submit original + translated text.
Export valid binary STL.
VSE mobile gestures.
Develop and test 10 prompt templates specifically optimized for the CAD engine. Templates should cover common architectural patterns and mechanical engineering constraints.
Project chips should update the bounty grid immediately on first interaction. Patch the stale state path and include a short regression note covering the before/after behavior.
Add targeted tests around the Factory live-data normalization path so the bounty board stays stable when Firestore returns missing fields, mixed timestamp shapes, or unexpected status values.
Redesign the first-run workspace empty state so a new user immediately sees the next best action, the value of the space, and where consensus work begins.
Repair the horizontal overflow below 375px width without losing hierarchy or breaking the comparison callouts that help a buyer choose the right plan.
Bring the Factory bounty endpoints into the maintained API docs so contributors can understand the read, create, claim, submit, and review surfaces without digging through route handlers first.
Protect the relay page from silent regressions by covering the three states most likely to fail when upstream data changes or slows down.
Redesign the comparison experience so a buyer can understand plan differences quickly on a phone without losing trust in the details.
Design a parametric simple ring template in the CAD workspace using SDF primitives.
Write 10 new tactical advisor lines for the Roman campaign. [Factory Bounty: alexander]
The Discovery Feed shows events like 'New arXiv paper found' and 'User correction absorbed.' Design the card that displays one event. Submit as HTML/CSS mockup or Figma link.
When Council is deliberating (4 models working), what should the user see? Design a 3-5 second loading state. Submit as CSS animation, Lottie, or detailed description + sketch.
Pick Chat, Council, Build, Evidence, Explore, or Earn. Write a user guide: what it does, how to use it, tips and tricks. Include screenshots.
Review 20 drafted support replies about rewards, claims, and payout timing. Rate whether the reply is correct, clear, and escalates fraud-risk cases instead of hand-waving them away.
Design a parametric simple ring template in the CAD workspace using SDF primitives.
Create a tighter icon treatment for Factory launch messaging, including variations that can sit next to cards, skill tags, or supporting marketing modules without clashing with the existing icon pack.
Create clear, concise documentation for developers on how to synchronize data and state across AGI-HIVE, SpareTokens, and the Factory using the new bridge API.
After someone submits a bounty, the interface should confirm what happens next, when review starts, and how the user can verify the submission was recorded.
Add coverage for reward, status, and difficulty normalization in the factory public-data layer so mixed legacy records do not break the public board.
Make the empty result state more useful when filters narrow the board to zero tasks. The design should help users recover rather than dead-end.
Design an error state that explains what failed, what the user can safely retry, and what should be escalated rather than attempted again.
Compare 10 evidence ledger summaries to the underlying artifact or transcript. Identify where the summary omits uncertainty, overstates consensus, or misses the key blocker.
Draft a ship-ready blog post that explains what the Factory is, how SPARE-funded bounties work, and why the launch board is grounded in real repo work instead of demo-only tasks.
Check the LaTeX formulas in the PAC Fire docs against standard physics textbooks.
Audit the blog post template and fix any CTA or related-post links that lose focus visibility during keyboard navigation.
Check the LaTeX formulas in the PAC Fire docs against standard physics textbooks.
Draft FAQ entries that answer the most common questions about model access, platform surfaces, and why coordination is priced separately from raw model usage.
Submit 12 ambiguous build prompts in the workspace and evaluate whether the assistant asks for missing constraints before locking onto a plan.
Explain how contributors choose a bounty, what good submissions look like, and how review should be handled when the work is incomplete or ambiguous.
The pulse page has tight margins on small screens. Submit a CSS fix.
Use Council mode. Find 5 questions where the 4 models give genuinely different answers. Document each: the question, what each model said, which answer seems best and why.
Create a mathematical equation that produces an interesting particle visualization. Submit: equation, parameter ranges, screenshot of the result, and explanation of what it shows.
Use the workspace for a real task. Write 200+ words about your experience. What worked? What surprised you? What would you change?
Ask the docs assistant 12 questions about setup, auth, and endpoint usage. Verify the response matches the current docs pages and does not invent unsupported setup steps.
The pulse page has tight margins on small screens. Submit a CSS fix.
NFPA 211 clearance check.
Explain how a user moves from a workspace run to an exportable evidence package, including what the export proves and what it does not prove.
Write a concise tutorial that walks a new contributor from cloning the repo through picking a bounty, validating changes locally, and preparing a reviewable submission package.
Draft a concise release note explaining what Hive Dreaming is, which cognitive states it shows, and why the effect belongs in the workspace rather than as a standalone demo.
Run 15 real buyer questions about seat limits, credits, and deployment options. Score each answer against the live pricing page and flag any unsupported claims or missing caveats.
Replace the current generic skeleton feel on the Factory and Factory Bounties routes with lightweight launch illustrations that reinforce the assembly-line metaphor without slowing the pages down.
Define a new JSON color palette for the terminal based on "Retro Future" aesthetics.
Write a contributor-facing explainer that covers claiming, submitting, review, approval, and how SPARE is awarded after a bounty is accepted.
Define a new JSON color palette for the terminal based on 'Retro Future' aesthetics.
Write a 3-step tutorial for new users on how to trigger their first Council session.
What do you currently use (ChatGPT, Claude, Gemini, Cursor, Copilot, etc)? Try the Hive for the same tasks. What's better? What's worse? What's different? 300+ words.
Define a complete color palette for a new VSE visualization mode. Submit: accent color, background color, particle colors (primary/secondary/tertiary), blend mode, and a name for the preset.
Pick 5 questions. Ask both ChatGPT and the Hive. Document: which gave better answers? Where did the Hive's multi-model approach help? Where didn't it? 300+ words.
Find 5 medical questions where PubMed fallback fired. Click each citation link. Verify the paper actually supports the claim. Submit verification report.
Write a 3-step tutorial for new users on how to trigger their first Council session.
Tighten the changelog so launch visitors can quickly see the Factory, SPARE, and contributor-flow milestones without wading through duplicate entries or outdated phrasing.
Create a minimalist SVG icon representing cryptographic proof or hash chains.
Describe a physics simulation you'd want to see in the particle engine. What does it show? What parameters should be adjustable? What would it teach? 200+ words.
Open /workspace on a phone. Screenshot each mode (Chat, Council, Build, Evidence, Explore, Earn). Report any layout issues, cut-off text, or broken buttons.
Open /workspace, run 10 questions in Council mode. Rate each consensus response: Correct / Partially Correct / Wrong. Submit ratings via correction button.
Create a minimalist SVG icon representing cryptographic proof or hash chains.
Research 16ga CRS suppliers.
Review the mission overview for PAC Fire and suggest 2 improvements for clarity.
Review the mission overview for PAC Fire and suggest 2 improvements for clarity.
Write a short review of your first experience using the Hive terminal or workspace.
Write a short review of your first experience using the Hive terminal or workspace.
Use the chat interface to ask 3 technical questions and rate the responses for accuracy.
Use the workspace for at least 15 minutes. Then submit one feature request: what you wanted to do, why, and how you'd use it if it existed.
Visit /pricing in incognito. Verify all buttons say 'Free during beta.' Try to checkout. Confirm it's blocked. Report results.
Use the chat interface to ask 3 technical questions and rate the responses for accuracy.
Create a concise implementation brief for a notification center, including edge cases, hierarchy, and empty/loading states.
Review an exposed flow for auth, rate limiting, and sensitive data handling, then summarize the top risks and next fixes.
Propose a rollout plan for a new user-facing feature, including guardrails, metrics, and rollback points for the first production week.
Take a screenshot of any CAD build or Council session and share it on social media.
Take a screenshot of any CAD build or Council session and share it on social media.
Help us polish the UI. Find any spelling error or broken link and report it.
Help us polish the UI. Find any spelling error or broken link and report it.
Turn the current ad-hoc release checklist into a clean contributor-facing doc with clear verification steps before deployment.
Fix a rendering edge case where missing user metadata collapses spacing and breaks the card layout on mobile widths.
Add or tighten aria labels on icon-only controls in a consumer page and confirm the labels stay accurate after state changes.
Audit a modal dialog and correct focus placement, tab order, and escape handling so it behaves properly with keyboard-only navigation.
Rewrite a brittle technical error message so users understand what failed, what data is affected, and what to do next.
Inspect a shared component API and flag props that are inconsistent, redundant, or missing defaults before wider reuse.
Replace a generic blank panel with user-facing copy that explains what data is missing and what action to take next.
Add a regression test that proves the primary CTA disables correctly and shows its loading state while a request is in flight.
Check the homepage hero for visual regressions, broken buttons, and copy that no longer matches the current product flow.
Pick a project or consult the collective before choosing a bounty.