{"schema_version":1,"research_id":"eoa_inverse_innovation_exp03_external48_20260801","source_assessment_id":"eoa_inverse_innovation_exp03_opportunity320_20260801","cell_id":"layer_decay_and_expiration_management__music_musicology","selection_stratum":"MIDDLE_BAND_AUDIT_Q3","search_queries":["site:music-encoding.org guidelines revisionDesc status superseded MEI","digital scholarly edition versioning current version superseded editions users official guidelines","music digital critical edition versioning persistent citation edition versions","site:digital-weber-gesamtausgabe.de version history digital edition","official repository withdrawal tombstone preservation policy version successor link archive quarantine","DataCite metadata IsPreviousVersionOf IsNewVersionOf version official","NDSA Levels of Digital Preservation fixity restore official storage","study performers wrong outdated score version digital sheet music revisions","digital music edition user study version citation problem","site:bls.gov/ooh archivists curators median pay 2025","Edition Humboldt digital old version newer version warning permalink","Global Indigenous Data Alliance CARE principles authority to control official"],"sources":[{"source_id":"S1","title":"Music Encoding Initiative Guidelines, Chapter 3: Metadata in MEI","publisher":"Music Encoding Initiative","url":"https://music-encoding.org/guidelines/v5/content/metadata.html","source_class":"STANDARD","publication_date":"undated; MEI Version 5.1","accessed_at":"2026-08-02","claims_supported":["MEI supports file descriptions, source descriptions, editorial declarations, responsibility statements, restrictions, revision histories, and associations between metadata and notation.","MEI states that revision histories are important for version control and that absent change logs, different file versions can be confused.","MEI recommends recording changes and identifies responsible agents and dates, but revisionDesc is optional and is not a discovery-demotion or retention system."]},{"source_id":"S2","title":"Digital Editions and Version Numbering","publisher":"Digital Humanities Quarterly","url":"https://dhq.digitalhumanities.org/vol/14/2/000455/000455.html","source_class":"PRIMARY_RESEARCH","publication_date":"2020","accessed_at":"2026-08-02","claims_supported":["A review of 30 recommended digital editions found version numbers in 23 percent and separately versioned individual data files in 13 percent.","Digital editions function as both scholarly publications and data, making identification of their changing states important to human and machine users.","The article documents a versioning policy for an operating scholarly edition and explains that release tagging alone works only when a repository state is explicitly labeled."]},{"source_id":"S3","title":"How to cite this digital edition?","publisher":"Digital Humanities Quarterly","url":"https://dhq.digitalhumanities.org/vol/15/3/000561/000561.html","source_class":"PRIMARY_RESEARCH","publication_date":"2021","accessed_at":"2026-08-02","claims_supported":["The study analyzed citation, permalink, and versioning practices across hundreds of digital scholarly editions and found that most still lacked a versioning strategy.","It reports user concerns about stability and uncertainty about citing digital resources.","It identifies actual practices including citable old versions, canonical current URLs, newer-version warnings, change histories, and tombstone pages.","It cautions that indiscriminate fine-grained versioning can create unnecessary versions that confuse users and increase storage and maintenance burdens."]},{"source_id":"S4","title":"Digital Methodology – edition humboldt digital","publisher":"Berlin-Brandenburg Academy of Sciences and Humanities","url":"https://edition-humboldt.de/about/index.xql?id=H0021024&l=en","source_class":"OFFICIAL_ORGANIZATION_DATA","publication_date":"2025-06-04","accessed_at":"2026-08-02","claims_supported":["An operating digital scholarly edition retains each annual published version, supplies version-specific permalinks and citation guidance, and maintains canonical URLs resolving to current versions.","The edition uses persistent identifiers, Git-based technical versioning, long-term Zenodo archiving, a public version history, and linked data dependencies.","The interface itself is not publicly versioned, illustrating that different editorial layers can have different lifecycle coverage."]},{"source_id":"S5","title":"Versions – edition humboldt digital","publisher":"Berlin-Brandenburg Academy of Sciences and Humanities","url":"https://edition-humboldt.de/about/index.xql?id=H0020382&l=en","source_class":"OFFICIAL_ORGANIZATION_DATA","publication_date":"2026-06","accessed_at":"2026-08-02","claims_supported":["The edition continued through version 12 in 2026.","Its version history covers thousands of journals, documents, letters, articles, index entries, and cross-linked entities, demonstrating that explicit version management can operate at substantial scholarly-edition scale."]},{"source_id":"S6","title":"Versioning","publisher":"Stanford Digital Repository Services","url":"https://sdr.library.stanford.edu/documentation/versioning","source_class":"OFFICIAL_ORGANIZATION_DATA","publication_date":"2024-08","accessed_at":"2026-08-02","claims_supported":["Stanford's repository exposes current and previous public versions, labels the version being viewed, and warns users when they view an older version.","Older versions remain available for citation while users receive a direct link to the latest version.","The repository distinguishes preservation history from the subset of versions intentionally exposed to the public."]},{"source_id":"S7","title":"Versioning","publisher":"DataCite","url":"https://support.datacite.org/docs/versioning","source_class":"STANDARD","publication_date":"2025-08","accessed_at":"2026-08-02","claims_supported":["DataCite provides standard IsNewVersionOf, IsPreviousVersionOf, HasVersion, and IsVersionOf relationships.","It recommends separate DOIs for major versions, metadata updates for minor versions, and explicit links between superseding versions.","Individual stewards determine the boundary between major and minor versions."]},{"source_id":"S8","title":"Preservation policy","publisher":"University of Edinburgh Research Data Service","url":"https://library.ed.ac.uk/research-support/research-data-service/after/data-repository/service-policies/preservation-policy","source_class":"OFFICIAL_GUIDANCE","publication_date":"2024-08-21","accessed_at":"2026-08-02","claims_supported":["The repository retains original bitstreams, backups, and checksums.","Withdrawn objects are removed from public view rather than deleted, with persistent tombstone citations, reasons, and replacement links.","Earlier and later versions are linked and the most recent version is clearly identified."]}],"problem_evidence":{"support":"MODERATE","rationale":"The problem is externally recognizable: music-specific MEI guidance explicitly warns that missing change logs makes file versions easy to confuse, while empirical studies find version identification uncommon across digital scholarly editions and explain resulting citation and authority ambiguity. However, the search found no measured incidence of performers or music scholars actually selecting superseded music-edition layers as endorsed, so music-specific prevalence and consequence magnitude remain unverified.","source_ids":["S1","S2","S3"]},"stakeholder_evidence":{"support":"WEAK","rationale":"Humanities users have reported stability and citation concerns, and operating scholarly editions and repositories have invested in version histories, canonical-current links, and old-version warnings. That demonstrates relevant institutional behavior, but no music-edition editor, performer, repository steward, rights holder, or community custodian was found requesting or committing resources to this full lifecycle bundle.","source_ids":["S3","S4","S6"]},"prior_art":{"proximity":"SUBSTANTIAL_COLLISION","closest_analogues":[{"name":"edition humboldt digital versioning and citation architecture","similarity":"An actual scholarly edition retains published versions, exposes version-specific permalinks and citation guidance, provides canonical current URLs, publishes a change history, uses Git internally, and archives data externally.","remaining_difference":"It versions whole published data releases rather than assigning current, superseded, archived, quarantined, and deletion-eligible states to heterogeneous within-work music layers; its public documentation does not describe dependency-gated quarantine, restore testing, preservation holds, or periodic exception revalidation.","source_ids":["S4","S5"]},{"name":"Stanford Digital Repository public versioning","similarity":"It preserves history, exposes selected prior versions, identifies the viewed version, warns on old versions, and links users to the latest version.","remaining_difference":"It is repository-item versioning, not scholarly classification of encodings, source transcriptions, annotations, renders, and editorial decisions by value, dependency, rights, or cultural-custody status.","source_ids":["S6"]},{"name":"University of Edinburgh repository withdrawal and tombstone policy","similarity":"It demotes withdrawn content from public view without deleting it, preserves identifiers and tombstones, links replacements, retains original bitstreams, and uses checksums.","remaining_difference":"Withdrawal is governed by repository-level legal or research-integrity reasons, not a recurring music-editorial lifecycle with fine-grained successor relationships, contested-reading protections, restoration trials, and revalidation.","source_ids":["S8"]}],"distinctive_claim_remaining":"The remaining bounded claim is not versioning, successor linking, latest-version warnings, tombstones, or reversible public withdrawal; those have close actual precedents. The testable difference is whether integrating object-level lifecycle states with music-editorial identity and dependency checks, scholarly and cultural holds, reversible quarantine, restore verification, and periodic revalidation reduces mistaken-current retrieval beyond a strong version-history-plus-latest-link baseline without obscuring significant variants or damaging reconstruction.","confidence":"HIGH"},"implementation_evidence":{"support":"STRONG","rationale":"The principal components already exist in standards and production systems: MEI supplies music-specific revision, responsibility, source, and restriction metadata; DataCite supplies successor relations; scholarly editions and repositories expose current and prior versions; repository policies implement withdrawal, tombstones, checksums, and preserved originals. Integration and reliable dependency discovery for heterogeneous music layers remain untested, but basic technical feasibility is well supported.","source_ids":["S1","S4","S6","S7","S8"]},"scores":{"meaningful_impact":{"score":3,"rationale":"Clear version identity protects citation and scholarly interpretation, and MEI itself identifies version confusion as a risk. Impact is capped because this search found no music-specific incident rate, performance harm, or maintenance-cost measurement.","source_ids":["S1","S2","S3"]},"stakeholder_pull":{"score":2,"rationale":"Users express general stability and citation concerns and institutions have implemented related features, but there is no direct demand, commitment, or willingness-to-pay evidence from a digital music-edition project.","source_ids":["S3","S4","S6"]},"incremental_advantage":{"score":3,"rationale":"Against folders or a latest pointer, the bundle adds meaningful safeguards; against the strongest actual baseline, most user-facing functions already exist. The residual advantage is dependency-aware, authority-governed classification and reversible quarantine across heterogeneous layers, whose effect has not been tested.","source_ids":["S4","S6","S7","S8"]},"distinctiveness_plausibility":{"score":2,"rationale":"The exact music-layer bundle was not located, but close scholarly-edition and repository systems cover version histories, latest pointers, warnings, successor links, withdrawal, tombstones, preserved originals, and checksums. Distinctiveness therefore rests on integration and domain granularity, not new component mechanisms.","source_ids":["S4","S6","S7","S8"]},"technical_implementability":{"score":4,"rationale":"Required metadata and repository behaviors are demonstrated in standards and operating services. The principal technical uncertainty is whether citations, derivatives, identifiers, and restrictions can be resolved with adequate recall before demotion or quarantine.","source_ids":["S1","S4","S6","S7","S8"]},"adoption_authority_feasibility":{"score":3,"rationale":"Scholarly-edition teams and repository services demonstrably operate version policies, making editor-steward governance credible. Feasibility is reduced by the need for joint decisions and by culturally responsive archival guidance requiring institution-and-community interpretation for affected materials.","source_ids":["S4","S6","S8"]},"evidence_readiness":{"score":4,"rationale":"Prior work identifies observable version-selection and citation problems and supplies a strong comparator consisting of citable history plus a canonical-current link or warning. A sandbox retrieval study can therefore measure mistaken-current selection and reconstruction without production changes.","source_ids":["S2","S3","S4","S6"]},"safety_net_benefit":{"score":5,"rationale":"Preserved originals, public-view withdrawal rather than deletion, persistent tombstones, replacement links, and checksums are established repository controls. They closely support the candidate's delete-nothing, reversible-quarantine first step.","source_ids":["S8"]},"scalability":{"score":3,"rationale":"MEI and DataCite provide reusable metadata, and edition humboldt demonstrates version management across thousands of interconnected objects. Scaling classification decisions remains constrained by scholarly significance, incomplete dependencies, rights, and collection-specific judgment.","source_ids":["S1","S5","S7","S8"]}},"score_confidence":"MODERATE","costs":{"first_evidence":{"band_2026_usd":"10K_TO_50K","scope":"Non-destructive audit and sandbox comparison for one work, including expert editorial and repository labor, artifact and dependency inventory, citation and restriction review, protocol design, participant coordination, retrieval-task evaluation, accessibility checks, test storage, software configuration, and reporting; no production change or permanent deletion.","confidence":"MODERATE","assumptions":["The work has a bounded set of tens to low hundreds of candidate artifacts and no more than 20 objects enter simulated quarantine.","Existing repository exports, identifiers, MEI or equivalent metadata, and test infrastructure are available.","The band includes loaded labor and institutional overhead; national 2025 mean wages were about $70,640 for archivists, $98,770 for web developers, and $148,100 for software developers.","Legal, rights, and cultural review is limited to screening and exclusion of uncertain material, not adjudication or licensing.","No new equipment is purchased beyond modest test storage or software services."],"source_ids":["S1","S8"]},"initial_deployment_startup":{"band_2026_usd":"50K_TO_250K","scope":"One-project preparation covering metadata crosswalks, lifecycle policy, editor-steward authority workflow, rights and cultural-custody controls, dependency indexing, user-interface labels and warnings, audit logs, quarantine storage, restore procedures, software integration, security review, training, and prelaunch evaluation.","confidence":"LOW","assumptions":["The existing edition and repository platforms are extended rather than replaced.","Work requires meaningful fractions of archivist, developer, interface, project-management, and scholarly-editor capacity.","Existing identifiers and preservation storage can be reused.","No collection-wide format migration, rights clearance campaign, dedicated hardware purchase, or custom preservation platform is included.","The range allows for benefits, overhead, contracting, compliance, coordination, and quality assurance beyond published wage rates."],"source_ids":["S1","S4","S6","S7","S8"]},"operational_launch":{"band_2026_usd":"50K_TO_250K","scope":"Controlled launch across one established edition project, including backlog triage, metadata remediation, dependency and citation review, software and storage operation, access-control and rights checks, editor and custodian escalation, training, communications, monitored discovery changes, restoration drills, and comparative evaluation.","confidence":"LOW","assumptions":["Launch is limited to one project or coherent repository collection.","Most objects can be classified through metadata-assisted review, with expert escalation for ambiguity.","Cited, unique, contested, restricted, culturally governed, or dependency-uncertain objects are held and not demoted automatically.","Existing preservation and hosting equipment remains adequate.","The range excludes consortium-wide rollout, litigation, major digitization, and permanent deletion."],"source_ids":["S4","S6","S8"]},"annual_recurring":{"band_2026_usd":"10K_TO_50K","scope":"Annual one-project operation covering metadata and successor-link maintenance, exception and hold review, rights and cultural-custody coordination, storage and software services, access logging, checksum and restoration checks, incident monitoring, periodic user evaluation, training updates, and governance reporting.","confidence":"LOW","assumptions":["Artifact growth and dispute volume remain modest.","The workflow is integrated into ordinary editorial and repository operations rather than staffed by a dedicated team.","Existing equipment, repository software, and preservation storage continue to be available.","The band includes loaded part-time expert, technical, and coordination labor plus modest recurring services.","Major archive migration, format remediation, or legal proceedings would move costs above this band."],"source_ids":["S4","S8"]}},"verified_pipeline_gates":{"externally_supported_problem":{"status":"YES","reason":"MEI's official music-encoding guidance explicitly identifies confusion between file versions when change histories are absent, and empirical digital-edition studies show that clear version identification remains uncommon. The gate passes for problem existence, not for music-specific prevalence or impact magnitude.","source_ids":["S1","S2","S3"]},"externally_credible_adopter_or_authorizer":{"status":"YES","reason":"Operating academy edition teams and university repository services demonstrably set and administer version, citation, preservation, and withdrawal policies. A designated scholarly editor and repository steward are therefore credible authorizers, subject to local rights and custody authority.","source_ids":["S4","S6","S8"]},"distinct_testable_incremental_claim":{"status":"YES","reason":"The incremental claim can compare a strong established baseline—citable immutable versions plus a canonical-current link or old-version warning—with object-level lifecycle states, dependency checks, holds, and reversible quarantine. Mistaken-current selections and reconstruction failures are observable outcomes.","source_ids":["S4","S6","S8"]},"bounded_next_evidence_step":{"status":"YES","reason":"One work and at most 20 candidate artifacts can be evaluated in a read-only sandbox with fixed tasks, blinded condition order, predefined authority-confusion coding, and restore checks; no live discovery change or deletion is required.","source_ids":["S4","S6","S8"]},"no_unresolved_safety_or_authority_stop":{"status":"YES","reason":"The next step is safe only if it remains non-destructive, excludes cited, unique, contested, restricted, culturally governed, or dependency-uncertain material, and obtains editor-steward consent plus any applicable rights-holder or community-custodian approval.","source_ids":["S8"]},"credible_cost_scope_and_range":{"status":"YES","reason":"The one-work evidence scope and one-project implementation scope are bounded, while broad bands accommodate expert, developer, compliance, coordination, software, storage, and evaluation uncertainty. Existing systems demonstrate that extension rather than greenfield construction is plausible.","source_ids":["S1","S4","S6","S8"]}},"next_evidence_step":"In one consenting project, preregister a non-live study of one work and no more than 20 candidate artifacts. First audit identities, citations, derivatives, restrictions, and scholarly significance. Then have representative users complete fixed retrieval and provenance-reconstruction tasks in counterbalanced sandbox conditions: (A) the strongest established baseline of immutable citable history plus canonical-current link and old-version warning, as in S4 and S6; and (B) that baseline plus explicit current/superseded/archived/quarantined labels, successor links, dependency and preservation holds, and restore-verified simulated quarantine. Compare mistaken-current selection rates, correct-version retrieval, reconstruction success, and visibility of contested readings. Falsify the incremental opportunity if condition B does not reduce mistaken-current selections, if the audit finds no material stale-authority burden, or if any included artifact, citation path, restriction, or provenance chain cannot be reconstructed and restored exactly. Make no production discovery change and permanently delete nothing.","blocking_evidence":["Music-specific prevalence remains unknown: S1 establishes that version confusion is possible, but S2 and S3 do not measure mistaken-current retrieval in digital music editions.","Direct stakeholder pull is missing: S3 documents general humanities citation and stability concerns, while S4 and S6 show institutional implementation rather than demand from performers, music scholars, or music editors.","The recall of identity, citation, derivative, and dependency discovery is unmeasured; S1 supports rich metadata but does not guarantee complete project records.","Marginal benefit over substantial prior art is unmeasured: S4, S6, and S8 already implement most visible lifecycle functions.","Local authority and restrictions must be verified before any project-specific study; repository policy in S8 establishes institutional controls but cannot substitute for project, rights-holder, or custodian consent.","Implementation effort depends on repository condition and backlog size; the published systems in S4-S8 do not provide directly transferable music-project cost histories."],"research_disposition":"KNOWN_PRACTICE_DIFFUSION","world_novelty_boundary":"This bounded English-language search found substantial prior art for version histories, current-version pointers, old-version warnings, version-specific citation, successor metadata, reversible withdrawal, tombstones, preserved originals, and integrity checks. It did not locate the full dependency-aware, authority-governed lifecycle bundle implemented for heterogeneous layers inside a digital critical music edition. That residual finding is not a world-novelty claim: non-English documentation, private project workflows, unpublished repository procedures, software code, and unindexed music-edition practices were not exhaustively searched."}