{"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_p04_kinship_to_care_translation_gateway","proposal_index":4,"version":0,"title":"Regenerative Kinship-to-Care Translation Gateway","problem":"Institutional care systems often require a bounded set of operational facts—who may receive information, participate in planning, provide practical support, or exercise formally documented authority—but a person's actual kinship and care network may not fit the household and relationship categories in ordinary intake records. Each case can therefore trigger repeated narration, staff interpretation, correction, and escalation. This translation burden is distinct from the legitimate rules governing consent, privacy, safeguarding, and legal decision authority. When routine mapping and genuine authority disputes enter the same pathway, ordinary cases stall while complex cases may be forced into misleading categories.","actors":["Patients or service users capable of identifying their care relationships and preferences","Chosen family, relatives, friends, neighbors, and other members of care networks","Formal guardians, proxies, or other legally recognized decision holders where applicable","Registration and intake staff","Clinicians, discharge planners, and social workers","Interpreters and accessibility-support personnel","An anthropologically informed relationship-mapping specialist","Institutional privacy, safeguarding, ethics, and legal personnel","Information-system and records stewards"],"observable_state":"Relationship fields are repeatedly corrected or contradicted; the same person is described differently across registration, clinical, and discharge records; staff repeatedly ask who performs which role; self-identified supporters are either treated as legally authoritative or excluded because they lack a familiar kin label; routine communication questions are escalated with authority disputes; mapping workload, exception queues, correction rates, specialist occupancy, and downstream use are not jointly visible.","consequence":"People may have to reconstruct intimate social relationships at every handoff. Appropriate supporters can be omitted from communication or planning, while another person can be assigned powers they do not possess. Staff time is consumed resolving representational mismatches, downstream coordination is delayed, and a simplified kinship label can conceal coercion, conflict, or the difference between practical care and binding decision authority.","affected_objective":"Reduce the recurring interpretation and handoff burden required to produce an accurate, role-specific care-network record while preserving the person's choices, privacy, safeguarding protections, formal authority rules, contextual complexity, and the right to decline participation or documentation.","intervention":"Place a governed kinship-to-care translation gateway at a stable intake or care-planning interface. For eligible cases, the person describes relevant relationships through an accessible elicitation process that does not require conventional kin labels. A versioned relationship-role template and auditable mapping tool convert that account into separate propositions about contact, information sharing, planning participation, practical support, and documented legal authority. The person validates the resulting map before release. A bounded specialist lane reviews only unsupported relationship structures, translation uncertainty, or inconsistent role claims. Contested authority, suspected coercion or abuse, incapacity, emergency exceptions, minors, contradictory legal documents, or inability to validate the map leave the gateway for existing safeguarding, ethics, legal, or clinical pathways. After each cycle, temporary narrative data are cleared, the released map is versioned, mapping rules and system interfaces are tested, conflicts are reviewed, and staff recover before the gateway accepts another case.","structural_mapping":[{"archetype_element":"Target transformation specification","domain_realization":"Transform an eligible person's self-described care network into a validated, role-specific institutional record that distinguishes communication, participation, support, emergency contact, and formally documented decision authority. The output records existing permissions and relationships; it does not create them."},{"archetype_element":"Activation barrier","domain_realization":"Repeated elicitation, interpretation, category negotiation, role separation, correction, and handoff caused by mismatch between lived kinship arrangements and institutionally required fields."},{"archetype_element":"Permitted pathway boundary","domain_realization":"The gateway may reduce representational and coordination friction but cannot waive privacy, consent, capacity, safeguarding, professional, or legal requirements or decide contested authority."},{"archetype_element":"Reusable facilitator","domain_realization":"A maintained relationship-role schema, auditable mapping tool, accessible elicitation protocol, and bounded specialist review lane that remain separate from each person's released record and can serve successive cases."},{"archetype_element":"Facilitator–substrate interface","domain_realization":"The interface accepts a person's descriptions of relationships, desired roles, information permissions, accessibility needs, existing formal documents, uncertainty, and conflict flags and returns a versioned map with explicit provenance and limits."},{"archetype_element":"Selectivity rule","domain_realization":"Routine, person-validated mapping enters the gateway; authority disputes, coercion indicators, incapacity, emergency exceptions, contradictory documents, safeguarding concerns, and meanings unsupported by the current schema are rerouted rather than normalized."},{"archetype_element":"Cofactor system","domain_realization":"The facilitator requires the person's voluntary participation, sufficient communication support, current institutional and legal role definitions, secure records infrastructure, and access to qualified specialist escalation."},{"archetype_element":"Contact-time window","domain_realization":"The gateway uses a bounded elicitation and validation encounter sufficient to separate roles and identify uncertainty; it does not prolong contact to resolve disputes outside its scope."},{"archetype_element":"Turnover capacity","domain_realization":"Turnover is the number of validated role maps released per gateway cycle, measured with contact time, specialist minutes, corrections, reroutes, downstream clarification requests, and recovery time."},{"archetype_element":"Saturation and interference","domain_realization":"Queue depth, mapping time, specialist occupancy, interpreter availability, schema exceptions, correction rates, coercion flags, interface failures, and downstream care-planning capacity distinguish excessive inflow from degraded gateway activity."},{"archetype_element":"Regeneration cycle","domain_realization":"Temporary narratives are purged according to policy, released maps and permissions are versioned, software and schema tests are rerun, outdated rules are quarantined, staff debrief and rotate, and readiness is verified before reuse."},{"archetype_element":"Byproduct guardrail","domain_realization":"Monitoring checks for fabricated legal authority, unwanted disclosure, coerced inclusion, omission of important supporters, culturally misleading labels, loss of relationship nuance, discriminatory rerouting, and downstream reliance beyond the map's stated scope."},{"archetype_element":"Equilibrium neutrality","domain_realization":"The gateway can accelerate accurate representation where a permissible coordination arrangement already exists. It cannot create capacity, consent, trust, legal authority, service eligibility, or agreement among parties who are in conflict."},{"archetype_element":"Deactivation rule","domain_realization":"The relevant rule set or full gateway pauses after a privacy breach, material role-mapping error, false authority assignment, failed purge, discriminatory pattern, stale governing rule, unresolved interface corruption, or inability to restore specialist readiness."}],"mechanism_mapping":[{"mechanism_slug":"interface_contract_design","role":"Separates input descriptions, requested roles, formal authority evidence, output fields, downstream guarantees, exceptions, and protected constraints at the institutional handoff.","counterfactual_removal":"Without an explicit contract, different departments reinterpret the same map, role categories silently expand, and the person must renegotiate relationships at each handoff."},{"mechanism_slug":"prevalidated_transformation_template","role":"Encodes an approved role-separation pathway that distinguishes social relationship, practical support, information permission, planning participation, and formal authority while retaining free-text context and uncertainty.","counterfactual_removal":"Without the maintained template, staff reconstruct these distinctions case by case, preserving the recurring interpretation burden and inconsistent outputs."},{"mechanism_slug":"workflow_automation_or_macro","role":"Generates the role-specific record, checks required validations and incompatibilities, versions permissions, logs transformations, and routes failed checks without deciding contested meanings.","counterfactual_removal":"Without reusable execution, repeated transcription and cross-system formatting remain case-proportional manual work and introduce new handoff errors."},{"mechanism_slug":"fast_track_with_eligibility_rules","role":"Admits routine person-validated mappings while sending incapacity, coercion, safeguarding, legal conflict, emergency exceptions, and unsupported structures to the appropriate full pathway.","counterfactual_removal":"Without bounded eligibility and rerouting, the gateway either becomes uselessly cautious or begins processing cases whose protective barriers must not be lowered."},{"mechanism_slug":"embedded_specialist_review_lane","role":"Provides limited anthropological and institutional interpretation for schema mismatches or translation uncertainty, with workload caps and escalation rather than discretionary authority assignment.","counterfactual_removal":"Without the specialist lane, unfamiliar arrangements are either forced into misleading categories or all nonstandard cases are rejected."},{"mechanism_slug":"inhibitor_and_poison_screen","role":"Screens for contradictory documents, coercion indicators, identity mismatch, unsupported language mediation, stale rules, and system incompatibility before the mapping facilitator acts.","counterfactual_removal":"Without upstream screening, the gateway can efficiently produce an internally consistent but unsafe or unauthorized record."},{"mechanism_slug":"catalyst_cofactor_system","role":"Checks the sufficiency of voluntary participation, communication support, current role definitions, secure infrastructure, and specialist coverage rather than treating them as invisible inputs.","counterfactual_removal":"Without cofactor checks, missing interpretation, accessibility, authority evidence, or security capacity is misclassified as an ordinary mapping problem."},{"mechanism_slug":"active_site_capacity_dashboard","role":"Displays admitted cases, queue depth, contact time, interpreter and specialist availability, reroutes, corrections, degradation signals, recovery state, and downstream care-planning load.","counterfactual_removal":"Without capacity observability, high demand can produce rushed validation, reviewer exhaustion, or maps waiting unused in an overloaded downstream stage."},{"mechanism_slug":"catalyst_regeneration_protocol","role":"Restores readiness through temporary-data purge, permission and schema synchronization, regression testing, rule refresh, conflict review, staff debriefing, rotation, and retirement of mappings that cannot be made reliable.","counterfactual_removal":"Without regeneration, stale rules, residual narratives, accumulated exceptions, software drift, and staff fatigue contaminate later cycles."},{"mechanism_slug":"turnover_and_selectivity_assay","role":"Compares useful mapping cycles with ordinary intake while measuring corrections, false authority assignments, unwanted disclosures, omissions, reroutes, discriminatory patterns, labor transfer, and degradation over time.","counterfactual_removal":"Without a baseline and full outcome distribution, faster form completion or easier case selection could be mistaken for safe catalytic translation."},{"mechanism_slug":"small_safe_to_fail_probe","role":"Tests the mapping pathway on bounded synthetic and authorized closed cases before it writes to live records or influences care coordination.","counterfactual_removal":"Without a contained probe, systematic category and interface errors would first appear in consequential live-care decisions."}],"causal_chain":["Eligible care-network cases repeatedly incur the same elicitation, role-separation, interpretation, and record-handoff burdens.","A governed interface contract and reusable relationship-role schema encode stable institutional distinctions without requiring conventional kin labels.","The person supplies relationship and permission information once through an accessible process and validates the generated propositions.","Deterministic mapping and validation perform repeatable record construction, while the specialist lane handles bounded schema or translation uncertainty.","Protective screens divert contested, coercive, incapacitated, legally contradictory, or otherwise high-risk cases to existing full-review pathways.","A scoped, versioned map is released to downstream staff, who can coordinate within its stated permissions without inferring additional authority.","Corrections, downstream clarification, privacy outcomes, exclusions, and side-path effects are monitored alongside cycle time and facilitator load.","Temporary material is cleared, rules and interfaces are refreshed, staff capacity is restored, and the gateway returns to a verified ready state."],"baseline":"The baseline is ordinary registration and care-planning practice under identical privacy, consent, capacity, safeguarding, documentation, and legal-authority standards. Staff collect conventional relationship labels in separate systems, ask follow-up questions as needs arise, consult social work or legal personnel ad hoc, and manually correct downstream records. Comparison must hold case eligibility and required institutional decisions constant and count the person's narration time, staff and interpreter time, specialist escalations, elapsed time to a validated record, corrections, duplicate questions, omitted supporters, false authority assignments, unwanted disclosures, reroutes, complaints, and downstream coordination burden.","nearest_rivals":["Additional social workers, interpreters, or registration staff: this expands labor in proportion to cases and is the stronger explanation if throughput changes mainly because more people perform the same intake work.","A redesigned electronic-record relationship field: this permanently improves representation but lacks a selective facilitator cycle, specialist exception pathway, activity monitoring, and regeneration.","An advance directive or formal proxy process: this documents legal decision authority but does not represent the wider network of communication, participation, and practical care roles.","General cultural-competence training: it may improve staff judgment but transfers broad capability rather than providing an enduring case-processing facilitator with turnover and recovery.","A patient portal contact form: it collects names and labels but does not separate scoped roles, validate authority boundaries, detect conflicts, or govern exceptions.","A community health-worker or navigator service: it is a closer rival when trust, advocacy, or relationship brokerage is the dominant barrier rather than translation into role-specific institutional records.","Permanent expansion of institutional family-recognition policy: this changes the underlying authorization or eligibility rules and is system redesign, not catalytic acceleration under an invariant boundary."],"remaining_contrastive_claim":"The intervention is catalytic only if the same separable gateway repeatedly converts eligible self-described care networks into accurate, scoped, person-validated records with lower recurring interpretation and handoff burden, preserves protective rules and contextual variation, and returns to a verified ready state. If improvement comes from added case-proportional staff, broader legal recognition, weakened privacy review, forced categorization, omitted difficult relationships, or uncounted interpreter and specialist labor, the catalytic interpretation fails.","authority_safety":{"decision_authority":"A capable person retains authority over voluntary identification of supporters and information-sharing preferences within governing rules. Formally recognized decision holders retain only their documented scope. Clinicians, safeguarding personnel, privacy officers, ethics bodies, and courts retain their respective authorities. The gateway steward may determine pathway eligibility, execute approved mappings, request validation, meter capacity, quarantine defective rules, and trigger a safety pause but may not create legal authority, decide capacity, resolve abuse allegations, or override the person's choices.","authorized_first_step":"The institutional privacy officer and care-records steward may jointly authorize an offline shadow probe using purpose-built synthetic networks and controlled copies of closed, de-identified records whose evaluation use is permitted. The gateway may generate hypothetical maps for comparison but may not write to live records, contact patients or supporters, alter prior care decisions, or assign operational permissions.","excluded_actions":["Creating or implying legal decision authority from kinship, intimacy, caregiving, co-residence, or patient preference alone","Treating a conventional relative as preferred when the person has identified another supporter","Sharing information beyond the person's validated permission and governing privacy rules","Processing suspected coercion, abuse, incapacity, contradictory authority, or emergency exceptions through the routine gateway","Forcing culturally specific relationships into inaccurate institutional labels","Excluding a relationship merely because the current schema does not represent it","Using the map to determine service eligibility, immigration status, financial liability, or unrelated institutional decisions","Retaining temporary relationship narratives beyond the authorized processing period","Changing role definitions or eligibility rules to meet throughput targets"],"halt_rollback":"Stop the affected mapping rule or full gateway immediately after suspected disclosure, coercion oversight, false authority assignment, material omission, discriminatory routing, interface corruption, or failed data purge. Prevent further downstream synchronization, preserve a minimal audit trail, notify the responsible privacy and care authorities, mark affected maps as unverified, revert open cases to the ordinary pathway without prejudice, correct or remove records under authorized procedures, contact affected persons only through approved channels, and require independent review before restart."},"negative_tests":{"strongest_counterevidence":"Under the same eligibility and authority rules, the gateway does not reduce total narration, interpretation, correction, or handoff work, or it increases false authority assignments, unwanted disclosures, omitted supporters, coercion misses, schema-driven distortion, discriminatory rerouting, complaints, or downstream confusion. Apparent gains arise from processing simpler networks, counting only staff time, shifting labor to patients or interpreters, or weakening validation.","problem_falsifier":"Observed delays and errors are principally caused by unresolved capacity, consent, abuse, legal authority, staff shortages, unavailable services, or active interpersonal conflict rather than a repeatable translation burden between lived care networks and institutional role records.","intervention_falsifier":"Across repeated eligible cases, the gateway cannot produce stable person-validated maps within its contact window, requires bespoke specialist interpretation for most cases, fails to reduce downstream clarification, cannot preserve contextual meaning and authority boundaries together, or cannot be regenerated without retaining case-specific knowledge or adding proportional labor.","risks":["The schema embeds dominant assumptions about kinship, household, gender, intimacy, or caregiving.","A concise role map creates false confidence and displaces continuing conversation with the person.","Coercive actors influence the elicitation or validation encounter.","Staff infer legal authority from practical caregiving or emotional closeness.","The person agrees to disclosure without adequate language, accessibility, or privacy support.","Important relational ambiguity is erased to satisfy required database fields.","Unsupported relationships are rerouted more often for marginalized groups.","Temporary narratives persist in logs, backups, analytics, or test environments.","The specialist becomes a bottleneck or discretionary arbiter of culturally legitimate relationships.","Frequent preference changes make downstream copies stale.","Faster mapping overloads social work, discharge planning, or communication channels.","Interpreter, patient, and community labor become hidden cofactors in apparent efficiency."]},"next_evidence_step":"Run a pre-registered offline shadow probe using no more than ten purpose-built synthetic care networks developed with compensated cultural, privacy, safeguarding, accessibility, and legal review, plus no more than four closed de-identified cases if their evaluation use is separately authorized. Include routine networks, nonconventional relationships, changing permissions, translation needs, and cases that must be rerouted. Compare the gateway with ordinary intake on total person-equivalent, staff, interpreter, and specialist time; correct separation of roles; preservation of free-text context; appropriate rerouting; correction burden; and downstream comprehension by blinded care planners. Any false authority assignment, unsafe disclosure, coercion miss, materially misleading label, prohibited inference, discriminatory routing signal, or failed temporary-data purge fails the probe. A passing result authorizes only consideration of a separately approved live pilot with voluntary participation and no effect on care eligibility.","prior_art_status":"UNSEARCHED","diversity_from_prior_proposals":"Proposal 1 transforms a pre-fieldwork research-entry request into a legitimate community and ethics disposition through a relationship-bearing liaison that reduces search, trust, translation, and convening burdens. Proposal 4 operates in care delivery rather than research access: it transforms a person's self-described support network into a scoped institutional coordination record and cannot grant field access or broker community authorization. Proposal 2 transforms completed ethnographic records into repository-ready archival packages through curation, constraint mapping, file processing, and preservation validation. Proposal 4 neither preserves research data nor prepares deposits; its substrate is a live care-network account and its output is a person-validated role map for bounded operational use. Proposal 3 transforms an analyst-codebook pairing into a coding-readiness disposition through reusable anchors and interpretive calibration. Proposal 4 does not calibrate researchers or analytic judgments; it translates social relationships across an institutional interface while separating practical roles from formal authority. Its adoption site, actors, substrate, output, downstream consequence, authority boundary, regeneration hazards, and causal path are independent of all three earlier proposals.","revision_record":{"parent_version":null,"progress_targets_addressed":["Generate exactly one additional proposal at index 4","Address a materially different problem from proposals 1, 2, and 3","Use an independently adoptable intervention and distinct causal path","Preserve reuse, interface selectivity, turnover, capacity, regeneration, neutrality, and deactivation","Specify actors, state, consequences, rivals, authority, safeguards, falsifiers, and bounded first evidence","Explain diversity from every earlier sealed proposal"],"conceptual_changes":["Initial version with no parent","Instantiated the recurring transformation as conversion of a self-described care network into a scoped institutional role record","Located the barrier in repeated kinship-to-institution translation rather than research access, archival preparation, or analyst calibration","Separated practical support, information permission, planning participation, and formal decision authority"],"operational_changes":["Initial version with no prior operations","Specified accessible elicitation, person validation, deterministic mapping, specialist exceptions, protective screening, downstream versioning, secure purge, recovery, and deactivation","Restricted first evidence to an offline shadow probe with synthetic and separately authorized closed cases"],"evidence_changes":["Prior art remains unsearched","Defined a bounded comparison with ordinary intake and blinded downstream comprehension review","Included patient-equivalent, interpreter, specialist, privacy, contextual, discriminatory-routing, and recovery outcomes"],"claim_changes":["Makes no claim of novelty, prevalence, demand, or effect size","Conditions the catalytic interpretation on repeated accurate mapping under unchanged authority and privacy rules","Explicitly distinguishes the proposal from all three earlier sealed candidates"]}}