{"actors":["Accessioning archivists who receive and establish initial control over donated or transferred collections","Stacks and retrieval staff who need current container locations and custody status","Preservation staff who assess unstable media, pests, mold, or housing needs","Digital-preservation and archival-description staff who create durable collection records","Repository managers or restriction officers who authorize access and disposition decisions"],"affected_objective":"Maintain immediate container-level custody, location, restriction, and preservation control during archival accessioning while producing coherent durable accession and description records.","arm":"ORDINARY_DIVERSE_P2","authority_safety":{"authorized_first_step":"Run a two-week, staff-only shadow exercise using one already-processed accession and no more than 30 reconstructed container events. Compare simulated waypoint entries with the completed accession record without changing labels, locations, permissions, finding aids, or collection-management systems.","decision_authority":"The repository manager authorizes the exercise; the accessioning archivist controls provisional entries; preservation or restriction officers control their respective flags; only authorized archival-description or collection-management staff may approve durable record changes.","excluded_actions":["Moving, relabeling, rehousing, deaccessioning, or opening collection containers based on shadow entries","Changing donor restrictions, legal status, ownership, retention, or public access","Writing provisional data into production accession records, finding aids, catalogs, or preservation systems","Recording unnecessary personal or sensitive information found in collection materials","Treating an inferred series, creator identity, condition, or rights status as verified"],"halt_rollback":"Stop the exercise if a shadow entry is mistaken for production authority, sensitive information is captured, or reconstructed custody state cannot be reconciled with the completed record. Disable access to the register, preserve a minimal incident log, and delete the shadow entries after review; no production records or physical arrangements require rollback."},"baseline":"New archival containers are tracked through paper slips, shared spreadsheets, staff memory, or direct entry into collection-management systems while accessioning, preservation review, restriction analysis, and hierarchical description proceed at different speeds. Immediate location and handling needs can therefore compete with the validation required for durable archival description.","candidate_id":"fast_slow_store_coupling__library_information_science__ORDINARY_DIVERSE_P2","causal_chain":["An incoming archival collection creates rapidly changing container locations, custody events, and preservation or restriction flags before durable arrangement and description are complete.","A bounded Accession Waypoint Register captures only the minimum provisional state needed to identify, locate, and safely route each container during intake.","Current operations read location and handling state from unexpired waypoint entries, while rights, access, disposition, and descriptive assertions require confirmation from authorized records or officers.","Transfer is triggered immediately by custody breaks or urgent preservation flags and otherwise occurs at scheduled accession-review checkpoints before provisional context is lost.","Accessioning and specialist staff reconcile container counts, validate restrictions and condition flags, normalize identifiers, preserve provenance, and separate observations from unverified descriptive hypotheses.","Validated state is incorporated into the accession record, preservation workflow, or archival description system, with each promoted field linked to its waypoint source and approving role.","Version and authority rules resolve differences in favor of the authorized durable record while retaining an auditable explanation of corrected location or identity mappings.","Entries are closed and removed from the active waypoint view after verified transfer, while unresolved exceptions remain visible within a capacity and age limit rather than becoming permanent shadow description."],"cell_id":"fast_slow_store_coupling__library_information_science","consequence":"Without governed coupling, repositories must either delay usable custody control until full validation is complete or rely on mutable intake notes that can lose container history and acquire unofficial authority. Directly treating every intake observation as canonical can instead preserve errors about identity, restrictions, condition, or arrangement.","diversity_from_prior_proposals":"The sealed P1 addresses reusable discoveries generated during live reference interactions. This opportunity instead addresses physical and administrative control of newly accessioned archival containers, uses custody and preservation state as the fast-store content, and consolidates through accession reconciliation and archival description rather than reference-knowledge curation.","experiment_id":"eoa_inverse_innovation_exp13_second_slot_policy60_20260806","intervention":"Create a staff-only Accession Waypoint Register as a fast store for provisional container identifiers, timestamps, current locations, custody transitions, processing status, and narrowly coded preservation or restriction alerts. Require authoritative confirmation for access, rights, disposition, and descriptive decisions. Trigger immediate review for custody discontinuities and urgent preservation alerts, plus scheduled reconciliation at each accession checkpoint. During transfer, authorized staff reconcile counts, validate flags against donor and preservation documentation, normalize identifiers, preserve provenance, and route approved fields into the accession record, preservation system, or archival description. Mark every waypoint provisional and time-bounded, cap unresolved entries, close transferred entries, and use linked versions and exception reports to reconcile divergence.","mechanism_mapping":[{"counterfactual_removal":"Without distinct stores, staff must either impose canonical-record validation on every intake movement or let provisional custody state persist in uncontrolled notes.","mechanism_slug":"two_store_architecture","role":"Separates a quickly mutable container-control register from integrated accession, preservation, and archival-description records."},{"counterfactual_removal":"Without transformation during transfer, provisional identifiers, inferred relationships, and coded alerts would merely be copied into durable records with their ambiguity intact.","mechanism_slug":"memory_consolidation","role":"Reconciles counts, validates specialist flags, normalizes identifiers, distinguishes observation from inference, and integrates provenance before durable promotion."},{"counterfactual_removal":"Without nearby current state, stacks and processing staff would repeatedly reconstruct container locations and handling status from slower, incomplete records.","mechanism_slug":"locality_of_reference","role":"Keeps the active accession's current container and custody state close to intake, stacks, and preservation work."},{"counterfactual_removal":"Without event and checkpoint timing, urgent custody or preservation exceptions could wait too long while routine entries could accumulate without integration.","mechanism_slug":"cadence","role":"Combines immediate exception transfer with scheduled accession-stage reconciliation."},{"counterfactual_removal":"Without identifiers, validation checks, and source links, container mismatches could be normalized into durable records without a detectable repair path.","mechanism_slug":"data_integrity","role":"Requires count reconciliation, controlled identifiers, field-level approval, and traceable correction before canonical integration."},{"counterfactual_removal":"Without linked revisions and an authority rule, the waypoint register and durable accession record could present competing locations or statuses.","mechanism_slug":"versioning","role":"Links provisional states to approved successors and makes the authorized durable record decisive after reconciliation."}],"nearest_rivals":["Direct real-time entry into the collection-management system: provides one record surface but may require canonical certainty before rapidly changing intake state is understood.","A container-movement log: records custody events but need not transform selected state into accession, preservation, and descriptive records or retire provisional authority after transfer.","An archival-processing task queue: schedules work but does not itself serve as the bounded low-latency source for current container state.","A duplicate backup of accession records: improves recoverability but gives both copies the same function and lacks asymmetric consolidation rules.","A preliminary finding aid: exposes provisional description for discovery, whereas the proposed fast store is an internal operational layer for custody and handling control."],"negative_tests":{"intervention_falsifier":"Reject the intervention if the shadow reconstruction cannot answer current-container questions from bounded entries, specialist reviewers cannot validate promoted fields from recorded provenance, transfer leaves conflicting active states, or unresolved entries repeatedly exceed the 30-record exercise cap.","problem_falsifier":"The inferred problem is unsupported if the existing accession workflow already provides low-friction current container control, field-level provisional status, timely specialist routing, transformative integration into durable records, and traceable reconciliation without parallel notes or ambiguous authority.","risks":["A provisional location may be followed after a container has moved.","Coded restriction or preservation alerts may be overinterpreted as verified determinations.","The register may become a shadow finding aid or permanent processing database.","Sensitive names or contents may be captured beyond the minimum needed for container control.","Identifier normalization may incorrectly merge distinct containers or split one container history.","Transfer work may accumulate and obscure rather than expose unresolved custody exceptions.","Staff may prioritize easily recorded physical state while neglecting contextual or community-sensitive description."],"strongest_counterevidence":"A repository's existing collection-management platform may already support rapid provisional container events, specialist flags, staged validation, durable promotion, and versioned reconciliation; a separate waypoint register would then duplicate state and increase conflict risk."},"next_evidence_step":"Using one completed accession, reconstruct no more than 30 historical container events in a staff-only shadow register over two weeks. Measure time to recover simulated current location and custody state, provenance completeness, reviewer agreement on field destinations, validation failures, identifier conflicts, transfer age, unresolved exceptions, and whether participants distinguish waypoint data from authorized records. Make no physical or production-system changes.","observable_state":"For each simulated container event, observe provisional identifier, capture time, stated location, custody predecessor, source, freshness deadline, preservation or restriction alert, read event, transfer trigger, reviewer role, validation result, normalized identifier, durable field destination, successor link, conflict resolution, closure time, and expiration. Aggregate state includes active-register size, lookup time, transfer age, unresolved custody breaks, validation failures, authority-confusion incidents, and reconciliation completeness.","prior_art_status":"UNSEARCHED","problem":"During archival accessioning, containers can be received, quarantined, moved, inventoried, and associated with provisional restrictions faster than staff can validate provenance, hierarchy, rights, condition, and durable description. Immediate custody and handling decisions need current local state, but intake notes are vulnerable to overwriting and may become unofficial descriptive records. The concrete problem is maintaining reliable short-horizon container control without prematurely canonizing provisional archival assertions.","proposal_index":2,"remaining_contrastive_claim":"The proposal instantiates fast–slow store coupling only if the waypoint register is actively used for bounded current container control and selected state undergoes validation and integration into authoritative archival records. If it merely holds items awaiting processing, it is an intake queue rather than the claimed architecture.","revision_record":{"claim_changes":["Initial version makes no claims about novelty, prevalence, demand, or effect size."],"conceptual_changes":["Initial candidate applies the archetype to provisional archival-container control coupled to durable accession, preservation, and description records."],"evidence_changes":["No external evidence or prior-art search was used; the problem and intervention are expressed through falsifiable observations."],"operational_changes":["Initial version limits the first step to a two-week shadow reconstruction of at most 30 events from one completed accession, with no physical or production changes."],"parent_version":null,"progress_targets_addressed":["Specified materially distinct actors, problem, intervention, causal path, routing, transfer, consolidation, eviction, authority, reconciliation, negative tests, risks, and bounded evidence collection."]},"schema_version":1,"structural_mapping":[{"archetype_element":"Fast volatile store","domain_realization":"A staff-only, capacity-bounded Accession Waypoint Register holding provisional container locations, custody transitions, processing state, and narrowly coded alerts."},{"archetype_element":"Slow integrated store","domain_realization":"Authorized accession records, preservation-management records, and archival-description systems containing validated provenance, restrictions, identifiers, hierarchy, and history."},{"archetype_element":"Read/write routing rule","domain_realization":"Intake and stacks staff may update current container state; preservation and restriction alerts route to specialists; access, rights, disposition, and descriptive decisions require slow-store or officer confirmation."},{"archetype_element":"Transfer trigger or cadence","domain_realization":"Custody discontinuities and urgent preservation alerts trigger immediate review, while ordinary state transfers at defined accession checkpoints."},{"archetype_element":"Consolidation transform","domain_realization":"Staff reconcile counts, validate alerts and restrictions, normalize identifiers, separate observation from hypothesis, attach provenance, and assign each approved field to its durable destination."},{"archetype_element":"Promotion and eviction rule","domain_realization":"Validated operational and descriptive fields are promoted; transferred entries close, superseded entries leave the active view, and unresolved exceptions remain only within age and capacity limits."},{"archetype_element":"Interference and overwrite guard","domain_realization":"Append-only custody transitions, stable temporary container IDs, urgent-review locks, and change history protect active state from silent replacement."},{"archetype_element":"Freshness and authority marker","domain_realization":"Every waypoint displays provisional status, capture time, responsible role, and expiration; authorized accession, preservation, and restriction records govern durable decisions."},{"archetype_element":"Consistency reconciliation check","domain_realization":"Container-count comparisons, successor links, exception reports, reviewer approvals, and version histories expose divergence and route repairs to the responsible archival role."}],"title":"Accession Waypoint Register for Container Control and Durable Archival Integration","version":0}