Engineering and Reliability
Evidence chronologies for failures, maintenance records and system capacity, with engineering judgment left to engineers.
Architecture defined The data model, risks, controls and intended decisions are documented. No operating system is implied. Risk tier 3 / 4
Problem
Reliability questions depend on records that are scattered across operators, regulators and maintenance systems, and a headline number often hides what was actually tested.
Evaluation method
Claims are traced to sources. Operational use would need evaluation against current system data.
Human review
Licensed engineers or the responsible safety authority decide. Public demonstrations have not had that review unless stated.
Decision authority
Delta Arc holds no engineering licence. Authority stays with licensed engineers, operators and regulators.
Permitted uses
- Public-record chronologies
- Comparing figures by method and evidence state
- Preparing questions for qualified engineers
Prohibited uses
- Engineering determinations or stamped opinions
- Airworthiness or safety certification decisions
- Maintenance instructions
- Reliability findings presented as fact
- Allocating liability
Decisions this could support
- Which records establish what happened and when
- Which capacity or failure figures measure different things
- What an engineer needs to verify next
Source hierarchy, strongest first
- Regulator and investigator records
- National laboratory and standards body publications
- Operator filings
- Press reporting, for context only
Domain rules
- Different figures stay attached to their own methods
- Open investigations are labeled as open
- No conclusion about fault
Data restrictions
- No controlled technical data
- No operator-confidential records without a written agreement
Applicable standards
- ISO 55000 asset management
- ISO 14224 reliability data
- IEC 61508 functional safety
- NERC reliability standards
Not claimed
- Professional engineering services
- Certification or airworthiness authority
Evidence in this domain
What a Poor Bridge Rating Can Establish
A National Bridge Inventory Poor rating records component deterioration; it is not by itself a finding that a bridge is unsafe.
Reopening Is Not Closure
An authority returning to normal does not tell you which recommendations were closed. Those are separate records.
An Allotment Is Not a Replacement
A published funding allotment marks one step. It does not show a grant, a dollar spent or a pipe removed.
A Cohort Rate Is Not a Conversion Factor
Thirteen percent of past queue requests reached operation. That does not mean 13 percent of today's queue will.
Where the evidence lives
14 primary sources, with what each can and cannot establish.
Proofs of concept in this domain
Examples, not limits. A reusable core does not replace domain validation. Each implementation needs its own sources, rules, controls, testing and qualified review for its intended use.