Kernel Build guide
Kernel Build is the project track for AI-assisted design delivery. It uses a defined process: free concept (qualifying projects), written scope lock, full design production, then handover.
Build flow
01
Concept direction
Prepare and review homepage concept to validate style and direction fit.
02
Scope and milestones
Define page map, revisions, deliverables, and out-of-scope boundaries in writing.
03
Design production
Build full page set, component library, responsive frames, and interaction behavior in the design workspace.
04
Handover
Deliver organized design files, export guidance, and implementation notes for dev handoff.
Commercial model
| Point | Rule |
|---|---|
| Pricing | Quote-based after direction and scope review |
| Milestones | 50% deposit after scope lock, 50% on final handover |
| Capacity lock | Project slot is reserved only after deposit |
| Refund policy | No refunds after production begins (see Billing terms) |
Delivery standard
✓ Build quality baseline
Clean design file structure with naming discipline
Component system with variants and reusable patterns
Responsive frames for scoped pages
Clickable prototype and behavior notes
Documented handover package
✕ Not part of this track
WordPress theme coding and builder setup
Server setup, deploy, or launch operations
Undefined acceptance criteria
Open-ended post-handover feature queue
Outputs
- Production-ready design file with approved page set and component library.
- Design tokens and style rules (typography, spacing, color, states).
- Clickable prototype and interaction notes for implementation teams.
- Handover documentation package with export and structure guidance.
Scope disciplineTreat new requests after scope lock as separate work. This keeps timeline, cost, and handover quality predictable.