{"schema_version":1,"experiment_id":"eoa_inverse_innovation_exp06_four_proposal_generalization60_20260803","cell_id":"catalytic_pathway_enablement__sociology_anthropology","arm":"COMPLETE_PROPOSAL_PORTFOLIO","candidate_id":"cpe_sa_p02_ethnographic_archive_deposit_workbench","proposal_index":2,"version":0,"title":"Regenerative Deposit Workbench for Governed Ethnographic Archives","problem":"Completed ethnographic records that are already eligible for preservation can remain in personal or project storage because each deposit must reconstruct the same conversion work: interpreting documented use constraints, classifying sensitive material, applying approved transformations, creating contextual metadata, packaging files, and proving that the package satisfies repository requirements. The work is necessary, but its repeatable portions are handled as bespoke projects. Researchers encounter the barrier when funding and team continuity are declining, while archivists repeatedly diagnose preventable format and documentation defects. Cases with unresolved consent, ownership, community authority, or safety concerns are mixed with technically remediable cases, consuming review capacity without creating a legitimate route to deposit.","actors":["Ethnographers and principal investigators responsible for completed research records","Research participants and communities represented in the records","Community data-governance bodies or recognized cultural custodians where applicable","Institutional data stewards and records officers","Qualitative-data archivists and repository curators","Research ethics and privacy personnel","A deposit-workbench steward","Approved metadata, transcription, and disclosure-risk specialists","Future authorized archive users"],"observable_state":"Potential deposits arrive in inconsistent structures with missing inventories, undocumented transformations, incompatible formats, unclear links between consent terms and files, repeated repository queries, and uncertain access classifications. Archivists spend time rediscovering the same defects; researchers repeat manual renaming, redaction, metadata, and packaging steps; queue depth and specialist occupancy are not distinguished from rights or authority disputes; completed packages are sometimes rejected, repeatedly revised, or abandoned.","consequence":"Preservable material may deteriorate, become unintelligible, or lose its chain of responsibility while researchers and archivists spend scarce attention on repeated conversion work. Indiscriminate acceleration could produce the opposite harm by depositing identifying, sacred, politically dangerous, collectively governed, or otherwise restricted material under an invalid access designation.","affected_objective":"Increase the rate at which already-authorized ethnographic record sets become repository-ready deposits while preserving consent constraints, community and institutional authority, contextual integrity, disclosure protections, refusal and withdrawal provisions, and repository acceptance standards.","intervention":"Create a bounded archival deposit workbench: a versioned intake contract, prevalidated transformation recipes, auditable packaging automation, and an embedded archival specialist lane. Eligible record sets enter only after the responsible authorities attest that preservation and the proposed access class are permitted. The workbench inventories files, maps documented constraints to individual objects, applies only approved format, naming, metadata, and disclosure-control transformations, validates outputs, and releases a candidate package to independent repository review. Unresolved authority, undocumented provenance, inconsistent consent, sacred or culturally restricted content, exceptional reidentification risk, and ambiguous future-use conditions are quarantined and returned for bespoke governance rather than repaired by automation. After each cycle, case data are removed from the processing environment, logs and transformation manifests are sealed, test fixtures are rerun, rules are refreshed when governing conditions change, and degraded recipes or tools are retired.","structural_mapping":[{"archetype_element":"Target transformation specification","domain_realization":"Convert an authorized but unstructured ethnographic record set into a validated repository-ready package containing preserved files, contextual metadata, a transformation manifest, documented restrictions, and a proposed access class. Repository acceptance remains a separate decision."},{"archetype_element":"Activation barrier","domain_realization":"Repeated interpretation of repository specifications, file inventory, constraint-to-object mapping, approved de-identification, format normalization, contextual description, packaging, and evidence reconstruction."},{"archetype_element":"Permitted pathway boundary","domain_realization":"The pathway may execute only transformations already permitted by applicable consent, community governance, institutional responsibility, law, and repository policy. It cannot create missing authority or convert prohibited reuse into permitted reuse."},{"archetype_element":"Reusable facilitator","domain_realization":"A governed workbench comprising versioned recipes, validation rules, packaging automation, and a bounded specialist review lane that can process successive deposits without becoming part of the released archive package."},{"archetype_element":"Facilitator–substrate interface","domain_realization":"A published manifest defines required file inventories, provenance, consent and governance attestations, proposed access class, sensitive-content flags, allowed transformations, metadata fields, formats, and exception disclosures."},{"archetype_element":"Selectivity rule","domain_realization":"Only deposits with traceable authority, sufficiently documented constraints, supported formats, and approved transformation classes receive automated or templated processing. Ambiguity triggers quarantine or bespoke review."},{"archetype_element":"Cofactor system","domain_realization":"The workbench requires sufficient documentation, secure computing, maintained repository specifications, qualified specialist judgment, and where applicable community-governance input. These complements are recorded rather than hidden as free catalytic capacity."},{"archetype_element":"Turnover capacity","domain_realization":"Useful turnover is accepted or repository-ready packages per workbench cycle, reported with specialist minutes, automation runtime, queue time, exceptions, rework, false-clearance findings, and recovery time."},{"archetype_element":"Saturation and interference","domain_realization":"Queue depth, specialist occupancy, validation failures, unsupported formats, exception frequency, secure-storage availability, policy drift, and repository review capacity distinguish excess inflow from degraded facilitator activity."},{"archetype_element":"Regeneration cycle","domain_realization":"Case workspaces are purged according to policy, credentials and conflicts are reset, manifests and logs are sealed, validation suites are rerun, repository requirements are resynchronized, staff recover, and only verified recipes return to service."},{"archetype_element":"Byproduct guardrail","domain_realization":"Validation searches for unintended disclosure, loss of contextual meaning, detached restrictions, altered evidentiary relationships, corrupted files, over-redaction, under-redaction, and access classifications inconsistent with source authority."},{"archetype_element":"Equilibrium neutrality","domain_realization":"The workbench accelerates preparation only when legitimate preservation and access conditions already exist. It cannot settle ownership disputes, retroactively broaden consent, appoint a cultural authority, or make unsafe future use acceptable."},{"archetype_element":"Deactivation rule","domain_realization":"Affected recipes or the full workbench pause upon confidentiality breach, unexplained output mutation, invalid constraint mapping, policy drift, false clearance of an ineligible object, failed workspace purge, specialist overload, or downstream repository saturation."}],"mechanism_mapping":[{"mechanism_slug":"prevalidated_transformation_template","role":"Encodes repository-accepted packaging, metadata, manifest, and constraint-recording structures while exposing only the case-specific fields that depositors may fill.","counterfactual_removal":"Without the maintained template, each project reconstructs the repository pathway and its evidentiary structure from the beginning, preserving the recurring activation burden."},{"mechanism_slug":"workflow_automation_or_macro","role":"Executes approved file inventory, checksum, naming, format-normalization, manifest-generation, and validation steps while logging every transformation and routing failures to exception review.","counterfactual_removal":"Without reusable execution, case-proportional manual work remains the main source of throughput, so the intervention becomes ordinary archival labor rather than a catalytic pathway."},{"mechanism_slug":"interface_contract_design","role":"Declares admissible inputs, required authority evidence, permitted transformations, output guarantees, repository boundaries, and version compatibility.","counterfactual_removal":"Without a stable contract, malformed cases enter processing, handoffs require repeated negotiation, and changes in repository requirements can silently invalidate outputs."},{"mechanism_slug":"inhibitor_and_poison_screen","role":"Screens incoming deposits for unresolved rights, contradictory consent records, unsupported encryption or formats, undocumented provenance, sensitive-content flags, malicious files, and repository-policy mismatch before the workbench acts.","counterfactual_removal":"Without upstream screening, incompatible cases occupy scarce capacity or corrupt the workflow, and an automated package can falsely appear safe because the decisive ambiguity was never represented."},{"mechanism_slug":"embedded_specialist_review_lane","role":"Provides bounded archival and disclosure-risk judgment for exceptions that fit the pathway but cannot be resolved by deterministic validation, with workload caps and escalation outside the workbench.","counterfactual_removal":"Without specialist interpretation, the workbench either rejects every nontrivial case or lets automation make contextual and ethical judgments beyond its competence."},{"mechanism_slug":"catalyst_cofactor_system","role":"Makes secure infrastructure, current repository specifications, authority documentation, specialist time, and community-governance input explicit activation dependencies whose presence, sufficiency, and compatibility are checked.","counterfactual_removal":"Without cofactor accounting, the workbench may appear reusable while quietly consuming undocumented labor, authority, or security capacity and failing when those complements are absent."},{"mechanism_slug":"active_site_capacity_dashboard","role":"Shows admitted deposits, processing occupancy, specialist queue, exception rate, validation drift, secure-workspace availability, recovery state, and repository receiving capacity.","counterfactual_removal":"Without capacity observability, more deposits can be admitted into a saturated or degraded workbench, increasing exposure time, queueing, staff pressure, and unreviewed output."},{"mechanism_slug":"catalyst_regeneration_protocol","role":"Restores the workbench through secure case purge, credential reset, log sealing, regression testing, rule refresh, staff recovery, and retirement of recipes whose reliable activity cannot be recovered.","counterfactual_removal":"Without regeneration, residual data, stale restrictions, software drift, and accumulated specialist fatigue contaminate later cycles even though the workbench remains nominally available."},{"mechanism_slug":"turnover_and_selectivity_assay","role":"Measures good packages per workbench cycle against ordinary preparation while tracking ineligible admissions, missed restrictions, corruption, over-redaction, rework, labor transfer, and degradation over successive cycles.","counterfactual_removal":"Without a matched baseline and off-target measures, easier case selection, added specialist labor, or lower contextual standards could be mistaken for catalytic performance."},{"mechanism_slug":"small_safe_to_fail_probe","role":"Tests the workbench on bounded copies of closed deposits, with no authority to release or alter archival records and with precommitted failure thresholds.","counterfactual_removal":"Without a contained probe, systematic transformation or constraint-mapping errors would first be discovered in live deposits where disclosure or contextual loss could be irreversible."}],"causal_chain":["Completed record sets repeatedly confront similar technical and documentary conversion burdens even when their preservation pathway is already authorized.","A stable intake contract separates eligible, sufficiently documented deposits from cases requiring new ethical, legal, cultural, or political decisions.","Prevalidated recipes and auditable automation perform the repeatable inventory, normalization, metadata, manifest, and packaging work at low marginal effort.","A bounded specialist lane evaluates contextual exceptions while ambiguous authority or unsafe material exits to bespoke governance.","Independent validation checks both target output and side paths, including disclosure, contextual distortion, restriction loss, file corruption, and excessive redaction.","The workbench releases a candidate package and transformation record to the repository, which retains acceptance and access-control authority.","Case data are purged from the facilitator, rules and tests are refreshed, staff capacity is restored, and the verified workbench becomes ready for another deposit.","Capacity, selectivity, degradation, and repository receiving load determine whether intake continues, slows, or stops."],"baseline":"The baseline is decentralized bespoke deposit preparation under identical preservation, consent, governance, privacy, and repository acceptance requirements. Each research team and archivist manually inventories, reformats, describes, restricts, packages, and revises a deposit. Comparison must hold record-set eligibility and intended access class constant and count depositor labor, archivist labor, specialist and community-governance labor, elapsed time, revisions, rejected objects, abandoned deposits, validation defects, disclosure findings, contextual loss, computing resources, and repository review burden.","nearest_rivals":["Additional archivists or project curators: this expands case-proportional capacity and is the stronger explanation if results depend mainly on more labor rather than repeated workbench turnover.","A repository submission form: it standardizes intake but lacks the selective execution, output validation, recovery cycle, and multi-case activity measurement of the proposed facilitator.","A standalone automated redaction tool: it performs one transformation but does not govern authority, contextual metadata, packaging, exceptions, regeneration, or repository handoff.","A mandatory deposit policy: it changes incentives or obligations but does not lower the recurring conversion barrier and may increase incompatible inflow.","Upstream consent and data-management redesign: it can remove ambiguity permanently and may be preferable when missing authorization, rather than repeated processing, is the dominant problem.","A one-time data-curation training program: it distributes skills to investigators but lacks an enduring facilitator that receives, releases, and regenerates across successive deposits.","A general digital-preservation migration service: it preserves file readability but does not selectively transform ethnographic records under consent, community-governance, contextual, and access constraints."],"remaining_contrastive_claim":"The intervention qualifies as catalytic only if the same separable workbench completes multiple authorized deposit-preparation cycles, measurably lowers recurring conversion burden relative to bespoke preparation, preserves or improves the full distribution of safety and contextual outcomes, and returns to a verified ready state after each case. If performance depends on proportional curator labor, relaxed repository standards, retroactive expansion of consent, omission of difficult objects, or permanent simplification of requirements, the catalytic interpretation fails.","authority_safety":{"decision_authority":"Researchers and institutional data custodians retain responsibility for proposing a deposit; participants, communities, or recognized cultural authorities retain any applicable rights over preservation and access; ethics, privacy, legal, and records bodies retain their scoped determinations; the repository retains authority to accept, reject, preserve, and enforce access conditions. The workbench steward may decide only intake eligibility, technical processing sequence, capacity pauses, validation status, and escalation.","authorized_first_step":"The repository director and institutional data steward may jointly authorize an offline shadow probe using controlled copies of previously accepted deposits for which evaluation use is permitted. The probe may reconstruct packages and compare manifests but may not release outputs, change archival masters, broaden access, reinterpret consent, or process unresolved live collections.","excluded_actions":["Inferring permission to preserve, share, or broaden future use from the mere existence of research files","Overriding individual, community, cultural, institutional, legal, ethical, or repository restrictions","Treating de-identification as sufficient authorization for deposit or reuse","Automatically transforming sacred, culturally restricted, politically dangerous, or authority-disputed material","Replacing contextual judgment with file-format or keyword checks","Changing an access class to improve throughput or acceptance rates","Retaining case data inside the reusable workbench beyond the authorized processing and recovery window","Releasing a generated package without independent repository validation","Using archived examples as training or test material beyond their permitted purposes"],"halt_rollback":"Immediately stop affected processing upon suspected disclosure, authority mismatch, corrupted master, unexplained transformation, failed purge, invalid restriction mapping, or material policy drift. Isolate the workspace, preserve audit evidence without copying substantive data beyond authorization, notify the responsible data custodian and repository security authority, destroy unauthorized derivatives where directed, restore from untouched controlled copies, return open deposits to the ordinary pathway without prejudice, and require independent approval before reactivation."},"negative_tests":{"strongest_counterevidence":"Comparable eligible deposits processed through the workbench require as much total human and community-governance labor as bespoke curation, or show more missed restrictions, disclosure findings, contextual distortion, corrupted relationships among records, over-redaction, repository revisions, or abandoned cases. Any apparent acceleration is explained by selecting cleaner collections, excluding difficult objects, adding specialist labor, or weakening documentation and access standards.","problem_falsifier":"Case review shows that deposit delay is not caused by repeatable conversion work but principally by unique and unresolved questions of consent, ownership, collective authority, safety, representation, or scholarly context that cannot legitimately be templated or automated.","intervention_falsifier":"Under fixed eligibility, access class, and acceptance standards, the workbench fails to reduce total preparation burden or cycle time across repeated cases, cannot restore a contamination-free ready state, accumulates unresolved exceptions faster than it processes deposits, or crosses any precommitted authority, disclosure, integrity, or contextual-quality threshold.","risks":["Automation propagates a systematic restriction-mapping or redaction error across many files.","Technically valid packaging strips records of interpretive context needed to prevent misuse.","Eligibility rules favor well-funded projects with orderly documentation and leave fragile collections behind.","Community-governance labor is treated as an unpriced cofactor and becomes the actual bottleneck.","Sensitive information persists in temporary files, logs, thumbnails, backups, or validation fixtures after nominal purge.","A stale recipe applies superseded repository, legal, ethical, or community requirements.","Over-redaction preserves privacy at the cost of rendering the archive misleading or unusable.","Under-redaction enables reidentification through relational, spatial, linguistic, or contextual clues.","The specialist lane becomes a rubber stamp or a single point of failure under deposit deadlines.","Faster preparation overloads repository appraisal, preservation, access review, or continuing restriction management.","Deposit manifests create false confidence that all authority and context can be reduced to structured fields.","Metrics reward accepted packages while hiding excluded objects, abandoned deposits, or shifted labor."]},"next_evidence_step":"Conduct a pre-registered shadow assay on controlled copies of no more than six previously accepted ethnographic deposits whose evaluation use is authorized. Select cases before examining workbench performance and include supported routine cases plus at least one case expected to trigger rerouting. Reconstruct each package using only evidence available at its original preparation date; compare it with archived bespoke preparation on total depositor, archivist, specialist, and governance labor, elapsed processing time, revisions, file integrity, metadata completeness, restriction fidelity, contextual preservation, excluded objects, and recovery effort. Independent repository and governance reviewers should inspect blinded manifests and a permitted sample of outputs. Any authority mismatch, new disclosure, unexplained content change, failed purge, incorrect access classification, or inability to reroute an ineligible case fails the probe. A passing shadow result authorizes only consideration of a separately reviewed live pilot.","prior_art_status":"UNSEARCHED","diversity_from_prior_proposals":"Proposal 1 addressed the pre-fieldwork transformation from a research-entry request to a legitimate community and ethics disposition through a relationship-bearing liaison and convening service. This proposal addresses a materially different post-fieldwork problem: transforming already-authorized completed records into repository-ready archival deposits. Its reusable facilitator is a governed technical and informational workbench with templates, automation, validation, and bounded archival review; its principal barrier is repeated curation and packaging rather than contact search, trust initiation, and decision convening. Its output is a validated deposit package submitted to an independent repository, not permission to enter a field site. It can be adopted by an archive without adopting the fieldwork-entry service, and the entry service can operate without this workbench; neither is a feature, population variant, or implementation stage required by the other.","revision_record":{"parent_version":null,"progress_targets_addressed":["Generate exactly one additional complete proposal at index 2","Select a problem materially different from proposal 1","Preserve reusable facilitation, selectivity, turnover, capacity, regeneration, neutrality, and deactivation","Provide complete actors, observable state, causal chain, rivals, authority, safeguards, falsifiers, and bounded evidence","Explain diversity from every earlier sealed proposal"],"conceptual_changes":["Initial version with no parent","Instantiated the recurring transformation as governed preparation of completed ethnographic records for archival deposit","Located catalytic leverage in a separable technical and informational workbench rather than a relationship broker","Defined repository readiness rather than repository acceptance or broader reuse permission as the accelerated endpoint"],"operational_changes":["Initial version with no prior operations","Specified intake attestations, constraint-to-object mapping, approved automation, specialist exceptions, quarantine, validation, secure purge, refresh, retirement, and downstream pacing","Restricted first evidence to an offline shadow assay on authorized copies of previously accepted deposits"],"evidence_changes":["Prior art remains unsearched","Defined a bounded multi-case comparison against archived bespoke preparation with independent review and hard failure criteria","Included labor transfer, excluded objects, contextual preservation, restriction fidelity, and facilitator recovery in the assay"],"claim_changes":["Makes no claim of novelty, prevalence, demand, or effect size","Conditions the catalytic interpretation on repeated workbench turnover under unchanged authority, access, and repository standards","Explicitly distinguishes the proposal from the earlier fieldwork-entry liaison candidate"]}}