f685f9a237
Three phases: quality gate → coordinated launch → operations. Defines what "launched" means concretely for planner gap analysis. From voice dump, distilled into actionable phases with concrete checkboxes. Co-authored-by: openhands <openhands@all-hands.dev> Reviewed-on: https://codeberg.org/johba/harb/pulls/894 Reviewed-by: review_bot <review_bot@noreply.codeberg.org>
3.8 KiB
VISION.md — What "done" looks like
What is harb
A DeFi protocol with a price-floor-backed token (KRK), governed by an AI-evolved optimizer that manages liquidity positions on Uniswap V3. Three user funnels: passive holders (buy and hold a floor-backed asset), stakers (leveraged directional exposure via Harberger tax as sentiment oracle), and competitors (snatch underpriced stakes for profit). The optimizer evolves through Push3 evolution and red-team adversarial testing.
North star
Get live, learn from the market. The primary goal is having a real protocol with real users generating real data — not perfecting things in isolation. Everything else follows from that.
This project is AI-operated. Development, review, deployment, community support, analytics — all run by agents with minimal human escalation. The human sets direction and makes judgment calls. The machines handle execution, quality, and day-to-day operations. A high-quality project with a solid roadmap and growing community, delivered by an autonomous factory.
Phase 1 — Quality gate & release pipeline
Before anything goes live, build confidence that the product works:
- E2E quality gate: automated tests covering every button, every page, desktop + mobile + all major browsers
- Conversion funnel verification: landing → Uniswap swap → staking app flow is smooth and measurable
- Release pipeline: fast, repeatable releases for frontend/backend updates. Contracts are immutable except the optimizer (upgradeable via UUPS).
- Reusable for every release — the quality gate runs on every deploy, not just launch
Phase 2 — Coordinated launch
Not a soft launch. A planned, date-specific event:
- Pre-launch: create a pitch deck / PDF explaining the protocol to influencers — what KRK is, how to buy, how to stake, what the floor means
- Influencer outreach: coordinate with crypto influencers to amplify on the same date. They buy supply, stake, and market to their audience simultaneously.
- Launch day: deploy LiquidityManager, register token, create Uniswap pool. Coordinated influencer push creates initial volume → price action → organic discovery.
- Goal: broad base of holders from day one, not a slow trickle
Phase 3 — Operations
Post-launch, the project needs sustained operations:
- Analytics: measure churn on landing page and staking page, track conversion funnel, user feedback loops
- Fast iteration: regular releases to fix issues, ship improvements based on user feedback
- Influencer waves: organize repeat coordinated pushes — influencers combine forces to create new bull cycles in the protocol
- Community: Discord (or similar) with:
- AI support bots trained on the protocol (help users swap, stake, understand the floor)
- Sentiment monitoring + regular community health reports
- Direct feedback channel to dev team
- Optimizer governance: release new evolved optimizers, eventually create a staker voting system for decentralized community-selected optimizer upgrades
- txnBot: automated on-chain operations — recenter triggers, protocol health monitoring, transaction execution
What we're NOT building
- No governance token (KRK is the token, staking IS governance exposure)
- No cross-chain (Base only for now)
- No yield farming / liquidity mining incentives
- No centralized exchange listings (Uniswap is the market)
- No mobile app (responsive web only)
What "launched" means (minimum)
- Quality gate passes on landing + staking app (desktop + mobile)
- Pitch deck exists and is reviewed
- At least 3 influencers committed to launch day
- LiquidityManager deployed on Base mainnet
- KRK token registered, Uniswap pool created and funded
- Analytics in place (basic funnel tracking)
- Community channel open with at least one support bot