{"actors":["Reference librarians and library assistants handling live patron questions","Subject librarians and electronic-resources staff who curate reusable guidance","Cataloging and metadata librarians who control authority and bibliographic records","Library privacy or service managers who set capture constraints"],"affected_objective":"Provide responsive reference service while preserving validated, provenance-bearing knowledge for later staff and catalog use.","arm":"COMMON_P1","authority_safety":{"authorized_first_step":"Run a ten-business-day shadow pilot at one reference desk with at most three participating staff and 50 de-identified trace entries; keep the ledger staff-only, make no production catalog or public-guide changes, and have a designated curator record hypothetical promotion decisions.","decision_authority":"The reference-service manager controls the pilot; designated subject or electronic-resources librarians approve knowledge-base promotion; authorized cataloging staff alone approve changes to catalog, authority, or holdings records; privacy staff may veto capture categories.","excluded_actions":["Recording patron names, identifiers, contact details, or verbatim sensitive queries","Displaying provisional traces to patrons as verified guidance","Automatically updating catalog, authority, holdings, licensing, or access-control records","Using the fast layer to make legal, privacy, collection-disposition, or account decisions","Retaining rejected or expired traces beyond the pilot retention window"],"halt_rollback":"Stop new capture if a privacy breach, patron-facing stale-use event, or unresolved authority conflict occurs. Quarantine affected entries, remove the staff shortcut to the ledger, export the audit log for review, and delete pilot traces after recording de-identified aggregate findings; production systems remain unchanged."},"baseline":"Staff search the catalog, research guides, and troubleshooting documentation during each interaction, while useful query reformulations, local terminology, access anomalies, and collection-location clues remain in personal notes or chat. Durable updates occur only when someone separately remembers to submit or make them.","candidate_id":"fast_slow_store_coupling__library_information_science__COMMON_P1","causal_chain":["Live reference work produces small, context-rich discoveries that may be useful immediately but are not yet validated for durable publication.","A bounded shift ledger captures those traces with low-friction fields and makes recent, unexpired traces searchable to authorized desk staff.","Risk and value rules route sensitive or record-changing matters directly to authorized slow-layer workflows while allowing reversible navigation hints to remain provisional.","End-of-shift triggers protect flagged traces, and a twice-weekly review moves selected traces into a consolidation queue before expiration.","Curators deduplicate entries, reproduce access claims, normalize terminology, attach source and uncertainty metadata, and classify each item as promote, defer, redirect, or discard.","Approved material is integrated into the curated reference knowledge base or forwarded to cataloging through its existing controlled workflow; the original trace retains a disposition link.","Version and freshness markers prevent the fast ledger from silently outranking durable records, while reconciliation checks expose conflicts and unresolved transfer backlog.","Expiration and capacity rules remove unpromoted traces, preserving a small working set without turning it into a shadow catalog."],"cell_id":"fast_slow_store_coupling__library_information_science","consequence":"Without governed transfer, potentially reusable discoveries can disappear with the shift, while unreviewed local notes can also persist as stale shadow guidance; forcing every observation directly into canonical systems instead raises validation burden during live service.","diversity_from_prior_proposals":"No prior proposals were inspected under runtime isolation, so diversity from them is not asserted; this candidate is specifically instantiated as a live-reference trace ledger coupled to curated library records.","experiment_id":"eoa_inverse_innovation_exp13_second_slot_policy60_20260806","intervention":"Create a staff-only Reference Trace Ledger as a fast store for de-identified, time-stamped query reformulations, local-vocabulary mappings, access anomalies, and collection-location clues. Permit desk staff to read only fresh entries for reversible search assistance. Trigger immediate routing for high-risk record discrepancies and twice-weekly consolidation for routine traces. During consolidation, authorized curators reproduce claims, deduplicate, normalize terms, preserve provenance and uncertainty, then either integrate an item into the durable reference knowledge base, refer it to controlled cataloging, or reject it. Mark every trace provisional, expire ordinary entries after 14 days, cap the ledger, and reconcile promoted items and conflicts through linked versions and an audit log.","mechanism_mapping":[{"counterfactual_removal":"Without separate stores, either live staff must perform canonical-quality documentation during patron interactions or fragile discoveries remain outside durable memory.","mechanism_slug":"two_store_architecture","role":"Separates a low-friction, short-lived reference ledger from the validated, provenance-bearing knowledge base and controlled catalog records."},{"counterfactual_removal":"Without consolidation, the ledger becomes a passive intake queue or shadow knowledge base rather than a source of coherent institutional memory.","mechanism_slug":"memory_consolidation","role":"Transforms provisional observations through reproduction, deduplication, normalization, uncertainty marking, and contextual integration."},{"counterfactual_removal":"Without locality of recent traces, the fast layer would not serve live work and would add capture overhead without an immediate-access function.","mechanism_slug":"locality_of_reference","role":"Keeps recent branch- and shift-relevant traces close to the staff who may need them during subsequent interactions."},{"counterfactual_removal":"Without cadence and event triggers, valuable traces may expire before review or accumulate into an unmanageable backlog.","mechanism_slug":"cadence","role":"Couples end-of-shift protection, immediate risk routing, and twice-weekly routine review to trace fragility and curator capacity."},{"counterfactual_removal":"Without explicit versions and authority markers, provisional and canonical statements could become competing truths.","mechanism_slug":"versioning","role":"Links each trace to its disposition and any durable successor while preserving the canonical record's authority."}],"nearest_rivals":["Direct editing of a shared FAQ or research guide: faster to implement, but asks live staff to canonicalize unverified observations and lacks a deliberately provisional store.","A ticket or intake queue: captures issues for later handling, but does not provide a bounded, fresh working set that authorized staff can reuse during live reference work.","A searchable staff chat channel: supports quick sharing, but normally lacks structured expiration, promotion transforms, authority markers, and reconciliation with durable records.","A cache of catalog or guide results: accelerates repeated retrieval, but does not consolidate new working traces into durable institutional knowledge."],"negative_tests":{"intervention_falsifier":"Reject the intervention if, during the bounded shadow pilot, eligible traces are not reused in simulated later searches, curators cannot determine dispositions from the captured provenance, the review backlog repeatedly exceeds the 50-entry cap, or staff cannot reliably distinguish provisional traces from authoritative records.","problem_falsifier":"The inferred problem is unsupported if baseline observation shows that potentially reusable discoveries are already captured through a timely governed workflow, canonical resources are usable within live-service constraints, and no sampled ad hoc trace is lost, duplicated, or treated as unofficial authority.","risks":["A provisional hint may be used after its freshness window or repeated to a patron as verified fact.","The ledger may accumulate noise and impose curation work without producing usable durable records.","Staff may under-document context, making later validation impossible.","Sensitive patron interests may be inferable even after obvious identifiers are omitted.","The fast store may become a shadow catalog if staff prefer it to controlled correction workflows.","Frequent contributors or memorable interactions may bias what is promoted into institutional memory."],"strongest_counterevidence":"An existing ticketing, catalog-correction, or knowledge-management workflow may already provide fast capture, live retrieval, controlled validation, and traceable promotion; if so, a second ledger would duplicate work and increase inconsistency risk."},"next_evidence_step":"For ten business days at one desk, compare a capped shadow ledger with the existing workflow using only de-identified synthetic or safely abstracted traces. Record capture time, later lookup attempts, freshness-label interpretation, curator disposition completeness, duplicate rate, unresolved backlog, and any privacy or authority exceptions. End after 50 entries or ten days, whichever comes first, and make no production changes.","observable_state":"For each trace, the pilot can observe capture timestamp, category, provenance completeness, freshness deadline, authorized reads, later lookup attempts, risk-routing path, review timestamp, curator disposition, duplicate linkage, validation outcome, durable-successor link, expiration, conflict flag, and queue age. Aggregate observations include lookup latency, stale-use events, transfer backlog, disposition completeness, and reconciliation failures without presuming improvement.","prior_art_status":"UNSEARCHED","problem":"During live reference interactions, staff discover effective query reformulations, local terms, resource-access failures, and collection-location clues that are immediately useful but too provisional for direct entry into catalogs or public guides. Existing quick notes are easy to lose or reuse after becoming stale, while canonical documentation requires validation and metadata work that may not fit the interaction. The concrete problem is preserving selected working traces without allowing them to become an unofficial source of truth.","proposal_index":1,"remaining_contrastive_claim":"The proposal is meaningfully different from ordinary caching or intake staging only if the fast ledger both serves bounded live retrieval and has a governed, transformative path into authoritative library memory; absent either property, its archetype fit fails.","revision_record":{"claim_changes":["Initial version makes no claims of novelty, prevalence, demand, or effect size."],"conceptual_changes":["Initial candidate instantiates fast–slow store coupling as provisional reference traces consolidated into curated library knowledge and controlled catalog workflows."],"evidence_changes":["No external evidence or prior-art search was used; all empirical statements are framed as testable conditions."],"operational_changes":["Initial version bounds the first step to one desk, ten business days, three staff, and 50 de-identified shadow entries with no production writes."],"parent_version":null,"progress_targets_addressed":["Concrete actors, state, consequence, routing, transfer, consolidation, eviction, authority, reconciliation, falsifiers, risks, and bounded evidence collection are specified."]},"schema_version":1,"structural_mapping":[{"archetype_element":"Fast volatile store","domain_realization":"A staff-only, capacity-capped Reference Trace Ledger containing de-identified, time-stamped, provisional discoveries with 14-day expiration."},{"archetype_element":"Slow integrated store","domain_realization":"The curated reference knowledge base and controlled catalog or authority-record workflows that preserve validated guidance, provenance, history, and access rules."},{"archetype_element":"Read/write routing rule","domain_realization":"Desk staff may write eligible traces and read only fresh traces for reversible search assistance; sensitive observations and record-changing discrepancies bypass reuse and go directly to authorized workflows."},{"archetype_element":"Transfer trigger or cadence","domain_realization":"End-of-shift protection for flagged traces, immediate routing for high-risk discrepancies, and twice-weekly review for routine material."},{"archetype_element":"Consolidation transform","domain_realization":"Curators reproduce claims, deduplicate, normalize terminology, attach sources and uncertainty, select the proper durable destination, and record rejection reasons."},{"archetype_element":"Promotion and eviction rule","domain_realization":"Only validated, reusable traces are promoted; deferred items retain a review date, while rejected, superseded, low-context, or 14-day-expired items leave the fast store."},{"archetype_element":"Freshness and authority marker","domain_realization":"Every ledger item displays provisional status, capture time, expiration, and responsible unit; durable records remain authoritative for patron guidance and record-changing decisions."},{"archetype_element":"Consistency reconciliation check","domain_realization":"Linked versions, disposition logs, conflict flags, and review of unresolved successors expose disagreement between traces and canonical resources and route repair to the appropriate owner."}],"title":"Reference Trace Ledger with Curated Canonical Transfer","version":0}