{"schema_version":1,"research_id":"eoa_inverse_innovation_exp06_external_evaluation_20260803","source_assessment_id":"ritualized_meaning_and_commitment_enactment__human_computer_interaction:P1:v0","cell_id":"ritualized_meaning_and_commitment_enactment__human_computer_interaction","search_queries":["site:w3.org WAI accessibility maturity model lifecycle personnel governance proof","site:gov.uk service standard accessibility multidisciplinary team service assessment user needs","organizational rituals team meetings HCI commitment accountability release gate research","software release accessibility governance commitments lifecycle user research traceability study","site:dl.acm.org accessibility software practice practitioners challenges organizational responsibility study","site:research.google/pubs accessibility software teams organizational barriers study","site:microsoft.com responsible innovation release review user impact assessment standard product lifecycle","site:gitlab.com handbook accessibility release review user research issues accountability","organizational rituals product development teams release ritual study HCI","team rituals product management release retrospective ritual practice toolkit","responsible innovation impact assessment product development lifecycle release gates official standard","site:dl.acm.org values at play values sensitive design product teams accountability commitments","\"Ritual Design: Crafting Team Rituals\" DOI","\"ritual design\" organizational change ACM CHI 2017 Ozenc Hagan","site:microsoft.com \"Responsible AI Standard\" impact assessment goals requirements product teams","site:gov.uk/service-manual service assessment accessibility user needs release ongoing","site:iso.org ISO 9241-210 human-centred design lifecycle users multidisciplinary","site:scrumguides.org Scrum Guide 2020 sprint review retrospective commitments adaptation","site:bls.gov/ooh project management specialists median pay 2025","site:eeoc.gov retaliation participation workplace internal complaints policy","site:bls.gov/oes project management specialists May 2025 hourly mean wage","site:bls.gov/ooh/business-and-financial/project-management-specialists.htm median annual wage 2025","site:bls.gov/oes user experience designer wage web developers digital interface designers 2025"],"sources":[{"source_id":"S1","title":"Accessibility Maturity Model","publisher":"World Wide Web Consortium, Accessible Platform Architectures Working Group","url":"https://www.w3.org/TR/maturity-model/","source_class":"OFFICIAL_GUIDANCE","publication_date":"2025-11-04","accessed_at":"2026-08-03","claims_supported":["Systematic accessibility governance is often unaddressed and this limits organizations' ability to sustain accessible products.","Accessibility should span conception, design, testing, release, maintenance, and obsolescence.","Its optimized maturity indicators include accessibility release gates, maintenance-release reinspection, disability-inclusive research, documented proof points, and monitored improvement.","The model targets managers, accessibility owners, and public or private organizations, but is a W3C Group Note rather than a W3C-endorsed standard."]},{"source_id":"S2","title":"“Accessibility people, you go work on that thing of yours over there”: Addressing Disability Inclusion in AI Product Organizations","publisher":"Google Research / Proceedings of AIES 2025","url":"https://research.google/pubs/accessibility-people-you-go-work-on-that-thing-of-yours-over-there-addressing-disability-inclusion-in-ai-product-organizations/","source_class":"PRIMARY_RESEARCH","publication_date":"2025","accessed_at":"2026-08-03","claims_supported":["Interviews with 25 practitioners identified systemic obstacles to addressing harms to disabled users in AI product organizations.","Existing accessibility practices may not capture all harms to disabled users.","The authors call for improvements to product-development processes and practitioner capabilities."]},{"source_id":"S3","title":"Testing for accessibility","publisher":"UK Government Digital Service, Service Manual","url":"https://www.gov.uk/service-manual/helping-people-to-use-your-service/testing-for-accessibility","source_class":"GOVERNMENT_OR_REGULATOR","publication_date":"2019-03-06; updated 2024-10-29","accessed_at":"2026-08-03","claims_supported":["GOV.UK service teams must consider accessibility at every stage, test with disabled users, and use assistive-technology testing.","An accessibility audit and remediation are required before public beta.","This identifies a real authorizer and an established release-adjacent accessibility workflow that cannot be replaced by a ritual."]},{"source_id":"S4","title":"Microsoft’s framework for building AI systems responsibly","publisher":"Microsoft","url":"https://blogs.microsoft.com/on-the-issues/2022/06/21/microsofts-framework-for-building-ai-systems-responsibly/","source_class":"COMMERCIAL_FIRST_PARTY","publication_date":"2022-06-21","accessed_at":"2026-08-03","claims_supported":["Microsoft operationalized abstract principles through concrete goals, lifecycle requirements, impact assessments, governance, and human oversight.","Its impact assessments examine stakeholders, intended benefits, and potential harms.","Microsoft reports that multidisciplinary development and product experience informed the standard, and that findings caused controls, restrictions, and retirement of capabilities."]},{"source_id":"S5","title":"How to Run a Work Ritual Reset Exercise","publisher":"Atlassian","url":"https://www.atlassian.com/team-playbook/plays/ritual-reset","source_class":"COMMERCIAL_FIRST_PARTY","publication_date":"not stated","accessed_at":"2026-08-03","claims_supported":["A first-party team play already treats recurring meetings, practices, and reports as rituals that can be audited, improved, or removed.","The play assigns owners and deadlines, uses ordinary project-management systems, checks results after three to four weeks, and recommends periodic reevaluation.","It is close prior art for ritual review and retirement, though not for release-specific user-impact commitments or protected nonparticipation."]},{"source_id":"S6","title":"Ritual Design Toolkit","publisher":"Interaction Foundry","url":"https://interactionfoundry.com/rdt","source_class":"COMMERCIAL_FIRST_PARTY","publication_date":"2020","accessed_at":"2026-08-03","claims_supported":["An existing toolkit provides a Ritual Design Canvas, storyboard, ideation cards, and a scope-create-test process.","It explicitly applies ritual design to workplaces, customer journeys, communities, and micro-interactions.","This substantially collides with the proposal's generic ritual canvas and prototyping elements but not its release-governance claim."]},{"source_id":"S7","title":"ISO 9241-210:2019 — Ergonomics of human-system interaction — Part 210: Human-centred design for interactive systems","publisher":"International Organization for Standardization","url":"https://www.iso.org/standard/77520.html","source_class":"STANDARD","publication_date":"2019-07; confirmed 2025","accessed_at":"2026-08-03","claims_supported":["The current international standard supplies requirements and recommendations for human-centred design throughout the lifecycle of interactive systems.","It is intended for people managing design and development processes and supplies a conformance checklist.","The standard establishes lifecycle human-centred management as prior art but does not prescribe ritualized recommitment."]},{"source_id":"S8","title":"Table 1. National employment and wage data from the Occupational Employment and Wage Statistics survey by occupation, May 2025","publisher":"U.S. Bureau of Labor Statistics","url":"https://www.bls.gov/news.release/ocwage.t01.htm","source_class":"GOVERNMENT_OR_REGULATOR","publication_date":"2026-05-15","accessed_at":"2026-08-03","claims_supported":["May 2025 national mean hourly wages were $53.24 for project-management specialists, $71.20 for software developers, and $56.49 for web and digital-interface designers.","These wage observations anchor labor-resource equivalents, before benefits, overhead, participant compensation, or procurement costs."]}],"problem_evidence":{"support":"MODERATE","rationale":"The problem class is visible: W3C explicitly describes unaddressed systematic accessibility governance, inconsistent lifecycle application, and the need for release gates and documentation, while primary interviews identify systemic organizational obstacles affecting disabled users. GOV.UK requires continuous accessibility work and pre-public-beta audit. None of the sources directly measures the proposal's narrower prevalence claim—loss or passive carry-forward of previously made user-impact commitments across releases and staff turnover—so the exact problem remains unquantified.","source_ids":["S1","S2","S3"]},"stakeholder_evidence":{"support":"STRONG","rationale":"Identifiable authorizers and adopters exist for adjacent workflows. GOV.UK requires service teams to test with disabled users and complete and remediate an accessibility audit before public beta. Microsoft applies lifecycle impact-assessment requirements to its product teams, and W3C addresses managers and accessibility-program owners. These sources demonstrate institutional pull for durable lifecycle accountability, although none expresses demand for the proposal's specific symbolic ritual.","source_ids":["S1","S3","S4"]},"prior_art":{"proximity":"SUBSTANTIAL_COLLISION","closest_analogues":[{"name":"W3C Accessibility Maturity Model lifecycle and release-gate proof points","similarity":"Provides repeatable accessibility governance, cross-functional documentation, disability-inclusive research, release gates, maintenance reinspection, metrics, and continuous improvement.","remaining_difference":"It does not require a marked symbolic interval, periodic re-consent to each inherited commitment, protected silence, witnessing, or ritual retirement.","source_ids":["S1"]},{"name":"Microsoft Responsible AI Standard and Impact Assessment","similarity":"Turns abstract values into multidisciplinary lifecycle requirements, stakeholder-and-harm assessment, controls, governance, documentation, iteration, and capability retirement.","remaining_difference":"It is an impact-assessment and policy system rather than a recurring ritual of witnessed re-consent, and it is scoped to AI.","source_ids":["S4"]},{"name":"GOV.UK accessibility testing and pre-public-beta audit","similarity":"Places authoritative accessibility evidence, disabled-user testing, remediation, and a hard release-adjacent checkpoint in an operating product workflow.","remaining_difference":"It tests conformance and user performance but does not reconstruct and renew prior cross-role commitments or preserve a consent-aware symbolic frame.","source_ids":["S3"]},{"name":"Atlassian Ritual Reset","similarity":"Audits recurring team practices, asks what to keep, improve, or remove, assigns owners and deadlines in normal work systems, and schedules follow-up review.","remaining_difference":"It manages team routines generally; it does not govern affected-user evidence, release authority, nonretaliatory abstention, or per-commitment dispositions.","source_ids":["S5"]},{"name":"Interaction Foundry Ritual Design Toolkit","similarity":"Already offers ritual scoping, a design canvas, sequence/storyboarding, prototyping, and outcome testing for workplace and service contexts.","remaining_difference":"It does not supply the proposal's accessibility, privacy, employment-power, release-authority, evidence-provenance, or practical-obligation controls.","source_ids":["S6"]},{"name":"ISO 9241-210 human-centred lifecycle management","similarity":"Establishes lifecycle-wide human-centred design requirements and management responsibilities for interactive systems.","remaining_difference":"It does not specify a release ritual or periodic re-consent to remembered user-impact obligations.","source_ids":["S7"]}],"distinctive_claim_remaining":"Holding time, authority, and evidence constant, adding a consent-aware, symbolically marked cycle of explicit renew/revise/decline choices, witnessing, and practical closure to a strong release checklist or impact assessment will increase the proportion and later recall of inherited user-impact commitments that receive an explicit disposition, empowered owner, resource decision, and deadline—without increasing coercion, disclosure pressure, or false confidence.","confidence":"HIGH"},"implementation_evidence":{"support":"MODERATE","rationale":"The operational pieces are implementable with existing meeting, form, workflow, audit, and project-tracking capabilities. W3C, GOV.UK, Microsoft, Atlassian, and Interaction Foundry demonstrate lifecycle gates, impact-assessment templates, ritual canvases, owner/deadline assignment, follow-up, and retirement. ISO confirms lifecycle human-centred management is technically conventional. Remaining uncertainties are socio-technical: whether private choices stay genuinely private under workplace hierarchy, whether affected-user evidence can be reused lawfully and respectfully, whether an independent reviewer receives real hold authority, and whether symbolic framing changes decisions rather than merely confidence.","source_ids":["S1","S3","S4","S5","S6","S7"]},"scores":{"meaningful_impact":{"score":4,"rationale":"If the intervention prevents acknowledged accessibility, control, privacy, or safety obligations from disappearing at release, the protected objective is important. Realized impact and frequency are unmeasured.","source_ids":["S1","S2","S3"]},"stakeholder_pull":{"score":4,"rationale":"Government and corporate product-governance systems already demand lifecycle accessibility or impact accountability, providing credible homes for the intervention. No source requests the ritualized layer specifically.","source_ids":["S1","S3","S4"]},"incremental_advantage":{"score":3,"rationale":"Explicit re-consent, protected nonparticipation, witnessing, and ritual repair could add memory and contestability beyond a checklist, but the ordinary checklist/impact-assessment comparator may capture most practical benefit.","source_ids":["S1","S3","S4","S5"]},"distinctiveness_plausibility":{"score":2,"rationale":"Lifecycle gates, impact assessments, ritual canvases, ritual review, owners, deadlines, follow-up, and retirement all have close analogues. Distinctiveness survives mainly in their consent-governed combination and its incremental-effect claim.","source_ids":["S1","S4","S5","S6","S7"]},"technical_implementability":{"score":5,"rationale":"A 30-minute workflow, versioned form, private input path, tracker integration, and audit log require ordinary collaboration and product-management technology; no novel technical capability is required.","source_ids":["S4","S5","S6","S8"]},"adoption_authority_feasibility":{"score":4,"rationale":"Release owners can retain formal authority while accessibility or governance reviewers hold a narrow pause right. Comparable government and corporate systems already locate requirements within existing product workflows.","source_ids":["S1","S3","S4"]},"evidence_readiness":{"score":3,"rationale":"The candidate supplies observable artifact outcomes, a strong counterfactual, safety outcomes, and a bounded rehearsal. Baseline prevalence, effect size, and longitudinal follow-through require proprietary records and field participation.","source_ids":["S1","S4","S5"]},"safety_net_benefit":{"score":3,"rationale":"Private input, abstention, independent pause, ordinary-process preservation, and retirement create useful safeguards. Their effectiveness under employment hierarchy and emotionally salient user stories has not been tested.","source_ids":["S2","S5","S6"]},"scalability":{"score":3,"rationale":"The workflow is lightweight and existing standards scale across organizations, but preparation, affected-user representation, evidence governance, independent review, and avoidance of rote enactment create recurring human bottlenecks.","source_ids":["S1","S4","S5","S8"]}},"score_confidence":"MODERATE","costs":{"first_evidence":{"band_2026_usd":"10K_TO_50K","scope":"Consent-reviewed, randomized crossover tabletop test with four volunteer cross-functional squads, two redacted historical releases, an active-checklist comparator, private participant measures, compensated affected-user review, and an independent safety report.","confidence":"MODERATE","assumptions":["Approximately 180-320 total participant, facilitator, research, preparation, analysis, and review hours.","Use existing collaboration and tracking tools; no production integration.","Apply 1.5-2.0 times wage overhead to BLS hourly benchmarks and separately compensate affected-user reviewers.","Excludes production-release delay and remediation work discovered by the exercise."],"source_ids":["S8"]},"initial_deployment_startup":{"band_2026_usd":"10K_TO_50K","scope":"Configure one team's workflow, evidence-provenance rules, accessible private-input channel, tracker fields, role permissions, training, and initial privacy/accessibility review after favorable evidence.","confidence":"MODERATE","assumptions":["Mostly configuration rather than custom software.","One product team and one release system.","Existing accessibility, privacy, and employment-policy functions are available.","Does not include resolving underlying product defects or buying new enterprise platforms."],"source_ids":["S1","S4","S5","S8"]},"operational_launch":{"band_2026_usd":"50K_TO_250K","scope":"Launch across approximately five to ten teams with reusable templates, integrations, steward training, affected-user compensation, governance documentation, accessibility validation, and an initial independent audit.","confidence":"LOW","assumptions":["Two to four existing workflow integrations are reused across teams.","No major regulated-data system or custom secure research repository is required.","Formal release authority remains unchanged.","Range reflects substantial variation in legal review, accessibility support, and enterprise integration effort."],"source_ids":["S1","S3","S4","S8"]},"annual_recurring":{"band_2026_usd":"50K_TO_250K","scope":"Annual resource equivalent for five to ten teams: preparation and attendance at selected gates, steward rotation, affected-user review, accommodations, record maintenance, quarterly drift checks, and one independent annual audit.","confidence":"LOW","assumptions":["Each team conducts four to twelve selected renewals annually, not one at every release.","Eight to ten participants spend roughly 30 minutes in each enactment plus preparation and closure time.","Underlying accessibility remediation, product changes, and release delays are excluded.","Loaded labor is anchored to 2025 BLS project-management, software, and interface-design wages."],"source_ids":["S5","S8"]}},"verified_pipeline_gates":{"externally_supported_problem":{"status":"YES","reason":"Official guidance and primary practitioner research support a material gap in sustained, systematic product accessibility governance, although exact cross-release commitment decay is not quantified.","source_ids":["S1","S2","S3"]},"externally_credible_adopter_or_authorizer":{"status":"YES","reason":"GOV.UK assessment and accessibility authorities and Microsoft's internal responsible-AI governance demonstrate identifiable organizations with authority and expressed need for lifecycle user-impact controls.","source_ids":["S3","S4"]},"distinct_testable_incremental_claim":{"status":"YES","reason":"The ritual can be compared directly with an active release checklist or impact assessment on explicit dispositions, ownership, resourcing, deadlines, delayed recall, and safety outcomes.","source_ids":["S1","S4","S5","S6"]},"bounded_next_evidence_step":{"status":"YES","reason":"A four-squad, two-case randomized crossover tabletop test is bounded, leaves production authority untouched, has an active comparator, and has advance and falsification criteria.","source_ids":["S4","S5","S6","S8"]},"no_unresolved_safety_or_authority_stop":{"status":"YES","reason":"For the bounded rehearsal, redaction, specific evidence-owner permission, optional private participation, independent halt authority, no production decision power, and deletion/rollback rules contain the known risks. Production adoption still requires local privacy, employment, accessibility, and research-governance review.","source_ids":["S2","S3","S4"]},"credible_cost_scope_and_range":{"status":"YES","reason":"The next step and deployment units are explicitly bounded; national occupational wage data anchor the labor equivalents. Integration and recurring-governance uncertainty is reflected in wider, lower-confidence bands.","source_ids":["S8"]}},"next_evidence_step":"Recruit four volunteer cross-functional product squads from one organization and obtain evidence-owner, accessibility, privacy, and independent-review approval. Using two completed, redacted releases with comparable unresolved user-impact commitments, randomize squads to a crossover: (A) the ordinary release review plus a strong active-decision checklist requiring disposition, owner, resource decision, deadline, and release status; and (B) the same evidence, timebox, fields, and authority plus the proposed marked threshold, silent review, renew/revise/decline choices, protected private/pass options, witnessing, and debrief. Pre-register primary outcomes: commitments correctly reconstructed; commitments receiving complete practical closure; unique decision-relevant obligations surfaced; one-week newcomer recall; time burden; and optional private reports of pressure, accessibility failure, disclosure concern, or false confidence. The incremental claim is falsified at this stage if B adds no unique decision-relevant obligation and improves neither closure completeness nor delayed recall over A, if gains disappear after controlling for extra time, or if any serious coercion, confidentiality, accessibility, or authority incident occurs. Advance to two live release gates only if the independent reviewer issues keep/adapt, no serious safety event occurs, and B shows a pre-registered practically meaningful advantage over A.","blocking_evidence":["No external source quantifies how often previously documented user-impact commitments are lost, passively deferred, or repeatedly re-established across ordinary release cycles.","No comparative evidence shows that symbolic marking, witnessing, or re-consent adds value beyond a well-designed active checklist or impact assessment with identical evidence, time, and authority.","No field evidence establishes that abstention, silence, and private input remain genuinely nonretaliatory under workplace hierarchy.","The reuse permissions, provenance quality, confidentiality constraints, and representativeness of affected-user journeys must be verified in a partner's proprietary records.","The proposal has not shown that ritual closure produces funded work, changed release dispositions, or sustained shipped-interface improvements at the following release.","A specific adopting organization's product owner, accessibility authority, privacy counsel, and independent reviewer have not yet accepted the proposed division of authority.","World novelty, patentability, freedom to operate, market size, and realized impact remain unmeasured."],"research_disposition":"PARTNERED_RESEARCH_PROGRAM","world_novelty_boundary":"This eight-source, non-exhaustive review establishes substantial adjacent and component-level prior art only. It does not measure world novelty, patentability, freedom to operate, market size, or realized impact, and it did not search patent databases, proprietary organizational practices, every ritual-design product, or every release-governance standard.","arm":"COMPLETE_PROPOSAL_PORTFOLIO","candidate_version":0,"controller_recommendation":{"action":"STOP_EMPIRICAL_RESEARCH_NEEDED","repairable":false,"material_progress_observed":true,"progress_targets":["Measure baseline prevalence and reconstructability from at least two completed release cycles without relying on participant recollection alone.","Secure written participation and narrow halt authority from a named release owner, accessibility lead, privacy or employment reviewer, and independent safety reviewer.","Run the pre-registered crossover against an active-decision checklist with equal evidence, time, fields, and authority.","Demonstrate a practically meaningful incremental gain in complete dispositions or delayed recall, not merely higher solemnity, satisfaction, or confidence.","Show through private reporting that pass, silence, dissent, and exit are accessible and carry no perceived professional penalty.","At a subsequent live gate, verify that renewed commitments remain funded, owned, on schedule, and capable of changing the release disposition."],"reason":"Bounded web research supports the problem class, credible authorizers, feasibility, costs, and extensive prior art, but cannot establish the proposal's remaining incremental claim or workplace-safety performance. Those questions require proprietary release artifacts, participating teams, private human-subject accounts, and comparative testing; therefore the next decision must follow empirical partnered research."},"proposal_index":1}