{"schema_version":1,"research_id":"eoa_inverse_innovation_exp04_external_evaluation_20260802","source_assessment_id":"layer_decay_and_expiration_management__aviation_aeronautics:PROPOSAL_FIRST:v0","cell_id":"layer_decay_and_expiration_management__aviation_aeronautics","search_queries":["site:faa.gov flight test data configuration control calibration data processing software configuration management","site:nasa.gov flight test data configuration management calibration files telemetry processing reproducibility","site:easa.europa.eu flight test data configuration control records retention","flight test instrumentation configuration management data processing calibration paper","IRIG 106 chapter 10 digital recording standard configuration metadata flight test official 2024","site:ch10.org flight test data metadata configuration standard IRIG 106 Chapter 10","ASAM ODS configuration management test data provenance versions official","flight test data management configuration lifecycle archive restore reproducibility","flight test data wrong calibration configuration analysis error incident report","site:nasa.gov mishap flight test data processing calibration configuration error","site:gov.uk military aviation flight test data configuration calibration records safety","FAA flight test data reduction calibration correction configuration management guidance","BLS aerospace engineers median pay May 2025 computer systems analysts software developers current","AWS S3 Glacier Deep Archive pricing official 2026 per GB","site:aws.amazon.com s3 pricing glacier deep archive data retrieval official","NASA flight test data archive information management configuration metadata","NIST contingency planning restore testing backups periodically test official SP 800-34","NARA digital records preservation fixity migration readable official guidance","FAA records retention flight test data configuration applicant certification records retention 14 CFR 21.49"],"sources":[{"source_id":"S1","title":"B2.3 - Integration of FTI Configuration Management with Flight Test Database for an Enhanced Digital Twin Development","publisher":"AMA Science / European Test and Telemetry Conference; authors from Turkish Aerospace","url":"https://www.ama-science.org/proceedings/details/5726","source_class":"PRIMARY_RESEARCH","publication_date":"2024-06-11","accessed_at":"2026-08-02","claims_supported":["Turkish Aerospace reports that flight-test-instrumentation configurations are managed across Excel, ERP, Jira, Teamcenter, DOORS, in-house tools, IADS, and other independent media.","The authors say this fragmentation divides work effort and propose consolidating FTI configuration management with flight-test data management to improve integrity, accuracy, reliability, and accessibility.","This is direct evidence of a named potential adopter expressing a closely related need, but it does not report stale-selection incidence, deletion failures, or measured intervention outcomes."]},{"source_id":"S2","title":"FAA Order 8200.48, Flight Inspection Standards","publisher":"Federal Aviation Administration","url":"https://www.faa.gov/documentLibrary/media/Order/8200.48.pdf","source_class":"OFFICIAL_GUIDANCE","publication_date":"2024-09-20","accessed_at":"2026-08-02","claims_supported":["FAA Flight Program Operations requires measurement-accuracy documentation and requires subsequent software-algorithm or avionics changes to continue meeting applicable standards.","Calibration procedures and intervals must be maintained; procedure or tolerance changes require acceptance by the Flight Program Operations Director of Maintenance.","Equipment build state and modifications must be recorded and updated, while formulas and algorithms used in flight-inspection measurements are subject to high safety and quality-assurance standards.","These controls demonstrate that configuration applicability and processing-algorithm identity can matter to safety-relevant aeronautical measurements."]},{"source_id":"S3","title":"Easy Access Rules for Initial Airworthiness and Environmental Protection, GM1 21.A.5 Record-keeping","publisher":"European Union Aviation Safety Agency","url":"https://www.easa.europa.eu/en/document-library/easy-access-rules/online-publications/easy-access-rules-initial-airworthiness-and?page=8","source_class":"GOVERNMENT_OR_REGULATOR","publication_date":"2024-07","accessed_at":"2026-08-02","claims_supported":["EASA states that design records are essential for configuration control and certification-basis compliance.","Required procedures identify retained records, assign archive responsibility and access, protect against deterioration or alteration, ensure continued readability, and define archive periods.","Design and continuing-airworthiness data may need retention throughout the product's operational life, constraining automatic deletion and requiring authorized retention classes."]},{"source_id":"S4","title":"IRIG Standard 106-24 Telemetry Standards","publisher":"Range Commanders Council, Telemetry Group","url":"https://www.irig106.org/wiki/irig_106-24","source_class":"STANDARD","publication_date":"2024-10","accessed_at":"2026-08-02","claims_supported":["IRIG 106 is an established aeronautical telemetry standard covering recorder formats, telemetry-attribute transfer, metadata configuration, and derived-parameter specification.","It supplies important interoperability and metadata prior art but does not, on the opened page, prescribe active-visibility expiry, dependency-gated disposition, quarantine, or archive-reprocessing tests."]},{"source_id":"S5","title":"ASAM ODS 6.2.1","publisher":"Association for Standardisation of Automation and Measuring Systems","url":"https://www.asam.net/standards/detail/ods/","source_class":"STANDARD","publication_date":"2026-01-26","accessed_at":"2026-08-02","claims_supported":["ASAM ODS is an established standard for persistent storage and retrieval of measured and calculated test data.","Its models cover test-stand calibration, testing workflows, instrumentation, relational storage, file exchange, and APIs.","ODS provides adaptable semantics so different clients can retrieve and interpret testing data, substantially overlapping the candidate's inventory, metadata, retrieval, and integration layer."]},{"source_id":"S6","title":"About the Digital Preservation Program","publisher":"U.S. National Archives and Records Administration","url":"https://www.archives.gov/preservation/digital-preservation/about","source_class":"OFFICIAL_GUIDANCE","publication_date":"2026-03-20","accessed_at":"2026-08-02","claims_supported":["NARA's preservation practice records fixities and preservation actions, captures descriptive and structural metadata, validates formats, creates manifests and logs, and performs regular audits.","NARA reports annual media sampling, periodic media migration, infrastructure monitoring, and regular emergency backup-restoration tests.","These practices support the technical plausibility and necessity of testing archives rather than treating file presence as proof of reconstructability."]},{"source_id":"S7","title":"National employment and wage data by occupation, May 2025","publisher":"U.S. Bureau of Labor Statistics","url":"https://www.bls.gov/news.release/ocwage.t01.htm","source_class":"OFFICIAL_ORGANIZATION_DATA","publication_date":"2026","accessed_at":"2026-08-02","claims_supported":["Mean annual wages reported for software developers and aerospace engineers are approximately $148,100 and $142,060 respectively; aerospace engineering technologists and technicians average about $91,310.","These wage levels support labor-dominated 2026 resource estimates after applying employer overhead, security, tooling, and management load assumptions."]},{"source_id":"S8","title":"Amazon S3 Glacier storage classes","publisher":"Amazon Web Services","url":"https://aws.amazon.com/s3/storage-classes/glacier/","source_class":"COMMERCIAL_FIRST_PARTY","publication_date":"undated","accessed_at":"2026-08-02","claims_supported":["Commercial hot-to-cold archival tiering is readily implementable, with retrieval options ranging from milliseconds to hours.","AWS lists S3 Glacier Deep Archive at $0.00099 per GB-month with retrieval within about twelve hours and high stated durability.","Storage media cost can be small relative to engineering, metadata reconciliation, controlled migration, security, licensing, validation, and restore-testing labor."]}],"problem_evidence":{"support":"MODERATE","rationale":"The problem class is visible and consequential: Turkish Aerospace directly reports fragmented FTI configuration and flight-test data-management media and seeks consolidation for integrity, accuracy, and reliability. FAA guidance independently shows that calibration state, algorithm changes, equipment build state, and documentation are controlled because measurement validity depends on them; EASA requires configuration-relevant records to remain readable and retrievable. However, no opened source quantifies how often obsolete processing packages remain ordinarily selectable, cause erroneous analyses, or become irretrievable. The candidate-specific prevalence and realized harm therefore remain unverified.","source_ids":["S1","S2","S3"]},"stakeholder_evidence":{"support":"STRONG","rationale":"Turkish Aerospace is an identifiable prospective adopter that has publicly expressed a closely matching integration need. Within regulated workflows, flight-test or flight-inspection configuration managers and chief engineers have operational authority, while FAA/EASA requirements and records or safety authorities constrain calibration changes, retention, access, and destruction. Evidence identifies plausible adopters and authorizers, although no organization has committed to this exact lifecycle-expiry pilot.","source_ids":["S1","S2","S3"]},"prior_art":{"proximity":"SUBSTANTIAL_COLLISION","closest_analogues":[{"name":"Turkish Aerospace integrated FTI configuration-management and flight-test database","similarity":"Directly proposes consolidating fragmented FTI configuration sources and flight-test data management to improve integrity, accuracy, reliability, and accessibility.","remaining_difference":"The published abstract does not describe expiry of ordinary selection visibility, inbound-dependency gates, reversible quarantine, tombstones, or end-to-end restoration of historical processing environments.","source_ids":["S1"]},{"name":"ASAM ODS test-data management standard","similarity":"Provides standardized persistent storage, metadata semantics, retrieval, calibration, instrumentation, workflow models, and tool-independent test-data interpretation.","remaining_difference":"The opened specification overview does not establish the candidate's aviation-specific applicability intervals or its combined expiry, hold, dependency, quarantine, and reconstruction-test policy.","source_ids":["S5"]},{"name":"FAA build-state, calibration, and flight-inspection software controls","similarity":"Requires recorded build state, controlled calibration procedures, documented algorithm changes, and evidence that changed configurations still meet measurement standards.","remaining_difference":"It governs accuracy and change control rather than bounding repository selection through lifecycle expiry or differentiated archival disposition.","source_ids":["S2"]},{"name":"IRIG 106 telemetry and metadata standards","similarity":"Standardizes aeronautical telemetry recording, metadata configuration, telemetry attributes, and derived-parameter specifications.","remaining_difference":"It does not supply the proposed repository-governance lifecycle or demonstrate safer package selection and historical reconstruction.","source_ids":["S4"]},{"name":"NARA digital-preservation and restoration practice","similarity":"Uses fixity, preservation metadata, manifests, audits, migration, monitoring, and restoration tests to maintain long-term usability.","remaining_difference":"It is generic archival practice, not an aviation processing-configuration selection and dependency-management system.","source_ids":["S6"]}],"distinctive_claim_remaining":"Against an existing immutable-version or manifest-based repository, adding applicability-aware expiry from ordinary new-run selection plus dependency- and hold-gated disposition, reversible quarantine, explicit tombstones, and exercised archive restoration will reduce stale-package selection errors by at least 30% in blinded tasks without causing any prespecified historical reconstruction to lose an exact configuration input. This is a contrastive and falsifiable systems-integration claim, not a claim that version control, test-data databases, metadata standards, retention schedules, tiered storage, or restore testing are individually novel.","confidence":"HIGH"},"implementation_evidence":{"support":"MODERATE","rationale":"Identity metadata, configuration-controlled baselines, standardized telemetry metadata, semantic test-data repositories, cold-storage tiering, fixity checks, audit logs, and restoration tests are all technically established. A read-only metadata overlay and prototype selection interface are therefore implementable without changing aircraft systems. The main uncertainties are organizational and empirical: unique identity reconciliation across legacy stores, completeness of inbound dependency discovery, proprietary-tool and license recreation, export-controlled or proprietary data handling, records-classification authority, analyst behavior, and deterministic reconstruction across changed runtimes. Production deletion cannot be delegated to a score and must remain subject to engineering, records, investigation, contractual, and legal holds.","source_ids":["S2","S3","S4","S5","S6","S8"]},"scores":{"meaningful_impact":{"score":4,"rationale":"Correct processing configuration affects measurement integrity and evidence used in engineering or airworthiness decisions; successful historical reconstruction also has substantial investigation and compliance value. Frequency and realized impact are not quantified.","source_ids":["S1","S2","S3"]},"stakeholder_pull":{"score":4,"rationale":"A named aerospace manufacturer publicly describes fragmented FTI configuration systems and seeks an integrated solution, while regulators visibly require related controls. No commitment to this exact intervention is documented.","source_ids":["S1","S2","S3"]},"incremental_advantage":{"score":3,"rationale":"The proposed bundle could improve selection safety and lifecycle accountability beyond static versioning or campaign closeout, but the incremental benefit over a well-implemented manifest, configuration-management database, and interface filter requires live comparison.","source_ids":["S1","S2","S5"]},"distinctiveness_plausibility":{"score":2,"rationale":"Most components are established in configuration management, test-data standards, regulated records control, archival tiering, and digital preservation. Distinctiveness is limited to their aviation-specific integration and measurable workflow effect.","source_ids":["S1","S2","S3","S4","S5","S6"]},"technical_implementability":{"score":4,"rationale":"Existing standards, metadata repositories, archival services, fixity mechanisms, and restore practices make a read-only prototype credible. Legacy identity, dependency, runtime, and licensing reconstruction remain material difficulties.","source_ids":["S4","S5","S6","S8"]},"adoption_authority_feasibility":{"score":3,"rationale":"Configuration managers and chief engineers can sponsor a read-only pilot, but production disposition requires coordination with engineering, records, safety, security, certification, contractual, and investigative authorities.","source_ids":["S2","S3"]},"evidence_readiness":{"score":3,"rationale":"The candidate supplies a bounded design and falsifiers, and external evidence supports the surrounding need and mechanisms. The decisive repository inventory, behavior comparison, dependency audit, and restoration results require proprietary campaign data and participant testing.","source_ids":["S1","S2","S5","S6"]},"safety_net_benefit":{"score":4,"rationale":"Quarantine, holds, explicit markers, immutable identities, and restoration exercises directly limit irreversible deletion and ambiguous absence, provided they are independently authorized and tested.","source_ids":["S3","S6"]},"scalability":{"score":3,"rationale":"Standards and commodity tiered storage support reuse across campaigns, but each aircraft program has different data rights, toolchains, schemas, dependencies, and retention authorities; scaling is more governance- and integration-limited than storage-limited.","source_ids":["S3","S4","S5","S8"]}},"score_confidence":"MODERATE","costs":{"first_evidence":{"band_2026_usd":"50K_TO_250K","scope":"Six-to-ten-week read-only study of one completed campaign: reconcile 30 packages, map manifests and holds, build a lightweight filtered-interface prototype, run blinded selection tasks, and restore five archived packages on test copies.","confidence":"MODERATE","assumptions":["Approximately 0.3-0.6 FTE software/data engineer, 0.3-0.6 FTE aerospace or flight-test engineer, part-time configuration/records authority, analyst participation, and 25-50% overhead or contractor premium.","No production integration, aircraft change, authoritative deletion, new certification basis, or large-scale data migration.","The sampled artifacts are already legally accessible and can be copied into an approved offline environment."],"source_ids":["S7","S8"]},"initial_deployment_startup":{"band_2026_usd":"250K_TO_1M","scope":"Single-program controlled implementation: authoritative identity and metadata schema, repository connectors, role-based selection filter, dependency registry, quarantine and tombstone functions, archive packaging, security review, procedures, and validation.","confidence":"LOW","assumptions":["Two-to-five loaded engineering FTE-equivalents for roughly six to twelve months plus program subject-matter review.","Existing repositories expose usable APIs or exports; no replacement of the primary flight-test data platform.","Legacy runtime licenses and export-controlled environments are available rather than newly procured."],"source_ids":["S5","S7","S8"]},"operational_launch":{"band_2026_usd":"1M_TO_5M","scope":"Organization-level launch across multiple active and completed campaigns, including legacy inventory reconciliation, production integrations, migration, access controls, authority approvals, validation, training, restore infrastructure, and monitored rollout.","confidence":"LOW","assumptions":["A multidisciplinary team of roughly 6-15 loaded FTE-equivalents for one to two years plus vendor, cybersecurity, records, and validation effort.","No aircraft or airborne-software modification and no attempt to ingest every historical raw-data byte into a new platform.","Costs are dominated by reconciliation, integration, assurance, and governance rather than cold-storage media."],"source_ids":["S2","S3","S5","S7","S8"]},"annual_recurring":{"band_2026_usd":"250K_TO_1M","scope":"Ongoing configuration curation, policy and hold review, dependency maintenance, access administration, archive storage, restore drills, format/runtime migration, audits, user support, and incident response for one flight-test organization.","confidence":"LOW","assumptions":["Two-to-five loaded FTE-equivalents, depending on campaign volume and automation.","Cold storage is priced near commodity archival tiers, but retrieval, active copies, tooling, security, and labor add cost.","No unusually large proprietary-license renewal or mandatory wholesale legacy conversion."],"source_ids":["S6","S7","S8"]}},"verified_pipeline_gates":{"externally_supported_problem":{"status":"YES","reason":"A named flight-test organization reports fragmented configuration and data-management media and links integration to integrity, accuracy, and reliability; FAA and EASA sources independently establish the importance of configuration, calibration, and retrievable records. Candidate-specific prevalence remains a field-measurement gap, not a failure of the existence gate.","source_ids":["S1","S2","S3"]},"externally_credible_adopter_or_authorizer":{"status":"YES","reason":"Turkish Aerospace is an identifiable prospective adopter expressing a related need. FAA guidance identifies operational acceptance authority for calibration changes, and EASA rules make design/production organizations and competent authorities credible authorizers for records controls.","source_ids":["S1","S2","S3"]},"distinct_testable_incremental_claim":{"status":"YES","reason":"The remaining claim compares an existing versioned/manifest repository with an applicability-filtered lifecycle interface and requires a measurable reduction in stale selections with no loss of historical reconstruction.","source_ids":["S1","S2","S5","S6"]},"bounded_next_evidence_step":{"status":"YES","reason":"A one-campaign, 30-package, five-restore, read-only crossover pilot has explicit comparators, metrics, success conditions, and stop rules and does not require production changes.","source_ids":["S2","S6"]},"no_unresolved_safety_or_authority_stop":{"status":"YES","reason":"For the bounded pilot only, test copies and proposed states avoid operational or destructive changes. Production disposition remains prohibited until holds, records authority, engineering authority, security, and reconstruction requirements are resolved.","source_ids":["S2","S3","S6"]},"credible_cost_scope_and_range":{"status":"YES","reason":"The four bands specify materially different scopes and state labor, integration, storage, and authority assumptions. Confidence is limited because repository size, legacy condition, licenses, and organizational assurance requirements are unknown.","source_ids":["S5","S7","S8"]}},"next_evidence_step":"With the configuration manager, chief engineer, records/safety representative, and data owner, pre-register a read-only pilot using approved test copies from one completed campaign. Sample 30 packages stratified as current, superseded, referenced, apparently orphaned, and archived. Two configuration engineers independently classify identity, aircraft/modification applicability, successor, dependencies, holds, and proposed state; reconcile against immutable flight manifests, reports, scripts, and investigation records. Randomize blinded analysts in a crossover comparison between the existing interface and a prototype that expires superseded packages from ordinary new-run selection while preserving explicit historical lookup. Use at least 20 scenario selections spanning historical reconstruction and hypothetical new runs. Separately restore five archived packages across age/format bands, verify hashes and exact input manifests, recreate the declared runtime, and compare deterministic inputs and outputs where supported. Record selection-error rate, time, confidence, inter-rater agreement, unsupported classifications, dependency misses, hold conflicts, restore latency/failure, and every proposed transition that would impair reconstruction. Advance only if stale-selection errors fall at least 30%, no correct-package availability is reduced, no held or referenced package is classified for irreversible removal, and all five packages restore with exact configuration inputs. Falsify the intervention for this scope if the error reduction is below 30%, any lifecycle filter hides the only applicable package, any proposed disposition conflicts with a verified dependency or hold, or any baseline-reconstructable case becomes unreconstructable. Make no production visibility, retention, or deletion changes.","blocking_evidence":["No externally measured prevalence of stale or ambiguously applicable processing configurations in a real flight-test repository.","No comparative evidence that lifecycle filtering improves analyst selection beyond immutable manifests, conventional configuration control, or a current-package filter.","No verified dependency graph showing that reports, plots, scripts, investigations, and external consumers can be discovered completely enough for disposition decisions.","No demonstration that archived packages, compatible tools, credentials, licenses, and runtimes can reconstruct historical processing rather than merely restore files.","No organization-specific mapping of certification records, legal or investigation holds, export controls, proprietary data rights, required destruction, and final disposition authority.","No empirical inventory volume, access pattern, storage footprint, integration complexity, or vendor quotation to narrow deployment and recurring costs.","No measurement of administrative burden, false-positive staleness flags, or the risk that expiry terminology is misread as destruction authority."],"research_disposition":"PARTNERED_RESEARCH_PROGRAM","world_novelty_boundary":"The search evaluated visible problem evidence, identifiable stakeholders, adjacent standards, products/practices, feasibility, and a contrastive claim. It did not establish world novelty, patentability, freedom to operate, market size, or realized impact. No close source found the entire aviation-specific combination of active-selection expiry, dependency- and hold-gated differentiated disposition, reversible quarantine, tombstones, and exercised reconstruction, but absence from this bounded search is not evidence of novelty.","arm":"PROPOSAL_FIRST","candidate_version":0,"controller_recommendation":{"action":"STOP_EMPIRICAL_RESEARCH_NEEDED","repairable":true,"material_progress_observed":true,"progress_targets":["Secure one flight-test organization and named configuration, engineering, records/safety, security, and data authorities for a read-only completed-campaign study.","Produce a reconciled inventory quantifying ambiguous identities, missing applicability metadata, superseded packages exposed for ordinary selection, verified dependencies, holds, and baseline reconstruction success.","Run the preregistered baseline-versus-lifecycle interface comparison and report selection errors, time, confidence, and adverse hidden-package events.","Complete five end-to-end archive restorations across age and format bands, including exact-input and runtime compatibility checks.","Build an organization-specific authority and retention matrix that distinguishes active expiry, archival demotion, quarantine, permanent retention, and authorized destruction.","Replace broad cost assumptions with repository volumes, integration estimates, staffing plans, licensing constraints, security requirements, and at least one implementation quotation.","Document a feature-level prior-art comparison against the organization's existing manifest/configuration system, ASAM ODS-compatible tools, IRIG metadata practices, and available test-lifecycle platforms."],"reason":"Bounded web research supports the problem class, adopter credibility, regulatory importance, and technical components, while also showing substantial collision with established configuration management, test-data standards, record retention, tiered storage, and preservation practice. The remaining value claim is behavioral and organization-specific. It cannot be resolved by more public web searching because it requires proprietary repository inspection, analyst participation, dependency validation, authority review, and live restoration tests."}}