{"as_of":"2026-08-22T06:21:00Z","caps":{"database_statements":6,"inbound":100,"outbound":100},"context_digest":"sha256:7c2c2539304361d3358be93a852bfdc0cb7d40919c7acbf9e0b8a3b8d4d4de46","coverage":[{"denominator":48,"lane":"reference_resolution","note":"Typed states for the displayed outbound observations.","records_observed":48,"source":"paper_references, paper_reference_links","source_observed_at":"2026-08-16T12:34:09.891729Z","state":"measured"},{"denominator":49,"lane":"standing_notices","note":"One-hop event checks from named stored sources.","records_observed":49,"source":"scholarly_work_events, retraction_status_cache","source_observed_at":"2026-08-21T06:32:19.484+00:00","state":"measured"},{"denominator":1,"lane":"inbound_itemization","note":"Pith citing papers itemized under the disclosed page cap.","records_observed":1,"source":"paper_references, paper_reference_links","source_observed_at":"2026-05-07T10:53:42.376564Z","state":"measured"},{"denominator":1,"lane":"external_citation_measurements","note":"A source-named dated measurement, never combined with another source.","records_observed":0,"source":"arxiv_reference","source_observed_at":"2026-05-12T09:26:26.181844Z","state":"measured"}],"external_citation_measurements":[],"inbound":[{"citation":{"cited_paper":{"arxiv_id":"2504.12517","last_updated":"2025-04-23T15:58:21Z","snapshot_observed_at":"2026-08-16T12:27:29.828080Z","submitted_at":"2025-04-16T22:30:54Z","title":"Code Improvement Practices at Meta","version":2},"cited_work":{"arxiv_id":"2504.12517","doi":null,"metadata_source":"arxiv_reference","pith_arxiv_id":"2504.12517","snapshot_observed_at":"2026-06-05T21:23:00.469572Z","title":"Code improvement practices at meta","venue":null,"work_id":"c3616ccb-f246-4e74-8ea3-09266a0f433b","year":2025},"citing_paper":{"arxiv_id":"2604.26667","last_updated":"2026-04-29T13:30:17Z","snapshot_observed_at":"2026-08-13T11:15:52.185023Z","submitted_at":"2026-04-29T13:30:17Z","title":"Will It Break in Production? Metric-Driven Prediction of Residual Defects in Python Systems","version":1},"reference_index":46,"source":"pdf_text","source_observed_at":"2026-05-07T10:53:42.376564Z"},"links":{"cited_paper":"/paper/2504.12517","citing_paper":"/paper/2604.26667"},"observation_digest":"sha256:9476369ef56973aeab082153c02dc032e65ae7c74b8184db4cefaec6dfbf0dcd","observation_id":"f6eed82f-6277-464b-8916-bf47a4fd4541","resolution":{"observed_at":"2026-05-12T09:26:26.183759Z","resolver_source":"arxiv_id","status":"verified_exact"},"standing_notice":{"events":[],"observation":"No event found in the named queried sources as of 2026-08-21T06:32:19.484+00:00.","reason":null,"source_receipts":[{"observed_at":"2026-08-21T06:32:19.484+00:00","source":"crossref"},{"observed_at":"2026-08-21T06:32:16.066871+00:00","source":"retraction_watch"}],"state":"measured"}}],"links":{"evidence":"/evidence","html":"/paper/2504.12517/citation-record","integrity":"/paper/2504.12517/integrity","json":"/paper/2504.12517/citation-record.json","paper":"/paper/2504.12517"},"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-16T12:34:10.512517Z","title":"Does code decay? assessing the evidence from change management data,","venue":null,"work_id":"0de162ed-1c95-41e5-8486-99524d8e8faf","year":2001},"citing_paper":{"arxiv_id":"2504.12517","last_updated":"2025-04-23T15:58:21Z","snapshot_observed_at":"2026-08-16T12:27:29.828080Z","submitted_at":"2025-04-16T22:30:54Z","title":"Code Improvement Practices at Meta","version":2},"reference_index":1,"source":"pdf_text","source_observed_at":"2026-08-16T12:34:09.712759Z"},"links":{"citing_paper":"/paper/2504.12517"},"observation_digest":"sha256:9a6063e8ea2842bb015168766256b4953d68c7e0040ff0208ad8fe9742b282fb","observation_id":"de13fbe3-8613-4658-a2ba-2c2c0d0d8c8a","resolution":{"observed_at":"2026-08-16T12:34:10.517547Z","resolver_source":"raw_fallback","status":"verified_fuzzy"},"standing_notice":{"events":[],"observation":"No event found in the named queried sources as of 2026-08-21T06:32:19.484+00:00.","reason":null,"source_receipts":[{"observed_at":"2026-08-21T06:32:19.484+00:00","source":"crossref"},{"observed_at":"2026-08-21T06:32:16.066871+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-16T12:34:09.717277Z","title":"An exploration of technical debt,","venue":null,"work_id":null,"year":2013},"citing_paper":{"arxiv_id":"2504.12517","last_updated":"2025-04-23T15:58:21Z","snapshot_observed_at":"2026-08-16T12:27:29.828080Z","submitted_at":"2025-04-16T22:30:54Z","title":"Code Improvement Practices at Meta","version":2},"reference_index":2,"source":"pdf_text","source_observed_at":"2026-08-16T12:34:09.717277Z"},"links":{"citing_paper":"/paper/2504.12517"},"observation_digest":"sha256:e4565647dd5f2712cc05882aaee6e15d59b80a75059f2a2dc32b782d92c970c9","observation_id":"28a3fbe2-3ed4-4a9e-972c-898e1f4ca3c3","resolution":{"observed_at":"2026-08-16T12:34:09.717277Z","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-16T12:34:10.488041Z","title":"Formulation and preliminary test of an empirical theory of coordination in software engineering,","venue":null,"work_id":"3f1dc0cb-4877-408e-ad7b-2a195ae7f371","year":2003},"citing_paper":{"arxiv_id":"2504.12517","last_updated":"2025-04-23T15:58:21Z","snapshot_observed_at":"2026-08-16T12:27:29.828080Z","submitted_at":"2025-04-16T22:30:54Z","title":"Code Improvement Practices at Meta","version":2},"reference_index":3,"source":"pdf_text","source_observed_at":"2026-08-16T12:34:09.721076Z"},"links":{"citing_paper":"/paper/2504.12517"},"observation_digest":"sha256:644757aaea732958112f9e7837ed83e572e1e92f554981e48ef281ebc7884b7f","observation_id":"d8dec32d-1e48-49b8-91f1-8152034db4d7","resolution":{"observed_at":"2026-08-16T12:34:10.493133Z","resolver_source":"raw_fallback","status":"verified_fuzzy"},"standing_notice":{"events":[],"observation":"No event found in the named queried sources as of 2026-08-21T06:32:19.484+00:00.","reason":null,"source_receipts":[{"observed_at":"2026-08-21T06:32:19.484+00:00","source":"crossref"},{"observed_at":"2026-08-21T06:32:16.066871+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-16T12:34:09.724618Z","title":"Continuous software engineering and beyond: trends and challenges,","venue":null,"work_id":null,"year":2014},"citing_paper":{"arxiv_id":"2504.12517","last_updated":"2025-04-23T15:58:21Z","snapshot_observed_at":"2026-08-16T12:27:29.828080Z","submitted_at":"2025-04-16T22:30:54Z","title":"Code Improvement Practices at Meta","version":2},"reference_index":4,"source":"pdf_text","source_observed_at":"2026-08-16T12:34:09.724618Z"},"links":{"citing_paper":"/paper/2504.12517"},"observation_digest":"sha256:846115ca7aac23d054702ce81f1772b20530dbc57e009d22221af2d3d7f2f65c","observation_id":"1009bfd8-116e-4979-bfdc-54bcf4d1e8bf","resolution":{"observed_at":"2026-08-16T12:34:09.724618Z","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-16T12:34:10.462125Z","title":"Taplin, Move fast and break things: How Facebook, Google, and Amazon have cornered culture and what it means for all of us","venue":null,"work_id":"f27a147b-18cd-4bed-9ed8-042731bc7c38","year":2017},"citing_paper":{"arxiv_id":"2504.12517","last_updated":"2025-04-23T15:58:21Z","snapshot_observed_at":"2026-08-16T12:27:29.828080Z","submitted_at":"2025-04-16T22:30:54Z","title":"Code Improvement Practices at Meta","version":2},"reference_index":5,"source":"pdf_text","source_observed_at":"2026-08-16T12:34:09.728405Z"},"links":{"citing_paper":"/paper/2504.12517"},"observation_digest":"sha256:658ca231dcb3368e334fcdd995345093fd8b1f9eb7b4a78e93e6f4135a18c6fa","observation_id":"b0bd9e5e-c10f-4043-8517-67fbc0a8182d","resolution":{"observed_at":"2026-08-16T12:34:10.467684Z","resolver_source":"raw_fallback","status":"verified_fuzzy"},"standing_notice":{"events":[],"observation":"No event found in the named queried sources as of 2026-08-21T06:32:19.484+00:00.","reason":null,"source_receipts":[{"observed_at":"2026-08-21T06:32:19.484+00:00","source":"crossref"},{"observed_at":"2026-08-21T06:32:16.066871+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-16T12:34:10.447310Z","title":"Refactoring for changeability: A way to go?","venue":null,"work_id":"39c44c49-fffd-4ec5-bfdd-e4317390e916","year":2005},"citing_paper":{"arxiv_id":"2504.12517","last_updated":"2025-04-23T15:58:21Z","snapshot_observed_at":"2026-08-16T12:27:29.828080Z","submitted_at":"2025-04-16T22:30:54Z","title":"Code Improvement Practices at Meta","version":2},"reference_index":6,"source":"pdf_text","source_observed_at":"2026-08-16T12:34:09.732501Z"},"links":{"citing_paper":"/paper/2504.12517"},"observation_digest":"sha256:635dcad57a0ba7753a74cc8549dc63df619ce1ba91d8b5596a20df5c7715409e","observation_id":"d43eec21-0d2f-404f-828c-d83d3488e6df","resolution":{"observed_at":"2026-08-16T12:34:10.451975Z","resolver_source":"raw_fallback","status":"verified_fuzzy"},"standing_notice":{"events":[],"observation":"No event found in the named queried sources as of 2026-08-21T06:32:19.484+00:00.","reason":null,"source_receipts":[{"observed_at":"2026-08-21T06:32:19.484+00:00","source":"crossref"},{"observed_at":"2026-08-21T06:32:16.066871+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-16T12:34:10.427285Z","title":"A case study on the impact of refactoring on quality and productivity in an agile team,","venue":null,"work_id":"2783282b-8bd5-4f4a-9a32-b9d7fda56d88","year":2007},"citing_paper":{"arxiv_id":"2504.12517","last_updated":"2025-04-23T15:58:21Z","snapshot_observed_at":"2026-08-16T12:27:29.828080Z","submitted_at":"2025-04-16T22:30:54Z","title":"Code Improvement Practices at Meta","version":2},"reference_index":7,"source":"pdf_text","source_observed_at":"2026-08-16T12:34:09.736402Z"},"links":{"citing_paper":"/paper/2504.12517"},"observation_digest":"sha256:faf6d571c54d785a8bfff7e581cd666ed06ebec0d07ffaaa47bee2f10004659b","observation_id":"768f16f2-fc1d-4305-80fc-63cee63e2511","resolution":{"observed_at":"2026-08-16T12:34:10.431597Z","resolver_source":"raw_fallback","status":"verified_fuzzy"},"standing_notice":{"events":[],"observation":"No event found in the named queried sources as of 2026-08-21T06:32:19.484+00:00.","reason":null,"source_receipts":[{"observed_at":"2026-08-21T06:32:19.484+00:00","source":"crossref"},{"observed_at":"2026-08-21T06:32:16.066871+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-16T12:34:10.414273Z","title":"A field study of refactoring challenges and benefits,","venue":null,"work_id":"bd38fd98-1a3f-40d1-b05c-bc7a79f43149","year":2012},"citing_paper":{"arxiv_id":"2504.12517","last_updated":"2025-04-23T15:58:21Z","snapshot_observed_at":"2026-08-16T12:27:29.828080Z","submitted_at":"2025-04-16T22:30:54Z","title":"Code Improvement Practices at Meta","version":2},"reference_index":8,"source":"pdf_text","source_observed_at":"2026-08-16T12:34:09.739879Z"},"links":{"citing_paper":"/paper/2504.12517"},"observation_digest":"sha256:0ab04eadd6fde483dd13414b1458d8665a372ea250f4c32db822872309a953d1","observation_id":"c3b37a51-62f4-46e2-a683-2c299cb738b4","resolution":{"observed_at":"2026-08-16T12:34:10.418959Z","resolver_source":"raw_fallback","status":"verified_fuzzy"},"standing_notice":{"events":[],"observation":"No event found in the named queried sources as of 2026-08-21T06:32:19.484+00:00.","reason":null,"source_receipts":[{"observed_at":"2026-08-21T06:32:19.484+00:00","source":"crossref"},{"observed_at":"2026-08-21T06:32:16.066871+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-16T12:34:10.401477Z","title":"Quantifying and mitigating turnover-induced knowledge loss: case studies of chrome and a project at avaya,","venue":null,"work_id":"04a4a5cf-762d-4bdc-826d-d170f284fc8f","year":2016},"citing_paper":{"arxiv_id":"2504.12517","last_updated":"2025-04-23T15:58:21Z","snapshot_observed_at":"2026-08-16T12:27:29.828080Z","submitted_at":"2025-04-16T22:30:54Z","title":"Code Improvement Practices at Meta","version":2},"reference_index":9,"source":"pdf_text","source_observed_at":"2026-08-16T12:34:09.743434Z"},"links":{"citing_paper":"/paper/2504.12517"},"observation_digest":"sha256:faa4cd5c546ae508ef4b74fabb6f14c3a4060d6b472bf5e4d005bab478fbd15d","observation_id":"8c9c001e-e355-4b6a-83be-d6445dc2ed72","resolution":{"observed_at":"2026-08-16T12:34:10.405887Z","resolver_source":"raw_fallback","status":"verified_fuzzy"},"standing_notice":{"events":[],"observation":"No event found in the named queried sources as of 2026-08-21T06:32:19.484+00:00.","reason":null,"source_receipts":[{"observed_at":"2026-08-21T06:32:19.484+00:00","source":"crossref"},{"observed_at":"2026-08-21T06:32:16.066871+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-16T12:34:10.389630Z","title":"Fowler, Refactoring","venue":null,"work_id":"45cfc47f-10c2-4dba-905d-c1df1befb7be","year":2018},"citing_paper":{"arxiv_id":"2504.12517","last_updated":"2025-04-23T15:58:21Z","snapshot_observed_at":"2026-08-16T12:27:29.828080Z","submitted_at":"2025-04-16T22:30:54Z","title":"Code Improvement Practices at Meta","version":2},"reference_index":10,"source":"pdf_text","source_observed_at":"2026-08-16T12:34:09.746781Z"},"links":{"citing_paper":"/paper/2504.12517"},"observation_digest":"sha256:08127da6fbe370b27d3984acf38adddcd70a6b7993a1df424757bc8a3f7edffb","observation_id":"e6bd56eb-f624-4126-bea2-ab721ea9d6cd","resolution":{"observed_at":"2026-08-16T12:34:10.393463Z","resolver_source":"raw_fallback","status":"verified_fuzzy"},"standing_notice":{"events":[],"observation":"No event found in the named queried sources as of 2026-08-21T06:32:19.484+00:00.","reason":null,"source_receipts":[{"observed_at":"2026-08-21T06:32:19.484+00:00","source":"crossref"},{"observed_at":"2026-08-21T06:32:16.066871+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-16T12:34:09.750310Z","title":"When does a refactoring induce bugs? an empirical study,","venue":null,"work_id":null,"year":2012},"citing_paper":{"arxiv_id":"2504.12517","last_updated":"2025-04-23T15:58:21Z","snapshot_observed_at":"2026-08-16T12:27:29.828080Z","submitted_at":"2025-04-16T22:30:54Z","title":"Code Improvement Practices at Meta","version":2},"reference_index":11,"source":"pdf_text","source_observed_at":"2026-08-16T12:34:09.750310Z"},"links":{"citing_paper":"/paper/2504.12517"},"observation_digest":"sha256:89633fe466da906e064f484e62ae3a335837e6e9f59fc352d8db7ed767231c26","observation_id":"b186fbbb-62c2-4fe1-8aff-63cab3edb0cf","resolution":{"observed_at":"2026-08-16T12:34:09.750310Z","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-16T12:34:10.369040Z","title":"Empirical evaluation of the impact of object- oriented code refactoring on quality attributes: A systematic literature review,","venue":null,"work_id":"8c4872f6-3cd1-45c8-8a4f-e81c474b67e7","year":2017},"citing_paper":{"arxiv_id":"2504.12517","last_updated":"2025-04-23T15:58:21Z","snapshot_observed_at":"2026-08-16T12:27:29.828080Z","submitted_at":"2025-04-16T22:30:54Z","title":"Code Improvement Practices at Meta","version":2},"reference_index":12,"source":"pdf_text","source_observed_at":"2026-08-16T12:34:09.753780Z"},"links":{"citing_paper":"/paper/2504.12517"},"observation_digest":"sha256:242bf06642a7b6bdac9bcf5081d87e8344d92407fd05ded2698e5b740d2b5047","observation_id":"cd706060-d2c0-462b-adfe-98da4f17baa5","resolution":{"observed_at":"2026-08-16T12:34:10.373317Z","resolver_source":"raw_fallback","status":"verified_fuzzy"},"standing_notice":{"events":[],"observation":"No event found in the named queried sources as of 2026-08-21T06:32:19.484+00:00.","reason":null,"source_receipts":[{"observed_at":"2026-08-21T06:32:19.484+00:00","source":"crossref"},{"observed_at":"2026-08-21T06:32:16.066871+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-16T12:34:09.757275Z","title":"Quantifying the effect of code smells on maintenance effort,","venue":null,"work_id":null,"year":2012},"citing_paper":{"arxiv_id":"2504.12517","last_updated":"2025-04-23T15:58:21Z","snapshot_observed_at":"2026-08-16T12:27:29.828080Z","submitted_at":"2025-04-16T22:30:54Z","title":"Code Improvement Practices at Meta","version":2},"reference_index":13,"source":"pdf_text","source_observed_at":"2026-08-16T12:34:09.757275Z"},"links":{"citing_paper":"/paper/2504.12517"},"observation_digest":"sha256:d7aa5138c6fef1ea08510e89516ce0ddb6c17055acf40e46cf0b4e8f6dbd58e3","observation_id":"9cee16c6-df9e-4966-8357-ece86996ef2c","resolution":{"observed_at":"2026-08-16T12:34:09.757275Z","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-16T12:34:10.346882Z","title":"Why we refactor? confessions of github contributors,","venue":null,"work_id":"5d96892f-cd25-4658-ae59-14ef183bc088","year":2016},"citing_paper":{"arxiv_id":"2504.12517","last_updated":"2025-04-23T15:58:21Z","snapshot_observed_at":"2026-08-16T12:27:29.828080Z","submitted_at":"2025-04-16T22:30:54Z","title":"Code Improvement Practices at Meta","version":2},"reference_index":14,"source":"pdf_text","source_observed_at":"2026-08-16T12:34:09.760989Z"},"links":{"citing_paper":"/paper/2504.12517"},"observation_digest":"sha256:61bda4b8fea2d7ab84a53ae3b4010fc73f71516dda24ffd0c7d2b0b6f2b6623f","observation_id":"0e088acd-34c2-4be1-9a88-eaa45237d404","resolution":{"observed_at":"2026-08-16T12:34:10.350868Z","resolver_source":"raw_fallback","status":"verified_fuzzy"},"standing_notice":{"events":[],"observation":"No event found in the named queried sources as of 2026-08-21T06:32:19.484+00:00.","reason":null,"source_receipts":[{"observed_at":"2026-08-21T06:32:19.484+00:00","source":"crossref"},{"observed_at":"2026-08-21T06:32:16.066871+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-16T12:34:10.334502Z","title":"Why developers refactor source code: A mining-based study,","venue":null,"work_id":"5c9bcad9-2cd8-4225-9760-63acdbcd77bd","year":2020},"citing_paper":{"arxiv_id":"2504.12517","last_updated":"2025-04-23T15:58:21Z","snapshot_observed_at":"2026-08-16T12:27:29.828080Z","submitted_at":"2025-04-16T22:30:54Z","title":"Code Improvement Practices at Meta","version":2},"reference_index":15,"source":"pdf_text","source_observed_at":"2026-08-16T12:34:09.764203Z"},"links":{"citing_paper":"/paper/2504.12517"},"observation_digest":"sha256:de05fdde9c80fdcb427236dcf941c45d7775de14473d6357f2ca1c36c4161dc1","observation_id":"bd05e3b3-6a37-4b9b-b472-239cdff1c60d","resolution":{"observed_at":"2026-08-16T12:34:10.339137Z","resolver_source":"raw_fallback","status":"verified_fuzzy"},"standing_notice":{"events":[],"observation":"No event found in the named queried sources as of 2026-08-21T06:32:19.484+00:00.","reason":null,"source_receipts":[{"observed_at":"2026-08-21T06:32:19.484+00:00","source":"crossref"},{"observed_at":"2026-08-21T06:32:16.066871+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-16T12:34:10.319660Z","title":"Six strategies for generalizing software engineering theories,","venue":null,"work_id":"c0c42181-5319-40f9-8104-330045f10c96","year":2015},"citing_paper":{"arxiv_id":"2504.12517","last_updated":"2025-04-23T15:58:21Z","snapshot_observed_at":"2026-08-16T12:27:29.828080Z","submitted_at":"2025-04-16T22:30:54Z","title":"Code Improvement Practices at Meta","version":2},"reference_index":16,"source":"pdf_text","source_observed_at":"2026-08-16T12:34:09.767521Z"},"links":{"citing_paper":"/paper/2504.12517"},"observation_digest":"sha256:3ce3db8db0eb6512352a3f5833e1ca9530c8f93235527e792613299c5226fbe4","observation_id":"a42b4bb3-ca90-4fdd-b66e-988d318df3e4","resolution":{"observed_at":"2026-08-16T12:34:10.324342Z","resolver_source":"raw_fallback","status":"verified_fuzzy"},"standing_notice":{"events":[],"observation":"No event found in the named queried sources as of 2026-08-21T06:32:19.484+00:00.","reason":null,"source_receipts":[{"observed_at":"2026-08-21T06:32:19.484+00:00","source":"crossref"},{"observed_at":"2026-08-21T06:32:16.066871+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-16T12:34:10.304698Z","title":"On the reproducibility of empirical software engineering studies based on data retrieved from development repositories,","venue":null,"work_id":"1e6d8382-8b1f-4a23-aebd-1f9dce5031d7","year":2012},"citing_paper":{"arxiv_id":"2504.12517","last_updated":"2025-04-23T15:58:21Z","snapshot_observed_at":"2026-08-16T12:27:29.828080Z","submitted_at":"2025-04-16T22:30:54Z","title":"Code Improvement Practices at Meta","version":2},"reference_index":17,"source":"pdf_text","source_observed_at":"2026-08-16T12:34:09.770892Z"},"links":{"citing_paper":"/paper/2504.12517"},"observation_digest":"sha256:830bc5ec4e7edffef2b96ef043ff84f05531eae1d60bb7447ada3d36a2db29ad","observation_id":"ba16e3cb-4504-4dc4-a99c-a1e999448849","resolution":{"observed_at":"2026-08-16T12:34:10.309002Z","resolver_source":"raw_fallback","status":"verified_fuzzy"},"standing_notice":{"events":[],"observation":"No event found in the named queried sources as of 2026-08-21T06:32:19.484+00:00.","reason":null,"source_receipts":[{"observed_at":"2026-08-21T06:32:19.484+00:00","source":"crossref"},{"observed_at":"2026-08-21T06:32:16.066871+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-16T12:34:10.290024Z","title":"Experiences from replicating a case study to investigate reproducibility of software development,","venue":null,"work_id":"5b30b0db-2f4d-4cc2-be3f-332ff7af9a7d","year":2010},"citing_paper":{"arxiv_id":"2504.12517","last_updated":"2025-04-23T15:58:21Z","snapshot_observed_at":"2026-08-16T12:27:29.828080Z","submitted_at":"2025-04-16T22:30:54Z","title":"Code Improvement Practices at Meta","version":2},"reference_index":18,"source":"pdf_text","source_observed_at":"2026-08-16T12:34:09.775329Z"},"links":{"citing_paper":"/paper/2504.12517"},"observation_digest":"sha256:0b268a8629edae53f9c01a0605705fa8ac2f6491f156a6b32d94274c12cb44d7","observation_id":"3c7ecfbd-219a-4d33-bd5e-611f7f65bfaa","resolution":{"observed_at":"2026-08-16T12:34:10.294954Z","resolver_source":"raw_fallback","status":"verified_fuzzy"},"standing_notice":{"events":[],"observation":"No event found in the named queried sources as of 2026-08-21T06:32:19.484+00:00.","reason":null,"source_receipts":[{"observed_at":"2026-08-21T06:32:19.484+00:00","source":"crossref"},{"observed_at":"2026-08-21T06:32:16.066871+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-16T12:34:09.779313Z","title":"Repro- ducibility and credibility in empirical software engineering: A case study based on a systematic literature review of the use of the szz algorithm,","venue":null,"work_id":null,"year":2018},"citing_paper":{"arxiv_id":"2504.12517","last_updated":"2025-04-23T15:58:21Z","snapshot_observed_at":"2026-08-16T12:27:29.828080Z","submitted_at":"2025-04-16T22:30:54Z","title":"Code Improvement Practices at Meta","version":2},"reference_index":19,"source":"pdf_text","source_observed_at":"2026-08-16T12:34:09.779313Z"},"links":{"citing_paper":"/paper/2504.12517"},"observation_digest":"sha256:b4c5e11a47c275a3be953e9e813d0b63ac19b1fd7680710cc87590223122467f","observation_id":"7bb164a8-a0cb-468a-b7b6-f7dbba24886d","resolution":{"observed_at":"2026-08-16T12:34:09.779313Z","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-16T12:34:10.270002Z","title":"Dead code removal at meta: Automatically deleting millions of lines of code and petabytes of deprecated data,","venue":null,"work_id":"da3075ad-0150-48b6-a9bc-3691e4b0d3fc","year":2023},"citing_paper":{"arxiv_id":"2504.12517","last_updated":"2025-04-23T15:58:21Z","snapshot_observed_at":"2026-08-16T12:27:29.828080Z","submitted_at":"2025-04-16T22:30:54Z","title":"Code Improvement Practices at Meta","version":2},"reference_index":20,"source":"pdf_text","source_observed_at":"2026-08-16T12:34:09.782869Z"},"links":{"citing_paper":"/paper/2504.12517"},"observation_digest":"sha256:0edc6500c23ed303acc5e51f775a65699b7b2d8b81332408c731958584cc543a","observation_id":"0c0fd4b8-84c8-48a9-aecd-47c3af623178","resolution":{"observed_at":"2026-08-16T12:34:10.274440Z","resolver_source":"raw_fallback","status":"verified_fuzzy"},"standing_notice":{"events":[],"observation":"No event found in the named queried sources as of 2026-08-21T06:32:19.484+00:00.","reason":null,"source_receipts":[{"observed_at":"2026-08-21T06:32:19.484+00:00","source":"crossref"},{"observed_at":"2026-08-21T06:32:16.066871+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-16T12:34:10.258746Z","title":"Assessing the state of software in a large enterprise,","venue":null,"work_id":"71bb8f36-e106-4b9b-80a3-7897bd46b80d","year":2010},"citing_paper":{"arxiv_id":"2504.12517","last_updated":"2025-04-23T15:58:21Z","snapshot_observed_at":"2026-08-16T12:27:29.828080Z","submitted_at":"2025-04-16T22:30:54Z","title":"Code Improvement Practices at Meta","version":2},"reference_index":21,"source":"pdf_text","source_observed_at":"2026-08-16T12:34:09.786283Z"},"links":{"citing_paper":"/paper/2504.12517"},"observation_digest":"sha256:d2383d67e4886ed0a7a53e95af01ba00ceb8169bbde20432f0e13e5be6dd0014","observation_id":"003df10b-c57d-4ab4-8d4b-9f4a75d9a23e","resolution":{"observed_at":"2026-08-16T12:34:10.262564Z","resolver_source":"raw_fallback","status":"verified_fuzzy"},"standing_notice":{"events":[],"observation":"No event found in the named queried sources as of 2026-08-21T06:32:19.484+00:00.","reason":null,"source_receipts":[{"observed_at":"2026-08-21T06:32:19.484+00:00","source":"crossref"},{"observed_at":"2026-08-21T06:32:16.066871+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-16T12:34:10.246968Z","title":"Beliefs, practices, and personalities of software engineers: a survey in a large software company,","venue":null,"work_id":"5bf1bc70-c816-459e-bc1b-107d14278c4a","year":2016},"citing_paper":{"arxiv_id":"2504.12517","last_updated":"2025-04-23T15:58:21Z","snapshot_observed_at":"2026-08-16T12:27:29.828080Z","submitted_at":"2025-04-16T22:30:54Z","title":"Code Improvement Practices at Meta","version":2},"reference_index":22,"source":"pdf_text","source_observed_at":"2026-08-16T12:34:09.790112Z"},"links":{"citing_paper":"/paper/2504.12517"},"observation_digest":"sha256:1ba000d71e490096d48147d43439f3b05671d539d80e1ee5a0d393e598026d2e","observation_id":"8968d0fd-8baa-4c4f-8c5d-7bbe46a04a26","resolution":{"observed_at":"2026-08-16T12:34:10.250757Z","resolver_source":"raw_fallback","status":"verified_fuzzy"},"standing_notice":{"events":[],"observation":"No event found in the named queried sources as of 2026-08-21T06:32:19.484+00:00.","reason":null,"source_receipts":[{"observed_at":"2026-08-21T06:32:19.484+00:00","source":"crossref"},{"observed_at":"2026-08-21T06:32:16.066871+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-16T12:34:10.234131Z","title":"Leffingwell, Scaling software agility: best practices for large enterprises","venue":null,"work_id":"8307c772-d045-4215-91c7-a6bc258c36b7","year":2007},"citing_paper":{"arxiv_id":"2504.12517","last_updated":"2025-04-23T15:58:21Z","snapshot_observed_at":"2026-08-16T12:27:29.828080Z","submitted_at":"2025-04-16T22:30:54Z","title":"Code Improvement Practices at Meta","version":2},"reference_index":23,"source":"pdf_text","source_observed_at":"2026-08-16T12:34:09.793502Z"},"links":{"citing_paper":"/paper/2504.12517"},"observation_digest":"sha256:a26b9116700657c1e5a96a0d6df1618c01340ee3a77c18a4ef6cb0019a3fd151","observation_id":"6b5a0107-9a49-4012-82aa-f1b5c36834f5","resolution":{"observed_at":"2026-08-16T12:34:10.238770Z","resolver_source":"raw_fallback","status":"verified_fuzzy"},"standing_notice":{"events":[],"observation":"No event found in the named queried sources as of 2026-08-21T06:32:19.484+00:00.","reason":null,"source_receipts":[{"observed_at":"2026-08-21T06:32:19.484+00:00","source":"crossref"},{"observed_at":"2026-08-21T06:32:16.066871+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-16T12:34:10.221201Z","title":"Prioritization of classes for refac- toring: A step towards improvement in software quality,","venue":null,"work_id":"41a46cbc-e58b-4d66-896c-e087b5048492","year":2015},"citing_paper":{"arxiv_id":"2504.12517","last_updated":"2025-04-23T15:58:21Z","snapshot_observed_at":"2026-08-16T12:27:29.828080Z","submitted_at":"2025-04-16T22:30:54Z","title":"Code Improvement Practices at Meta","version":2},"reference_index":24,"source":"pdf_text","source_observed_at":"2026-08-16T12:34:09.797153Z"},"links":{"citing_paper":"/paper/2504.12517"},"observation_digest":"sha256:7b523fdd5115058241dbb2a0ac687d474152cd2e25e14081612486539da210ff","observation_id":"2a60c1fe-041e-412f-870a-4ad33f9899d8","resolution":{"observed_at":"2026-08-16T12:34:10.225405Z","resolver_source":"raw_fallback","status":"verified_fuzzy"},"standing_notice":{"events":[],"observation":"No event found in the named queried sources as of 2026-08-21T06:32:19.484+00:00.","reason":null,"source_receipts":[{"observed_at":"2026-08-21T06:32:19.484+00:00","source":"crossref"},{"observed_at":"2026-08-21T06:32:16.066871+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-16T12:34:10.207545Z","title":"The dimensions of maintenance,","venue":null,"work_id":"5e2cf2f6-0981-4955-b59d-63531d0315d7","year":1976},"citing_paper":{"arxiv_id":"2504.12517","last_updated":"2025-04-23T15:58:21Z","snapshot_observed_at":"2026-08-16T12:27:29.828080Z","submitted_at":"2025-04-16T22:30:54Z","title":"Code Improvement Practices at Meta","version":2},"reference_index":25,"source":"pdf_text","source_observed_at":"2026-08-16T12:34:09.800647Z"},"links":{"citing_paper":"/paper/2504.12517"},"observation_digest":"sha256:187236c5563a4968bb443ba8675fc68df510716ead0cab869c50901ec1755ad5","observation_id":"1d4e2830-fc0d-4e5a-80aa-d00f47a2447f","resolution":{"observed_at":"2026-08-16T12:34:10.211972Z","resolver_source":"raw_fallback","status":"verified_fuzzy"},"standing_notice":{"events":[],"observation":"No event found in the named queried sources as of 2026-08-21T06:32:19.484+00:00.","reason":null,"source_receipts":[{"observed_at":"2026-08-21T06:32:19.484+00:00","source":"crossref"},{"observed_at":"2026-08-21T06:32:16.066871+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-16T12:34:10.196194Z","title":"Identifying reasons for software changes using historic databases,","venue":null,"work_id":"a2a9561f-b28a-482a-9d16-1541071d8e0c","year":2000},"citing_paper":{"arxiv_id":"2504.12517","last_updated":"2025-04-23T15:58:21Z","snapshot_observed_at":"2026-08-16T12:27:29.828080Z","submitted_at":"2025-04-16T22:30:54Z","title":"Code Improvement Practices at Meta","version":2},"reference_index":26,"source":"pdf_text","source_observed_at":"2026-08-16T12:34:09.804336Z"},"links":{"citing_paper":"/paper/2504.12517"},"observation_digest":"sha256:c3adfa0c4ac56f45937da0bbe322f239afb30fadfb1b1e0a478df4c5ad54ded2","observation_id":"9fdb82a4-e32a-497d-9abe-9cf96ee8796d","resolution":{"observed_at":"2026-08-16T12:34:10.200077Z","resolver_source":"raw_fallback","status":"verified_fuzzy"},"standing_notice":{"events":[],"observation":"No event found in the named queried sources as of 2026-08-21T06:32:19.484+00:00.","reason":null,"source_receipts":[{"observed_at":"2026-08-21T06:32:19.484+00:00","source":"crossref"},{"observed_at":"2026-08-21T06:32:16.066871+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-16T12:34:10.182443Z","title":"An exploratory study on self-admitted technical debt,","venue":null,"work_id":"e242837d-8290-435d-bb71-72516c99f241","year":2014},"citing_paper":{"arxiv_id":"2504.12517","last_updated":"2025-04-23T15:58:21Z","snapshot_observed_at":"2026-08-16T12:27:29.828080Z","submitted_at":"2025-04-16T22:30:54Z","title":"Code Improvement Practices at Meta","version":2},"reference_index":27,"source":"pdf_text","source_observed_at":"2026-08-16T12:34:09.808136Z"},"links":{"citing_paper":"/paper/2504.12517"},"observation_digest":"sha256:8e3646a1c9a128c4d0483f0c33d1cd1279f6ed15357462114123289d29d1b3f2","observation_id":"a6837832-e374-4c33-8ac4-2024642abd26","resolution":{"observed_at":"2026-08-16T12:34:10.187410Z","resolver_source":"raw_fallback","status":"verified_fuzzy"},"standing_notice":{"events":[],"observation":"No event found in the named queried sources as of 2026-08-21T06:32:19.484+00:00.","reason":null,"source_receipts":[{"observed_at":"2026-08-21T06:32:19.484+00:00","source":"crossref"},{"observed_at":"2026-08-21T06:32:16.066871+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-16T12:34:10.169256Z","title":"Does gamification work?–a literature review of empirical studies on gamification,","venue":null,"work_id":"ada52656-12d6-48f6-963b-23082c42bd97","year":2014},"citing_paper":{"arxiv_id":"2504.12517","last_updated":"2025-04-23T15:58:21Z","snapshot_observed_at":"2026-08-16T12:27:29.828080Z","submitted_at":"2025-04-16T22:30:54Z","title":"Code Improvement Practices at Meta","version":2},"reference_index":28,"source":"pdf_text","source_observed_at":"2026-08-16T12:34:09.811895Z"},"links":{"citing_paper":"/paper/2504.12517"},"observation_digest":"sha256:7f5e40b9d2d1a655c26b059e59feff40b8837006d356e0b792712a5b409ab1a1","observation_id":"3419b81f-acb9-41b4-9c7e-3cbeffd56b50","resolution":{"observed_at":"2026-08-16T12:34:10.174232Z","resolver_source":"raw_fallback","status":"verified_fuzzy"},"standing_notice":{"events":[],"observation":"No event found in the named queried sources as of 2026-08-21T06:32:19.484+00:00.","reason":null,"source_receipts":[{"observed_at":"2026-08-21T06:32:19.484+00:00","source":"crossref"},{"observed_at":"2026-08-21T06:32:16.066871+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-16T12:34:10.157387Z","title":"Gamification in theory and action: A survey,","venue":null,"work_id":"94233140-f97d-4ca6-b8db-8e6c8b5e244c","year":2015},"citing_paper":{"arxiv_id":"2504.12517","last_updated":"2025-04-23T15:58:21Z","snapshot_observed_at":"2026-08-16T12:27:29.828080Z","submitted_at":"2025-04-16T22:30:54Z","title":"Code Improvement Practices at Meta","version":2},"reference_index":29,"source":"pdf_text","source_observed_at":"2026-08-16T12:34:09.815512Z"},"links":{"citing_paper":"/paper/2504.12517"},"observation_digest":"sha256:6e76c6be1401cf1b4cc60a4b565f97f08dfbf707db4b0762cf72dabd71f08778","observation_id":"c36a6138-7f6e-414c-b946-ba933059404d","resolution":{"observed_at":"2026-08-16T12:34:10.161277Z","resolver_source":"raw_fallback","status":"verified_fuzzy"},"standing_notice":{"events":[],"observation":"No event found in the named queried sources as of 2026-08-21T06:32:19.484+00:00.","reason":null,"source_receipts":[{"observed_at":"2026-08-21T06:32:19.484+00:00","source":"crossref"},{"observed_at":"2026-08-21T06:32:16.066871+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-16T12:34:10.145796Z","title":"Lupton, The quantified self","venue":null,"work_id":"886362db-337b-467b-bdaf-71af6f9860d7","year":2016},"citing_paper":{"arxiv_id":"2504.12517","last_updated":"2025-04-23T15:58:21Z","snapshot_observed_at":"2026-08-16T12:27:29.828080Z","submitted_at":"2025-04-16T22:30:54Z","title":"Code Improvement Practices at Meta","version":2},"reference_index":30,"source":"pdf_text","source_observed_at":"2026-08-16T12:34:09.819270Z"},"links":{"citing_paper":"/paper/2504.12517"},"observation_digest":"sha256:f6a6692c661c4bfa79e9b3a7e012473e4209ce666d8f69e2c0c92fbdb0152991","observation_id":"c038bd7b-8392-43da-bcc5-45339ff7eac3","resolution":{"observed_at":"2026-08-16T12:34:10.149529Z","resolver_source":"raw_fallback","status":"verified_fuzzy"},"standing_notice":{"events":[],"observation":"No event found in the named queried sources as of 2026-08-21T06:32:19.484+00:00.","reason":null,"source_receipts":[{"observed_at":"2026-08-21T06:32:19.484+00:00","source":"crossref"},{"observed_at":"2026-08-21T06:32:16.066871+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-16T12:34:10.134748Z","title":"Modeling the centrality of developer output with software supply chains,","venue":null,"work_id":"7dd3616e-f905-41a8-bd26-ba8bedd5f5c1","year":2023},"citing_paper":{"arxiv_id":"2504.12517","last_updated":"2025-04-23T15:58:21Z","snapshot_observed_at":"2026-08-16T12:27:29.828080Z","submitted_at":"2025-04-16T22:30:54Z","title":"Code Improvement Practices at Meta","version":2},"reference_index":31,"source":"pdf_text","source_observed_at":"2026-08-16T12:34:09.822789Z"},"links":{"citing_paper":"/paper/2504.12517"},"observation_digest":"sha256:772c6857e28bf27caff538ebafac927f80603fbc6970b48c340c16563b7fe621","observation_id":"eeebb402-37ec-4b06-9bd8-b8c4e98341b7","resolution":{"observed_at":"2026-08-16T12:34:10.138628Z","resolver_source":"raw_fallback","status":"verified_fuzzy"},"standing_notice":{"events":[],"observation":"No event found in the named queried sources as of 2026-08-21T06:32:19.484+00:00.","reason":null,"source_receipts":[{"observed_at":"2026-08-21T06:32:19.484+00:00","source":"crossref"},{"observed_at":"2026-08-21T06:32:16.066871+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-16T12:34:10.123103Z","title":"Measuring productivity impact with diff authoring time,","venue":null,"work_id":"dd287645-1f3e-4543-9be4-0fdfb9b6b061","year":2025},"citing_paper":{"arxiv_id":"2504.12517","last_updated":"2025-04-23T15:58:21Z","snapshot_observed_at":"2026-08-16T12:27:29.828080Z","submitted_at":"2025-04-16T22:30:54Z","title":"Code Improvement Practices at Meta","version":2},"reference_index":32,"source":"pdf_text","source_observed_at":"2026-08-16T12:34:09.826206Z"},"links":{"citing_paper":"/paper/2504.12517"},"observation_digest":"sha256:4b6c8e5d3582aca303fcd39eac97654c9a2f86336a56b3174c6ee6feb1c9387f","observation_id":"32b0021b-03a6-421b-bc70-5140830f5770","resolution":{"observed_at":"2026-08-16T12:34:10.126965Z","resolver_source":"raw_fallback","status":"verified_fuzzy"},"standing_notice":{"events":[],"observation":"No event found in the named queried sources as of 2026-08-21T06:32:19.484+00:00.","reason":null,"source_receipts":[{"observed_at":"2026-08-21T06:32:19.484+00:00","source":"crossref"},{"observed_at":"2026-08-21T06:32:16.066871+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-16T12:34:10.110037Z","title":"Developer fluency: Achieving true mastery in software projects,","venue":null,"work_id":"5f29f460-421a-4058-b7af-a72e50c53767","year":2010},"citing_paper":{"arxiv_id":"2504.12517","last_updated":"2025-04-23T15:58:21Z","snapshot_observed_at":"2026-08-16T12:27:29.828080Z","submitted_at":"2025-04-16T22:30:54Z","title":"Code Improvement Practices at Meta","version":2},"reference_index":33,"source":"pdf_text","source_observed_at":"2026-08-16T12:34:09.829825Z"},"links":{"citing_paper":"/paper/2504.12517"},"observation_digest":"sha256:ffe16929238e520ff94b48783ed9611503bd1095cdadbfe807d14e244bcbb6e3","observation_id":"771d548c-0601-48df-9b71-7e879a4110cb","resolution":{"observed_at":"2026-08-16T12:34:10.115164Z","resolver_source":"raw_fallback","status":"verified_fuzzy"},"standing_notice":{"events":[],"observation":"No event found in the named queried sources as of 2026-08-21T06:32:19.484+00:00.","reason":null,"source_receipts":[{"observed_at":"2026-08-21T06:32:19.484+00:00","source":"crossref"},{"observed_at":"2026-08-21T06:32:16.066871+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-16T12:34:09.833776Z","title":"A new status index derived from sociometric analysis,","venue":null,"work_id":null,"year":1953},"citing_paper":{"arxiv_id":"2504.12517","last_updated":"2025-04-23T15:58:21Z","snapshot_observed_at":"2026-08-16T12:27:29.828080Z","submitted_at":"2025-04-16T22:30:54Z","title":"Code Improvement Practices at Meta","version":2},"reference_index":34,"source":"pdf_text","source_observed_at":"2026-08-16T12:34:09.833776Z"},"links":{"citing_paper":"/paper/2504.12517"},"observation_digest":"sha256:732ad2e9f56933494bff3de36088ca826be569cb350329a3107d14775adae06c","observation_id":"da0b89d2-24fd-479e-b707-36c4288e5482","resolution":{"observed_at":"2026-08-16T12:34:09.833776Z","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-08-16T12:34:09.837298Z","title":"A complexity measure,","venue":null,"work_id":null,"year":1976},"citing_paper":{"arxiv_id":"2504.12517","last_updated":"2025-04-23T15:58:21Z","snapshot_observed_at":"2026-08-16T12:27:29.828080Z","submitted_at":"2025-04-16T22:30:54Z","title":"Code Improvement Practices at Meta","version":2},"reference_index":35,"source":"pdf_text","source_observed_at":"2026-08-16T12:34:09.837298Z"},"links":{"citing_paper":"/paper/2504.12517"},"observation_digest":"sha256:e61b8024b41940a49a816411d9b2837e90e2728de8d23dfd816d7ca68821870b","observation_id":"36efd339-0aaa-441d-b228-64d3980a0e51","resolution":{"observed_at":"2026-08-16T12:34:09.837298Z","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-16T12:34:10.077792Z","title":"Matching methods for causal inference: A review and a look forward,","venue":null,"work_id":"c9e48025-6626-4386-9aa7-26cc4461604b","year":2010},"citing_paper":{"arxiv_id":"2504.12517","last_updated":"2025-04-23T15:58:21Z","snapshot_observed_at":"2026-08-16T12:27:29.828080Z","submitted_at":"2025-04-16T22:30:54Z","title":"Code Improvement Practices at Meta","version":2},"reference_index":36,"source":"pdf_text","source_observed_at":"2026-08-16T12:34:09.840964Z"},"links":{"citing_paper":"/paper/2504.12517"},"observation_digest":"sha256:21a67a77e6748dd376863ba5e1bc8f9b093cee4cb6d075b46b9aee4569ad1869","observation_id":"099f1576-f4f0-42f1-992f-c08338f73678","resolution":{"observed_at":"2026-08-16T12:34:10.081504Z","resolver_source":"raw_fallback","status":"verified_fuzzy"},"standing_notice":{"events":[],"observation":"No event found in the named queried sources as of 2026-08-21T06:32:19.484+00:00.","reason":null,"source_receipts":[{"observed_at":"2026-08-21T06:32:19.484+00:00","source":"crossref"},{"observed_at":"2026-08-21T06:32:16.066871+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-16T12:34:10.066209Z","title":"Software developers’ perceptions of productivity,","venue":null,"work_id":"32929187-d74c-472a-ba6c-03589fbcbc47","year":2014},"citing_paper":{"arxiv_id":"2504.12517","last_updated":"2025-04-23T15:58:21Z","snapshot_observed_at":"2026-08-16T12:27:29.828080Z","submitted_at":"2025-04-16T22:30:54Z","title":"Code Improvement Practices at Meta","version":2},"reference_index":37,"source":"pdf_text","source_observed_at":"2026-08-16T12:34:09.844628Z"},"links":{"citing_paper":"/paper/2504.12517"},"observation_digest":"sha256:a6d75962e0901a92217fddb87117f926c3f92cdcc081de599312a35355d28702","observation_id":"85b033f7-e7c2-4ecb-99c1-7074c166ab67","resolution":{"observed_at":"2026-08-16T12:34:10.070252Z","resolver_source":"raw_fallback","status":"verified_fuzzy"},"standing_notice":{"events":[],"observation":"No event found in the named queried sources as of 2026-08-21T06:32:19.484+00:00.","reason":null,"source_receipts":[{"observed_at":"2026-08-21T06:32:19.484+00:00","source":"crossref"},{"observed_at":"2026-08-21T06:32:16.066871+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-16T12:34:10.054406Z","title":"Putting it all together: Using socio-technical networks to predict failures,","venue":null,"work_id":"9044dc62-988e-43f7-8a2e-3ef32c1d81a9","year":2009},"citing_paper":{"arxiv_id":"2504.12517","last_updated":"2025-04-23T15:58:21Z","snapshot_observed_at":"2026-08-16T12:27:29.828080Z","submitted_at":"2025-04-16T22:30:54Z","title":"Code Improvement Practices at Meta","version":2},"reference_index":38,"source":"pdf_text","source_observed_at":"2026-08-16T12:34:09.848230Z"},"links":{"citing_paper":"/paper/2504.12517"},"observation_digest":"sha256:52018959665d61145ff394d70752ec56c52eb023282371923d0b51118cf0c39f","observation_id":"12952fb1-a2dd-42f4-877f-51bfc7faafc8","resolution":{"observed_at":"2026-08-16T12:34:10.058378Z","resolver_source":"raw_fallback","status":"verified_fuzzy"},"standing_notice":{"events":[],"observation":"No event found in the named queried sources as of 2026-08-21T06:32:19.484+00:00.","reason":null,"source_receipts":[{"observed_at":"2026-08-21T06:32:19.484+00:00","source":"crossref"},{"observed_at":"2026-08-21T06:32:16.066871+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-16T12:34:10.043264Z","title":"Predicting defects using network analysis on dependency graphs,","venue":null,"work_id":"6e4557bd-5f4f-4b38-978b-fc767df8ed26","year":2008},"citing_paper":{"arxiv_id":"2504.12517","last_updated":"2025-04-23T15:58:21Z","snapshot_observed_at":"2026-08-16T12:27:29.828080Z","submitted_at":"2025-04-16T22:30:54Z","title":"Code Improvement Practices at Meta","version":2},"reference_index":39,"source":"pdf_text","source_observed_at":"2026-08-16T12:34:09.851814Z"},"links":{"citing_paper":"/paper/2504.12517"},"observation_digest":"sha256:ebcfcfa0f29a70e02b4c0b74da169fbe81b1dcf9451bfbf4ac61cbed39de47df","observation_id":"60e175d1-4520-4659-81e6-2d5f68c68c3d","resolution":{"observed_at":"2026-08-16T12:34:10.047142Z","resolver_source":"raw_fallback","status":"verified_fuzzy"},"standing_notice":{"events":[],"observation":"No event found in the named queried sources as of 2026-08-21T06:32:19.484+00:00.","reason":null,"source_receipts":[{"observed_at":"2026-08-21T06:32:19.484+00:00","source":"crossref"},{"observed_at":"2026-08-21T06:32:16.066871+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-16T12:34:10.031057Z","title":"Categorizing bugs with social networks: a case study on four open source software communities,","venue":null,"work_id":"591fb91b-472d-41b4-bc7d-412501241ae1","year":2013},"citing_paper":{"arxiv_id":"2504.12517","last_updated":"2025-04-23T15:58:21Z","snapshot_observed_at":"2026-08-16T12:27:29.828080Z","submitted_at":"2025-04-16T22:30:54Z","title":"Code Improvement Practices at Meta","version":2},"reference_index":40,"source":"pdf_text","source_observed_at":"2026-08-16T12:34:09.855327Z"},"links":{"citing_paper":"/paper/2504.12517"},"observation_digest":"sha256:a2dee5bb88618da3da4abc71a5c7212a22825fe974fcc5584e36194ca65ab12c","observation_id":"2a6c0d17-ecce-4954-8209-0e11ff9b6e3a","resolution":{"observed_at":"2026-08-16T12:34:10.035294Z","resolver_source":"raw_fallback","status":"verified_fuzzy"},"standing_notice":{"events":[],"observation":"No event found in the named queried sources as of 2026-08-21T06:32:19.484+00:00.","reason":null,"source_receipts":[{"observed_at":"2026-08-21T06:32:19.484+00:00","source":"crossref"},{"observed_at":"2026-08-21T06:32:16.066871+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-16T12:34:10.018008Z","title":"The small-world effect: The influence of macro-level properties of developer collaboration networks on open-source project success,","venue":null,"work_id":"04314158-987f-4360-a6ac-f31a2ef89fd4","year":2010},"citing_paper":{"arxiv_id":"2504.12517","last_updated":"2025-04-23T15:58:21Z","snapshot_observed_at":"2026-08-16T12:27:29.828080Z","submitted_at":"2025-04-16T22:30:54Z","title":"Code Improvement Practices at Meta","version":2},"reference_index":41,"source":"pdf_text","source_observed_at":"2026-08-16T12:34:09.858743Z"},"links":{"citing_paper":"/paper/2504.12517"},"observation_digest":"sha256:48645fcd21b1f0e23865d9a7a696dad57ade067998bf40eca73a229ad6518457","observation_id":"480cbfb0-b85b-4190-aefc-e67897e37183","resolution":{"observed_at":"2026-08-16T12:34:10.022881Z","resolver_source":"raw_fallback","status":"verified_fuzzy"},"standing_notice":{"events":[],"observation":"No event found in the named queried sources as of 2026-08-21T06:32:19.484+00:00.","reason":null,"source_receipts":[{"observed_at":"2026-08-21T06:32:19.484+00:00","source":"crossref"},{"observed_at":"2026-08-21T06:32:16.066871+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-16T12:34:09.999596Z","title":"Using social network analysis for mining collaboration data in a defect tracking system for risk and vulnerability analysis,","venue":null,"work_id":"0ef8ec71-24ab-4333-81d9-f9306d60e083","year":2011},"citing_paper":{"arxiv_id":"2504.12517","last_updated":"2025-04-23T15:58:21Z","snapshot_observed_at":"2026-08-16T12:27:29.828080Z","submitted_at":"2025-04-16T22:30:54Z","title":"Code Improvement Practices at Meta","version":2},"reference_index":42,"source":"pdf_text","source_observed_at":"2026-08-16T12:34:09.862127Z"},"links":{"citing_paper":"/paper/2504.12517"},"observation_digest":"sha256:0efff3e6ece4e9b7e3a584fc5f594e3903096829a23fbe9c4f9cbeaf25405151","observation_id":"ecc5c2ff-8d5b-49d9-a8c2-976aa3ab1c78","resolution":{"observed_at":"2026-08-16T12:34:10.008930Z","resolver_source":"raw_fallback","status":"verified_fuzzy"},"standing_notice":{"events":[],"observation":"No event found in the named queried sources as of 2026-08-21T06:32:19.484+00:00.","reason":null,"source_receipts":[{"observed_at":"2026-08-21T06:32:19.484+00:00","source":"crossref"},{"observed_at":"2026-08-21T06:32:16.066871+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-16T12:34:09.985231Z","title":"Characterizing and understanding software developer networks in security development,","venue":null,"work_id":"5c64aee4-026a-4b21-a830-9146cd5e9ecc","year":2021},"citing_paper":{"arxiv_id":"2504.12517","last_updated":"2025-04-23T15:58:21Z","snapshot_observed_at":"2026-08-16T12:27:29.828080Z","submitted_at":"2025-04-16T22:30:54Z","title":"Code Improvement Practices at Meta","version":2},"reference_index":43,"source":"pdf_text","source_observed_at":"2026-08-16T12:34:09.865563Z"},"links":{"citing_paper":"/paper/2504.12517"},"observation_digest":"sha256:043d0f1f59901af4e3669ccfc7e3edc5313a86de148c66a4547c9479bc3052e8","observation_id":"1184ec5f-dddb-4c2d-b941-959315ea6af5","resolution":{"observed_at":"2026-08-16T12:34:09.990334Z","resolver_source":"raw_fallback","status":"verified_fuzzy"},"standing_notice":{"events":[],"observation":"No event found in the named queried sources as of 2026-08-21T06:32:19.484+00:00.","reason":null,"source_receipts":[{"observed_at":"2026-08-21T06:32:19.484+00:00","source":"crossref"},{"observed_at":"2026-08-21T06:32:16.066871+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-16T12:34:09.973336Z","title":"Boehm, Software Engineering Economics","venue":null,"work_id":"81f51b74-3124-4706-a7d2-001a714a27fc","year":1981},"citing_paper":{"arxiv_id":"2504.12517","last_updated":"2025-04-23T15:58:21Z","snapshot_observed_at":"2026-08-16T12:27:29.828080Z","submitted_at":"2025-04-16T22:30:54Z","title":"Code Improvement Practices at Meta","version":2},"reference_index":44,"source":"pdf_text","source_observed_at":"2026-08-16T12:34:09.869138Z"},"links":{"citing_paper":"/paper/2504.12517"},"observation_digest":"sha256:4e26d5670b501ddf4686a33c434c7ac4233bc24be50a0815a05e2d12acf392b7","observation_id":"85a6becc-9550-4619-a817-241086ded735","resolution":{"observed_at":"2026-08-16T12:34:09.977325Z","resolver_source":"raw_fallback","status":"verified_fuzzy"},"standing_notice":{"events":[],"observation":"No event found in the named queried sources as of 2026-08-21T06:32:19.484+00:00.","reason":null,"source_receipts":[{"observed_at":"2026-08-21T06:32:19.484+00:00","source":"crossref"},{"observed_at":"2026-08-21T06:32:16.066871+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-16T12:34:09.961121Z","title":"Missing data in software engineering,","venue":null,"work_id":"1157a78c-648e-40d3-944c-0556c55b70da","year":2008},"citing_paper":{"arxiv_id":"2504.12517","last_updated":"2025-04-23T15:58:21Z","snapshot_observed_at":"2026-08-16T12:27:29.828080Z","submitted_at":"2025-04-16T22:30:54Z","title":"Code Improvement Practices at Meta","version":2},"reference_index":45,"source":"pdf_text","source_observed_at":"2026-08-16T12:34:09.872586Z"},"links":{"citing_paper":"/paper/2504.12517"},"observation_digest":"sha256:20422bcfd044bc993e2bcd2833abd86053c83883927f7371041d410dc2fa53e8","observation_id":"85b3f3b1-01c0-4d99-a9c1-7d88ed797053","resolution":{"observed_at":"2026-08-16T12:34:09.965118Z","resolver_source":"raw_fallback","status":"verified_fuzzy"},"standing_notice":{"events":[],"observation":"No event found in the named queried sources as of 2026-08-21T06:32:19.484+00:00.","reason":null,"source_receipts":[{"observed_at":"2026-08-21T06:32:19.484+00:00","source":"crossref"},{"observed_at":"2026-08-21T06:32:16.066871+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-16T12:34:09.948766Z","title":"Software support tools and experimental work,","venue":null,"work_id":"6504c354-76ce-48a4-afdd-d378998de059","year":2007},"citing_paper":{"arxiv_id":"2504.12517","last_updated":"2025-04-23T15:58:21Z","snapshot_observed_at":"2026-08-16T12:27:29.828080Z","submitted_at":"2025-04-16T22:30:54Z","title":"Code Improvement Practices at Meta","version":2},"reference_index":46,"source":"pdf_text","source_observed_at":"2026-08-16T12:34:09.876168Z"},"links":{"citing_paper":"/paper/2504.12517"},"observation_digest":"sha256:a7ad3960c3a1538f5534510a21a9ce20815f0ec4795a256965a6fd08a21874ca","observation_id":"2ff7746a-7214-44a5-af89-c20eae17b4b9","resolution":{"observed_at":"2026-08-16T12:34:09.952702Z","resolver_source":"raw_fallback","status":"verified_fuzzy"},"standing_notice":{"events":[],"observation":"No event found in the named queried sources as of 2026-08-21T06:32:19.484+00:00.","reason":null,"source_receipts":[{"observed_at":"2026-08-21T06:32:19.484+00:00","source":"crossref"},{"observed_at":"2026-08-21T06:32:16.066871+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-16T12:34:09.935508Z","title":"Organizational volatility and its effects on software defects,","venue":null,"work_id":"c85f9cac-de35-4b5e-a8be-e5cfaa105640","year":2010},"citing_paper":{"arxiv_id":"2504.12517","last_updated":"2025-04-23T15:58:21Z","snapshot_observed_at":"2026-08-16T12:27:29.828080Z","submitted_at":"2025-04-16T22:30:54Z","title":"Code Improvement Practices at Meta","version":2},"reference_index":47,"source":"pdf_text","source_observed_at":"2026-08-16T12:34:09.879769Z"},"links":{"citing_paper":"/paper/2504.12517"},"observation_digest":"sha256:d80dad6da8a452e02ce665bb1d0f4a44998e1387dc4a6a8d5256a701303d64cf","observation_id":"29f0e009-c34d-42e4-8727-0538c9c73f18","resolution":{"observed_at":"2026-08-16T12:34:09.940463Z","resolver_source":"raw_fallback","status":"verified_fuzzy"},"standing_notice":{"events":[],"observation":"No event found in the named queried sources as of 2026-08-21T06:32:19.484+00:00.","reason":null,"source_receipts":[{"observed_at":"2026-08-21T06:32:19.484+00:00","source":"crossref"},{"observed_at":"2026-08-21T06:32:16.066871+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-16T12:34:09.921853Z","title":"Engineering big data solutions,","venue":null,"work_id":"51b64cb3-da8d-41f1-bc6a-1e8c7acbad5e","year":2014},"citing_paper":{"arxiv_id":"2504.12517","last_updated":"2025-04-23T15:58:21Z","snapshot_observed_at":"2026-08-16T12:27:29.828080Z","submitted_at":"2025-04-16T22:30:54Z","title":"Code Improvement Practices at Meta","version":2},"reference_index":48,"source":"pdf_text","source_observed_at":"2026-08-16T12:34:09.891729Z"},"links":{"citing_paper":"/paper/2504.12517"},"observation_digest":"sha256:e6c6a001df1b84415776f15e0a8f72b4dd2a18c82f47f0a95942e39de201158f","observation_id":"8c1dab82-0251-4273-b97a-e75424caf28e","resolution":{"observed_at":"2026-08-16T12:34:09.926845Z","resolver_source":"raw_fallback","status":"verified_fuzzy"},"standing_notice":{"events":[],"observation":"No event found in the named queried sources as of 2026-08-21T06:32:19.484+00:00.","reason":null,"source_receipts":[{"observed_at":"2026-08-21T06:32:19.484+00:00","source":"crossref"},{"observed_at":"2026-08-21T06:32:16.066871+00:00","source":"retraction_watch"}],"state":"measured"}}],"paper":{"arxiv_id":"2504.12517","last_updated":"2025-04-23T15:58:21Z","latest_version":2,"primary_category":"cs.SE","snapshot_observed_at":"2026-08-16T12:27:29.828080Z","submitted_at":"2025-04-16T22:30:54Z","title":"Code Improvement Practices at Meta"},"reference_resolution":{"displayed":48,"state_counts":{"malformed_identifier":0,"metadata_mismatch":0,"parse_uncertain":0,"unresolved":7,"verified_exact":0,"verified_fuzzy":41},"total_outbound_references":48},"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-21T06:32:19.484+00:00","source":"crossref"},{"observed_at":"2026-08-21T06:32:16.066871+00:00","source":"retraction_watch"}],"thesis":"As of 22 August 2026, this Paper Citation Record lists 48 of 48 outbound references and 1 inbound Pith citation observation for arXiv:2504.12517."}