Principles

Principles define how decisions are made when tradeoffs exist.
They are applied whenever contributors disagree on direction.

Decision Rules

• If two designs perform similarly, choose the simpler one.
• If a solution increases tooling or vendor dependency, it is disfavored.
• If a feature cannot be parameterized, it does not belong in the core architecture.
• If a design cannot be documented clearly, it is not ready.
• If a proposal adds complexity without increasing durability, reject it.
• If a solution works only for a single vehicle configuration, defer it to later phases.

Scope Discipline

• Phase 1 focuses on the shell as a standalone structural system.
• Vehicle-specific integration is deferred unless strictly necessary.
• Interior layouts are secondary to structure and geometry.
• Optional features must not pollute the core model.

Collaboration

• Disagreement is expected; undocumented opinion is not.
• Proposals must include rationale and tradeoffs.
• Changes to core geometry require explicit justification.
• Authority comes from clarity, not seniority.

Evolution

• Designs are expected to change.
• Principles evolve more slowly than implementations.
• Backward compatibility is preferred but not guaranteed.