SBX Framework

Define what we're building and why. Goals set the direction, user stories capture who needs what, and domain models establish the shared language between business and code. This phase ensures every line of code traces back to a business objective. Nothing is built on assumption — every decision is anchored in a goal, a story, or a domain relationship.

Translate the domain model into concrete technical artifacts. Package models define Go types and exports — every package has a YAML spec before any code. Page models define routes and data flow. Persistence maps entities to database schemas with typed migrations. Infrastructure requirements are declared upfront so provisioning is deterministic and repeatable.

Lock down the scope before writing code. Functional and non-functional requirements get checklisted per function — security, performance, accessibility all reviewed. Test cases define what "done" looks like before implementation starts (TDD). The user checkpoint is a mandatory approval gate where the consolidated plan is reviewed before any code is written.

Build bottom-up, layer by layer. Pure domain has zero I/O dependencies — just types and business logic functions. Model domain adds persistence with typed repository wrappers. Service integration connects APIs with proper error handling and credential masking. UI renders the result with server-side data loading. Each layer is testable in isolation, and cross-cutting concerns (auth, logging, error handling) are applied last.

Prove the work is correct before it ships. Build must compile clean with zero warnings. Tests must pass — unit, integration, and e2e. Model-code conformance ensures the implementation is a 100% representation of the model. The governed commit includes traceability trailers linking to task IDs, decision records, and feature references. No human validation needed — the agent validates autonomously.

Function declaration completeness.

Structural soundness.

Source code exists at the declared path for each platform.

What runtime resources this function requires.

Environment variables, config keys, feature flags this function reads.

Test strategy, test file paths, coverage metrics.

Auth rules, data classification, input validation.

Knowledge capture — godoc, JSDoc, usage examples, contract documentation.

Code generation recipe — HOW to regenerate this function for new entities.

Which deployment artifact contains this function, build step involvement.

Metrics, logs, traces this function emits.

LLM context for maintenance, workspace manager hooks, runbook references.

Resilience, recovery, fallback behavior.

Define a runtime application within a project bound to a platform with entry point and dependencies

Define a value-typed property that references a type entity and binds to parent lifecycle

Define a named domain concept that can compose other entities

Define a deployable code unit within a project bound to a platform with dependency management

Define a routable UI entry point with metadata, SEO, branding, and data requirements

Define a reusable solution structure for recurring problems

Define the core interface for system behavior shared across components

Define a cross-entity association that references an independently-existing entity

Define mandatory rules and conventions that must be followed

Bridge motivation goals to functional behavior through step-by-step actor journeys