Section 94 of 105
91. Compiler Input Authenticity and Authority
Stable section ID: S05-CON-014-SECTION-94 · 25 content blocks
The Engineering Compiler shall accept authoritative inputs only from authenticated and authorized sources.
Compiler inputs shall identify:
- Source.
- Creator or issuing system.
- Approval status.
- Version.
- Effective date.
- Integrity hash or signature where required.
- Applicable scope.
- Authority class.
- Dependencies.
- Known limitations.
Inputs may include:
- BDL packages.
- Building BIOS baselines.
- Engineering Rules.
- Interface specifications.
- Engineering Profiles.
- Product records.
- Material and environmental data.
- Test and certification evidence.
- Authorized design decisions.
Untrusted, expired, withdrawn, conflicting, or unverifiable inputs shall be rejected, quarantined, or restricted according to their consequence.
AI-generated text, inferred values, informal messages, uncontrolled spreadsheets, or manufacturer claims shall not become authoritative compiler instructions merely because they are machine-readable.
External dependencies shall be version-pinned or otherwise controlled. A compilation result shall not change because an external database, service, model, or standard was silently updated.