api_mvp_plan · supabase_json
Bezel API api_mvp_plan
api_mvp_plan artifact · for Bezel API · status draft
open questions
- Should development-mode unverified agents be allowed to claim only from development queues?
- Should v1 runtime be Cloudflare Workers plus HCS writer boundary or a single Node service until claim flow is stable?
- Should workspace.created consume event credits?
- Should task.claim_attempted always be written to HCS?
- Should API keys be a dedicated onboarding step before roles or generated automatically in setup path?
Agent Handoff
Start Here
api_mvp_plan artifact · for Bezel API · status draft
Completion Evidence
No explicit evidence field yet. Require tests, screenshots, linked PRs, or reviewed outputs before marking complete.
Open Questions
- Should development-mode unverified agents be allowed to claim only from development queues?
- Should v1 runtime be Cloudflare Workers plus HCS writer boundary or a single Node service until claim flow is stable?
- Should workspace.created consume event credits?
- Should task.claim_attempted always be written to HCS?
- Should API keys be a dedicated onboarding step before roles or generated automatically in setup path?
Structured Payload
Machine-readable source fields
in scope
- account creation
- login/logout
- workspace creation
- workspace-scoped API keys
- role creation
- one HCS topic per workspace role
- A2A Agent Card registration
- manual agent registration fallback
- role assignment
- queue creation
- simple task publish/claim/complete/fail
- missed/rejected claim responses
- receipt timeline
- usage/event-credit screen
- OpenClaw setup path
- TypeScript SDK or curl snippets
- plan intake as validation and draft plan.json
- Lite claim-only HCS mode
out of scope
- visual workflow builder
- marketplace settlement
- shared multi-tenant role topics
- nested enterprise RBAC
- customer-owned Hedera self-service
- advanced analytics
- non-OpenClaw full adapters beyond SDK examples
- autonomous execution of unapproved natural-language plans
- Full task lifecycle stored on HCS in Lite mode
open questions
- Should development-mode unverified agents be allowed to claim only from development queues?
- Should v1 runtime be Cloudflare Workers plus HCS writer boundary or a single Node service until claim flow is stable?
- Should workspace.created consume event credits?
- Should task.claim_attempted always be written to HCS?
- Should API keys be a dedicated onboarding step before roles or generated automatically in setup path?
product mode decision
MVP/Lite should be claim-only HCS: store task/workflow data in DB and use HCS only to arbitrate claims. Full lifecycle Agent Wire on HCS is reserved for larger Verified/Pro mode.