Architectural Principles
Core principles — Active Object Component, Build To Last, Creative Then Protocol Lock
Tags
Overview
Purpose
Core principles — Active Object Component, Build To Last, Creative Then Protocol Lock
Rules
AOC-001: Active Object Component is the FIRST goto in any architectural or placement decision
Every entity, artifact, and resource in the workspace must be an Active Object Component: - ACTIVE: discoverable by the framework, scannable by CLI, browsable in sbx web - OBJECT: typed with a model/schema, has metadata, participates in traceability - COMPONENT: composable, reusable across projects, pluggable into different contexts
AOC-002: Nothing is a passive file dump — every artifact participates in framework governance
Files without metadata, type, or discoverability are invisible to the framework. Invisible artifacts get lost, duplicated, or forgotten. Every file must be reachable via sbx CLI commands and browsable in sbx web.
AOC-003: All AOC entities must support cross-project referencing and sharing
Sharing, copying, modifying, and composing across projects is the key to creativity and efficiency. An entity locked to one project cannot be reused.
BTL-001: Build to last — for ages. No shortcuts in production code.
Non-optimal, non-performant, non-secure solutions are ONLY allowed during: - Mockup/preview HTML prototyping (exploration phase) - SDLC rapid component implementation (preview/sandbox phase) After exploration: refactoring fills up the models. Models are the source of truth.
BTL-002: Models are the source of truth — implementation is a 100% representation of the model
Every implementation must trace back to its model. All deviations are bugs. When building a similar solution, scan existing models and solutions first.
BTL-003: Before building new: scan existing solutions by tags, patterns, or model analysis
Copy proven solution if it fits, apply required modifications. This applies during every SDLC step — check `sbx knowledge list --type solution` and `sbx knowledge list --type pattern` before writing code.
CPL-001: During exploration — maximize creative freedom, cross-project sharing, rapid iteration
Copying, modifying, and composing across projects is the KEY to creativity. Only during experimenting can you find the best way forward. Shortcuts are allowed: non-optimal, non-performant, non-secure is fine during exploration.
CPL-002: Once settled — full protocol-oriented workflow, no shortcuts, no bypasses
Every protocol and every step exists because it must — result of 20+ years experience. Protocols provide quality control and confidence in the solution. No shortcuts, no bypasses, no 'good enough' — protocol compliance is mandatory.
CPL-003: Every protocol step is there because it must be — trust the process
The framework's protocols are battle-tested over 20 years across 50+ projects. They are not bureaucracy — they are quality assurance. Each step catches specific classes of errors that would otherwise reach production.