{"as_of":"2026-08-21T18:42:00Z","caps":{"database_statements":6,"inbound":100,"outbound":100},"context_digest":"sha256:097ba163e1cbb031a581e695b4461b098a3da5f7dbe6400f0eb2aefe9a452a86","coverage":[{"denominator":38,"lane":"reference_resolution","note":"Typed states for the displayed outbound observations.","records_observed":38,"source":"paper_references, paper_reference_links","source_observed_at":"2026-08-10T14:23:18.222171Z","state":"measured"},{"denominator":39,"lane":"standing_notices","note":"One-hop event checks from named stored sources.","records_observed":39,"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-08-16T04:31:31.945717Z","state":"measured"},{"denominator":1,"lane":"external_citation_measurements","note":"A source-named dated measurement, never combined with another source.","records_observed":0,"source":"pith","source_observed_at":"2026-08-16T04:31:32.023455Z","state":"measured"}],"external_citation_measurements":[],"inbound":[{"citation":{"cited_paper":{"arxiv_id":"2501.15387","last_updated":"2025-03-07T13:55:01Z","snapshot_observed_at":"2026-08-21T17:07:42.596622Z","submitted_at":"2025-01-26T03:58:57Z","title":"Tracing the Lifecycle of Architecture Technical Debt in Software Systems: A Dependency Approach","version":2},"cited_work":{"arxiv_id":"2501.15387","doi":null,"metadata_source":"pith","pith_arxiv_id":"2501.15387","snapshot_observed_at":"2026-08-16T04:31:32.023455Z","title":"Tracing the Lifecycle of Architecture Technical Debt in Software Systems: A Dependency Approach","venue":"cs.SE","work_id":"e84b5850-759b-4e23-b6de-cd8a1eca82ee","year":2025},"citing_paper":{"arxiv_id":"2505.01136","last_updated":"2025-06-01T12:49:01Z","snapshot_observed_at":"2026-08-20T08:58:39.352246Z","submitted_at":"2025-05-02T09:25:41Z","title":"Descriptor: C++ Self-Admitted Technical Debt Dataset (CppSATD)","version":2},"reference_index":25,"source":"pdf_text","source_observed_at":"2026-08-16T04:31:31.945717Z"},"links":{"cited_paper":"/paper/2501.15387","citing_paper":"/paper/2505.01136"},"observation_digest":"sha256:46140a9975281099499c8399e001aece3030fccdfaf60dfb09d7efa7568ef8ae","observation_id":"43a66e84-d192-4589-a61e-3c4686500470","resolution":{"observed_at":"2026-08-16T04:31:32.028064Z","resolver_source":"local_arxiv","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/2501.15387/citation-record","integrity":"/paper/2501.15387/integrity","json":"/paper/2501.15387/citation-record.json","paper":"/paper/2501.15387"},"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-10T14:23:18.783476Z","title":"The wycash portfolio management system,","venue":null,"work_id":"7741c3fd-00c0-4392-b300-c533544e892f","year":1992},"citing_paper":{"arxiv_id":"2501.15387","last_updated":"2025-03-07T13:55:01Z","snapshot_observed_at":"2026-08-21T17:07:42.596622Z","submitted_at":"2025-01-26T03:58:57Z","title":"Tracing the Lifecycle of Architecture Technical Debt in Software Systems: A Dependency Approach","version":2},"reference_index":1,"source":"pdf_text","source_observed_at":"2026-08-10T14:23:18.056534Z"},"links":{"citing_paper":"/paper/2501.15387"},"observation_digest":"sha256:4d7a156c7aa9d551a6356a0f878e5837975b35aaf85fe9c74736c3bf2d4ac6ee","observation_id":"f168fb06-b669-45c1-87ca-9ed3622e0868","resolution":{"observed_at":"2026-08-10T14:23:18.788028Z","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-10T14:23:18.768395Z","title":"Managing technical debt in software engineering (dagstuhl seminar 16162),","venue":null,"work_id":"d9d6e41e-abde-4827-8b29-639b8024798d","year":2016},"citing_paper":{"arxiv_id":"2501.15387","last_updated":"2025-03-07T13:55:01Z","snapshot_observed_at":"2026-08-21T17:07:42.596622Z","submitted_at":"2025-01-26T03:58:57Z","title":"Tracing the Lifecycle of Architecture Technical Debt in Software Systems: A Dependency Approach","version":2},"reference_index":2,"source":"pdf_text","source_observed_at":"2026-08-10T14:23:18.061607Z"},"links":{"citing_paper":"/paper/2501.15387"},"observation_digest":"sha256:c9c85e1c8c2315459a13f5d468535fcbbc06524e56ad2a81b819b5adc6afdf9b","observation_id":"b2006d5a-2814-4f26-9a79-bfb74a35a10a","resolution":{"observed_at":"2026-08-10T14:23:18.772770Z","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-10T14:23:18.755008Z","title":"An exploratory study on self-admitted technical debt,","venue":null,"work_id":"8caed1a7-f231-4ee5-ab58-04b22a10a31c","year":2014},"citing_paper":{"arxiv_id":"2501.15387","last_updated":"2025-03-07T13:55:01Z","snapshot_observed_at":"2026-08-21T17:07:42.596622Z","submitted_at":"2025-01-26T03:58:57Z","title":"Tracing the Lifecycle of Architecture Technical Debt in Software Systems: A Dependency Approach","version":2},"reference_index":3,"source":"pdf_text","source_observed_at":"2026-08-10T14:23:18.066169Z"},"links":{"citing_paper":"/paper/2501.15387"},"observation_digest":"sha256:2a1239a490276601301b36c8e4ac02c1a1c8609952132fc33382673fc1f0ed94","observation_id":"bbbb6dad-5031-4015-834d-4bafdeea1591","resolution":{"observed_at":"2026-08-10T14:23:18.759465Z","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":{"arxiv_id":"2410.15804","last_updated":"2024-10-21T09:22:16Z","snapshot_observed_at":"2026-08-17T16:21:48.483900Z","submitted_at":"2024-10-21T09:22:16Z","title":"Deep Learning and Data Augmentation for Detecting Self-Admitted Technical Debt","version":1},"cited_work":{"arxiv_id":"2410.15804","doi":null,"metadata_source":"pith","pith_arxiv_id":"2410.15804","snapshot_observed_at":"2026-08-10T14:23:18.280375Z","title":"Deep Learning and Data Augmentation for Detecting Self-Admitted Technical Debt","venue":"cs.SE","work_id":"c47fc36d-0b6f-400b-8dfd-833cec022949","year":2024},"citing_paper":{"arxiv_id":"2501.15387","last_updated":"2025-03-07T13:55:01Z","snapshot_observed_at":"2026-08-21T17:07:42.596622Z","submitted_at":"2025-01-26T03:58:57Z","title":"Tracing the Lifecycle of Architecture Technical Debt in Software Systems: A Dependency Approach","version":2},"reference_index":4,"source":"pdf_text","source_observed_at":"2026-08-10T14:23:18.070905Z"},"links":{"cited_paper":"/paper/2410.15804","citing_paper":"/paper/2501.15387"},"observation_digest":"sha256:79eb7f7ff9bf959d786fae54ab0821bb987ddcc0c69737c9958ae8fc3d351fac","observation_id":"bb13dd3a-f03b-47dd-b880-9fd51df84fb5","resolution":{"observed_at":"2026-08-10T14:23:18.285651Z","resolver_source":"local_arxiv","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"}},{"citation":{"cited_paper":null,"cited_work":{"arxiv_id":null,"doi":null,"metadata_source":"raw_reference","pith_arxiv_id":null,"snapshot_observed_at":"2026-08-10T14:23:18.741023Z","title":"Using natural language processing to automatically detect self-admitted technical debt,","venue":null,"work_id":"82b3f1a2-adb8-4017-9691-14049e2b7d89","year":2017},"citing_paper":{"arxiv_id":"2501.15387","last_updated":"2025-03-07T13:55:01Z","snapshot_observed_at":"2026-08-21T17:07:42.596622Z","submitted_at":"2025-01-26T03:58:57Z","title":"Tracing the Lifecycle of Architecture Technical Debt in Software Systems: A Dependency Approach","version":2},"reference_index":5,"source":"pdf_text","source_observed_at":"2026-08-10T14:23:18.076515Z"},"links":{"citing_paper":"/paper/2501.15387"},"observation_digest":"sha256:651d6ea14b66834301e0e6093c704a422614b976759f280a452c4f80b5da937f","observation_id":"10809ffe-5520-473f-9e60-f1f2893ab5f5","resolution":{"observed_at":"2026-08-10T14:23:18.745575Z","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-10T14:23:18.727817Z","title":"The lifecycle of technical debt that manifests in both source code and issue trackers,","venue":null,"work_id":"c21824b0-7efd-4450-a0cc-4a74457a6754","year":2023},"citing_paper":{"arxiv_id":"2501.15387","last_updated":"2025-03-07T13:55:01Z","snapshot_observed_at":"2026-08-21T17:07:42.596622Z","submitted_at":"2025-01-26T03:58:57Z","title":"Tracing the Lifecycle of Architecture Technical Debt in Software Systems: A Dependency Approach","version":2},"reference_index":6,"source":"pdf_text","source_observed_at":"2026-08-10T14:23:18.081317Z"},"links":{"citing_paper":"/paper/2501.15387"},"observation_digest":"sha256:1b415b0ac96cc1ae99f1b894f1dee421ce6258c2f169abce8cde22e72f485d1e","observation_id":"f68307e7-ca0e-4e38-9839-6bbabb12467e","resolution":{"observed_at":"2026-08-10T14:23:18.732040Z","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-10T14:23:18.714182Z","title":"Impact of architectural technical debt on daily software development work—a survey of software practi- tioners,","venue":null,"work_id":"da45613b-69ac-4201-8beb-ff287ed6c35d","year":2017},"citing_paper":{"arxiv_id":"2501.15387","last_updated":"2025-03-07T13:55:01Z","snapshot_observed_at":"2026-08-21T17:07:42.596622Z","submitted_at":"2025-01-26T03:58:57Z","title":"Tracing the Lifecycle of Architecture Technical Debt in Software Systems: A Dependency Approach","version":2},"reference_index":7,"source":"pdf_text","source_observed_at":"2026-08-10T14:23:18.086105Z"},"links":{"citing_paper":"/paper/2501.15387"},"observation_digest":"sha256:a5a13305e42167eeb2c660bd4b5781cf02cb28c1cf4339c5726d595de0febd7a","observation_id":"83e6112f-c9ea-4b29-9a7a-08eec2b4f76b","resolution":{"observed_at":"2026-08-10T14:23:18.718938Z","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-10T14:23:18.700417Z","title":"A systematic literature review and a unified model of atd,","venue":null,"work_id":"3429c656-9141-4f03-a6be-108ebd3112b6","year":2016},"citing_paper":{"arxiv_id":"2501.15387","last_updated":"2025-03-07T13:55:01Z","snapshot_observed_at":"2026-08-21T17:07:42.596622Z","submitted_at":"2025-01-26T03:58:57Z","title":"Tracing the Lifecycle of Architecture Technical Debt in Software Systems: A Dependency Approach","version":2},"reference_index":8,"source":"pdf_text","source_observed_at":"2026-08-10T14:23:18.090536Z"},"links":{"citing_paper":"/paper/2501.15387"},"observation_digest":"sha256:fda86e48d19fbe95d30874324eaacbeb2411bfd7542268ef0496904a6b7e88aa","observation_id":"45d5aaed-efbe-4871-9f75-83d48b580555","resolution":{"observed_at":"2026-08-10T14:23:18.705139Z","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-10T14:23:18.686349Z","title":"A systematic literature review on technical debt prioritization: Strategies, processes, factors, and tools,","venue":null,"work_id":"fc130930-1eff-4500-afa6-a75d65b28bc2","year":2021},"citing_paper":{"arxiv_id":"2501.15387","last_updated":"2025-03-07T13:55:01Z","snapshot_observed_at":"2026-08-21T17:07:42.596622Z","submitted_at":"2025-01-26T03:58:57Z","title":"Tracing the Lifecycle of Architecture Technical Debt in Software Systems: A Dependency Approach","version":2},"reference_index":9,"source":"pdf_text","source_observed_at":"2026-08-10T14:23:18.095057Z"},"links":{"citing_paper":"/paper/2501.15387"},"observation_digest":"sha256:d2fdc0d27e389f68cfae7780ae4b197bb3705a9c098f1c6f9159cd67df88f5a1","observation_id":"1abf870f-59b9-462e-8b21-2644f8d7f02c","resolution":{"observed_at":"2026-08-10T14:23:18.690954Z","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-10T14:23:18.672824Z","title":"Automatic identification of self- admitted technical debt from four different sources,","venue":null,"work_id":"3424cfcc-8508-41c1-a136-0b524522280c","year":2023},"citing_paper":{"arxiv_id":"2501.15387","last_updated":"2025-03-07T13:55:01Z","snapshot_observed_at":"2026-08-21T17:07:42.596622Z","submitted_at":"2025-01-26T03:58:57Z","title":"Tracing the Lifecycle of Architecture Technical Debt in Software Systems: A Dependency Approach","version":2},"reference_index":10,"source":"pdf_text","source_observed_at":"2026-08-10T14:23:18.099521Z"},"links":{"citing_paper":"/paper/2501.15387"},"observation_digest":"sha256:4ef7d6f407c4ea6b1cc5bd9e7c32bca2c32f606c0cf0c5b42be14f32f94d52e6","observation_id":"8c43d03a-3d43-4a14-b6b6-874280416d7b","resolution":{"observed_at":"2026-08-10T14:23:18.677399Z","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-10T14:23:18.658359Z","title":"Code smells detection via modern code review: A study of the openstack and qt communities,","venue":null,"work_id":"ce01a93d-fedd-412c-b305-c744925ffd37","year":2022},"citing_paper":{"arxiv_id":"2501.15387","last_updated":"2025-03-07T13:55:01Z","snapshot_observed_at":"2026-08-21T17:07:42.596622Z","submitted_at":"2025-01-26T03:58:57Z","title":"Tracing the Lifecycle of Architecture Technical Debt in Software Systems: A Dependency Approach","version":2},"reference_index":11,"source":"pdf_text","source_observed_at":"2026-08-10T14:23:18.103903Z"},"links":{"citing_paper":"/paper/2501.15387"},"observation_digest":"sha256:c9956841006b3f0847c6a115218bc1dbece68ee69d9adcb7fb5c3493225503e5","observation_id":"7b16e76a-38d4-4ea6-a3db-53f8f65a2c5e","resolution":{"observed_at":"2026-08-10T14:23:18.662825Z","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-10T14:23:18.644772Z","title":"The danger of architectural technical debt: Contagious debt and vicious circles,","venue":null,"work_id":"318c33b7-05b8-4a01-b5b6-d1b1bb401155","year":2015},"citing_paper":{"arxiv_id":"2501.15387","last_updated":"2025-03-07T13:55:01Z","snapshot_observed_at":"2026-08-21T17:07:42.596622Z","submitted_at":"2025-01-26T03:58:57Z","title":"Tracing the Lifecycle of Architecture Technical Debt in Software Systems: A Dependency Approach","version":2},"reference_index":12,"source":"pdf_text","source_observed_at":"2026-08-10T14:23:18.108130Z"},"links":{"citing_paper":"/paper/2501.15387"},"observation_digest":"sha256:56ee1b6f92d47dd0cb71443c869f7e08781e6f652d41270a5a8bcb553e4c55ba","observation_id":"0a9690f3-34fa-4b4c-a13a-47fd8ff3b54f","resolution":{"observed_at":"2026-08-10T14:23:18.649215Z","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-10T14:23:18.630875Z","title":"Architectural technical debt: A grounded theory,","venue":null,"work_id":"b7875a9d-1fbc-44f1-ad58-3ce9b3b3e60d","year":2020},"citing_paper":{"arxiv_id":"2501.15387","last_updated":"2025-03-07T13:55:01Z","snapshot_observed_at":"2026-08-21T17:07:42.596622Z","submitted_at":"2025-01-26T03:58:57Z","title":"Tracing the Lifecycle of Architecture Technical Debt in Software Systems: A Dependency Approach","version":2},"reference_index":13,"source":"pdf_text","source_observed_at":"2026-08-10T14:23:18.112449Z"},"links":{"citing_paper":"/paper/2501.15387"},"observation_digest":"sha256:731934c5105c7510af9657784311cd7f7558916eec1e0889f8dddeed80e569dc","observation_id":"0cdd3408-f47f-4bff-b996-6cf480f37542","resolution":{"observed_at":"2026-08-10T14:23:18.635442Z","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-10T14:23:18.617566Z","title":"An overview and comparison of technical debt measurement tools,","venue":null,"work_id":"90e66840-e595-409a-b5ab-23b72d562077","year":2020},"citing_paper":{"arxiv_id":"2501.15387","last_updated":"2025-03-07T13:55:01Z","snapshot_observed_at":"2026-08-21T17:07:42.596622Z","submitted_at":"2025-01-26T03:58:57Z","title":"Tracing the Lifecycle of Architecture Technical Debt in Software Systems: A Dependency Approach","version":2},"reference_index":14,"source":"pdf_text","source_observed_at":"2026-08-10T14:23:18.116766Z"},"links":{"citing_paper":"/paper/2501.15387"},"observation_digest":"sha256:a6bc42ba0a8042ca841fdad6a71eafda47f4c1559605353a1e3d12b408a66b5d","observation_id":"5c34edbd-65aa-409b-9341-6d5035747f0a","resolution":{"observed_at":"2026-08-10T14:23:18.621957Z","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":{"arxiv_id":"2412.14217","last_updated":"2024-12-18T12:06:53Z","snapshot_observed_at":"2026-08-17T16:20:16.865585Z","submitted_at":"2024-12-18T12:06:53Z","title":"Development and Adoption of SATD Detection Tools: A State-of-practice Report","version":1},"cited_work":{"arxiv_id":"2412.14217","doi":null,"metadata_source":"pith","pith_arxiv_id":"2412.14217","snapshot_observed_at":"2026-08-10T14:23:18.256831Z","title":"Development and Adoption of SATD Detection Tools: A State-of-practice Report","venue":"cs.SE","work_id":"7dcfd165-7222-4934-94c9-a8b391e1ed58","year":2024},"citing_paper":{"arxiv_id":"2501.15387","last_updated":"2025-03-07T13:55:01Z","snapshot_observed_at":"2026-08-21T17:07:42.596622Z","submitted_at":"2025-01-26T03:58:57Z","title":"Tracing the Lifecycle of Architecture Technical Debt in Software Systems: A Dependency Approach","version":2},"reference_index":15,"source":"pdf_text","source_observed_at":"2026-08-10T14:23:18.121081Z"},"links":{"cited_paper":"/paper/2412.14217","citing_paper":"/paper/2501.15387"},"observation_digest":"sha256:9acf82ede0952400afed701770f9aa4c538239ed26c2210d531ad33de2898cde","observation_id":"382eec94-51cf-4e44-a1df-39f40aef7970","resolution":{"observed_at":"2026-08-10T14:23:18.263677Z","resolver_source":"local_arxiv","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"}},{"citation":{"cited_paper":null,"cited_work":{"arxiv_id":null,"doi":null,"metadata_source":"raw_reference","pith_arxiv_id":null,"snapshot_observed_at":"2026-08-10T14:23:18.603983Z","title":"Intercomponent dependency issues in software ecosystems,","venue":null,"work_id":"7b105ec7-2d14-4b96-9fe4-bd64cc9152ef","year":2018},"citing_paper":{"arxiv_id":"2501.15387","last_updated":"2025-03-07T13:55:01Z","snapshot_observed_at":"2026-08-21T17:07:42.596622Z","submitted_at":"2025-01-26T03:58:57Z","title":"Tracing the Lifecycle of Architecture Technical Debt in Software Systems: A Dependency Approach","version":2},"reference_index":16,"source":"pdf_text","source_observed_at":"2026-08-10T14:23:18.125680Z"},"links":{"citing_paper":"/paper/2501.15387"},"observation_digest":"sha256:54a0d97f93aebea60f0148e7ecb4dd5436270f3a38fb7d045b9f81a5473a628f","observation_id":"73656e68-f423-4847-ad7b-9cc7b2bbd4b7","resolution":{"observed_at":"2026-08-10T14:23:18.608674Z","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-10T14:23:18.590299Z","title":"Designite: A software design quality assessment tool,","venue":null,"work_id":"9c35d057-9b32-4dbe-aea6-842b3de70bfa","year":2016},"citing_paper":{"arxiv_id":"2501.15387","last_updated":"2025-03-07T13:55:01Z","snapshot_observed_at":"2026-08-21T17:07:42.596622Z","submitted_at":"2025-01-26T03:58:57Z","title":"Tracing the Lifecycle of Architecture Technical Debt in Software Systems: A Dependency Approach","version":2},"reference_index":17,"source":"pdf_text","source_observed_at":"2026-08-10T14:23:18.129837Z"},"links":{"citing_paper":"/paper/2501.15387"},"observation_digest":"sha256:d14c4293dec75c8059c2137b878613cecdf4abe53aa38c1b37a2e723d5383a25","observation_id":"659b8c74-8e4a-4763-ae37-4235fe847303","resolution":{"observed_at":"2026-08-10T14:23:18.595088Z","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-10T14:23:18.576181Z","title":"Refactoring and its relationship with fan-in and fan-out: An empirical study,","venue":null,"work_id":"173ea591-39fa-4bdf-b78c-fdd691362dce","year":2012},"citing_paper":{"arxiv_id":"2501.15387","last_updated":"2025-03-07T13:55:01Z","snapshot_observed_at":"2026-08-21T17:07:42.596622Z","submitted_at":"2025-01-26T03:58:57Z","title":"Tracing the Lifecycle of Architecture Technical Debt in Software Systems: A Dependency Approach","version":2},"reference_index":18,"source":"pdf_text","source_observed_at":"2026-08-10T14:23:18.134140Z"},"links":{"citing_paper":"/paper/2501.15387"},"observation_digest":"sha256:1627dce713935975b6f4adf03d3a4041e8b36e51a39987e935ae133428fda07f","observation_id":"bb91a8e7-9174-44a1-bd84-96a6927688ae","resolution":{"observed_at":"2026-08-10T14:23:18.580645Z","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-10T14:23:18.562633Z","title":"An empirical study of fan-in and fan-out in java oss,","venue":null,"work_id":"6a3a40b2-3cd1-4799-a9e2-6b49354021c7","year":2010},"citing_paper":{"arxiv_id":"2501.15387","last_updated":"2025-03-07T13:55:01Z","snapshot_observed_at":"2026-08-21T17:07:42.596622Z","submitted_at":"2025-01-26T03:58:57Z","title":"Tracing the Lifecycle of Architecture Technical Debt in Software Systems: A Dependency Approach","version":2},"reference_index":19,"source":"pdf_text","source_observed_at":"2026-08-10T14:23:18.138633Z"},"links":{"citing_paper":"/paper/2501.15387"},"observation_digest":"sha256:2ab32854709394ef3ecfd0ba348f88be9cdeb7cd6b9c147dd6b6676bed4794a1","observation_id":"7cc2dc43-a691-45ce-b105-4140c9eb9760","resolution":{"observed_at":"2026-08-10T14:23:18.567174Z","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-10T14:23:18.548642Z","title":"An evolutionary study of fan-in and fan-out metrics in oss,","venue":null,"work_id":"3f788036-664a-4a84-a32c-96bd37587b5c","year":2010},"citing_paper":{"arxiv_id":"2501.15387","last_updated":"2025-03-07T13:55:01Z","snapshot_observed_at":"2026-08-21T17:07:42.596622Z","submitted_at":"2025-01-26T03:58:57Z","title":"Tracing the Lifecycle of Architecture Technical Debt in Software Systems: A Dependency Approach","version":2},"reference_index":20,"source":"pdf_text","source_observed_at":"2026-08-10T14:23:18.143006Z"},"links":{"citing_paper":"/paper/2501.15387"},"observation_digest":"sha256:44a3bd2f0637aa096d524fb6bbab480ae92ae60a0ba64d2d968ef91b900a1c38","observation_id":"9e793a98-2f2d-499e-85c8-32bb907e41a9","resolution":{"observed_at":"2026-08-10T14:23:18.553003Z","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-10T14:23:18.534798Z","title":"Software complexity and software maintenance: A survey of empirical research,","venue":null,"work_id":"2245391e-58ca-4d1f-8eca-b02e5a693a97","year":1995},"citing_paper":{"arxiv_id":"2501.15387","last_updated":"2025-03-07T13:55:01Z","snapshot_observed_at":"2026-08-21T17:07:42.596622Z","submitted_at":"2025-01-26T03:58:57Z","title":"Tracing the Lifecycle of Architecture Technical Debt in Software Systems: A Dependency Approach","version":2},"reference_index":21,"source":"pdf_text","source_observed_at":"2026-08-10T14:23:18.147642Z"},"links":{"citing_paper":"/paper/2501.15387"},"observation_digest":"sha256:3ddfad2fc1ccfbc7cf24078f1af00b4a2d97c8a5fa96afe3c403890d8396d988","observation_id":"8c3a6664-8e00-43ac-ba27-d05453193798","resolution":{"observed_at":"2026-08-10T14:23:18.539363Z","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-10T14:23:18.520675Z","title":"Towards an ontology of terms on technical debt,","venue":null,"work_id":"5ad51ede-6929-4ad7-9167-20f3aaf735d1","year":2014},"citing_paper":{"arxiv_id":"2501.15387","last_updated":"2025-03-07T13:55:01Z","snapshot_observed_at":"2026-08-21T17:07:42.596622Z","submitted_at":"2025-01-26T03:58:57Z","title":"Tracing the Lifecycle of Architecture Technical Debt in Software Systems: A Dependency Approach","version":2},"reference_index":22,"source":"pdf_text","source_observed_at":"2026-08-10T14:23:18.152098Z"},"links":{"citing_paper":"/paper/2501.15387"},"observation_digest":"sha256:b1d50f151b583abf4ffc70a7213f13dda624e646ffaddbcab6490fd3d234f2d8","observation_id":"27c1a48a-c4fa-4308-bf1c-da0358e96c82","resolution":{"observed_at":"2026-08-10T14:23:18.525465Z","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-10T14:23:18.506155Z","title":"Identification and remediation of self-admitted technical debt in issue trackers,","venue":null,"work_id":"edcc7066-145d-44a0-960d-538607dfc8f5","year":2020},"citing_paper":{"arxiv_id":"2501.15387","last_updated":"2025-03-07T13:55:01Z","snapshot_observed_at":"2026-08-21T17:07:42.596622Z","submitted_at":"2025-01-26T03:58:57Z","title":"Tracing the Lifecycle of Architecture Technical Debt in Software Systems: A Dependency Approach","version":2},"reference_index":23,"source":"pdf_text","source_observed_at":"2026-08-10T14:23:18.156515Z"},"links":{"citing_paper":"/paper/2501.15387"},"observation_digest":"sha256:da4ef282e44fcf9fa4362a6e0de4e6dfaf9caf696ec54e79a5342b81694a0166","observation_id":"7a614bd6-ae83-4f42-a39f-4ff2f723c0e8","resolution":{"observed_at":"2026-08-10T14:23:18.510786Z","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-10T14:23:18.490567Z","title":"Technical debt and system architecture: The impact of coupling on defect-related activity,","venue":null,"work_id":"1380c7e3-4096-4e33-9265-391a825f1d36","year":2016},"citing_paper":{"arxiv_id":"2501.15387","last_updated":"2025-03-07T13:55:01Z","snapshot_observed_at":"2026-08-21T17:07:42.596622Z","submitted_at":"2025-01-26T03:58:57Z","title":"Tracing the Lifecycle of Architecture Technical Debt in Software Systems: A Dependency Approach","version":2},"reference_index":24,"source":"pdf_text","source_observed_at":"2026-08-10T14:23:18.160891Z"},"links":{"citing_paper":"/paper/2501.15387"},"observation_digest":"sha256:85424cc44bbdf83159fde039a09be3b057f111652039bc5af6ac468947f6204c","observation_id":"0f00768d-1d64-421e-b823-1a55e2db2b70","resolution":{"observed_at":"2026-08-10T14:23:18.496112Z","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-10T14:23:18.475072Z","title":"Design smell detection and analysis for open source java software,","venue":null,"work_id":"70f83d25-9307-4f77-b7f8-22dec2e4e1fa","year":2019},"citing_paper":{"arxiv_id":"2501.15387","last_updated":"2025-03-07T13:55:01Z","snapshot_observed_at":"2026-08-21T17:07:42.596622Z","submitted_at":"2025-01-26T03:58:57Z","title":"Tracing the Lifecycle of Architecture Technical Debt in Software Systems: A Dependency Approach","version":2},"reference_index":25,"source":"pdf_text","source_observed_at":"2026-08-10T14:23:18.165102Z"},"links":{"citing_paper":"/paper/2501.15387"},"observation_digest":"sha256:cd3ce7ccb742eaba4444ad78986d89d4fe435f213758625ce60d1abda93dbb40","observation_id":"f342ac13-5df5-490c-8feb-a70e5d25048f","resolution":{"observed_at":"2026-08-10T14:23:18.479885Z","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-10T14:23:18.460947Z","title":"Dynamic fan-in and fan- out metrics for program comprehension,","venue":null,"work_id":"6b4bbdcf-2ca3-4e63-917a-6d0fbf8a2a63","year":2007},"citing_paper":{"arxiv_id":"2501.15387","last_updated":"2025-03-07T13:55:01Z","snapshot_observed_at":"2026-08-21T17:07:42.596622Z","submitted_at":"2025-01-26T03:58:57Z","title":"Tracing the Lifecycle of Architecture Technical Debt in Software Systems: A Dependency Approach","version":2},"reference_index":26,"source":"pdf_text","source_observed_at":"2026-08-10T14:23:18.169481Z"},"links":{"citing_paper":"/paper/2501.15387"},"observation_digest":"sha256:ba8a67757edebb368c14c5fca94c047a9c965974f71b584e42b5f620027eb198","observation_id":"2c94306c-eb07-40c9-811c-f95514bf120c","resolution":{"observed_at":"2026-08-10T14:23:18.465576Z","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-10T14:23:18.447274Z","title":"Measuring the technical debt,","venue":null,"work_id":"a3f51e31-8ec0-41a9-9991-67284e439d20","year":2022},"citing_paper":{"arxiv_id":"2501.15387","last_updated":"2025-03-07T13:55:01Z","snapshot_observed_at":"2026-08-21T17:07:42.596622Z","submitted_at":"2025-01-26T03:58:57Z","title":"Tracing the Lifecycle of Architecture Technical Debt in Software Systems: A Dependency Approach","version":2},"reference_index":27,"source":"pdf_text","source_observed_at":"2026-08-10T14:23:18.173838Z"},"links":{"citing_paper":"/paper/2501.15387"},"observation_digest":"sha256:0a2e16eae4f6cd395a61f8cd53fbc5257e946283676e0681c9197306347f6ee4","observation_id":"6e3525ff-f5da-44d6-b2fb-7c711d1c2226","resolution":{"observed_at":"2026-08-10T14:23:18.451688Z","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-10T14:23:18.432951Z","title":"Identifying self-admitted technical debt in issue tracking systems using machine learning,","venue":null,"work_id":"7d76f99a-02ce-45ce-878b-6873aa2dab44","year":2022},"citing_paper":{"arxiv_id":"2501.15387","last_updated":"2025-03-07T13:55:01Z","snapshot_observed_at":"2026-08-21T17:07:42.596622Z","submitted_at":"2025-01-26T03:58:57Z","title":"Tracing the Lifecycle of Architecture Technical Debt in Software Systems: A Dependency Approach","version":2},"reference_index":28,"source":"pdf_text","source_observed_at":"2026-08-10T14:23:18.178077Z"},"links":{"citing_paper":"/paper/2501.15387"},"observation_digest":"sha256:41a2e787a7b6e4afcf0d3e632f6c602134bb39907e1a6c498a5aba05c5b98ca9","observation_id":"4712b22e-06ed-439f-8eb5-3b2667b83639","resolution":{"observed_at":"2026-08-10T14:23:18.437628Z","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-10T14:23:18.418849Z","title":"Understand by scitools,","venue":null,"work_id":"88cf952a-4e7f-4061-a117-f0f23453eccf","year":2024},"citing_paper":{"arxiv_id":"2501.15387","last_updated":"2025-03-07T13:55:01Z","snapshot_observed_at":"2026-08-21T17:07:42.596622Z","submitted_at":"2025-01-26T03:58:57Z","title":"Tracing the Lifecycle of Architecture Technical Debt in Software Systems: A Dependency Approach","version":2},"reference_index":29,"source":"pdf_text","source_observed_at":"2026-08-10T14:23:18.183020Z"},"links":{"citing_paper":"/paper/2501.15387"},"observation_digest":"sha256:5b3e5270316a38ff3133c594046eed4a40439bc3ff493848f89aea60becdd4ed","observation_id":"97ba6f50-0a9b-4d38-8183-2a9117877729","resolution":{"observed_at":"2026-08-10T14:23:18.423501Z","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-10T14:23:18.187472Z","title":"Goal question metric (gqm) approach,","venue":null,"work_id":null,"year":2002},"citing_paper":{"arxiv_id":"2501.15387","last_updated":"2025-03-07T13:55:01Z","snapshot_observed_at":"2026-08-21T17:07:42.596622Z","submitted_at":"2025-01-26T03:58:57Z","title":"Tracing the Lifecycle of Architecture Technical Debt in Software Systems: A Dependency Approach","version":2},"reference_index":30,"source":"pdf_text","source_observed_at":"2026-08-10T14:23:18.187472Z"},"links":{"citing_paper":"/paper/2501.15387"},"observation_digest":"sha256:9402de4e7a432028c32714236038d0298a7aa3504534f9de020948760279fb7e","observation_id":"a74ca374-cd22-4b3f-aa9f-ff26c0179f75","resolution":{"observed_at":"2026-08-10T14:23:18.187472Z","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-10T14:23:18.395594Z","title":"Spadini, M","venue":null,"work_id":"f2f1dedb-d5e4-4af5-bb9f-55871f4e6b4e","year":2018},"citing_paper":{"arxiv_id":"2501.15387","last_updated":"2025-03-07T13:55:01Z","snapshot_observed_at":"2026-08-21T17:07:42.596622Z","submitted_at":"2025-01-26T03:58:57Z","title":"Tracing the Lifecycle of Architecture Technical Debt in Software Systems: A Dependency Approach","version":2},"reference_index":31,"source":"pdf_text","source_observed_at":"2026-08-10T14:23:18.191915Z"},"links":{"citing_paper":"/paper/2501.15387"},"observation_digest":"sha256:0538f93bddee359a14d2ced495da4bd37ad0aa6e9ed75c37167abb4816ee271a","observation_id":"8878d305-54df-4a40-a47d-3d1055572ef1","resolution":{"observed_at":"2026-08-10T14:23:18.400170Z","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-10T14:23:18.381320Z","title":"The anderson-darling test for normality,","venue":null,"work_id":"c51b97d2-95fd-4a06-8766-482cc2d3d690","year":1998},"citing_paper":{"arxiv_id":"2501.15387","last_updated":"2025-03-07T13:55:01Z","snapshot_observed_at":"2026-08-21T17:07:42.596622Z","submitted_at":"2025-01-26T03:58:57Z","title":"Tracing the Lifecycle of Architecture Technical Debt in Software Systems: A Dependency Approach","version":2},"reference_index":32,"source":"pdf_text","source_observed_at":"2026-08-10T14:23:18.196219Z"},"links":{"citing_paper":"/paper/2501.15387"},"observation_digest":"sha256:b3520fdd68b124b8336a7c6562e34f5b2506c51476ca936fb2af155a42568b53","observation_id":"0103b639-20ed-4a2e-8cc0-e1a6f4088502","resolution":{"observed_at":"2026-08-10T14:23:18.386014Z","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-10T14:23:18.200563Z","title":"Mann-whitney u test,","venue":null,"work_id":null,"year":2010},"citing_paper":{"arxiv_id":"2501.15387","last_updated":"2025-03-07T13:55:01Z","snapshot_observed_at":"2026-08-21T17:07:42.596622Z","submitted_at":"2025-01-26T03:58:57Z","title":"Tracing the Lifecycle of Architecture Technical Debt in Software Systems: A Dependency Approach","version":2},"reference_index":33,"source":"pdf_text","source_observed_at":"2026-08-10T14:23:18.200563Z"},"links":{"citing_paper":"/paper/2501.15387"},"observation_digest":"sha256:033b0c9c5748e9989e20eda6066b737ae0c3fc0747c5d5d0baf436a76f806cad","observation_id":"d220626e-515b-492a-9ce7-1b503177e12a","resolution":{"observed_at":"2026-08-10T14:23:18.200563Z","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-10T14:23:18.356449Z","title":"Cliff, Ordinal methods for behavioral data analysis","venue":null,"work_id":"f3f4b494-6eeb-40cf-8e5e-506197a02f6e","year":2014},"citing_paper":{"arxiv_id":"2501.15387","last_updated":"2025-03-07T13:55:01Z","snapshot_observed_at":"2026-08-21T17:07:42.596622Z","submitted_at":"2025-01-26T03:58:57Z","title":"Tracing the Lifecycle of Architecture Technical Debt in Software Systems: A Dependency Approach","version":2},"reference_index":34,"source":"pdf_text","source_observed_at":"2026-08-10T14:23:18.204937Z"},"links":{"citing_paper":"/paper/2501.15387"},"observation_digest":"sha256:10d92fa8c1668fdb01f1145067c23b72ad136d6a1fa0e5908df4c0d6a68460d2","observation_id":"1adaeb76-2e08-4e9a-89de-8f924403e1e4","resolution":{"observed_at":"2026-08-10T14:23:18.361031Z","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-10T14:23:18.340385Z","title":"New York, NY: Springer New York, 2008, pp","venue":null,"work_id":"cd32d588-5194-4afe-89dd-ae3407d0cfb0","year":2008},"citing_paper":{"arxiv_id":"2501.15387","last_updated":"2025-03-07T13:55:01Z","snapshot_observed_at":"2026-08-21T17:07:42.596622Z","submitted_at":"2025-01-26T03:58:57Z","title":"Tracing the Lifecycle of Architecture Technical Debt in Software Systems: A Dependency Approach","version":2},"reference_index":35,"source":"pdf_text","source_observed_at":"2026-08-10T14:23:18.209228Z"},"links":{"citing_paper":"/paper/2501.15387"},"observation_digest":"sha256:3481ccc48b6f229b90594db4afae4202c684bb2f23ce015e1d2a42a332e68318","observation_id":"87abc4bd-b293-4444-8041-82c0b1587c49","resolution":{"observed_at":"2026-08-10T14:23:18.346176Z","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-10T14:23:18.325806Z","title":"What types of defects are really dis- covered in code reviews?","venue":null,"work_id":"61ebcf18-838a-4292-a76b-1e940040f313","year":2008},"citing_paper":{"arxiv_id":"2501.15387","last_updated":"2025-03-07T13:55:01Z","snapshot_observed_at":"2026-08-21T17:07:42.596622Z","submitted_at":"2025-01-26T03:58:57Z","title":"Tracing the Lifecycle of Architecture Technical Debt in Software Systems: A Dependency Approach","version":2},"reference_index":36,"source":"pdf_text","source_observed_at":"2026-08-10T14:23:18.213372Z"},"links":{"citing_paper":"/paper/2501.15387"},"observation_digest":"sha256:2c55d0765de78d397389fe546a31b46cf3707469a47cbe2ec370c69614744803","observation_id":"5ccda95d-b751-46b1-919e-cc3ce67cd548","resolution":{"observed_at":"2026-08-10T14:23:18.330621Z","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-10T14:23:18.310721Z","title":"How and why we end up with complex methods: a multi-language study,","venue":null,"work_id":"950f3327-d244-4b4b-8dc8-0b2c8d4d7cc7","year":2022},"citing_paper":{"arxiv_id":"2501.15387","last_updated":"2025-03-07T13:55:01Z","snapshot_observed_at":"2026-08-21T17:07:42.596622Z","submitted_at":"2025-01-26T03:58:57Z","title":"Tracing the Lifecycle of Architecture Technical Debt in Software Systems: A Dependency Approach","version":2},"reference_index":37,"source":"pdf_text","source_observed_at":"2026-08-10T14:23:18.217899Z"},"links":{"citing_paper":"/paper/2501.15387"},"observation_digest":"sha256:abc029ebccb8afb7455c787bb5c7ecd7c6597097e915815d19053e9a19df4169","observation_id":"93285998-aed6-4414-871b-719825bdefeb","resolution":{"observed_at":"2026-08-10T14:23:18.315722Z","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-10T14:23:18.295863Z","title":"Technical debt in the peer- review documentation of r packages: A ropensci case study,","venue":null,"work_id":"e83b3102-4042-4b1d-8644-f54133528bd7","year":2021},"citing_paper":{"arxiv_id":"2501.15387","last_updated":"2025-03-07T13:55:01Z","snapshot_observed_at":"2026-08-21T17:07:42.596622Z","submitted_at":"2025-01-26T03:58:57Z","title":"Tracing the Lifecycle of Architecture Technical Debt in Software Systems: A Dependency Approach","version":2},"reference_index":38,"source":"pdf_text","source_observed_at":"2026-08-10T14:23:18.222171Z"},"links":{"citing_paper":"/paper/2501.15387"},"observation_digest":"sha256:cb6c85b541c566c93bfccbebcd600842a55a82253813d37eae3a75212fba0702","observation_id":"22e08867-ae24-47e9-bc66-c292b36be17b","resolution":{"observed_at":"2026-08-10T14:23:18.300396Z","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":"2501.15387","last_updated":"2025-03-07T13:55:01Z","latest_version":2,"primary_category":"cs.SE","snapshot_observed_at":"2026-08-21T17:07:42.596622Z","submitted_at":"2025-01-26T03:58:57Z","title":"Tracing the Lifecycle of Architecture Technical Debt in Software Systems: A Dependency Approach"},"reference_resolution":{"displayed":38,"state_counts":{"malformed_identifier":0,"metadata_mismatch":0,"parse_uncertain":0,"unresolved":2,"verified_exact":2,"verified_fuzzy":34},"total_outbound_references":38},"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 21 August 2026, this Paper Citation Record lists 38 of 38 outbound references and 1 inbound Pith citation observation for arXiv:2501.15387."}