Explicit non-goals
Defines claims and implementation directions that BeforeMetal deliberately excludes from its committed scope.
Section relationships
| ID | Name | Applies through | Non-goal |
|---|---|---|---|
| NOGOAL-001 | Perfect reality | Always | BeforeMetal will not claim exact, universal, or context-free physical truth. |
| NOGOAL-002 | Simulation is not universal physical proof | Always | BeforeMetal will not claim that simulation alone replaces physical evidence when a use case, safety case, certification program, regulatory process, or separately qualified accuracy claim requires it. |
| NOGOAL-003 | Certification authority | Beta | BeforeMetal will not be represented as safety or regulatory certification evidence without a separate qualification program. |
| NOGOAL-004 | Full CAD replacement | Beta | BeforeMetal will not provide general solid modeling, drafting, tolerancing, manufacturing drawings, or CAM. |
| NOGOAL-005 | Full EDA replacement | Beta | BeforeMetal will not provide complete schematic capture, PCB layout, signal-integrity, or manufacturing tooling. |
| NOGOAL-006 | Native CFD | Beta | BeforeMetal will not build a general production CFD solver into the portable product. |
| NOGOAL-007 | Native nonlinear FEA | Beta | BeforeMetal will not build a general production nonlinear FEA solver into the portable product. |
| NOGOAL-008 | Native production SPICE | Beta | BeforeMetal will not require a production-compatible transistor-level SPICE solver in the portable product. |
| NOGOAL-009 | Individual rain droplets | Beta | MVP and beta rain will not require droplet-resolved impact, film, splash, drainage, or fluid-structure simulation. |
| NOGOAL-010 | Photorealism gate | Beta | Photorealistic rendering will not be an MVP or beta acceptance condition. |
| NOGOAL-011 | ML training framework | Always | BeforeMetal will not replace PyTorch, JAX, distributed trainers, or experiment-tracking platforms. |
| NOGOAL-012 | Universal backend parity | Always | BeforeMetal will not promise identical trajectories or capabilities across distinct mechanics or multiphysics backends. |
| NOGOAL-013 | Universal bitwise determinism | Always | BeforeMetal SHALL guarantee bit-for-bit repeatability only for explicitly qualified configurations. It will not claim identical binary results across every platform, GPU path, extension, or external solver. |
| NOGOAL-014 | Hard real-time desktop | Beta | A normal desktop process will not be described as a qualified hard-real-time HIL system. |
| NOGOAL-015 | Multi-tenant cloud platform | Beta | Hosted accounts, billing, multi-tenant isolation, and global distributed orchestration are outside MVP and beta. |
| NOGOAL-016 | Unqualified component truth | Always | Community, manufacturer, or assumed models will not be presented as physically validated or independently evidence-qualified without applicable traceable evidence. |
| NOGOAL-017 | Extension is not implementation | Always | A generic backend, adapter, or extension point will not be described as support for a physical capability until an implementation and its evidence exist. |
| NOGOAL-018 | Universal model catalog | Always | BeforeMetal will not claim to ship validated models for every robot, component, material, circuit, or environment; project-specific modeling, evidence selection, or calibration may remain necessary for a claimed use case. |
| NOGOAL-019 | Property storage is not simulation | Always | BeforeMetal will not claim that a constitutive, transport, resistive, dissipative, interfacial, or other engineering property affects a run merely because the property is stored; active support requires a consuming model or solver capability and an explicit compiled disposition. |
| NOGOAL-020 | Universal multiphysics completeness | Always | BeforeMetal will not claim that one model, solver, backend, or release resolves every relevant physical domain, scale, coupling, or failure mechanism at production fidelity. |
| NOGOAL-021 | Universal arbitrary precision | Always | The portable product will not require arbitrary-precision arithmetic for every physical value; higher-precision, interval, decimal, or other specialist numeric profiles remain explicit versioned capabilities unless a later qualified product profile adopts them. |
Change rationale (NOGOAL-013): The previous wording described unsupported configurations only as exceptions and did not state where a repeatability guarantee may apply. The revised non-goal limits bit-for-bit repeatability guarantees to explicitly qualified configurations and rejects universal cross-platform, GPU, extension, and external-solver equivalence claims.
Change rationale (NOGOAL-002, NOGOAL-016, NOGOAL-018, NOGOAL-019, NOGOAL-020): ADR-0001 makes physical assets and team-run tests optional for the Portable MVP without turning simulation into an unsupported guarantee of reality. Broad property representation and an extensible solver suite are required architectural boundaries, but each active effect still needs a declared consuming capability, validity envelope, and evidence status.
Change rationale (NOGOAL-021): ADR-0006 keeps a versioned route to higher precision without imposing an arbitrary-precision dependency or implying that more arithmetic digits automatically improve an approximate physical model. Bounded wider intermediates used for correct parsing, validation, hashing, or overflow detection are not prohibited.
Generated from the canonical specification. Edit section metadata or prose in docs/requirements.md; the website rebuilds this page and its relationships automatically.