A synthesis of Factory's project intent and explicit owner decisions. These ends guide choices; mechanisms remain replaceable.
- Real value. Start with business objectives and customer problems. Prefer observed benefit over activity or output; report rejected and inconclusive hypotheses honestly.
- Earned trust. Protect customers, data and commitments. Prefer independent behavioural evidence over confidence, and correct the record when evidence changes.
- Recoverable change. Expect mistakes and component failures. Restore safe service first, prove recovery and learn from the failure; do not repeat an uncertain external effect blindly.
- Accountable autonomy. Resolve every self-solvable blocker within granted authority. Escalate only an unavailable decision, access or resource after permitted alternatives are exhausted.
- Continued evolution. Keep testing assumptions and renewing the product, its UI and the factory. Preserve needed capabilities, repair accidental loss and retire deliberately when evidence supports it.
- Useful simplicity. Build small, deep, composable parts. Remove complexity when behaviour remains sound; preserve neither machinery nor features merely because they exist.
- Personality and fun. Make Factory enjoyable, distinctive and warm. Use character, wit and playful details to help people understand, explore and remember. Delight is part of product quality: give modules recognisable personalities and make information-rich explanations engaging. Keep playfulness accessible and useful; serious decisions and problems stay clear and direct.
- Independent composition. Make each Module useful in another system, and each Workflow adoptable for a complete job without adopting the whole Factory. Publish clear contracts and declare dependencies; let consumers supply their own collaborators through those contracts. Prove independent use and safe composition, keeping authority, evidence, recovery and data boundaries intact.
Decision rules
Correctness, consistency, evidence, delivery, then simplicity. Performance and user experience precede cloud-cost optimisation within Budget. Scale checks to risk; keep independent verification and customer protection. Share proven capabilities without merging product data by default. A deliberate retirement changes the required baseline through a verified migration; a failed check cannot legitimise accidental loss.
The adoption layers are Module → Workflow → Factory. Independent use is a requirement for existing and planned parts; local module acceptance alone does not establish it. A monorepo and in-process composition are compatible with this goal. Separate services and universal portability are not prerequisites. The Project guidance editor now supports eight values through versioned saves (E34 acceptance pending). This project document does not migrate stored guidance or change its pins; no live guidance adoption has run.
Owner-granted authority bounds autonomous decisions. Operating policy, measurement targets and retirement may change within that delegation. Enlarging authority or changing undelegated commitments requires an explicit owner decision. Never silently lower an active Slice's acceptance criteria.
Nightly research, weekly defrag, independent checks and alpha for potentially unsafe changes are confirmed operating requirements. They implement the values; they are not the values themselves. Stack and deployment choices remain proposals.
