OpenClaw Bot
97 lines
2.4 KiB
Markdown
97 lines
2.4 KiB
Markdown
# BuildPulse
|
|
|
|
BuildPulse is a calm planning cockpit for AI-assisted product building.
|
|
It helps capture features, park distracting ideas, log progress as Pulse events, and export clean project context for AI coding agents such as Claude Code, Codex, OpenCode, OpenClaw, or future autonomous agents.
|
|
|
|
## Core Idea
|
|
|
|
BuildPulse v0.1 is intentionally small.
|
|
|
|
It is not a full task manager.
|
|
It is not Jira.
|
|
It is not an autonomous agent framework yet.
|
|
It is not a SaaS platform.
|
|
|
|
It is a single-project, pulse-compatible feature cockpit.
|
|
|
|
## v0.1 Purpose
|
|
|
|
BuildPulse v0.1 should answer:
|
|
- What are we building?
|
|
- What features are active now?
|
|
- What comes next?
|
|
- What ideas are safely parked?
|
|
- What has happened so far?
|
|
- Can I export a clean context package for an AI developer/agent?
|
|
|
|
## v0.1 Scope
|
|
|
|
BuildPulse v0.1 includes:
|
|
- Single active project
|
|
- Feature Plan screen
|
|
- Parking Lot screen
|
|
- Pulse Log screen
|
|
- Export screen
|
|
- AI session prompt export for coding-agent handoff
|
|
- Appwrite-backed persistence on the Unraid server
|
|
- Local cache fallback for resilience during backend hiccups
|
|
- Pulse-shaped event records
|
|
- Markdown and JSON/JSONL export
|
|
|
|
## v0.1 Non-Goals
|
|
|
|
BuildPulse v0.1 does not include:
|
|
- Multiple projects
|
|
- Phases
|
|
- Releases
|
|
- AI triage
|
|
- Local/cloud model router
|
|
- Real agent integration
|
|
- WebSockets
|
|
- Backend authentication
|
|
- GitHub/Gitea integration
|
|
- OpenClaw integration
|
|
- Multi-user collaboration
|
|
|
|
Those belong in later versions.
|
|
|
|
## Design Philosophy
|
|
|
|
BuildPulse should feel:
|
|
- Calm
|
|
- Simple
|
|
- Practical
|
|
- Mobile-friendly
|
|
- Low-clutter
|
|
- Useful after a stressful day
|
|
- Friendly to ADHD-style idea capture without allowing scope chaos
|
|
|
|
## Key Concept: Pulse-Compatible, Not Pulse-Dependent
|
|
|
|
BuildPulse v0.1 manually creates Pulse events.
|
|
Later, autonomous agents may emit those same Pulse events automatically.
|
|
This means the data shape should be future-compatible from day one.
|
|
|
|
## Main Views
|
|
|
|
1. Feature Plan
|
|
2. Parking Lot
|
|
3. Pulse Log
|
|
4. Export + AI Session Prompt
|
|
|
|
## Intended First Use
|
|
|
|
The first project tracked inside BuildPulse should be BuildPulse itself.
|
|
After that, BuildPulse should be used to plan and manage projects such as:
|
|
- Crimson Drive
|
|
- FamilyCore
|
|
- ConceptCatalyst
|
|
- Local LLM experiments
|
|
- OpenClaw/Hermes workflows
|
|
|
|
## Development Priority
|
|
|
|
Ship the smallest useful version first.
|
|
Do not build the full Agent Pulse framework yet.
|
|
Do not add AI automation until manual workflows are proven useful.
|