{"as_of":"2026-08-09T19:07:00Z","caps":{"database_statements":6,"inbound":100,"outbound":100},"context_digest":"sha256:50e98bdcf8fb22195eaf2c57cd0540895f061a5c7960def16331b884abaaedbf","coverage":[{"denominator":36,"lane":"reference_resolution","note":"Typed states for the displayed outbound observations.","records_observed":36,"source":"paper_references, paper_reference_links","source_observed_at":"2026-08-06T18:05:31.906627Z","state":"measured"},{"denominator":36,"lane":"standing_notices","note":"One-hop event checks from named stored sources.","records_observed":36,"source":"scholarly_work_events, retraction_status_cache","source_observed_at":"2026-08-09T06:31:02.800959+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/2507.09220/citation-record","integrity":"/paper/2507.09220/integrity","json":"/paper/2507.09220/citation-record.json","paper":"/paper/2507.09220"},"outbound":[{"citation":{"cited_paper":null,"cited_work":{"arxiv_id":null,"doi":null,"metadata_source":"raw_reference","pith_arxiv_id":null,"snapshot_observed_at":"2026-08-06T18:05:38.974913Z","title":"From requirements to UML models and back: How automatic processing of text can support requirements engineering,","venue":null,"work_id":"87d780a4-f942-4bdc-b8a8-b383e1df5026","year":2014},"citing_paper":{"arxiv_id":"2507.09220","last_updated":"2025-07-12T09:34:39Z","snapshot_observed_at":"2026-08-06T17:58:59.423001Z","submitted_at":"2025-07-12T09:34:39Z","title":"Explainability as a Compliance Requirement: What Regulated Industries Need from AI Tools for Design Artifact Generation","version":1},"reference_index":1,"source":"pdf_text","source_observed_at":"2026-08-06T18:05:28.034105Z"},"links":{"citing_paper":"/paper/2507.09220"},"observation_digest":"sha256:f3dec50dcab0b8525652b362dc187e488bae50c4813de6db5150a8a25c005972","observation_id":"443a7443-9bd9-498b-a98a-8bea5e5473b5","resolution":{"observed_at":"2026-08-06T18:05:38.979744Z","resolver_source":"raw_fallback","status":"verified_fuzzy"},"standing_notice":{"events":[],"observation":"No event found in the named queried sources as of 2026-08-09T06:31:02.800959+00:00.","reason":null,"source_receipts":[{"observed_at":"2026-08-09T06:31:02.800959+00:00","source":"crossref"},{"observed_at":"2026-08-09T06:30:57.326959+00:00","source":"retraction_watch"}],"state":"measured"}},{"citation":{"cited_paper":null,"cited_work":{"arxiv_id":null,"doi":null,"metadata_source":"raw_reference","pith_arxiv_id":null,"snapshot_observed_at":"2026-08-06T18:05:38.776493Z","title":"Requirements Engineering: A roadmap,","venue":null,"work_id":"911b33cc-5679-460b-8132-4e95b1247bcc","year":2000},"citing_paper":{"arxiv_id":"2507.09220","last_updated":"2025-07-12T09:34:39Z","snapshot_observed_at":"2026-08-06T17:58:59.423001Z","submitted_at":"2025-07-12T09:34:39Z","title":"Explainability as a Compliance Requirement: What Regulated Industries Need from AI Tools for Design Artifact Generation","version":1},"reference_index":2,"source":"pdf_text","source_observed_at":"2026-08-06T18:05:28.182571Z"},"links":{"citing_paper":"/paper/2507.09220"},"observation_digest":"sha256:d264452a6e62b8d448d8132781bb7606028ce374dc56d2ed7910d3a97535db09","observation_id":"269823d4-206e-4f56-b31d-7dee925d86ed","resolution":{"observed_at":"2026-08-06T18:05:38.935333Z","resolver_source":"raw_fallback","status":"verified_fuzzy"},"standing_notice":{"events":[],"observation":"No event found in the named queried sources as of 2026-08-09T06:31:02.800959+00:00.","reason":null,"source_receipts":[{"observed_at":"2026-08-09T06:31:02.800959+00:00","source":"crossref"},{"observed_at":"2026-08-09T06:30:57.326959+00:00","source":"retraction_watch"}],"state":"measured"}},{"citation":{"cited_paper":null,"cited_work":{"arxiv_id":null,"doi":null,"metadata_source":"raw_reference","pith_arxiv_id":null,"snapshot_observed_at":"2026-08-06T18:05:38.662647Z","title":"Requirements traceabil- ity technologies and technology transfer decision support: A systematic review,","venue":null,"work_id":"5f643115-5934-49da-8989-0d04d72cc3c4","year":2018},"citing_paper":{"arxiv_id":"2507.09220","last_updated":"2025-07-12T09:34:39Z","snapshot_observed_at":"2026-08-06T17:58:59.423001Z","submitted_at":"2025-07-12T09:34:39Z","title":"Explainability as a Compliance Requirement: What Regulated Industries Need from AI Tools for Design Artifact Generation","version":1},"reference_index":3,"source":"pdf_text","source_observed_at":"2026-08-06T18:05:28.283394Z"},"links":{"citing_paper":"/paper/2507.09220"},"observation_digest":"sha256:e0610e5866ab4d359d71c066e338f634eb65a37f6433e4d75302291d198e0ef9","observation_id":"68a991ed-15e6-40bf-9a61-67137f3e192f","resolution":{"observed_at":"2026-08-06T18:05:38.683710Z","resolver_source":"raw_fallback","status":"verified_fuzzy"},"standing_notice":{"events":[],"observation":"No event found in the named queried sources as of 2026-08-09T06:31:02.800959+00:00.","reason":null,"source_receipts":[{"observed_at":"2026-08-09T06:31:02.800959+00:00","source":"crossref"},{"observed_at":"2026-08-09T06:30:57.326959+00:00","source":"retraction_watch"}],"state":"measured"}},{"citation":{"cited_paper":null,"cited_work":{"arxiv_id":null,"doi":null,"metadata_source":"raw_reference","pith_arxiv_id":null,"snapshot_observed_at":"2026-08-06T18:05:38.285116Z","title":"Requirements engineering in automotive development-experiences and challenges,","venue":null,"work_id":"a1fdda93-d17f-4424-9e4a-90a88aed9f2b","year":2002},"citing_paper":{"arxiv_id":"2507.09220","last_updated":"2025-07-12T09:34:39Z","snapshot_observed_at":"2026-08-06T17:58:59.423001Z","submitted_at":"2025-07-12T09:34:39Z","title":"Explainability as a Compliance Requirement: What Regulated Industries Need from AI Tools for Design Artifact Generation","version":1},"reference_index":4,"source":"pdf_text","source_observed_at":"2026-08-06T18:05:28.387325Z"},"links":{"citing_paper":"/paper/2507.09220"},"observation_digest":"sha256:8b3bd03d6e4ac4a2aa296204d8835043dd935286d4f6e11f503bb838c56569b2","observation_id":"83fdbf2f-104b-43e3-a9d3-449fe343adec","resolution":{"observed_at":"2026-08-06T18:05:38.448882Z","resolver_source":"raw_fallback","status":"verified_fuzzy"},"standing_notice":{"events":[],"observation":"No event found in the named queried sources as of 2026-08-09T06:31:02.800959+00:00.","reason":null,"source_receipts":[{"observed_at":"2026-08-09T06:31:02.800959+00:00","source":"crossref"},{"observed_at":"2026-08-09T06:30:57.326959+00:00","source":"retraction_watch"}],"state":"measured"}},{"citation":{"cited_paper":null,"cited_work":{"arxiv_id":null,"doi":null,"metadata_source":"raw_reference","pith_arxiv_id":null,"snapshot_observed_at":"2026-08-06T18:05:38.032948Z","title":"Challenges of working with artifacts in require- ments engineering and software engineering,","venue":null,"work_id":"b2eb749f-2245-43dc-ac2d-ba6644fc89a2","year":null},"citing_paper":{"arxiv_id":"2507.09220","last_updated":"2025-07-12T09:34:39Z","snapshot_observed_at":"2026-08-06T17:58:59.423001Z","submitted_at":"2025-07-12T09:34:39Z","title":"Explainability as a Compliance Requirement: What Regulated Industries Need from AI Tools for Design Artifact Generation","version":1},"reference_index":5,"source":"pdf_text","source_observed_at":"2026-08-06T18:05:28.492012Z"},"links":{"citing_paper":"/paper/2507.09220"},"observation_digest":"sha256:c1e2ff5697365cfc2f5e42a86cbe26aa4e3c00b275a55258280a2861f20ec54a","observation_id":"c172ecfd-88f3-4dab-bd18-5586227412f1","resolution":{"observed_at":"2026-08-06T18:05:38.129639Z","resolver_source":"raw_fallback","status":"verified_fuzzy"},"standing_notice":{"events":[],"observation":"No event found in the named queried sources as of 2026-08-09T06:31:02.800959+00:00.","reason":null,"source_receipts":[{"observed_at":"2026-08-09T06:31:02.800959+00:00","source":"crossref"},{"observed_at":"2026-08-09T06:30:57.326959+00:00","source":"retraction_watch"}],"state":"measured"}},{"citation":{"cited_paper":null,"cited_work":{"arxiv_id":null,"doi":null,"metadata_source":"raw_reference","pith_arxiv_id":null,"snapshot_observed_at":"2026-08-06T18:05:37.788241Z","title":"From requirements to code: A full model-driven development perspective,","venue":null,"work_id":"812563bf-a3cf-49f1-8f1a-fdbf5fc8077f","year":2011},"citing_paper":{"arxiv_id":"2507.09220","last_updated":"2025-07-12T09:34:39Z","snapshot_observed_at":"2026-08-06T17:58:59.423001Z","submitted_at":"2025-07-12T09:34:39Z","title":"Explainability as a Compliance Requirement: What Regulated Industries Need from AI Tools for Design Artifact Generation","version":1},"reference_index":6,"source":"pdf_text","source_observed_at":"2026-08-06T18:05:28.582629Z"},"links":{"citing_paper":"/paper/2507.09220"},"observation_digest":"sha256:c083449779b036a764d5a911eca0b1a183c10395dc240fea8129bd1bb5fd282e","observation_id":"09497f3c-2f9f-4886-b4f1-c68d3a30e93c","resolution":{"observed_at":"2026-08-06T18:05:37.880734Z","resolver_source":"raw_fallback","status":"verified_fuzzy"},"standing_notice":{"events":[],"observation":"No event found in the named queried sources as of 2026-08-09T06:31:02.800959+00:00.","reason":null,"source_receipts":[{"observed_at":"2026-08-09T06:31:02.800959+00:00","source":"crossref"},{"observed_at":"2026-08-09T06:30:57.326959+00:00","source":"retraction_watch"}],"state":"measured"}},{"citation":{"cited_paper":null,"cited_work":{"arxiv_id":null,"doi":null,"metadata_source":"raw_reference","pith_arxiv_id":null,"snapshot_observed_at":"2026-08-06T18:05:37.432066Z","title":"Aurum and C","venue":null,"work_id":"afaf9f99-04ae-4fd9-8183-769057d839cb","year":2005},"citing_paper":{"arxiv_id":"2507.09220","last_updated":"2025-07-12T09:34:39Z","snapshot_observed_at":"2026-08-06T17:58:59.423001Z","submitted_at":"2025-07-12T09:34:39Z","title":"Explainability as a Compliance Requirement: What Regulated Industries Need from AI Tools for Design Artifact Generation","version":1},"reference_index":7,"source":"pdf_text","source_observed_at":"2026-08-06T18:05:28.678926Z"},"links":{"citing_paper":"/paper/2507.09220"},"observation_digest":"sha256:83f530b641a2a165cca7b42a8a1781241ac4a1623f0d9b417217a5ea23eb306b","observation_id":"2b365a21-5585-49fb-85da-08fd25c67a04","resolution":{"observed_at":"2026-08-06T18:05:37.656130Z","resolver_source":"raw_fallback","status":"verified_fuzzy"},"standing_notice":{"events":[],"observation":"No event found in the named queried sources as of 2026-08-09T06:31:02.800959+00:00.","reason":null,"source_receipts":[{"observed_at":"2026-08-09T06:31:02.800959+00:00","source":"crossref"},{"observed_at":"2026-08-09T06:30:57.326959+00:00","source":"retraction_watch"}],"state":"measured"}},{"citation":{"cited_paper":null,"cited_work":{"arxiv_id":null,"doi":null,"metadata_source":"raw_reference","pith_arxiv_id":null,"snapshot_observed_at":"2026-08-06T18:05:37.101000Z","title":"An NLP approach for cross-domain ambiguity detection in requirements engineering,","venue":null,"work_id":"de7925d9-57d8-4214-a44f-0818f9978201","year":2019},"citing_paper":{"arxiv_id":"2507.09220","last_updated":"2025-07-12T09:34:39Z","snapshot_observed_at":"2026-08-06T17:58:59.423001Z","submitted_at":"2025-07-12T09:34:39Z","title":"Explainability as a Compliance Requirement: What Regulated Industries Need from AI Tools for Design Artifact Generation","version":1},"reference_index":8,"source":"pdf_text","source_observed_at":"2026-08-06T18:05:28.779617Z"},"links":{"citing_paper":"/paper/2507.09220"},"observation_digest":"sha256:0851ef8d172800292a1bf901cb0d567e74723c70cd7ad81e68f9b0eaa8bba73c","observation_id":"8a3874fd-5bf1-4d02-bc42-57d3f315a9a4","resolution":{"observed_at":"2026-08-06T18:05:37.238162Z","resolver_source":"raw_fallback","status":"verified_fuzzy"},"standing_notice":{"events":[],"observation":"No event found in the named queried sources as of 2026-08-09T06:31:02.800959+00:00.","reason":null,"source_receipts":[{"observed_at":"2026-08-09T06:31:02.800959+00:00","source":"crossref"},{"observed_at":"2026-08-09T06:30:57.326959+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-08-06T18:05:28.881794Z","title":"Software testing with large language models: Survey, landscape, and vision,","venue":null,"work_id":null,"year":2024},"citing_paper":{"arxiv_id":"2507.09220","last_updated":"2025-07-12T09:34:39Z","snapshot_observed_at":"2026-08-06T17:58:59.423001Z","submitted_at":"2025-07-12T09:34:39Z","title":"Explainability as a Compliance Requirement: What Regulated Industries Need from AI Tools for Design Artifact Generation","version":1},"reference_index":9,"source":"pdf_text","source_observed_at":"2026-08-06T18:05:28.881794Z"},"links":{"citing_paper":"/paper/2507.09220"},"observation_digest":"sha256:acd7eebbb95cb94ef57d306d685a27fb879fd3689bdd0e62fbfcb9b3c933a051","observation_id":"1c400561-cd9f-4cef-8e1a-9b94d5a84eb1","resolution":{"observed_at":"2026-08-06T18:05:28.881794Z","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":"raw_reference","pith_arxiv_id":null,"snapshot_observed_at":"2026-08-06T18:05:36.877426Z","title":"Natural language processing for requirements engineering: A systematic mapping study,","venue":null,"work_id":"500d0f9d-7006-4f44-81be-58562b478f39","year":2021},"citing_paper":{"arxiv_id":"2507.09220","last_updated":"2025-07-12T09:34:39Z","snapshot_observed_at":"2026-08-06T17:58:59.423001Z","submitted_at":"2025-07-12T09:34:39Z","title":"Explainability as a Compliance Requirement: What Regulated Industries Need from AI Tools for Design Artifact Generation","version":1},"reference_index":10,"source":"pdf_text","source_observed_at":"2026-08-06T18:05:28.947288Z"},"links":{"citing_paper":"/paper/2507.09220"},"observation_digest":"sha256:200d4d241142293efe9c94356170a66220fc742d532d1e91e445c4d3c8abe4e2","observation_id":"5f5d3300-d565-44bc-9bed-fc53efdc93ae","resolution":{"observed_at":"2026-08-06T18:05:36.993864Z","resolver_source":"raw_fallback","status":"verified_fuzzy"},"standing_notice":{"events":[],"observation":"No event found in the named queried sources as of 2026-08-09T06:31:02.800959+00:00.","reason":null,"source_receipts":[{"observed_at":"2026-08-09T06:31:02.800959+00:00","source":"crossref"},{"observed_at":"2026-08-09T06:30:57.326959+00:00","source":"retraction_watch"}],"state":"measured"}},{"citation":{"cited_paper":null,"cited_work":{"arxiv_id":null,"doi":null,"metadata_source":"raw_reference","pith_arxiv_id":null,"snapshot_observed_at":"2026-08-06T18:05:36.655902Z","title":"AI-based ques- tion answering assistance for analyzing natural-language requirements,","venue":null,"work_id":"ed8035ef-7807-4f84-9785-745c18d8a844","year":2023},"citing_paper":{"arxiv_id":"2507.09220","last_updated":"2025-07-12T09:34:39Z","snapshot_observed_at":"2026-08-06T17:58:59.423001Z","submitted_at":"2025-07-12T09:34:39Z","title":"Explainability as a Compliance Requirement: What Regulated Industries Need from AI Tools for Design Artifact Generation","version":1},"reference_index":11,"source":"pdf_text","source_observed_at":"2026-08-06T18:05:29.015359Z"},"links":{"citing_paper":"/paper/2507.09220"},"observation_digest":"sha256:8e8fe893b0700cead6c553c5c476803fd803796f8153fcee8b02e233fdcf8c43","observation_id":"11684529-a88a-4cd7-9ed0-cf892d1ec2fd","resolution":{"observed_at":"2026-08-06T18:05:36.733330Z","resolver_source":"raw_fallback","status":"verified_fuzzy"},"standing_notice":{"events":[],"observation":"No event found in the named queried sources as of 2026-08-09T06:31:02.800959+00:00.","reason":null,"source_receipts":[{"observed_at":"2026-08-09T06:31:02.800959+00:00","source":"crossref"},{"observed_at":"2026-08-09T06:30:57.326959+00:00","source":"retraction_watch"}],"state":"measured"}},{"citation":{"cited_paper":null,"cited_work":{"arxiv_id":null,"doi":null,"metadata_source":"raw_reference","pith_arxiv_id":null,"snapshot_observed_at":"2026-08-06T18:05:36.416181Z","title":"Machine learning in requirements engineering: A mapping study,","venue":null,"work_id":"56da71aa-b9aa-41ed-a3c9-9a616ed52d29","year":2021},"citing_paper":{"arxiv_id":"2507.09220","last_updated":"2025-07-12T09:34:39Z","snapshot_observed_at":"2026-08-06T17:58:59.423001Z","submitted_at":"2025-07-12T09:34:39Z","title":"Explainability as a Compliance Requirement: What Regulated Industries Need from AI Tools for Design Artifact Generation","version":1},"reference_index":12,"source":"pdf_text","source_observed_at":"2026-08-06T18:05:29.117981Z"},"links":{"citing_paper":"/paper/2507.09220"},"observation_digest":"sha256:c6247d5b11184678c68635158e90a12e84f51160b22b2eb7b45ad6bda1292924","observation_id":"a44870a1-c61f-4b19-93f2-71ed9c813409","resolution":{"observed_at":"2026-08-06T18:05:36.521761Z","resolver_source":"raw_fallback","status":"verified_fuzzy"},"standing_notice":{"events":[],"observation":"No event found in the named queried sources as of 2026-08-09T06:31:02.800959+00:00.","reason":null,"source_receipts":[{"observed_at":"2026-08-09T06:31:02.800959+00:00","source":"crossref"},{"observed_at":"2026-08-09T06:30:57.326959+00:00","source":"retraction_watch"}],"state":"measured"}},{"citation":{"cited_paper":null,"cited_work":{"arxiv_id":null,"doi":null,"metadata_source":"raw_reference","pith_arxiv_id":null,"snapshot_observed_at":"2026-08-06T18:05:36.206446Z","title":"Large language models for software engi- neering: A systematic literature review,","venue":null,"work_id":"924f92f2-ecfc-44a1-bfb8-51638d78ef01","year":2024},"citing_paper":{"arxiv_id":"2507.09220","last_updated":"2025-07-12T09:34:39Z","snapshot_observed_at":"2026-08-06T17:58:59.423001Z","submitted_at":"2025-07-12T09:34:39Z","title":"Explainability as a Compliance Requirement: What Regulated Industries Need from AI Tools for Design Artifact Generation","version":1},"reference_index":13,"source":"pdf_text","source_observed_at":"2026-08-06T18:05:29.219641Z"},"links":{"citing_paper":"/paper/2507.09220"},"observation_digest":"sha256:5f5c9e0219e81cd292c0e590e06cc7d7cdc33a614084230059e2fcb1e5526f20","observation_id":"3f09048b-2107-443c-bb33-8c165734c4c0","resolution":{"observed_at":"2026-08-06T18:05:36.293818Z","resolver_source":"raw_fallback","status":"verified_fuzzy"},"standing_notice":{"events":[],"observation":"No event found in the named queried sources as of 2026-08-09T06:31:02.800959+00:00.","reason":null,"source_receipts":[{"observed_at":"2026-08-09T06:31:02.800959+00:00","source":"crossref"},{"observed_at":"2026-08-09T06:30:57.326959+00:00","source":"retraction_watch"}],"state":"measured"}},{"citation":{"cited_paper":null,"cited_work":{"arxiv_id":null,"doi":null,"metadata_source":"raw_reference","pith_arxiv_id":null,"snapshot_observed_at":"2026-08-06T18:05:35.986563Z","title":"Exploring explainability: A definition, a model, and a knowledge catalogue,","venue":null,"work_id":"dba4c441-5e5f-4c44-9438-5737693e8742","year":2021},"citing_paper":{"arxiv_id":"2507.09220","last_updated":"2025-07-12T09:34:39Z","snapshot_observed_at":"2026-08-06T17:58:59.423001Z","submitted_at":"2025-07-12T09:34:39Z","title":"Explainability as a Compliance Requirement: What Regulated Industries Need from AI Tools for Design Artifact Generation","version":1},"reference_index":14,"source":"pdf_text","source_observed_at":"2026-08-06T18:05:29.313368Z"},"links":{"citing_paper":"/paper/2507.09220"},"observation_digest":"sha256:76497124d06811468aad1d8db8913cd391da1db8573c05de98b4d22d612bd4f9","observation_id":"879bece6-13c6-476e-890e-b2ca3a3edfb7","resolution":{"observed_at":"2026-08-06T18:05:36.073410Z","resolver_source":"raw_fallback","status":"verified_fuzzy"},"standing_notice":{"events":[],"observation":"No event found in the named queried sources as of 2026-08-09T06:31:02.800959+00:00.","reason":null,"source_receipts":[{"observed_at":"2026-08-09T06:31:02.800959+00:00","source":"crossref"},{"observed_at":"2026-08-09T06:30:57.326959+00:00","source":"retraction_watch"}],"state":"measured"}},{"citation":{"cited_paper":null,"cited_work":{"arxiv_id":null,"doi":null,"metadata_source":"raw_reference","pith_arxiv_id":null,"snapshot_observed_at":"2026-08-06T18:05:35.759516Z","title":"Explainability as a non-functional requirement: challenges and recommendations,","venue":null,"work_id":"ff9a22b0-879f-4330-9e6c-8a6568c0fce6","year":2020},"citing_paper":{"arxiv_id":"2507.09220","last_updated":"2025-07-12T09:34:39Z","snapshot_observed_at":"2026-08-06T17:58:59.423001Z","submitted_at":"2025-07-12T09:34:39Z","title":"Explainability as a Compliance Requirement: What Regulated Industries Need from AI Tools for Design Artifact Generation","version":1},"reference_index":15,"source":"pdf_text","source_observed_at":"2026-08-06T18:05:29.407600Z"},"links":{"citing_paper":"/paper/2507.09220"},"observation_digest":"sha256:2b5b6cb6c0c05960a1a4654753310061e5e644c2fdc221fe69a1504e65d1f8b6","observation_id":"78488e53-b44c-46c3-8ab7-ba1513ca8e88","resolution":{"observed_at":"2026-08-06T18:05:35.841818Z","resolver_source":"raw_fallback","status":"verified_fuzzy"},"standing_notice":{"events":[],"observation":"No event found in the named queried sources as of 2026-08-09T06:31:02.800959+00:00.","reason":null,"source_receipts":[{"observed_at":"2026-08-09T06:31:02.800959+00:00","source":"crossref"},{"observed_at":"2026-08-09T06:30:57.326959+00:00","source":"retraction_watch"}],"state":"measured"}},{"citation":{"cited_paper":null,"cited_work":{"arxiv_id":null,"doi":null,"metadata_source":"raw_reference","pith_arxiv_id":null,"snapshot_observed_at":"2026-08-06T18:05:35.545521Z","title":"On the assessment of generative ai in modeling tasks: an experience report with chatgpt and uml,","venue":null,"work_id":"36cf8c87-d08b-403b-8eae-7581fe0b56e0","year":2023},"citing_paper":{"arxiv_id":"2507.09220","last_updated":"2025-07-12T09:34:39Z","snapshot_observed_at":"2026-08-06T17:58:59.423001Z","submitted_at":"2025-07-12T09:34:39Z","title":"Explainability as a Compliance Requirement: What Regulated Industries Need from AI Tools for Design Artifact Generation","version":1},"reference_index":16,"source":"pdf_text","source_observed_at":"2026-08-06T18:05:29.475563Z"},"links":{"citing_paper":"/paper/2507.09220"},"observation_digest":"sha256:3f7a347cfc3cf0623318003b42afc7b3d0d2ef3c8604063bb643c3dc81f307e6","observation_id":"4d951a14-3ac2-4059-8d68-7d6ed8a4ec20","resolution":{"observed_at":"2026-08-06T18:05:35.647089Z","resolver_source":"raw_fallback","status":"verified_fuzzy"},"standing_notice":{"events":[],"observation":"No event found in the named queried sources as of 2026-08-09T06:31:02.800959+00:00.","reason":null,"source_receipts":[{"observed_at":"2026-08-09T06:31:02.800959+00:00","source":"crossref"},{"observed_at":"2026-08-09T06:30:57.326959+00:00","source":"retraction_watch"}],"state":"measured"}},{"citation":{"cited_paper":null,"cited_work":{"arxiv_id":null,"doi":null,"metadata_source":"raw_reference","pith_arxiv_id":null,"snapshot_observed_at":"2026-08-06T18:05:35.327108Z","title":"Automated, interactive, and traceable domain modelling empowered by artificial intelligence,","venue":null,"work_id":"5963bbb7-41b3-44b5-afc2-4b0309dfc02e","year":2022},"citing_paper":{"arxiv_id":"2507.09220","last_updated":"2025-07-12T09:34:39Z","snapshot_observed_at":"2026-08-06T17:58:59.423001Z","submitted_at":"2025-07-12T09:34:39Z","title":"Explainability as a Compliance Requirement: What Regulated Industries Need from AI Tools for Design Artifact Generation","version":1},"reference_index":17,"source":"pdf_text","source_observed_at":"2026-08-06T18:05:29.565875Z"},"links":{"citing_paper":"/paper/2507.09220"},"observation_digest":"sha256:581818f6746d84de6d12b3b51dd2a1907e21b058151b701eeae1ca8f68a850ae","observation_id":"ccd41832-d15c-462e-9c5c-7ab1a7aff368","resolution":{"observed_at":"2026-08-06T18:05:35.432298Z","resolver_source":"raw_fallback","status":"verified_fuzzy"},"standing_notice":{"events":[],"observation":"No event found in the named queried sources as of 2026-08-09T06:31:02.800959+00:00.","reason":null,"source_receipts":[{"observed_at":"2026-08-09T06:31:02.800959+00:00","source":"crossref"},{"observed_at":"2026-08-09T06:30:57.326959+00:00","source":"retraction_watch"}],"state":"measured"}},{"citation":{"cited_paper":null,"cited_work":{"arxiv_id":null,"doi":null,"metadata_source":"raw_reference","pith_arxiv_id":null,"snapshot_observed_at":"2026-08-06T18:05:35.097199Z","title":"Generating sequence diagram from natural language requirements,","venue":null,"work_id":"d58c6245-17a8-45eb-b4fd-4af3fdacc0e6","year":2021},"citing_paper":{"arxiv_id":"2507.09220","last_updated":"2025-07-12T09:34:39Z","snapshot_observed_at":"2026-08-06T17:58:59.423001Z","submitted_at":"2025-07-12T09:34:39Z","title":"Explainability as a Compliance Requirement: What Regulated Industries Need from AI Tools for Design Artifact Generation","version":1},"reference_index":18,"source":"pdf_text","source_observed_at":"2026-08-06T18:05:29.634253Z"},"links":{"citing_paper":"/paper/2507.09220"},"observation_digest":"sha256:0a8b8f8c99be5ba5cc811a5500c3c63487e19197f5892b8f2e83649952db7bf3","observation_id":"67eecb23-2f2e-494a-98a7-a6a36acfbfe3","resolution":{"observed_at":"2026-08-06T18:05:35.208810Z","resolver_source":"raw_fallback","status":"verified_fuzzy"},"standing_notice":{"events":[],"observation":"No event found in the named queried sources as of 2026-08-09T06:31:02.800959+00:00.","reason":null,"source_receipts":[{"observed_at":"2026-08-09T06:31:02.800959+00:00","source":"crossref"},{"observed_at":"2026-08-09T06:30:57.326959+00:00","source":"retraction_watch"}],"state":"measured"}},{"citation":{"cited_paper":null,"cited_work":{"arxiv_id":null,"doi":null,"metadata_source":"raw_reference","pith_arxiv_id":null,"snapshot_observed_at":"2026-08-06T18:05:34.937825Z","title":"An active learning approach for improving the accuracy of automated domain model extraction,","venue":null,"work_id":"03e240a7-3cf1-48b1-8c9a-034f56775a26","year":2019},"citing_paper":{"arxiv_id":"2507.09220","last_updated":"2025-07-12T09:34:39Z","snapshot_observed_at":"2026-08-06T17:58:59.423001Z","submitted_at":"2025-07-12T09:34:39Z","title":"Explainability as a Compliance Requirement: What Regulated Industries Need from AI Tools for Design Artifact Generation","version":1},"reference_index":19,"source":"pdf_text","source_observed_at":"2026-08-06T18:05:29.684454Z"},"links":{"citing_paper":"/paper/2507.09220"},"observation_digest":"sha256:f76f2a5a923dc3d2dec9afedd76cfb7fa90b6780dfb52fd8ad816ebe11d11e7a","observation_id":"931462a7-36fe-406a-b315-f89675efd686","resolution":{"observed_at":"2026-08-06T18:05:35.015451Z","resolver_source":"raw_fallback","status":"verified_fuzzy"},"standing_notice":{"events":[],"observation":"No event found in the named queried sources as of 2026-08-09T06:31:02.800959+00:00.","reason":null,"source_receipts":[{"observed_at":"2026-08-09T06:31:02.800959+00:00","source":"crossref"},{"observed_at":"2026-08-09T06:30:57.326959+00:00","source":"retraction_watch"}],"state":"measured"}},{"citation":{"cited_paper":null,"cited_work":{"arxiv_id":null,"doi":null,"metadata_source":"raw_reference","pith_arxiv_id":null,"snapshot_observed_at":"2026-08-06T18:05:34.724543Z","title":"Challenges in applying large language models to requirements engineering tasks,","venue":null,"work_id":"8274d940-7559-455e-a24b-a42b7727d9e5","year":2024},"citing_paper":{"arxiv_id":"2507.09220","last_updated":"2025-07-12T09:34:39Z","snapshot_observed_at":"2026-08-06T17:58:59.423001Z","submitted_at":"2025-07-12T09:34:39Z","title":"Explainability as a Compliance Requirement: What Regulated Industries Need from AI Tools for Design Artifact Generation","version":1},"reference_index":20,"source":"pdf_text","source_observed_at":"2026-08-06T18:05:29.746861Z"},"links":{"citing_paper":"/paper/2507.09220"},"observation_digest":"sha256:58db32576685e2352b2746f0c2c3e43acb335707462af9216c78c4bc8637793f","observation_id":"46d84735-a72a-4200-be4b-f31a7661e271","resolution":{"observed_at":"2026-08-06T18:05:34.786759Z","resolver_source":"raw_fallback","status":"verified_fuzzy"},"standing_notice":{"events":[],"observation":"No event found in the named queried sources as of 2026-08-09T06:31:02.800959+00:00.","reason":null,"source_receipts":[{"observed_at":"2026-08-09T06:31:02.800959+00:00","source":"crossref"},{"observed_at":"2026-08-09T06:30:57.326959+00:00","source":"retraction_watch"}],"state":"measured"}},{"citation":{"cited_paper":null,"cited_work":{"arxiv_id":null,"doi":null,"metadata_source":"raw_reference","pith_arxiv_id":null,"snapshot_observed_at":"2026-08-06T18:05:34.589366Z","title":"Detecting requirements defects with NLP patterns: An industrial experience in the railway domain,","venue":null,"work_id":"e92a6f34-dedb-462b-bbbc-3ef6a335548f","year":2018},"citing_paper":{"arxiv_id":"2507.09220","last_updated":"2025-07-12T09:34:39Z","snapshot_observed_at":"2026-08-06T17:58:59.423001Z","submitted_at":"2025-07-12T09:34:39Z","title":"Explainability as a Compliance Requirement: What Regulated Industries Need from AI Tools for Design Artifact Generation","version":1},"reference_index":21,"source":"pdf_text","source_observed_at":"2026-08-06T18:05:29.836795Z"},"links":{"citing_paper":"/paper/2507.09220"},"observation_digest":"sha256:9500412aa8096c72ef105fb999d7d212fe56b8af7f2a23d67371d0804bd60324","observation_id":"e68bbffc-61e9-4bf9-bda1-fdb2af4ddead","resolution":{"observed_at":"2026-08-06T18:05:34.655988Z","resolver_source":"raw_fallback","status":"verified_fuzzy"},"standing_notice":{"events":[],"observation":"No event found in the named queried sources as of 2026-08-09T06:31:02.800959+00:00.","reason":null,"source_receipts":[{"observed_at":"2026-08-09T06:31:02.800959+00:00","source":"crossref"},{"observed_at":"2026-08-09T06:30:57.326959+00:00","source":"retraction_watch"}],"state":"measured"}},{"citation":{"cited_paper":null,"cited_work":{"arxiv_id":null,"doi":null,"metadata_source":"raw_reference","pith_arxiv_id":null,"snapshot_observed_at":"2026-08-06T18:05:34.488376Z","title":"A systematic liter- ature review on using natural language processing in software require- ments engineering,","venue":null,"work_id":"02af1098-9a05-407b-968b-97109ec11c54","year":2024},"citing_paper":{"arxiv_id":"2507.09220","last_updated":"2025-07-12T09:34:39Z","snapshot_observed_at":"2026-08-06T17:58:59.423001Z","submitted_at":"2025-07-12T09:34:39Z","title":"Explainability as a Compliance Requirement: What Regulated Industries Need from AI Tools for Design Artifact Generation","version":1},"reference_index":22,"source":"pdf_text","source_observed_at":"2026-08-06T18:05:29.902545Z"},"links":{"citing_paper":"/paper/2507.09220"},"observation_digest":"sha256:18e841e99e1ce23bfa7e5d042c67de82641fd38f036eedd3f0f009929fc86918","observation_id":"33e62a35-b799-456f-ba65-00c96b730d4f","resolution":{"observed_at":"2026-08-06T18:05:34.524607Z","resolver_source":"raw_fallback","status":"verified_fuzzy"},"standing_notice":{"events":[],"observation":"No event found in the named queried sources as of 2026-08-09T06:31:02.800959+00:00.","reason":null,"source_receipts":[{"observed_at":"2026-08-09T06:31:02.800959+00:00","source":"crossref"},{"observed_at":"2026-08-09T06:30:57.326959+00:00","source":"retraction_watch"}],"state":"measured"}},{"citation":{"cited_paper":null,"cited_work":{"arxiv_id":null,"doi":null,"metadata_source":"raw_reference","pith_arxiv_id":null,"snapshot_observed_at":"2026-08-06T18:05:34.358620Z","title":"Practitioners’ perceptions of the goals and visual explanations of defect prediction models,","venue":null,"work_id":"2fb05721-f0bb-4c5a-889b-90d565c03e03","year":2021},"citing_paper":{"arxiv_id":"2507.09220","last_updated":"2025-07-12T09:34:39Z","snapshot_observed_at":"2026-08-06T17:58:59.423001Z","submitted_at":"2025-07-12T09:34:39Z","title":"Explainability as a Compliance Requirement: What Regulated Industries Need from AI Tools for Design Artifact Generation","version":1},"reference_index":23,"source":"pdf_text","source_observed_at":"2026-08-06T18:05:30.088785Z"},"links":{"citing_paper":"/paper/2507.09220"},"observation_digest":"sha256:e3a542516c2d011a332b2f12ab350c8f1bdee90e2b83df072d915c1eae82837d","observation_id":"a877c5f7-ba22-4030-8aea-9252c36ef03b","resolution":{"observed_at":"2026-08-06T18:05:34.427459Z","resolver_source":"raw_fallback","status":"verified_fuzzy"},"standing_notice":{"events":[],"observation":"No event found in the named queried sources as of 2026-08-09T06:31:02.800959+00:00.","reason":null,"source_receipts":[{"observed_at":"2026-08-09T06:31:02.800959+00:00","source":"crossref"},{"observed_at":"2026-08-09T06:30:57.326959+00:00","source":"retraction_watch"}],"state":"measured"}},{"citation":{"cited_paper":null,"cited_work":{"arxiv_id":null,"doi":null,"metadata_source":"raw_reference","pith_arxiv_id":null,"snapshot_observed_at":"2026-08-06T18:05:34.230706Z","title":"Transparency and explainability of AI systems: From ethical guidelines to requirements,","venue":null,"work_id":"3fad6321-77ef-44d9-9c7e-17ae7865f7ae","year":2023},"citing_paper":{"arxiv_id":"2507.09220","last_updated":"2025-07-12T09:34:39Z","snapshot_observed_at":"2026-08-06T17:58:59.423001Z","submitted_at":"2025-07-12T09:34:39Z","title":"Explainability as a Compliance Requirement: What Regulated Industries Need from AI Tools for Design Artifact Generation","version":1},"reference_index":24,"source":"pdf_text","source_observed_at":"2026-08-06T18:05:30.249031Z"},"links":{"citing_paper":"/paper/2507.09220"},"observation_digest":"sha256:0f02e0a8996d67c1d9e8b2f01a211b2ce82c2736bfc15739eebe77605b3872f2","observation_id":"f57c642a-5813-46f0-b532-008d8219e19e","resolution":{"observed_at":"2026-08-06T18:05:34.279157Z","resolver_source":"raw_fallback","status":"verified_fuzzy"},"standing_notice":{"events":[],"observation":"No event found in the named queried sources as of 2026-08-09T06:31:02.800959+00:00.","reason":null,"source_receipts":[{"observed_at":"2026-08-09T06:31:02.800959+00:00","source":"crossref"},{"observed_at":"2026-08-09T06:30:57.326959+00:00","source":"retraction_watch"}],"state":"measured"}},{"citation":{"cited_paper":null,"cited_work":{"arxiv_id":null,"doi":null,"metadata_source":"raw_reference","pith_arxiv_id":null,"snapshot_observed_at":"2026-08-06T18:05:34.109955Z","title":"Can requirements engineering support explainable artificial intelligence? towards a user-centric ap- proach for explainability requirements,","venue":null,"work_id":"639e4a6d-1661-4e41-93e9-c85ed6276c1e","year":2022},"citing_paper":{"arxiv_id":"2507.09220","last_updated":"2025-07-12T09:34:39Z","snapshot_observed_at":"2026-08-06T17:58:59.423001Z","submitted_at":"2025-07-12T09:34:39Z","title":"Explainability as a Compliance Requirement: What Regulated Industries Need from AI Tools for Design Artifact Generation","version":1},"reference_index":25,"source":"pdf_text","source_observed_at":"2026-08-06T18:05:30.372226Z"},"links":{"citing_paper":"/paper/2507.09220"},"observation_digest":"sha256:5edbeea6d9c7d5bdfc479b78f49f6d48f99db0076c528b8f362488c30872a927","observation_id":"d49f3a06-e963-423f-bfef-825b5874f45b","resolution":{"observed_at":"2026-08-06T18:05:34.162739Z","resolver_source":"raw_fallback","status":"verified_fuzzy"},"standing_notice":{"events":[],"observation":"No event found in the named queried sources as of 2026-08-09T06:31:02.800959+00:00.","reason":null,"source_receipts":[{"observed_at":"2026-08-09T06:31:02.800959+00:00","source":"crossref"},{"observed_at":"2026-08-09T06:30:57.326959+00:00","source":"retraction_watch"}],"state":"measured"}},{"citation":{"cited_paper":null,"cited_work":{"arxiv_id":null,"doi":null,"metadata_source":"raw_reference","pith_arxiv_id":null,"snapshot_observed_at":"2026-08-06T18:05:33.969621Z","title":"Explainable AI for software engineering,","venue":null,"work_id":"e567031e-a662-4b8e-bfc5-9b66a08f5d7f","year":2021},"citing_paper":{"arxiv_id":"2507.09220","last_updated":"2025-07-12T09:34:39Z","snapshot_observed_at":"2026-08-06T17:58:59.423001Z","submitted_at":"2025-07-12T09:34:39Z","title":"Explainability as a Compliance Requirement: What Regulated Industries Need from AI Tools for Design Artifact Generation","version":1},"reference_index":26,"source":"pdf_text","source_observed_at":"2026-08-06T18:05:30.534971Z"},"links":{"citing_paper":"/paper/2507.09220"},"observation_digest":"sha256:1c3ce72fbcd5b38b01a93ab963a8333aa30f243c43cc082f9d8c3c588e052808","observation_id":"d5b79dfd-06c9-421e-ba63-f11fcdc0f174","resolution":{"observed_at":"2026-08-06T18:05:34.041780Z","resolver_source":"raw_fallback","status":"verified_fuzzy"},"standing_notice":{"events":[],"observation":"No event found in the named queried sources as of 2026-08-09T06:31:02.800959+00:00.","reason":null,"source_receipts":[{"observed_at":"2026-08-09T06:31:02.800959+00:00","source":"crossref"},{"observed_at":"2026-08-09T06:30:57.326959+00:00","source":"retraction_watch"}],"state":"measured"}},{"citation":{"cited_paper":{"arxiv_id":"2406.17325","last_updated":"2024-06-25T07:18:56Z","snapshot_observed_at":"2026-07-06T18:36:34.369503Z","submitted_at":"2024-06-25T07:18:56Z","title":"AI Tool Use and Adoption in Software Development by Individuals and Organizations: A Grounded Theory Study","version":1},"cited_work":{"arxiv_id":null,"doi":null,"metadata_source":null,"pith_arxiv_id":"2406.17325","snapshot_observed_at":"2026-08-06T18:05:30.691259Z","title":"Ai tool use and adoption in software development by individuals and organizations: a grounded theory study,","venue":null,"work_id":null,"year":2024},"citing_paper":{"arxiv_id":"2507.09220","last_updated":"2025-07-12T09:34:39Z","snapshot_observed_at":"2026-08-06T17:58:59.423001Z","submitted_at":"2025-07-12T09:34:39Z","title":"Explainability as a Compliance Requirement: What Regulated Industries Need from AI Tools for Design Artifact Generation","version":1},"reference_index":27,"source":"pdf_text","source_observed_at":"2026-08-06T18:05:30.691259Z"},"links":{"cited_paper":"/paper/2406.17325","citing_paper":"/paper/2507.09220"},"observation_digest":"sha256:8a6fe8c7866d04b5140d9e0a02f4503bab34998936bb5ce36425c074f4542dde","observation_id":"5f350442-628b-431f-8455-3cfceae301ad","resolution":{"observed_at":"2026-08-06T18:05:30.691259Z","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":"raw_reference","pith_arxiv_id":null,"snapshot_observed_at":"2026-08-06T18:05:33.840369Z","title":"Navigating the complexity of generative ai adoption in software engineering,","venue":null,"work_id":"ef49630d-3ede-49d6-b432-7a10efa80045","year":2024},"citing_paper":{"arxiv_id":"2507.09220","last_updated":"2025-07-12T09:34:39Z","snapshot_observed_at":"2026-08-06T17:58:59.423001Z","submitted_at":"2025-07-12T09:34:39Z","title":"Explainability as a Compliance Requirement: What Regulated Industries Need from AI Tools for Design Artifact Generation","version":1},"reference_index":28,"source":"pdf_text","source_observed_at":"2026-08-06T18:05:30.817111Z"},"links":{"citing_paper":"/paper/2507.09220"},"observation_digest":"sha256:1aaade223dbfdda69ba429dc486bfe976e1feaa125abc5801c79ec798a2372ea","observation_id":"2a69ce4c-cc1a-4e6b-bd0d-798ad5a5c3da","resolution":{"observed_at":"2026-08-06T18:05:33.905173Z","resolver_source":"raw_fallback","status":"verified_fuzzy"},"standing_notice":{"events":[],"observation":"No event found in the named queried sources as of 2026-08-09T06:31:02.800959+00:00.","reason":null,"source_receipts":[{"observed_at":"2026-08-09T06:31:02.800959+00:00","source":"crossref"},{"observed_at":"2026-08-09T06:30:57.326959+00:00","source":"retraction_watch"}],"state":"measured"}},{"citation":{"cited_paper":null,"cited_work":{"arxiv_id":null,"doi":null,"metadata_source":"raw_reference","pith_arxiv_id":null,"snapshot_observed_at":"2026-08-06T18:05:33.724292Z","title":"Classifying ambiguous requirements: An explainable approach in the railway indus- try,","venue":null,"work_id":"a1d17c4a-2b33-45d9-8061-b37f6857d00e","year":2024},"citing_paper":{"arxiv_id":"2507.09220","last_updated":"2025-07-12T09:34:39Z","snapshot_observed_at":"2026-08-06T17:58:59.423001Z","submitted_at":"2025-07-12T09:34:39Z","title":"Explainability as a Compliance Requirement: What Regulated Industries Need from AI Tools for Design Artifact Generation","version":1},"reference_index":29,"source":"pdf_text","source_observed_at":"2026-08-06T18:05:30.952232Z"},"links":{"citing_paper":"/paper/2507.09220"},"observation_digest":"sha256:f6688039c0a3719736b84b875ae41dd8a84183d771f0d399f550740f7db1fd54","observation_id":"bcf0d15b-2338-461a-8add-f9989ab69e77","resolution":{"observed_at":"2026-08-06T18:05:33.774898Z","resolver_source":"raw_fallback","status":"verified_fuzzy"},"standing_notice":{"events":[],"observation":"No event found in the named queried sources as of 2026-08-09T06:31:02.800959+00:00.","reason":null,"source_receipts":[{"observed_at":"2026-08-09T06:31:02.800959+00:00","source":"crossref"},{"observed_at":"2026-08-09T06:30:57.326959+00:00","source":"retraction_watch"}],"state":"measured"}},{"citation":{"cited_paper":null,"cited_work":{"arxiv_id":null,"doi":null,"metadata_source":"raw_reference","pith_arxiv_id":null,"snapshot_observed_at":"2026-08-06T18:05:33.588216Z","title":"Designing NLP-based solutions for requirements variability management: Experiences from a design science study at visma,","venue":null,"work_id":"b9b276b4-6ed5-47ef-a348-98b90e8ede68","year":2024},"citing_paper":{"arxiv_id":"2507.09220","last_updated":"2025-07-12T09:34:39Z","snapshot_observed_at":"2026-08-06T17:58:59.423001Z","submitted_at":"2025-07-12T09:34:39Z","title":"Explainability as a Compliance Requirement: What Regulated Industries Need from AI Tools for Design Artifact Generation","version":1},"reference_index":30,"source":"pdf_text","source_observed_at":"2026-08-06T18:05:31.055815Z"},"links":{"citing_paper":"/paper/2507.09220"},"observation_digest":"sha256:365d91af6b7864741bb8ecd45ed6f25d5b160680f0f439a34bd420b905eb0f71","observation_id":"f25ac43e-bdd9-4c35-af08-3c4e69e00993","resolution":{"observed_at":"2026-08-06T18:05:33.656411Z","resolver_source":"raw_fallback","status":"verified_fuzzy"},"standing_notice":{"events":[],"observation":"No event found in the named queried sources as of 2026-08-09T06:31:02.800959+00:00.","reason":null,"source_receipts":[{"observed_at":"2026-08-09T06:31:02.800959+00:00","source":"crossref"},{"observed_at":"2026-08-09T06:30:57.326959+00:00","source":"retraction_watch"}],"state":"measured"}},{"citation":{"cited_paper":null,"cited_work":{"arxiv_id":null,"doi":null,"metadata_source":"raw_reference","pith_arxiv_id":null,"snapshot_observed_at":"2026-08-06T18:05:33.465717Z","title":"User stories and natural language processing: A systematic literature review,","venue":null,"work_id":"d63fa2e3-74da-48d1-b09f-a387bc631603","year":null},"citing_paper":{"arxiv_id":"2507.09220","last_updated":"2025-07-12T09:34:39Z","snapshot_observed_at":"2026-08-06T17:58:59.423001Z","submitted_at":"2025-07-12T09:34:39Z","title":"Explainability as a Compliance Requirement: What Regulated Industries Need from AI Tools for Design Artifact Generation","version":1},"reference_index":31,"source":"pdf_text","source_observed_at":"2026-08-06T18:05:31.194727Z"},"links":{"citing_paper":"/paper/2507.09220"},"observation_digest":"sha256:94a30d2df6cf3066714d2e441bb7b5a46896a7c52ddaa447ebf6d9ea9bce16a5","observation_id":"1ed51096-fdc2-45fc-8457-c9af130420cd","resolution":{"observed_at":"2026-08-06T18:05:33.518520Z","resolver_source":"raw_fallback","status":"verified_fuzzy"},"standing_notice":{"events":[],"observation":"No event found in the named queried sources as of 2026-08-09T06:31:02.800959+00:00.","reason":null,"source_receipts":[{"observed_at":"2026-08-09T06:31:02.800959+00:00","source":"crossref"},{"observed_at":"2026-08-09T06:30:57.326959+00:00","source":"retraction_watch"}],"state":"measured"}},{"citation":{"cited_paper":null,"cited_work":{"arxiv_id":null,"doi":null,"metadata_source":"raw_reference","pith_arxiv_id":null,"snapshot_observed_at":"2026-08-06T18:05:33.236376Z","title":"Applications of natural language process- ing in software traceability: A systematic mapping study,","venue":null,"work_id":"178659c0-cd86-48a3-8bf8-c4c7106f1615","year":2023},"citing_paper":{"arxiv_id":"2507.09220","last_updated":"2025-07-12T09:34:39Z","snapshot_observed_at":"2026-08-06T17:58:59.423001Z","submitted_at":"2025-07-12T09:34:39Z","title":"Explainability as a Compliance Requirement: What Regulated Industries Need from AI Tools for Design Artifact Generation","version":1},"reference_index":32,"source":"pdf_text","source_observed_at":"2026-08-06T18:05:31.334234Z"},"links":{"citing_paper":"/paper/2507.09220"},"observation_digest":"sha256:c8ffd593d68272afee00dc7beadd319f35b1b74ed057eb699e12aa8a0efcd1d8","observation_id":"403e4c7a-779d-42da-8772-d20570b3e828","resolution":{"observed_at":"2026-08-06T18:05:33.348918Z","resolver_source":"raw_fallback","status":"verified_fuzzy"},"standing_notice":{"events":[],"observation":"No event found in the named queried sources as of 2026-08-09T06:31:02.800959+00:00.","reason":null,"source_receipts":[{"observed_at":"2026-08-09T06:31:02.800959+00:00","source":"crossref"},{"observed_at":"2026-08-09T06:30:57.326959+00:00","source":"retraction_watch"}],"state":"measured"}},{"citation":{"cited_paper":null,"cited_work":{"arxiv_id":null,"doi":null,"metadata_source":"raw_reference","pith_arxiv_id":null,"snapshot_observed_at":"2026-08-06T18:05:32.986903Z","title":"The use of nlp-based text representation techniques to support requirement engineering tasks: A systematic mapping review,","venue":null,"work_id":"e9419abd-1050-4d16-86da-7e20d24003c2","year":2022},"citing_paper":{"arxiv_id":"2507.09220","last_updated":"2025-07-12T09:34:39Z","snapshot_observed_at":"2026-08-06T17:58:59.423001Z","submitted_at":"2025-07-12T09:34:39Z","title":"Explainability as a Compliance Requirement: What Regulated Industries Need from AI Tools for Design Artifact Generation","version":1},"reference_index":33,"source":"pdf_text","source_observed_at":"2026-08-06T18:05:31.510951Z"},"links":{"citing_paper":"/paper/2507.09220"},"observation_digest":"sha256:92eef92d17b4917042ddc4b1eb7f5042dcdd9eec9744a8c599c9d03482a31dbb","observation_id":"7b864bfa-85df-4f6f-ba0c-895afd5ffeb4","resolution":{"observed_at":"2026-08-06T18:05:33.108705Z","resolver_source":"raw_fallback","status":"verified_fuzzy"},"standing_notice":{"events":[],"observation":"No event found in the named queried sources as of 2026-08-09T06:31:02.800959+00:00.","reason":null,"source_receipts":[{"observed_at":"2026-08-09T06:31:02.800959+00:00","source":"crossref"},{"observed_at":"2026-08-09T06:30:57.326959+00:00","source":"retraction_watch"}],"state":"measured"}},{"citation":{"cited_paper":null,"cited_work":{"arxiv_id":null,"doi":null,"metadata_source":"raw_reference","pith_arxiv_id":null,"snapshot_observed_at":"2026-08-06T18:05:32.698639Z","title":"Convenience sampling, random sampling, and snowball sampling: How does sampling affect the validity of research?","venue":null,"work_id":"01194ce0-4a94-4393-9c03-39c22042a86a","year":2015},"citing_paper":{"arxiv_id":"2507.09220","last_updated":"2025-07-12T09:34:39Z","snapshot_observed_at":"2026-08-06T17:58:59.423001Z","submitted_at":"2025-07-12T09:34:39Z","title":"Explainability as a Compliance Requirement: What Regulated Industries Need from AI Tools for Design Artifact Generation","version":1},"reference_index":34,"source":"pdf_text","source_observed_at":"2026-08-06T18:05:31.631412Z"},"links":{"citing_paper":"/paper/2507.09220"},"observation_digest":"sha256:84ee0e798f779fd2b67feb184dcb80fe0b5896f504d5a90fd953293639412f31","observation_id":"8b62761d-8c2b-4888-85f1-35b15ebcc167","resolution":{"observed_at":"2026-08-06T18:05:32.851100Z","resolver_source":"raw_fallback","status":"verified_fuzzy"},"standing_notice":{"events":[],"observation":"No event found in the named queried sources as of 2026-08-09T06:31:02.800959+00:00.","reason":null,"source_receipts":[{"observed_at":"2026-08-09T06:31:02.800959+00:00","source":"crossref"},{"observed_at":"2026-08-09T06:30:57.326959+00:00","source":"retraction_watch"}],"state":"measured"}},{"citation":{"cited_paper":null,"cited_work":{"arxiv_id":null,"doi":null,"metadata_source":"raw_reference","pith_arxiv_id":null,"snapshot_observed_at":"2026-08-06T18:05:32.386736Z","title":"Charmaz, Constructing grounded theory: A practical guide through qualitative analysis","venue":null,"work_id":"d828df55-68a9-4035-9389-a9168ad04a10","year":2006},"citing_paper":{"arxiv_id":"2507.09220","last_updated":"2025-07-12T09:34:39Z","snapshot_observed_at":"2026-08-06T17:58:59.423001Z","submitted_at":"2025-07-12T09:34:39Z","title":"Explainability as a Compliance Requirement: What Regulated Industries Need from AI Tools for Design Artifact Generation","version":1},"reference_index":35,"source":"pdf_text","source_observed_at":"2026-08-06T18:05:31.752969Z"},"links":{"citing_paper":"/paper/2507.09220"},"observation_digest":"sha256:db5cccb22bb00615c74af11c3a6e0e3f10a1948856d64c5668e7db7b9d7a8813","observation_id":"66ffcf5d-4231-4f21-b6e7-c81785fed6a7","resolution":{"observed_at":"2026-08-06T18:05:32.553780Z","resolver_source":"raw_fallback","status":"verified_fuzzy"},"standing_notice":{"events":[],"observation":"No event found in the named queried sources as of 2026-08-09T06:31:02.800959+00:00.","reason":null,"source_receipts":[{"observed_at":"2026-08-09T06:31:02.800959+00:00","source":"crossref"},{"observed_at":"2026-08-09T06:30:57.326959+00:00","source":"retraction_watch"}],"state":"measured"}},{"citation":{"cited_paper":null,"cited_work":{"arxiv_id":null,"doi":null,"metadata_source":"raw_reference","pith_arxiv_id":null,"snapshot_observed_at":"2026-08-06T18:05:32.102444Z","title":null,"venue":null,"work_id":"060cfd86-a94e-49dd-a76a-b5b86399c121","year":1985},"citing_paper":{"arxiv_id":"2507.09220","last_updated":"2025-07-12T09:34:39Z","snapshot_observed_at":"2026-08-06T17:58:59.423001Z","submitted_at":"2025-07-12T09:34:39Z","title":"Explainability as a Compliance Requirement: What Regulated Industries Need from AI Tools for Design Artifact Generation","version":1},"reference_index":36,"source":"pdf_text","source_observed_at":"2026-08-06T18:05:31.906627Z"},"links":{"citing_paper":"/paper/2507.09220"},"observation_digest":"sha256:add47461dbf84a7688bd3a5862a99d998ab53d0f2cf88d56a8ed30ffdd0467d7","observation_id":"994df5ac-b62e-45e1-94db-5e63e8ec30f5","resolution":{"observed_at":"2026-08-06T18:05:32.199963Z","resolver_source":"raw_fallback","status":"unresolved"},"standing_notice":{"events":[],"observation":"No event found in the named queried sources as of 2026-08-09T06:31:02.800959+00:00.","reason":null,"source_receipts":[{"observed_at":"2026-08-09T06:31:02.800959+00:00","source":"crossref"},{"observed_at":"2026-08-09T06:30:57.326959+00:00","source":"retraction_watch"}],"state":"measured"}}],"paper":{"arxiv_id":"2507.09220","last_updated":"2025-07-12T09:34:39Z","latest_version":1,"primary_category":"cs.SE","snapshot_observed_at":"2026-08-06T17:58:59.423001Z","submitted_at":"2025-07-12T09:34:39Z","title":"Explainability as a Compliance Requirement: What Regulated Industries Need from AI Tools for Design Artifact Generation"},"reference_resolution":{"displayed":36,"state_counts":{"malformed_identifier":0,"metadata_mismatch":0,"parse_uncertain":0,"unresolved":3,"verified_exact":0,"verified_fuzzy":33},"total_outbound_references":36},"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-09T06:31:02.800959+00:00","source":"crossref"},{"observed_at":"2026-08-09T06:30:57.326959+00:00","source":"retraction_watch"}],"thesis":"As of 9 August 2026, this Paper Citation Record lists 36 of 36 outbound references and 0 inbound Pith citation observations for arXiv:2507.09220."}