{"as_of":"2026-08-08T20:06:00Z","caps":{"database_statements":6,"inbound":100,"outbound":100},"context_digest":"sha256:8a4dd7dc0380adc234a4ddda7e19876355b190ee03b16e5458671e58916f323b","coverage":[{"denominator":56,"lane":"reference_resolution","note":"Typed states for the displayed outbound observations.","records_observed":56,"source":"paper_references, paper_reference_links","source_observed_at":"2026-06-27T12:25:42.492883Z","state":"measured"},{"denominator":56,"lane":"standing_notices","note":"One-hop event checks from named stored sources.","records_observed":56,"source":"scholarly_work_events, retraction_status_cache","source_observed_at":"2026-08-08T06:32:00.761636+00:00","state":"measured"},{"denominator":0,"lane":"inbound_itemization","note":"Pith citing papers itemized under the disclosed page cap.","records_observed":0,"source":"paper_references, paper_reference_links","source_observed_at":null,"state":"measured"},{"denominator":1,"lane":"external_citation_measurements","note":"A source-named dated measurement, never combined with another source.","records_observed":0,"source":"cited_works","source_observed_at":null,"state":"measured"}],"external_citation_measurements":[],"inbound":[],"links":{"evidence":"/evidence","html":"/paper/2606.10882/citation-record","integrity":"/paper/2606.10882/integrity","json":"/paper/2606.10882/citation-record.json","paper":"/paper/2606.10882"},"outbound":[{"citation":{"cited_paper":null,"cited_work":{"arxiv_id":null,"doi":null,"metadata_source":null,"pith_arxiv_id":null,"snapshot_observed_at":"2026-06-27T12:25:42.492883Z","title":"Healthcare professionals’ use of mobile phones and the internet in clinical practice,","venue":null,"work_id":null,"year":2013},"citing_paper":{"arxiv_id":"2606.10882","last_updated":"2026-06-09T13:56:31Z","snapshot_observed_at":"2026-08-06T14:55:34.402749Z","submitted_at":"2026-06-09T13:56:31Z","title":"From Quality Properties to Practice: A Guideline and Workflow for Explainability Requirements","version":1},"reference_index":1,"source":"pdf_text","source_observed_at":"2026-06-27T12:25:42.492883Z"},"links":{"citing_paper":"/paper/2606.10882"},"observation_digest":"sha256:ede135075b2284f077e471be55e7f61f5637433b16a89706bf7a5fe283ba9de9","observation_id":"90b22aa6-1615-4376-a757-6b5011069805","resolution":{"observed_at":"2026-06-27T12:25:42.492883Z","resolver_source":null,"status":"unresolved"},"standing_notice":{"events":[],"reason":"canonical_work_link_unavailable","source_receipts":[],"state":"unavailable"}},{"citation":{"cited_paper":null,"cited_work":{"arxiv_id":null,"doi":null,"metadata_source":null,"pith_arxiv_id":null,"snapshot_observed_at":"2026-06-27T12:25:42.492883Z","title":"Leakiness and creepiness in app space: perceptions of privacy and mobile app use,","venue":null,"work_id":null,"year":2014},"citing_paper":{"arxiv_id":"2606.10882","last_updated":"2026-06-09T13:56:31Z","snapshot_observed_at":"2026-08-06T14:55:34.402749Z","submitted_at":"2026-06-09T13:56:31Z","title":"From Quality Properties to Practice: A Guideline and Workflow for Explainability Requirements","version":1},"reference_index":2,"source":"pdf_text","source_observed_at":"2026-06-27T12:25:42.492883Z"},"links":{"citing_paper":"/paper/2606.10882"},"observation_digest":"sha256:2b04ca0d0071a5c75fb753d6624fa472416f4f98130234c2c9c648edf7e810f6","observation_id":"6a52d2db-e11e-45ab-8c94-3f3cfc2c5b81","resolution":{"observed_at":"2026-06-27T12:25:42.492883Z","resolver_source":null,"status":"unresolved"},"standing_notice":{"events":[],"reason":"canonical_work_link_unavailable","source_receipts":[],"state":"unavailable"}},{"citation":{"cited_paper":null,"cited_work":{"arxiv_id":null,"doi":null,"metadata_source":null,"pith_arxiv_id":null,"snapshot_observed_at":"2026-06-27T12:25:42.492883Z","title":"Artificial intelligence in dermatology image analysis: Current develop- ments and future trends,","venue":null,"work_id":null,"year":2022},"citing_paper":{"arxiv_id":"2606.10882","last_updated":"2026-06-09T13:56:31Z","snapshot_observed_at":"2026-08-06T14:55:34.402749Z","submitted_at":"2026-06-09T13:56:31Z","title":"From Quality Properties to Practice: A Guideline and Workflow for Explainability Requirements","version":1},"reference_index":3,"source":"pdf_text","source_observed_at":"2026-06-27T12:25:42.492883Z"},"links":{"citing_paper":"/paper/2606.10882"},"observation_digest":"sha256:67feb0cb8e32f1fbc069c0a824e1f996432f870eb34e7e2a3dab20a6580cfb5c","observation_id":"25efb2a7-a9a1-4b0f-80a6-f1e2c8b9e9b7","resolution":{"observed_at":"2026-06-27T12:25:42.492883Z","resolver_source":null,"status":"unresolved"},"standing_notice":{"events":[],"reason":"canonical_work_link_unavailable","source_receipts":[],"state":"unavailable"}},{"citation":{"cited_paper":null,"cited_work":{"arxiv_id":null,"doi":null,"metadata_source":null,"pith_arxiv_id":null,"snapshot_observed_at":"2026-06-27T12:25:42.492883Z","title":"Peeking inside the black-box: a survey on explainable artificial intelligence (xai),","venue":null,"work_id":null,"year":2018},"citing_paper":{"arxiv_id":"2606.10882","last_updated":"2026-06-09T13:56:31Z","snapshot_observed_at":"2026-08-06T14:55:34.402749Z","submitted_at":"2026-06-09T13:56:31Z","title":"From Quality Properties to Practice: A Guideline and Workflow for Explainability Requirements","version":1},"reference_index":4,"source":"pdf_text","source_observed_at":"2026-06-27T12:25:42.492883Z"},"links":{"citing_paper":"/paper/2606.10882"},"observation_digest":"sha256:918716f772915bbde43092bcfc3e840f0c1ccf34061f1d3447cb3b6718e8b426","observation_id":"3b9110c1-2af1-4729-96b2-96baac3aebdf","resolution":{"observed_at":"2026-06-27T12:25:42.492883Z","resolver_source":null,"status":"unresolved"},"standing_notice":{"events":[],"reason":"canonical_work_link_unavailable","source_receipts":[],"state":"unavailable"}},{"citation":{"cited_paper":null,"cited_work":{"arxiv_id":null,"doi":null,"metadata_source":null,"pith_arxiv_id":null,"snapshot_observed_at":"2026-06-27T12:25:42.492883Z","title":"A study on the mental models of users concerning existing software,","venue":null,"work_id":null,"year":2022},"citing_paper":{"arxiv_id":"2606.10882","last_updated":"2026-06-09T13:56:31Z","snapshot_observed_at":"2026-08-06T14:55:34.402749Z","submitted_at":"2026-06-09T13:56:31Z","title":"From Quality Properties to Practice: A Guideline and Workflow for Explainability Requirements","version":1},"reference_index":5,"source":"pdf_text","source_observed_at":"2026-06-27T12:25:42.492883Z"},"links":{"citing_paper":"/paper/2606.10882"},"observation_digest":"sha256:28e34b071fd19d68f625f9833fb5f8cb4a7430cd48964119d9aa1dcbe8be210e","observation_id":"92e6a404-13e4-438a-861b-f8fe92f1ed2a","resolution":{"observed_at":"2026-06-27T12:25:42.492883Z","resolver_source":null,"status":"unresolved"},"standing_notice":{"events":[],"reason":"canonical_work_link_unavailable","source_receipts":[],"state":"unavailable"}},{"citation":{"cited_paper":null,"cited_work":{"arxiv_id":null,"doi":null,"metadata_source":null,"pith_arxiv_id":null,"snapshot_observed_at":"2026-06-27T12:25:42.492883Z","title":"Explanations in everyday software systems: Towards a taxonomy for explainability needs,","venue":null,"work_id":null,"year":2024},"citing_paper":{"arxiv_id":"2606.10882","last_updated":"2026-06-09T13:56:31Z","snapshot_observed_at":"2026-08-06T14:55:34.402749Z","submitted_at":"2026-06-09T13:56:31Z","title":"From Quality Properties to Practice: A Guideline and Workflow for Explainability Requirements","version":1},"reference_index":6,"source":"pdf_text","source_observed_at":"2026-06-27T12:25:42.492883Z"},"links":{"citing_paper":"/paper/2606.10882"},"observation_digest":"sha256:e610ab5fbc1e441873a93d45234c6938e6f7ce00e708038977a3cbd43694b31d","observation_id":"4ee65c69-322e-4cd0-a797-8fc3d5473eb5","resolution":{"observed_at":"2026-06-27T12:25:42.492883Z","resolver_source":null,"status":"unresolved"},"standing_notice":{"events":[],"reason":"canonical_work_link_unavailable","source_receipts":[],"state":"unavailable"}},{"citation":{"cited_paper":null,"cited_work":{"arxiv_id":null,"doi":null,"metadata_source":null,"pith_arxiv_id":null,"snapshot_observed_at":"2026-06-27T12:25:42.492883Z","title":"Framing what can be explained – an operational taxonomy for explainability needs,","venue":null,"work_id":null,"year":2025},"citing_paper":{"arxiv_id":"2606.10882","last_updated":"2026-06-09T13:56:31Z","snapshot_observed_at":"2026-08-06T14:55:34.402749Z","submitted_at":"2026-06-09T13:56:31Z","title":"From Quality Properties to Practice: A Guideline and Workflow for Explainability Requirements","version":1},"reference_index":7,"source":"pdf_text","source_observed_at":"2026-06-27T12:25:42.492883Z"},"links":{"citing_paper":"/paper/2606.10882"},"observation_digest":"sha256:563320a12f1b8617c22a688ae79f0d8e009d6f476d935087e7092058793f5ad3","observation_id":"370d07a4-750b-4535-aa0e-42eccd63692e","resolution":{"observed_at":"2026-06-27T12:25:42.492883Z","resolver_source":null,"status":"unresolved"},"standing_notice":{"events":[],"reason":"canonical_work_link_unavailable","source_receipts":[],"state":"unavailable"}},{"citation":{"cited_paper":null,"cited_work":{"arxiv_id":null,"doi":null,"metadata_source":null,"pith_arxiv_id":null,"snapshot_observed_at":"2026-06-27T12:25:42.492883Z","title":"Context, content, consent- how to design user-centered privacy explanations (s)","venue":null,"work_id":null,"year":2023},"citing_paper":{"arxiv_id":"2606.10882","last_updated":"2026-06-09T13:56:31Z","snapshot_observed_at":"2026-08-06T14:55:34.402749Z","submitted_at":"2026-06-09T13:56:31Z","title":"From Quality Properties to Practice: A Guideline and Workflow for Explainability Requirements","version":1},"reference_index":8,"source":"pdf_text","source_observed_at":"2026-06-27T12:25:42.492883Z"},"links":{"citing_paper":"/paper/2606.10882"},"observation_digest":"sha256:966fd58a2d48a0c63044313b19c5c817fe1a7d215a782266a391a17ec9f028a9","observation_id":"939f286c-f154-43d4-b389-3c3687f6edc3","resolution":{"observed_at":"2026-06-27T12:25:42.492883Z","resolver_source":null,"status":"unresolved"},"standing_notice":{"events":[],"reason":"canonical_work_link_unavailable","source_receipts":[],"state":"unavailable"}},{"citation":{"cited_paper":null,"cited_work":{"arxiv_id":null,"doi":null,"metadata_source":null,"pith_arxiv_id":null,"snapshot_observed_at":"2026-06-27T12:25:42.492883Z","title":"Exploring explainability: a definition, a model, and a knowledge catalogue,","venue":null,"work_id":null,"year":2021},"citing_paper":{"arxiv_id":"2606.10882","last_updated":"2026-06-09T13:56:31Z","snapshot_observed_at":"2026-08-06T14:55:34.402749Z","submitted_at":"2026-06-09T13:56:31Z","title":"From Quality Properties to Practice: A Guideline and Workflow for Explainability Requirements","version":1},"reference_index":9,"source":"pdf_text","source_observed_at":"2026-06-27T12:25:42.492883Z"},"links":{"citing_paper":"/paper/2606.10882"},"observation_digest":"sha256:b733c14febaeddf7f0920727ab79a585ef98670c5f41e1e8a3ccac441c39ba7b","observation_id":"ed7e9637-6d4a-407b-8bf3-cde9d526afbe","resolution":{"observed_at":"2026-06-27T12:25:42.492883Z","resolver_source":null,"status":"unresolved"},"standing_notice":{"events":[],"reason":"canonical_work_link_unavailable","source_receipts":[],"state":"unavailable"}},{"citation":{"cited_paper":null,"cited_work":{"arxiv_id":null,"doi":null,"metadata_source":null,"pith_arxiv_id":null,"snapshot_observed_at":"2026-06-27T12:25:42.492883Z","title":"Automatic generation of explainability requirements and software explanations from user reviews,","venue":null,"work_id":null,"year":2025},"citing_paper":{"arxiv_id":"2606.10882","last_updated":"2026-06-09T13:56:31Z","snapshot_observed_at":"2026-08-06T14:55:34.402749Z","submitted_at":"2026-06-09T13:56:31Z","title":"From Quality Properties to Practice: A Guideline and Workflow for Explainability Requirements","version":1},"reference_index":10,"source":"pdf_text","source_observed_at":"2026-06-27T12:25:42.492883Z"},"links":{"citing_paper":"/paper/2606.10882"},"observation_digest":"sha256:26aa45c0934d2f445f37cc60c75cf05ef8227e898cfdfc4e8721d9edb2912a53","observation_id":"d4bbbc49-ef4d-4796-804a-04ef6dd15414","resolution":{"observed_at":"2026-06-27T12:25:42.492883Z","resolver_source":null,"status":"unresolved"},"standing_notice":{"events":[],"reason":"canonical_work_link_unavailable","source_receipts":[],"state":"unavailable"}},{"citation":{"cited_paper":{"arxiv_id":"2401.13110","last_updated":"2024-01-23T21:47:12Z","snapshot_observed_at":"2026-08-04T22:46:17.607824Z","submitted_at":"2024-01-23T21:47:12Z","title":"XAI for All: Can Large Language Models Simplify Explainable AI?","version":1},"cited_work":{"arxiv_id":"2401.13110","doi":null,"metadata_source":"arxiv_reference","pith_arxiv_id":"2401.13110","snapshot_observed_at":"2026-07-03T06:47:43.812886Z","title":"XAI for all: Can large language models simplify explainable AI?","venue":null,"work_id":"ff150a21-904b-4c9b-8895-2f5f05041833","year":2024},"citing_paper":{"arxiv_id":"2606.10882","last_updated":"2026-06-09T13:56:31Z","snapshot_observed_at":"2026-08-06T14:55:34.402749Z","submitted_at":"2026-06-09T13:56:31Z","title":"From Quality Properties to Practice: A Guideline and Workflow for Explainability Requirements","version":1},"reference_index":11,"source":"pdf_text","source_observed_at":"2026-06-27T12:25:42.492883Z"},"links":{"cited_paper":"/paper/2401.13110","citing_paper":"/paper/2606.10882"},"observation_digest":"sha256:7a925bcc6f23b23551d6dce90130f3b81fa73b192fd9026be8b769667e7ebbca","observation_id":"f32cba46-10b8-4297-9486-2cdab9b4edc9","resolution":{"observed_at":"2026-07-03T06:47:43.814376Z","resolver_source":"arxiv_id","status":"verified_exact"},"standing_notice":{"events":[],"observation":"No event found in the named queried sources as of 2026-08-08T06:32:00.761636+00:00.","reason":null,"source_receipts":[{"observed_at":"2026-08-08T06:32:00.761636+00:00","source":"crossref"},{"observed_at":"2026-08-08T06:31:55.24221+00:00","source":"retraction_watch"}],"state":"measured"}},{"citation":{"cited_paper":null,"cited_work":{"arxiv_id":null,"doi":null,"metadata_source":null,"pith_arxiv_id":null,"snapshot_observed_at":"2026-06-27T12:25:42.492883Z","title":"A survey of contrastive and counterfactual explanation generation methods for explainable artificial intelligence,","venue":null,"work_id":null,"year":2021},"citing_paper":{"arxiv_id":"2606.10882","last_updated":"2026-06-09T13:56:31Z","snapshot_observed_at":"2026-08-06T14:55:34.402749Z","submitted_at":"2026-06-09T13:56:31Z","title":"From Quality Properties to Practice: A Guideline and Workflow for Explainability Requirements","version":1},"reference_index":12,"source":"pdf_text","source_observed_at":"2026-06-27T12:25:42.492883Z"},"links":{"citing_paper":"/paper/2606.10882"},"observation_digest":"sha256:fb3f6d3481fa76d1536485fb43c4823b117abee6b5a001532d022e80c4ac5d09","observation_id":"22f24c35-0c4c-4595-a702-c539bf5ced0a","resolution":{"observed_at":"2026-06-27T12:25:42.492883Z","resolver_source":null,"status":"unresolved"},"standing_notice":{"events":[],"reason":"canonical_work_link_unavailable","source_receipts":[],"state":"unavailable"}},{"citation":{"cited_paper":null,"cited_work":{"arxiv_id":null,"doi":null,"metadata_source":null,"pith_arxiv_id":null,"snapshot_observed_at":"2026-06-27T12:25:42.492883Z","title":"Llm-generated explanations for recommender systems,","venue":null,"work_id":null,"year":2024},"citing_paper":{"arxiv_id":"2606.10882","last_updated":"2026-06-09T13:56:31Z","snapshot_observed_at":"2026-08-06T14:55:34.402749Z","submitted_at":"2026-06-09T13:56:31Z","title":"From Quality Properties to Practice: A Guideline and Workflow for Explainability Requirements","version":1},"reference_index":13,"source":"pdf_text","source_observed_at":"2026-06-27T12:25:42.492883Z"},"links":{"citing_paper":"/paper/2606.10882"},"observation_digest":"sha256:236cf656695081abae9b053f3ed929a4da7a0eec742c76887a1791d9c78a60f6","observation_id":"be6380d3-80be-4915-a5c3-6cd97f8caa22","resolution":{"observed_at":"2026-06-27T12:25:42.492883Z","resolver_source":null,"status":"unresolved"},"standing_notice":{"events":[],"reason":"canonical_work_link_unavailable","source_receipts":[],"state":"unavailable"}},{"citation":{"cited_paper":null,"cited_work":{"arxiv_id":null,"doi":null,"metadata_source":null,"pith_arxiv_id":null,"snapshot_observed_at":"2026-06-27T12:25:42.492883Z","title":"Is Stack Overflow obsolete? an empirical study of the characteristics of ChatGPT answers to Stack Overflow questions,","venue":null,"work_id":null,"year":2024},"citing_paper":{"arxiv_id":"2606.10882","last_updated":"2026-06-09T13:56:31Z","snapshot_observed_at":"2026-08-06T14:55:34.402749Z","submitted_at":"2026-06-09T13:56:31Z","title":"From Quality Properties to Practice: A Guideline and Workflow for Explainability Requirements","version":1},"reference_index":14,"source":"pdf_text","source_observed_at":"2026-06-27T12:25:42.492883Z"},"links":{"citing_paper":"/paper/2606.10882"},"observation_digest":"sha256:eb876d8a2af5d37b26bb8193c9634f42e18d595d0be5875408c1c44b6afff5ab","observation_id":"0d58eec9-dcdf-4803-a14c-9781ba4e88c2","resolution":{"observed_at":"2026-06-27T12:25:42.492883Z","resolver_source":null,"status":"unresolved"},"standing_notice":{"events":[],"reason":"canonical_work_link_unavailable","source_receipts":[],"state":"unavailable"}},{"citation":{"cited_paper":null,"cited_work":{"arxiv_id":null,"doi":null,"metadata_source":null,"pith_arxiv_id":null,"snapshot_observed_at":"2026-06-27T12:25:42.492883Z","title":"Replication Package: From Quality Properties to Practice: A Guideline and Workflow for Explainability Requirements,","venue":null,"work_id":null,"year":null},"citing_paper":{"arxiv_id":"2606.10882","last_updated":"2026-06-09T13:56:31Z","snapshot_observed_at":"2026-08-06T14:55:34.402749Z","submitted_at":"2026-06-09T13:56:31Z","title":"From Quality Properties to Practice: A Guideline and Workflow for Explainability Requirements","version":1},"reference_index":15,"source":"pdf_text","source_observed_at":"2026-06-27T12:25:42.492883Z"},"links":{"citing_paper":"/paper/2606.10882"},"observation_digest":"sha256:e1a6c90baf59a4741b86dc04bac1f9edc4e3c49f9a909444cddcb963e198be12","observation_id":"566bfa97-49ea-42c9-80ea-770e40b8d4d6","resolution":{"observed_at":"2026-06-27T12:25:42.492883Z","resolver_source":null,"status":"unresolved"},"standing_notice":{"events":[],"reason":"canonical_work_link_unavailable","source_receipts":[],"state":"unavailable"}},{"citation":{"cited_paper":null,"cited_work":{"arxiv_id":null,"doi":"10.5281/zenodo.20396663","metadata_source":"openalex","pith_arxiv_id":null,"snapshot_observed_at":"2026-08-05T02:28:24.338817Z","title":"Available: https://doi.org/10.5281/zenodo.20396663","venue":"Zenodo (CERN European Organization for Nuclear Research)","work_id":"a96d150d-d1f2-4222-ac66-b101cb919098","year":null},"citing_paper":{"arxiv_id":"2606.10882","last_updated":"2026-06-09T13:56:31Z","snapshot_observed_at":"2026-08-06T14:55:34.402749Z","submitted_at":"2026-06-09T13:56:31Z","title":"From Quality Properties to Practice: A Guideline and Workflow for Explainability Requirements","version":1},"reference_index":16,"source":"pdf_text","source_observed_at":"2026-06-27T12:25:42.492883Z"},"links":{"citing_paper":"/paper/2606.10882"},"observation_digest":"sha256:3116eb41da32b6a1dad5e84744698555fc0ad66ce4bd6a1d21e2a5171527bb01","observation_id":"4c3fdb4b-ee37-435b-af6c-515fd0a568b6","resolution":{"observed_at":"2026-06-27T12:30:55.438109Z","resolver_source":"doi","status":"verified_exact"},"standing_notice":{"events":[],"observation":"No event found in the named queried sources as of 2026-08-08T06:32:00.761636+00:00.","reason":null,"source_receipts":[{"observed_at":"2026-08-08T06:32:00.761636+00:00","source":"crossref"},{"observed_at":"2026-08-08T06:31:55.24221+00:00","source":"retraction_watch"}],"state":"measured"}},{"citation":{"cited_paper":null,"cited_work":{"arxiv_id":null,"doi":null,"metadata_source":null,"pith_arxiv_id":null,"snapshot_observed_at":"2026-06-27T12:25:42.492883Z","title":"Explainability as a non-functional requirement: challenges and recommendations,","venue":null,"work_id":null,"year":2020},"citing_paper":{"arxiv_id":"2606.10882","last_updated":"2026-06-09T13:56:31Z","snapshot_observed_at":"2026-08-06T14:55:34.402749Z","submitted_at":"2026-06-09T13:56:31Z","title":"From Quality Properties to Practice: A Guideline and Workflow for Explainability Requirements","version":1},"reference_index":17,"source":"pdf_text","source_observed_at":"2026-06-27T12:25:42.492883Z"},"links":{"citing_paper":"/paper/2606.10882"},"observation_digest":"sha256:1d07f21a3fd70ca500377619100ce155fc55659edca2f27f82d53cbe8bcc326b","observation_id":"205fadee-de41-4aa1-87e2-cb5206c4f868","resolution":{"observed_at":"2026-06-27T12:25:42.492883Z","resolver_source":null,"status":"unresolved"},"standing_notice":{"events":[],"reason":"canonical_work_link_unavailable","source_receipts":[],"state":"unavailable"}},{"citation":{"cited_paper":null,"cited_work":{"arxiv_id":null,"doi":null,"metadata_source":null,"pith_arxiv_id":null,"snapshot_observed_at":"2026-06-27T12:25:42.492883Z","title":"Explainability as a non-functional requirement,","venue":null,"work_id":null,"year":2019},"citing_paper":{"arxiv_id":"2606.10882","last_updated":"2026-06-09T13:56:31Z","snapshot_observed_at":"2026-08-06T14:55:34.402749Z","submitted_at":"2026-06-09T13:56:31Z","title":"From Quality Properties to Practice: A Guideline and Workflow for Explainability Requirements","version":1},"reference_index":18,"source":"pdf_text","source_observed_at":"2026-06-27T12:25:42.492883Z"},"links":{"citing_paper":"/paper/2606.10882"},"observation_digest":"sha256:e03a6fae3a369f4bfca9aa1197100cf3abb98b970814e931550d48d3a61262c2","observation_id":"954d5a8d-22bc-488b-ae19-c4126f451d12","resolution":{"observed_at":"2026-06-27T12:25:42.492883Z","resolver_source":null,"status":"unresolved"},"standing_notice":{"events":[],"reason":"canonical_work_link_unavailable","source_receipts":[],"state":"unavailable"}},{"citation":{"cited_paper":null,"cited_work":{"arxiv_id":null,"doi":null,"metadata_source":null,"pith_arxiv_id":null,"snapshot_observed_at":"2026-06-27T12:25:42.492883Z","title":"From app features to explanation needs: Analyzing correlations and predictive potential,","venue":null,"work_id":null,"year":2025},"citing_paper":{"arxiv_id":"2606.10882","last_updated":"2026-06-09T13:56:31Z","snapshot_observed_at":"2026-08-06T14:55:34.402749Z","submitted_at":"2026-06-09T13:56:31Z","title":"From Quality Properties to Practice: A Guideline and Workflow for Explainability Requirements","version":1},"reference_index":19,"source":"pdf_text","source_observed_at":"2026-06-27T12:25:42.492883Z"},"links":{"citing_paper":"/paper/2606.10882"},"observation_digest":"sha256:23269b5c42bac1d5eea929eca2524752ab997c0c337170b54597b830e4a660c0","observation_id":"6bcc7c6b-50a3-4477-88da-c3fa458ee388","resolution":{"observed_at":"2026-06-27T12:25:42.492883Z","resolver_source":null,"status":"unresolved"},"standing_notice":{"events":[],"reason":"canonical_work_link_unavailable","source_receipts":[],"state":"unavailable"}},{"citation":{"cited_paper":null,"cited_work":{"arxiv_id":null,"doi":null,"metadata_source":null,"pith_arxiv_id":null,"snapshot_observed_at":"2026-06-27T12:25:42.492883Z","title":"Immersive and enjoyable explanations - on distinct explainability requirements in games,","venue":null,"work_id":null,"year":2026},"citing_paper":{"arxiv_id":"2606.10882","last_updated":"2026-06-09T13:56:31Z","snapshot_observed_at":"2026-08-06T14:55:34.402749Z","submitted_at":"2026-06-09T13:56:31Z","title":"From Quality Properties to Practice: A Guideline and Workflow for Explainability Requirements","version":1},"reference_index":20,"source":"pdf_text","source_observed_at":"2026-06-27T12:25:42.492883Z"},"links":{"citing_paper":"/paper/2606.10882"},"observation_digest":"sha256:7bd21423d09520a9f930e4f639c931484c0afd8b6c696d058963769b244d07c6","observation_id":"ea3d5904-ad7c-42ee-92d6-76998bbcc3cb","resolution":{"observed_at":"2026-06-27T12:25:42.492883Z","resolver_source":null,"status":"unresolved"},"standing_notice":{"events":[],"reason":"canonical_work_link_unavailable","source_receipts":[],"state":"unavailable"}},{"citation":{"cited_paper":null,"cited_work":{"arxiv_id":null,"doi":null,"metadata_source":null,"pith_arxiv_id":null,"snapshot_observed_at":"2026-06-27T12:25:42.492883Z","title":"Misunderstandings by design: Using erroneous tutorials to induce mental model conflicts and the need for explanations,","venue":null,"work_id":null,"year":2026},"citing_paper":{"arxiv_id":"2606.10882","last_updated":"2026-06-09T13:56:31Z","snapshot_observed_at":"2026-08-06T14:55:34.402749Z","submitted_at":"2026-06-09T13:56:31Z","title":"From Quality Properties to Practice: A Guideline and Workflow for Explainability Requirements","version":1},"reference_index":21,"source":"pdf_text","source_observed_at":"2026-06-27T12:25:42.492883Z"},"links":{"citing_paper":"/paper/2606.10882"},"observation_digest":"sha256:2d1fd1c98aa70f1a140d9a02f36f9da4dca18dc908ffe66d77bd3dd5e851d62d","observation_id":"7ab06160-9854-451e-b952-97da50c24d76","resolution":{"observed_at":"2026-06-27T12:25:42.492883Z","resolver_source":null,"status":"unresolved"},"standing_notice":{"events":[],"reason":"canonical_work_link_unavailable","source_receipts":[],"state":"unavailable"}},{"citation":{"cited_paper":null,"cited_work":{"arxiv_id":null,"doi":null,"metadata_source":null,"pith_arxiv_id":null,"snapshot_observed_at":"2026-06-27T12:25:42.492883Z","title":"Writing better software explanations: A guideline-based approach,","venue":null,"work_id":null,"year":2026},"citing_paper":{"arxiv_id":"2606.10882","last_updated":"2026-06-09T13:56:31Z","snapshot_observed_at":"2026-08-06T14:55:34.402749Z","submitted_at":"2026-06-09T13:56:31Z","title":"From Quality Properties to Practice: A Guideline and Workflow for Explainability Requirements","version":1},"reference_index":22,"source":"pdf_text","source_observed_at":"2026-06-27T12:25:42.492883Z"},"links":{"citing_paper":"/paper/2606.10882"},"observation_digest":"sha256:6b21842f509a12ec6bf085ae96f3f167e6ef6d988c0342518f62d3c5a6a3c49e","observation_id":"e43b601b-9e69-4b3e-b3cc-3f6d2baee2e7","resolution":{"observed_at":"2026-06-27T12:25:42.492883Z","resolver_source":null,"status":"unresolved"},"standing_notice":{"events":[],"reason":"canonical_work_link_unavailable","source_receipts":[],"state":"unavailable"}},{"citation":{"cited_paper":null,"cited_work":{"arxiv_id":null,"doi":null,"metadata_source":null,"pith_arxiv_id":null,"snapshot_observed_at":"2026-06-27T12:25:42.492883Z","title":"Understanding usefulness in developer explanations on stack overflow,","venue":null,"work_id":null,"year":2026},"citing_paper":{"arxiv_id":"2606.10882","last_updated":"2026-06-09T13:56:31Z","snapshot_observed_at":"2026-08-06T14:55:34.402749Z","submitted_at":"2026-06-09T13:56:31Z","title":"From Quality Properties to Practice: A Guideline and Workflow for Explainability Requirements","version":1},"reference_index":23,"source":"pdf_text","source_observed_at":"2026-06-27T12:25:42.492883Z"},"links":{"citing_paper":"/paper/2606.10882"},"observation_digest":"sha256:3efa95c57c0893a9282ec7e235656173838beee1ff25967b9914d11377db4b29","observation_id":"e17603d9-caa1-4bc7-8d59-456516506419","resolution":{"observed_at":"2026-06-27T12:25:42.492883Z","resolver_source":null,"status":"unresolved"},"standing_notice":{"events":[],"reason":"canonical_work_link_unavailable","source_receipts":[],"state":"unavailable"}},{"citation":{"cited_paper":null,"cited_work":{"arxiv_id":null,"doi":null,"metadata_source":null,"pith_arxiv_id":null,"snapshot_observed_at":"2026-06-27T12:25:42.492883Z","title":"Iden- tifying explanation needs: Towards a catalog of user-based indicators,","venue":null,"work_id":null,"year":2025},"citing_paper":{"arxiv_id":"2606.10882","last_updated":"2026-06-09T13:56:31Z","snapshot_observed_at":"2026-08-06T14:55:34.402749Z","submitted_at":"2026-06-09T13:56:31Z","title":"From Quality Properties to Practice: A Guideline and Workflow for Explainability Requirements","version":1},"reference_index":24,"source":"pdf_text","source_observed_at":"2026-06-27T12:25:42.492883Z"},"links":{"citing_paper":"/paper/2606.10882"},"observation_digest":"sha256:8cb1738a632d2e76d9c6b883524ff44851af0a8563691c9308660fc845b4808e","observation_id":"8ddce865-c19c-4c45-9d23-723829862cfc","resolution":{"observed_at":"2026-06-27T12:25:42.492883Z","resolver_source":null,"status":"unresolved"},"standing_notice":{"events":[],"reason":"canonical_work_link_unavailable","source_receipts":[],"state":"unavailable"}},{"citation":{"cited_paper":null,"cited_work":{"arxiv_id":null,"doi":null,"metadata_source":null,"pith_arxiv_id":null,"snapshot_observed_at":"2026-06-27T12:25:42.492883Z","title":"Modeling and evaluating per- sonas with software explainability requirements,","venue":null,"work_id":null,"year":2021},"citing_paper":{"arxiv_id":"2606.10882","last_updated":"2026-06-09T13:56:31Z","snapshot_observed_at":"2026-08-06T14:55:34.402749Z","submitted_at":"2026-06-09T13:56:31Z","title":"From Quality Properties to Practice: A Guideline and Workflow for Explainability Requirements","version":1},"reference_index":25,"source":"pdf_text","source_observed_at":"2026-06-27T12:25:42.492883Z"},"links":{"citing_paper":"/paper/2606.10882"},"observation_digest":"sha256:f7c837190733c7b5f2e082ad218b77129e12fa9ed46b9a9dd68db87e5290311f","observation_id":"08bfbe9a-f1c9-4936-8a76-2436770a4d2c","resolution":{"observed_at":"2026-06-27T12:25:42.492883Z","resolver_source":null,"status":"unresolved"},"standing_notice":{"events":[],"reason":"canonical_work_link_unavailable","source_receipts":[],"state":"unavailable"}},{"citation":{"cited_paper":null,"cited_work":{"arxiv_id":null,"doi":null,"metadata_source":null,"pith_arxiv_id":null,"snapshot_observed_at":"2026-06-27T12:25:42.492883Z","title":"Explanation needs in app reviews: Taxonomy and automated detection,","venue":null,"work_id":null,"year":2023},"citing_paper":{"arxiv_id":"2606.10882","last_updated":"2026-06-09T13:56:31Z","snapshot_observed_at":"2026-08-06T14:55:34.402749Z","submitted_at":"2026-06-09T13:56:31Z","title":"From Quality Properties to Practice: A Guideline and Workflow for Explainability Requirements","version":1},"reference_index":26,"source":"pdf_text","source_observed_at":"2026-06-27T12:25:42.492883Z"},"links":{"citing_paper":"/paper/2606.10882"},"observation_digest":"sha256:3856906b39fb0dd347ffd84faafc39a1c36f5a6a02e32a9d9817e419b73acaf4","observation_id":"b05ba113-08e5-413f-9262-e1fb1dfb1e97","resolution":{"observed_at":"2026-06-27T12:25:42.492883Z","resolver_source":null,"status":"unresolved"},"standing_notice":{"events":[],"reason":"canonical_work_link_unavailable","source_receipts":[],"state":"unavailable"}},{"citation":{"cited_paper":null,"cited_work":{"arxiv_id":null,"doi":null,"metadata_source":null,"pith_arxiv_id":null,"snapshot_observed_at":"2026-06-27T12:25:42.492883Z","title":"A review of taxonomies of explainable artificial intelligence (xai) methods,","venue":null,"work_id":null,"year":2022},"citing_paper":{"arxiv_id":"2606.10882","last_updated":"2026-06-09T13:56:31Z","snapshot_observed_at":"2026-08-06T14:55:34.402749Z","submitted_at":"2026-06-09T13:56:31Z","title":"From Quality Properties to Practice: A Guideline and Workflow for Explainability Requirements","version":1},"reference_index":27,"source":"pdf_text","source_observed_at":"2026-06-27T12:25:42.492883Z"},"links":{"citing_paper":"/paper/2606.10882"},"observation_digest":"sha256:a78b98b9e666cf8326bde869b0ed7ff79ab1603099021a449001f26d5d83a162","observation_id":"09328840-aebd-4797-8a92-8accd6529b54","resolution":{"observed_at":"2026-06-27T12:25:42.492883Z","resolver_source":null,"status":"unresolved"},"standing_notice":{"events":[],"reason":"canonical_work_link_unavailable","source_receipts":[],"state":"unavailable"}},{"citation":{"cited_paper":null,"cited_work":{"arxiv_id":null,"doi":null,"metadata_source":null,"pith_arxiv_id":null,"snapshot_observed_at":"2026-06-27T12:25:42.492883Z","title":"Requirements elicitation tech- niques: a systematic literature review based on the maturity of the techniques,","venue":null,"work_id":null,"year":2018},"citing_paper":{"arxiv_id":"2606.10882","last_updated":"2026-06-09T13:56:31Z","snapshot_observed_at":"2026-08-06T14:55:34.402749Z","submitted_at":"2026-06-09T13:56:31Z","title":"From Quality Properties to Practice: A Guideline and Workflow for Explainability Requirements","version":1},"reference_index":28,"source":"pdf_text","source_observed_at":"2026-06-27T12:25:42.492883Z"},"links":{"citing_paper":"/paper/2606.10882"},"observation_digest":"sha256:bd116c4aa61d32a6c8793f9c0ea8e549960fb200e962ac863e58093723af41e9","observation_id":"5a013a15-8da1-48ca-b8d0-cc1d17157b47","resolution":{"observed_at":"2026-06-27T12:25:42.492883Z","resolver_source":null,"status":"unresolved"},"standing_notice":{"events":[],"reason":"canonical_work_link_unavailable","source_receipts":[],"state":"unavailable"}},{"citation":{"cited_paper":null,"cited_work":{"arxiv_id":null,"doi":null,"metadata_source":null,"pith_arxiv_id":null,"snapshot_observed_at":"2026-06-27T12:25:42.492883Z","title":"Successful requirement elicita- tion by combining requirement engineering techniques,","venue":null,"work_id":null,"year":2008},"citing_paper":{"arxiv_id":"2606.10882","last_updated":"2026-06-09T13:56:31Z","snapshot_observed_at":"2026-08-06T14:55:34.402749Z","submitted_at":"2026-06-09T13:56:31Z","title":"From Quality Properties to Practice: A Guideline and Workflow for Explainability Requirements","version":1},"reference_index":29,"source":"pdf_text","source_observed_at":"2026-06-27T12:25:42.492883Z"},"links":{"citing_paper":"/paper/2606.10882"},"observation_digest":"sha256:eef56aadcb9e717e38b75f84f543dd4e344aaf91781c927588854e56c1358bf8","observation_id":"038d19fc-3b9f-43d5-947a-e8cecc96085a","resolution":{"observed_at":"2026-06-27T12:25:42.492883Z","resolver_source":null,"status":"unresolved"},"standing_notice":{"events":[],"reason":"canonical_work_link_unavailable","source_receipts":[],"state":"unavailable"}},{"citation":{"cited_paper":null,"cited_work":{"arxiv_id":null,"doi":null,"metadata_source":null,"pith_arxiv_id":null,"snapshot_observed_at":"2026-06-27T12:25:42.492883Z","title":"How to elicit explainability requirements? a com- parison of interviews, focus groups, and surveys,","venue":null,"work_id":null,"year":2025},"citing_paper":{"arxiv_id":"2606.10882","last_updated":"2026-06-09T13:56:31Z","snapshot_observed_at":"2026-08-06T14:55:34.402749Z","submitted_at":"2026-06-09T13:56:31Z","title":"From Quality Properties to Practice: A Guideline and Workflow for Explainability Requirements","version":1},"reference_index":30,"source":"pdf_text","source_observed_at":"2026-06-27T12:25:42.492883Z"},"links":{"citing_paper":"/paper/2606.10882"},"observation_digest":"sha256:1beb09d50bae07ceca3ac74651ea9d6a962933795fa2d339690ca43a57baa313","observation_id":"31a44010-cc77-42a5-b057-75c617e95d5d","resolution":{"observed_at":"2026-06-27T12:25:42.492883Z","resolver_source":null,"status":"unresolved"},"standing_notice":{"events":[],"reason":"canonical_work_link_unavailable","source_receipts":[],"state":"unavailable"}},{"citation":{"cited_paper":null,"cited_work":{"arxiv_id":null,"doi":null,"metadata_source":null,"pith_arxiv_id":null,"snapshot_observed_at":"2026-06-27T12:25:42.492883Z","title":"Non-functional re- quirements elicitation guideline for agile methods,","venue":null,"work_id":null,"year":2017},"citing_paper":{"arxiv_id":"2606.10882","last_updated":"2026-06-09T13:56:31Z","snapshot_observed_at":"2026-08-06T14:55:34.402749Z","submitted_at":"2026-06-09T13:56:31Z","title":"From Quality Properties to Practice: A Guideline and Workflow for Explainability Requirements","version":1},"reference_index":31,"source":"pdf_text","source_observed_at":"2026-06-27T12:25:42.492883Z"},"links":{"citing_paper":"/paper/2606.10882"},"observation_digest":"sha256:666b7c8e6585b57b45c1b9a75eda45a6c37ca9ad456bca93286884f802e84953","observation_id":"0d973c8b-aecb-42ca-9adb-8280fb24186e","resolution":{"observed_at":"2026-06-27T12:25:42.492883Z","resolver_source":null,"status":"unresolved"},"standing_notice":{"events":[],"reason":"canonical_work_link_unavailable","source_receipts":[],"state":"unavailable"}},{"citation":{"cited_paper":null,"cited_work":{"arxiv_id":null,"doi":null,"metadata_source":null,"pith_arxiv_id":null,"snapshot_observed_at":"2026-06-27T12:25:42.492883Z","title":"A model for evaluating requirements elicitation techniques in software development projects","venue":null,"work_id":null,"year":2020},"citing_paper":{"arxiv_id":"2606.10882","last_updated":"2026-06-09T13:56:31Z","snapshot_observed_at":"2026-08-06T14:55:34.402749Z","submitted_at":"2026-06-09T13:56:31Z","title":"From Quality Properties to Practice: A Guideline and Workflow for Explainability Requirements","version":1},"reference_index":32,"source":"pdf_text","source_observed_at":"2026-06-27T12:25:42.492883Z"},"links":{"citing_paper":"/paper/2606.10882"},"observation_digest":"sha256:f87510fe285846a617ad3d109df4ac239fea77aa9ac978b2d2fbc346e6b75062","observation_id":"df123214-5efb-4907-ac11-1e81e4db9d47","resolution":{"observed_at":"2026-06-27T12:25:42.492883Z","resolver_source":null,"status":"unresolved"},"standing_notice":{"events":[],"reason":"canonical_work_link_unavailable","source_receipts":[],"state":"unavailable"}},{"citation":{"cited_paper":null,"cited_work":{"arxiv_id":null,"doi":null,"metadata_source":null,"pith_arxiv_id":null,"snapshot_observed_at":"2026-06-27T12:25:42.492883Z","title":"The role of domain knowledge in requirements elicitation via interviews: an exploratory study,","venue":null,"work_id":null,"year":2014},"citing_paper":{"arxiv_id":"2606.10882","last_updated":"2026-06-09T13:56:31Z","snapshot_observed_at":"2026-08-06T14:55:34.402749Z","submitted_at":"2026-06-09T13:56:31Z","title":"From Quality Properties to Practice: A Guideline and Workflow for Explainability Requirements","version":1},"reference_index":33,"source":"pdf_text","source_observed_at":"2026-06-27T12:25:42.492883Z"},"links":{"citing_paper":"/paper/2606.10882"},"observation_digest":"sha256:3838ce69494c4b9a79d31414c207ad982914300b958f543bedc35d2cdd933c2b","observation_id":"66df6c51-be60-4fba-b954-87b5910701a3","resolution":{"observed_at":"2026-06-27T12:25:42.492883Z","resolver_source":null,"status":"unresolved"},"standing_notice":{"events":[],"reason":"canonical_work_link_unavailable","source_receipts":[],"state":"unavailable"}},{"citation":{"cited_paper":null,"cited_work":{"arxiv_id":null,"doi":null,"metadata_source":null,"pith_arxiv_id":null,"snapshot_observed_at":"2026-06-27T12:25:42.492883Z","title":"How does users’ app knowledge influence the preferred level of detail and format of software explanations?","venue":null,"work_id":null,"year":2025},"citing_paper":{"arxiv_id":"2606.10882","last_updated":"2026-06-09T13:56:31Z","snapshot_observed_at":"2026-08-06T14:55:34.402749Z","submitted_at":"2026-06-09T13:56:31Z","title":"From Quality Properties to Practice: A Guideline and Workflow for Explainability Requirements","version":1},"reference_index":34,"source":"pdf_text","source_observed_at":"2026-06-27T12:25:42.492883Z"},"links":{"citing_paper":"/paper/2606.10882"},"observation_digest":"sha256:c4f1b56791d92dfc4505bcd99017375a91244e7d7ea6438f7336cb2d88c09f96","observation_id":"5d19869e-7476-47d5-9a02-dd3e42c68463","resolution":{"observed_at":"2026-06-27T12:25:42.492883Z","resolver_source":null,"status":"unresolved"},"standing_notice":{"events":[],"reason":"canonical_work_link_unavailable","source_receipts":[],"state":"unavailable"}},{"citation":{"cited_paper":null,"cited_work":{"arxiv_id":null,"doi":null,"metadata_source":null,"pith_arxiv_id":null,"snapshot_observed_at":"2026-06-27T12:25:42.492883Z","title":"Do users’ explainability needs in software change with mood?","venue":null,"work_id":null,"year":2025},"citing_paper":{"arxiv_id":"2606.10882","last_updated":"2026-06-09T13:56:31Z","snapshot_observed_at":"2026-08-06T14:55:34.402749Z","submitted_at":"2026-06-09T13:56:31Z","title":"From Quality Properties to Practice: A Guideline and Workflow for Explainability Requirements","version":1},"reference_index":35,"source":"pdf_text","source_observed_at":"2026-06-27T12:25:42.492883Z"},"links":{"citing_paper":"/paper/2606.10882"},"observation_digest":"sha256:641df21d3ffa6d52faabc4bc69b444fbb442356c1826ebfd2f273b10c529d801","observation_id":"31d22d2a-60b5-4928-8c16-63b7b8b23fe7","resolution":{"observed_at":"2026-06-27T12:25:42.492883Z","resolver_source":null,"status":"unresolved"},"standing_notice":{"events":[],"reason":"canonical_work_link_unavailable","source_receipts":[],"state":"unavailable"}},{"citation":{"cited_paper":null,"cited_work":{"arxiv_id":null,"doi":null,"metadata_source":null,"pith_arxiv_id":null,"snapshot_observed_at":"2026-06-27T12:25:42.492883Z","title":"Automating explanation need management in app reviews: A case study from the navigation app industry,","venue":null,"work_id":null,"year":2025},"citing_paper":{"arxiv_id":"2606.10882","last_updated":"2026-06-09T13:56:31Z","snapshot_observed_at":"2026-08-06T14:55:34.402749Z","submitted_at":"2026-06-09T13:56:31Z","title":"From Quality Properties to Practice: A Guideline and Workflow for Explainability Requirements","version":1},"reference_index":36,"source":"pdf_text","source_observed_at":"2026-06-27T12:25:42.492883Z"},"links":{"citing_paper":"/paper/2606.10882"},"observation_digest":"sha256:01e41161561fdf40f41c138bdf39f5ff247562f747f88743c3283fbb52417af1","observation_id":"6b47d5b7-93b4-4459-8d3e-6e260841fcad","resolution":{"observed_at":"2026-06-27T12:25:42.492883Z","resolver_source":null,"status":"unresolved"},"standing_notice":{"events":[],"reason":"canonical_work_link_unavailable","source_receipts":[],"state":"unavailable"}},{"citation":{"cited_paper":null,"cited_work":{"arxiv_id":null,"doi":null,"metadata_source":null,"pith_arxiv_id":null,"snapshot_observed_at":"2026-06-27T12:25:42.492883Z","title":"How explainable is your system? towards a quality model for explainability,","venue":null,"work_id":null,"year":2024},"citing_paper":{"arxiv_id":"2606.10882","last_updated":"2026-06-09T13:56:31Z","snapshot_observed_at":"2026-08-06T14:55:34.402749Z","submitted_at":"2026-06-09T13:56:31Z","title":"From Quality Properties to Practice: A Guideline and Workflow for Explainability Requirements","version":1},"reference_index":37,"source":"pdf_text","source_observed_at":"2026-06-27T12:25:42.492883Z"},"links":{"citing_paper":"/paper/2606.10882"},"observation_digest":"sha256:24e7be1dd9b4b220418ead5d70cb284eaf0910c2d839e9dd58bba721d091b980","observation_id":"c0d162e6-4824-43be-85e4-6d853595b888","resolution":{"observed_at":"2026-06-27T12:25:42.492883Z","resolver_source":null,"status":"unresolved"},"standing_notice":{"events":[],"reason":"canonical_work_link_unavailable","source_receipts":[],"state":"unavailable"}},{"citation":{"cited_paper":null,"cited_work":{"arxiv_id":null,"doi":null,"metadata_source":null,"pith_arxiv_id":null,"snapshot_observed_at":"2026-06-27T12:25:42.492883Z","title":"Exploring the means to measure explainability: Metrics, heuris- tics and questionnaires,","venue":null,"work_id":null,"year":2025},"citing_paper":{"arxiv_id":"2606.10882","last_updated":"2026-06-09T13:56:31Z","snapshot_observed_at":"2026-08-06T14:55:34.402749Z","submitted_at":"2026-06-09T13:56:31Z","title":"From Quality Properties to Practice: A Guideline and Workflow for Explainability Requirements","version":1},"reference_index":38,"source":"pdf_text","source_observed_at":"2026-06-27T12:25:42.492883Z"},"links":{"citing_paper":"/paper/2606.10882"},"observation_digest":"sha256:afeb3ef49f3778d28afbfbbb73b00579cc28fd2cc89abcfd905d196e78d1a387","observation_id":"850a5abd-4499-4014-9a22-324e531ad6fd","resolution":{"observed_at":"2026-06-27T12:25:42.492883Z","resolver_source":null,"status":"unresolved"},"standing_notice":{"events":[],"reason":"canonical_work_link_unavailable","source_receipts":[],"state":"unavailable"}},{"citation":{"cited_paper":null,"cited_work":{"arxiv_id":null,"doi":null,"metadata_source":null,"pith_arxiv_id":null,"snapshot_observed_at":"2026-06-27T12:25:42.492883Z","title":"Chapter 81 experimental evidence on the existence of hypothetical bias in value elicitation methods,","venue":null,"work_id":null,"year":2008},"citing_paper":{"arxiv_id":"2606.10882","last_updated":"2026-06-09T13:56:31Z","snapshot_observed_at":"2026-08-06T14:55:34.402749Z","submitted_at":"2026-06-09T13:56:31Z","title":"From Quality Properties to Practice: A Guideline and Workflow for Explainability Requirements","version":1},"reference_index":39,"source":"pdf_text","source_observed_at":"2026-06-27T12:25:42.492883Z"},"links":{"citing_paper":"/paper/2606.10882"},"observation_digest":"sha256:ca5e8e93835ec0e0fde7eb913b8431907881647e599499f44e31b48c8681262c","observation_id":"057d842e-859b-43fb-8967-e2dd01b3c448","resolution":{"observed_at":"2026-06-27T12:25:42.492883Z","resolver_source":null,"status":"unresolved"},"standing_notice":{"events":[],"reason":"canonical_work_link_unavailable","source_receipts":[],"state":"unavailable"}},{"citation":{"cited_paper":null,"cited_work":{"arxiv_id":null,"doi":null,"metadata_source":null,"pith_arxiv_id":null,"snapshot_observed_at":"2026-06-27T12:25:42.492883Z","title":"Designing end-user personas for explainability requirements using mixed methods research,","venue":null,"work_id":null,"year":2023},"citing_paper":{"arxiv_id":"2606.10882","last_updated":"2026-06-09T13:56:31Z","snapshot_observed_at":"2026-08-06T14:55:34.402749Z","submitted_at":"2026-06-09T13:56:31Z","title":"From Quality Properties to Practice: A Guideline and Workflow for Explainability Requirements","version":1},"reference_index":40,"source":"pdf_text","source_observed_at":"2026-06-27T12:25:42.492883Z"},"links":{"citing_paper":"/paper/2606.10882"},"observation_digest":"sha256:3ee074df8c9addd31cfd66121e6ef3baa7877b094c3b808a84aa6cc24307b9da","observation_id":"8b14b42c-fb5c-4fa7-a378-85facd8a2f9e","resolution":{"observed_at":"2026-06-27T12:25:42.492883Z","resolver_source":null,"status":"unresolved"},"standing_notice":{"events":[],"reason":"canonical_work_link_unavailable","source_receipts":[],"state":"unavailable"}},{"citation":{"cited_paper":null,"cited_work":{"arxiv_id":null,"doi":null,"metadata_source":null,"pith_arxiv_id":null,"snapshot_observed_at":"2026-06-27T12:25:42.492883Z","title":"On the pulse of requirements elicitation: Physiological triggers and explainability needs,","venue":null,"work_id":null,"year":2024},"citing_paper":{"arxiv_id":"2606.10882","last_updated":"2026-06-09T13:56:31Z","snapshot_observed_at":"2026-08-06T14:55:34.402749Z","submitted_at":"2026-06-09T13:56:31Z","title":"From Quality Properties to Practice: A Guideline and Workflow for Explainability Requirements","version":1},"reference_index":41,"source":"pdf_text","source_observed_at":"2026-06-27T12:25:42.492883Z"},"links":{"citing_paper":"/paper/2606.10882"},"observation_digest":"sha256:cf2c4a0b8d5944d8e9021bc43621a0bc351ed486c6919eb5c0aa9beb98a3a12c","observation_id":"ad5ddcb8-b8db-4787-abb1-9ff9ab35cabe","resolution":{"observed_at":"2026-06-27T12:25:42.492883Z","resolver_source":null,"status":"unresolved"},"standing_notice":{"events":[],"reason":"canonical_work_link_unavailable","source_receipts":[],"state":"unavailable"}},{"citation":{"cited_paper":null,"cited_work":{"arxiv_id":null,"doi":null,"metadata_source":null,"pith_arxiv_id":null,"snapshot_observed_at":"2026-06-27T12:25:42.492883Z","title":"Requirements on explanations: A quality framework for explainability,","venue":null,"work_id":null,"year":2022},"citing_paper":{"arxiv_id":"2606.10882","last_updated":"2026-06-09T13:56:31Z","snapshot_observed_at":"2026-08-06T14:55:34.402749Z","submitted_at":"2026-06-09T13:56:31Z","title":"From Quality Properties to Practice: A Guideline and Workflow for Explainability Requirements","version":1},"reference_index":42,"source":"pdf_text","source_observed_at":"2026-06-27T12:25:42.492883Z"},"links":{"citing_paper":"/paper/2606.10882"},"observation_digest":"sha256:da38f62465560702feb0535879805cec13631d1a2a1e2218c3f776f59a4103cf","observation_id":"b30acebc-9767-4e62-9c13-69d86b7d9d5f","resolution":{"observed_at":"2026-06-27T12:25:42.492883Z","resolver_source":null,"status":"unresolved"},"standing_notice":{"events":[],"reason":"canonical_work_link_unavailable","source_receipts":[],"state":"unavailable"}},{"citation":{"cited_paper":null,"cited_work":{"arxiv_id":null,"doi":null,"metadata_source":null,"pith_arxiv_id":null,"snapshot_observed_at":"2026-06-27T12:25:42.492883Z","title":"Advancing requirements engineering through generative ai: Assessing the role of llms,","venue":null,"work_id":null,"year":2024},"citing_paper":{"arxiv_id":"2606.10882","last_updated":"2026-06-09T13:56:31Z","snapshot_observed_at":"2026-08-06T14:55:34.402749Z","submitted_at":"2026-06-09T13:56:31Z","title":"From Quality Properties to Practice: A Guideline and Workflow for Explainability Requirements","version":1},"reference_index":43,"source":"pdf_text","source_observed_at":"2026-06-27T12:25:42.492883Z"},"links":{"citing_paper":"/paper/2606.10882"},"observation_digest":"sha256:ba2958f2cc8309e1fdbe2d69009d32818eb2dff8e336ec1a5abec09ddc49c773","observation_id":"a265293f-a8e1-48b9-a9a4-6e64de00c1d7","resolution":{"observed_at":"2026-06-27T12:25:42.492883Z","resolver_source":null,"status":"unresolved"},"standing_notice":{"events":[],"reason":"canonical_work_link_unavailable","source_receipts":[],"state":"unavailable"}},{"citation":{"cited_paper":null,"cited_work":{"arxiv_id":null,"doi":null,"metadata_source":null,"pith_arxiv_id":null,"snapshot_observed_at":"2026-06-27T12:25:42.492883Z","title":"Challenges in applying large language models to requirements engineering tasks,","venue":null,"work_id":null,"year":2024},"citing_paper":{"arxiv_id":"2606.10882","last_updated":"2026-06-09T13:56:31Z","snapshot_observed_at":"2026-08-06T14:55:34.402749Z","submitted_at":"2026-06-09T13:56:31Z","title":"From Quality Properties to Practice: A Guideline and Workflow for Explainability Requirements","version":1},"reference_index":44,"source":"pdf_text","source_observed_at":"2026-06-27T12:25:42.492883Z"},"links":{"citing_paper":"/paper/2606.10882"},"observation_digest":"sha256:d537b30d44c603c6d9dcf0b7a7b8c5191c86da78602e9d9e40f9c111e0effc60","observation_id":"498d29e3-558a-45d6-9184-9d390c09da3a","resolution":{"observed_at":"2026-06-27T12:25:42.492883Z","resolver_source":null,"status":"unresolved"},"standing_notice":{"events":[],"reason":"canonical_work_link_unavailable","source_receipts":[],"state":"unavailable"}},{"citation":{"cited_paper":null,"cited_work":{"arxiv_id":null,"doi":null,"metadata_source":null,"pith_arxiv_id":null,"snapshot_observed_at":"2026-06-27T12:25:42.492883Z","title":"Unleashing the potential of prompt engineering for large language models,","venue":null,"work_id":null,"year":2025},"citing_paper":{"arxiv_id":"2606.10882","last_updated":"2026-06-09T13:56:31Z","snapshot_observed_at":"2026-08-06T14:55:34.402749Z","submitted_at":"2026-06-09T13:56:31Z","title":"From Quality Properties to Practice: A Guideline and Workflow for Explainability Requirements","version":1},"reference_index":45,"source":"pdf_text","source_observed_at":"2026-06-27T12:25:42.492883Z"},"links":{"citing_paper":"/paper/2606.10882"},"observation_digest":"sha256:470e07867568196a6da45e3af6fbae57ae5b08dcb824639b2c738ae156063757","observation_id":"d713c531-722f-4f19-bd09-8f1f45e2c118","resolution":{"observed_at":"2026-06-27T12:25:42.492883Z","resolver_source":null,"status":"unresolved"},"standing_notice":{"events":[],"reason":"canonical_work_link_unavailable","source_receipts":[],"state":"unavailable"}},{"citation":{"cited_paper":null,"cited_work":{"arxiv_id":null,"doi":null,"metadata_source":null,"pith_arxiv_id":null,"snapshot_observed_at":"2026-06-27T12:25:42.492883Z","title":"Using flow to improve com- munication of requirements in globally distributed software projects,","venue":null,"work_id":null,"year":2009},"citing_paper":{"arxiv_id":"2606.10882","last_updated":"2026-06-09T13:56:31Z","snapshot_observed_at":"2026-08-06T14:55:34.402749Z","submitted_at":"2026-06-09T13:56:31Z","title":"From Quality Properties to Practice: A Guideline and Workflow for Explainability Requirements","version":1},"reference_index":46,"source":"pdf_text","source_observed_at":"2026-06-27T12:25:42.492883Z"},"links":{"citing_paper":"/paper/2606.10882"},"observation_digest":"sha256:62eabac43bc32c9c3e45b9e43da0bc230802c4c31489e54d709ba76cd91a8d58","observation_id":"23b5b713-ac3f-4c77-b4e4-93fba269b404","resolution":{"observed_at":"2026-06-27T12:25:42.492883Z","resolver_source":null,"status":"unresolved"},"standing_notice":{"events":[],"reason":"canonical_work_link_unavailable","source_receipts":[],"state":"unavailable"}},{"citation":{"cited_paper":null,"cited_work":{"arxiv_id":null,"doi":null,"metadata_source":null,"pith_arxiv_id":null,"snapshot_observed_at":"2026-06-27T12:25:42.492883Z","title":"Wohlin, P","venue":null,"work_id":null,"year":2012},"citing_paper":{"arxiv_id":"2606.10882","last_updated":"2026-06-09T13:56:31Z","snapshot_observed_at":"2026-08-06T14:55:34.402749Z","submitted_at":"2026-06-09T13:56:31Z","title":"From Quality Properties to Practice: A Guideline and Workflow for Explainability Requirements","version":1},"reference_index":47,"source":"pdf_text","source_observed_at":"2026-06-27T12:25:42.492883Z"},"links":{"citing_paper":"/paper/2606.10882"},"observation_digest":"sha256:9bcdcd2a9fe5ec6df6f9ffd0013ce4c4d915cbd9dba3702d53fa6833369594cf","observation_id":"c0abb703-aa78-414c-9472-33dde3363bec","resolution":{"observed_at":"2026-06-27T12:25:42.492883Z","resolver_source":null,"status":"unresolved"},"standing_notice":{"events":[],"reason":"canonical_work_link_unavailable","source_receipts":[],"state":"unavailable"}},{"citation":{"cited_paper":null,"cited_work":{"arxiv_id":null,"doi":"10.5281/zenodo.20359756","metadata_source":"openalex","pith_arxiv_id":null,"snapshot_observed_at":"2026-08-05T02:28:24.338817Z","title":"Multidimensional Gold-Standard Dataset for Explanation Needs in App Reviews,","venue":"Zenodo (CERN European Organization for Nuclear Research)","work_id":"cdad6ee0-b6a7-4e07-9c3c-49db49b2fb23","year":2026},"citing_paper":{"arxiv_id":"2606.10882","last_updated":"2026-06-09T13:56:31Z","snapshot_observed_at":"2026-08-06T14:55:34.402749Z","submitted_at":"2026-06-09T13:56:31Z","title":"From Quality Properties to Practice: A Guideline and Workflow for Explainability Requirements","version":1},"reference_index":48,"source":"pdf_text","source_observed_at":"2026-06-27T12:25:42.492883Z"},"links":{"citing_paper":"/paper/2606.10882"},"observation_digest":"sha256:6f0d3a13e85b5136a99a6bcb9ef9d05f2460bdda27a8ebc9ec654a75d44f5585","observation_id":"24b49ea9-dba3-413a-950b-fe999a71511e","resolution":{"observed_at":"2026-06-27T12:30:55.436640Z","resolver_source":"doi","status":"verified_exact"},"standing_notice":{"events":[],"observation":"No event found in the named queried sources as of 2026-08-08T06:32:00.761636+00:00.","reason":null,"source_receipts":[{"observed_at":"2026-08-08T06:32:00.761636+00:00","source":"crossref"},{"observed_at":"2026-08-08T06:31:55.24221+00:00","source":"retraction_watch"}],"state":"measured"}},{"citation":{"cited_paper":null,"cited_work":{"arxiv_id":null,"doi":null,"metadata_source":null,"pith_arxiv_id":null,"snapshot_observed_at":"2026-06-27T12:25:42.492883Z","title":"Systems and software engineering — life cycle processes — requirements engineering,","venue":null,"work_id":null,"year":2018},"citing_paper":{"arxiv_id":"2606.10882","last_updated":"2026-06-09T13:56:31Z","snapshot_observed_at":"2026-08-06T14:55:34.402749Z","submitted_at":"2026-06-09T13:56:31Z","title":"From Quality Properties to Practice: A Guideline and Workflow for Explainability Requirements","version":1},"reference_index":49,"source":"pdf_text","source_observed_at":"2026-06-27T12:25:42.492883Z"},"links":{"citing_paper":"/paper/2606.10882"},"observation_digest":"sha256:7cec87de1521c26c7da80775f11fd98bcfd90b8aa118393f4b05f7ace2247d50","observation_id":"a14bf7c0-9742-4976-a90c-58eab602837f","resolution":{"observed_at":"2026-06-27T12:25:42.492883Z","resolver_source":null,"status":"unresolved"},"standing_notice":{"events":[],"reason":"canonical_work_link_unavailable","source_receipts":[],"state":"unavailable"}},{"citation":{"cited_paper":null,"cited_work":{"arxiv_id":null,"doi":null,"metadata_source":null,"pith_arxiv_id":null,"snapshot_observed_at":"2026-06-27T12:25:42.492883Z","title":"Requirements engineering und management,","venue":null,"work_id":null,"year":2009},"citing_paper":{"arxiv_id":"2606.10882","last_updated":"2026-06-09T13:56:31Z","snapshot_observed_at":"2026-08-06T14:55:34.402749Z","submitted_at":"2026-06-09T13:56:31Z","title":"From Quality Properties to Practice: A Guideline and Workflow for Explainability Requirements","version":1},"reference_index":50,"source":"pdf_text","source_observed_at":"2026-06-27T12:25:42.492883Z"},"links":{"citing_paper":"/paper/2606.10882"},"observation_digest":"sha256:22af90fee02353848606946644782cb858b6e9d9616ff513c86f7a74f36ca3e6","observation_id":"9c6a9bd3-5c73-4bd9-b5c3-faed76ff5a58","resolution":{"observed_at":"2026-06-27T12:25:42.492883Z","resolver_source":null,"status":"unresolved"},"standing_notice":{"events":[],"reason":"canonical_work_link_unavailable","source_receipts":[],"state":"unavailable"}},{"citation":{"cited_paper":null,"cited_work":{"arxiv_id":null,"doi":null,"metadata_source":null,"pith_arxiv_id":null,"snapshot_observed_at":"2026-06-27T12:25:42.492883Z","title":null,"venue":null,"work_id":null,"year":2005},"citing_paper":{"arxiv_id":"2606.10882","last_updated":"2026-06-09T13:56:31Z","snapshot_observed_at":"2026-08-06T14:55:34.402749Z","submitted_at":"2026-06-09T13:56:31Z","title":"From Quality Properties to Practice: A Guideline and Workflow for Explainability Requirements","version":1},"reference_index":51,"source":"pdf_text","source_observed_at":"2026-06-27T12:25:42.492883Z"},"links":{"citing_paper":"/paper/2606.10882"},"observation_digest":"sha256:a9eacf8277eeee8b21c876e8b977a2aaaf987e1343cb34f3ed76d5e1006e3d58","observation_id":"07c2bec7-2182-4e46-8c3c-15dcd7ca6826","resolution":{"observed_at":"2026-06-27T12:25:42.492883Z","resolver_source":null,"status":"unresolved"},"standing_notice":{"events":[],"reason":"canonical_work_link_unavailable","source_receipts":[],"state":"unavailable"}},{"citation":{"cited_paper":null,"cited_work":{"arxiv_id":null,"doi":null,"metadata_source":null,"pith_arxiv_id":null,"snapshot_observed_at":"2026-06-27T12:25:42.492883Z","title":"Empirical research on requirements quality: a systematic mapping study,","venue":null,"work_id":null,"year":2022},"citing_paper":{"arxiv_id":"2606.10882","last_updated":"2026-06-09T13:56:31Z","snapshot_observed_at":"2026-08-06T14:55:34.402749Z","submitted_at":"2026-06-09T13:56:31Z","title":"From Quality Properties to Practice: A Guideline and Workflow for Explainability Requirements","version":1},"reference_index":52,"source":"pdf_text","source_observed_at":"2026-06-27T12:25:42.492883Z"},"links":{"citing_paper":"/paper/2606.10882"},"observation_digest":"sha256:de15ad3b7bc0dfcd9e254aef77782ad60223d36d1c18540c774038031bd0279e","observation_id":"0df7db2c-700f-4554-8c5f-27de746bbf28","resolution":{"observed_at":"2026-06-27T12:25:42.492883Z","resolver_source":null,"status":"unresolved"},"standing_notice":{"events":[],"reason":"canonical_work_link_unavailable","source_receipts":[],"state":"unavailable"}},{"citation":{"cited_paper":null,"cited_work":{"arxiv_id":null,"doi":null,"metadata_source":null,"pith_arxiv_id":null,"snapshot_observed_at":"2026-06-27T12:25:42.492883Z","title":"A systematic literature review on quality criteria for agile requirements specifications,","venue":null,"work_id":null,"year":2018},"citing_paper":{"arxiv_id":"2606.10882","last_updated":"2026-06-09T13:56:31Z","snapshot_observed_at":"2026-08-06T14:55:34.402749Z","submitted_at":"2026-06-09T13:56:31Z","title":"From Quality Properties to Practice: A Guideline and Workflow for Explainability Requirements","version":1},"reference_index":53,"source":"pdf_text","source_observed_at":"2026-06-27T12:25:42.492883Z"},"links":{"citing_paper":"/paper/2606.10882"},"observation_digest":"sha256:fc34cde404401434948e69f602d413b72d0e9e5accccce9d62160ffd809632e3","observation_id":"1f0d1504-4979-4099-9fed-ef0e2f048a0c","resolution":{"observed_at":"2026-06-27T12:25:42.492883Z","resolver_source":null,"status":"unresolved"},"standing_notice":{"events":[],"reason":"canonical_work_link_unavailable","source_receipts":[],"state":"unavailable"}},{"citation":{"cited_paper":null,"cited_work":{"arxiv_id":null,"doi":null,"metadata_source":null,"pith_arxiv_id":null,"snapshot_observed_at":"2026-06-27T12:25:42.492883Z","title":"Explainable software systems: from requirements analysis to system evaluation,","venue":null,"work_id":null,"year":2022},"citing_paper":{"arxiv_id":"2606.10882","last_updated":"2026-06-09T13:56:31Z","snapshot_observed_at":"2026-08-06T14:55:34.402749Z","submitted_at":"2026-06-09T13:56:31Z","title":"From Quality Properties to Practice: A Guideline and Workflow for Explainability Requirements","version":1},"reference_index":54,"source":"pdf_text","source_observed_at":"2026-06-27T12:25:42.492883Z"},"links":{"citing_paper":"/paper/2606.10882"},"observation_digest":"sha256:f04d1cfadd02909127e96469f63d4e8c6de6fb8374853f5dfc7929431d7047d5","observation_id":"b7adc1c9-71ac-4a92-9577-9b7d04353115","resolution":{"observed_at":"2026-06-27T12:25:42.492883Z","resolver_source":null,"status":"unresolved"},"standing_notice":{"events":[],"reason":"canonical_work_link_unavailable","source_receipts":[],"state":"unavailable"}},{"citation":{"cited_paper":null,"cited_work":{"arxiv_id":null,"doi":null,"metadata_source":null,"pith_arxiv_id":null,"snapshot_observed_at":"2026-06-27T12:25:42.492883Z","title":"The impact of readability on trust in infor- mation,","venue":null,"work_id":null,"year":2021},"citing_paper":{"arxiv_id":"2606.10882","last_updated":"2026-06-09T13:56:31Z","snapshot_observed_at":"2026-08-06T14:55:34.402749Z","submitted_at":"2026-06-09T13:56:31Z","title":"From Quality Properties to Practice: A Guideline and Workflow for Explainability Requirements","version":1},"reference_index":55,"source":"pdf_text","source_observed_at":"2026-06-27T12:25:42.492883Z"},"links":{"citing_paper":"/paper/2606.10882"},"observation_digest":"sha256:942edea4ee425bc17f30f759e96cf892810ef372751cda446f4bfebbf319eef3","observation_id":"b362b76d-0b4b-449c-8cda-828478105abf","resolution":{"observed_at":"2026-06-27T12:25:42.492883Z","resolver_source":null,"status":"unresolved"},"standing_notice":{"events":[],"reason":"canonical_work_link_unavailable","source_receipts":[],"state":"unavailable"}},{"citation":{"cited_paper":null,"cited_work":{"arxiv_id":null,"doi":null,"metadata_source":null,"pith_arxiv_id":null,"snapshot_observed_at":"2026-06-27T12:25:42.492883Z","title":"What can be con- cluded from user feedback? — an empirical study,","venue":null,"work_id":null,"year":2023},"citing_paper":{"arxiv_id":"2606.10882","last_updated":"2026-06-09T13:56:31Z","snapshot_observed_at":"2026-08-06T14:55:34.402749Z","submitted_at":"2026-06-09T13:56:31Z","title":"From Quality Properties to Practice: A Guideline and Workflow for Explainability Requirements","version":1},"reference_index":56,"source":"pdf_text","source_observed_at":"2026-06-27T12:25:42.492883Z"},"links":{"citing_paper":"/paper/2606.10882"},"observation_digest":"sha256:30e6105ca6ed5b6904b38c00140cf87cc10517c74349f4f0c55a778e596e143c","observation_id":"e0f11e5e-0862-4d7e-8975-b3a3ba3b421b","resolution":{"observed_at":"2026-06-27T12:25:42.492883Z","resolver_source":null,"status":"unresolved"},"standing_notice":{"events":[],"reason":"canonical_work_link_unavailable","source_receipts":[],"state":"unavailable"}}],"paper":{"arxiv_id":"2606.10882","last_updated":"2026-06-09T13:56:31Z","latest_version":1,"primary_category":"cs.SE","snapshot_observed_at":"2026-08-06T14:55:34.402749Z","submitted_at":"2026-06-09T13:56:31Z","title":"From Quality Properties to Practice: A Guideline and Workflow for Explainability Requirements"},"reference_resolution":{"displayed":56,"state_counts":{"malformed_identifier":0,"metadata_mismatch":0,"parse_uncertain":0,"unresolved":53,"verified_exact":3,"verified_fuzzy":0},"total_outbound_references":56},"refusal":"A citation records a reference. It does not transfer a finding from one paper to another.","schema":"pith.paper-citation-record.v1","standing_sources":[{"observed_at":"2026-08-08T06:32:00.761636+00:00","source":"crossref"},{"observed_at":"2026-08-08T06:31:55.24221+00:00","source":"retraction_watch"}],"thesis":"As of 8 August 2026, this Paper Citation Record lists 56 of 56 outbound references and 0 inbound Pith citation observations for arXiv:2606.10882."}