AI-Declaration.md
The AI-DECLARATION.md specification aims to enhance transparency in AI-generated code. It encourages developers to include a structured declaration file in their repositories to clarify AI usage. This initiative is designed to promote best practices while allowing creators to showcase their skills effectively.
- ▪The AI-DECLARATION.md file uses YAML frontmatter for structured fields and includes a required Notes section.
- ▪It defines various levels of AI involvement, ranging from none to auto, to categorize the extent of AI's role in the development process.
- ▪The specification also allows for the declaration of processes and components to provide granular details on AI's contribution.
Hacker News (Newest) files mainly under programming. We currently carry 5,306 of its stories.
Story provenance
Source · retrieval · rights · ranking — open for full record
inspect →
Story provenance
Attribution is not the same as permission. This drawer separates discovery metadata, excerpts, WeSearch-generated summaries, reuse status, and whether the publisher receives the visit. Nothing here claims a legal grant the publisher has not made.
Record
| Original publisher | GitHub |
| Canonical URL | https://github.com/DimwitLabs/AI-DECLARATION.md |
| Publication time | Sat, 23 May 2026 05:53:35 +0000 |
| Retrieval time | 2026-05-23T06:07:24.938Z |
| Last seen | 2026-05-23T06:07:24.938Z |
| Headline source | Publisher (no WeSearch rewrite) |
| Excerpt source | publisher body |
| Excerpt method | First ~120 words (~800 chars) of extracted publisher body, fair-use limited. |
| Summary | WeSearch · cerebras-chat (WeSearch summarizer) |
| Summary source text | contentText |
| Citation coverage | Summary is a WeSearch-generated derivative; primary citation is the original publisher URL. |
| Cluster | None |
| Cluster logic | Not yet clustered, or no peer story found in the clustering window. |
| Ranking reason | Story pages are not engagement-ranked. Hub feeds use recency, with optional source-diversified chronological ordering (cap consecutive stories per source). No personalized ranking. |
| Publisher visit | Yes — open original |
| Substitutes article? | No — link-out required for full text |
Rights status (four layers)
WeSearch handling by dimension
| Indexing | May the item be indexed (stored, ranked, made findable)? | Allowed |
| Snippet | May a short excerpt of the publisher's text be shown? | Allowed |
| AI summary | May WeSearch generate its own short summary of the article? | Limited |
| Retrieval / RAG | May the content be exposed for third-party retrieval-augmented generation? | Not asserted |
| Model training | May the content be used to train AI models? | Not asserted |
| Commercial reuse | May the content be reused commercially? | Not permitted |
Basis: Derived from the published RSS/Atom feed. Contact: [email protected]. Reviewed: 2026-07-24.
Opening excerpt (first ~120 words) tap to expand
AI-DECLARATION.md Summary AI-generated code is a reality of our time and it is both a blessing and a curse. The problem is not the code in itself but transparency and clarity. At least, that is the working theory of this specification. The suggestion is simple: to invite everyone to include a structured AI-DECLARATION.md file like they include other files in a repository to make the AI-usage crystal clear and, more importantly, to make it a widespread convention to do so. This is not to discourage usage of LLM- and other code-generation in the future. On the contrary, it is an enabler. When you declare what parts of the code were, in fact, generated, a skeptic can immediately look into just those parts to satisfy their urge to re-verify and double-check.
…
Excerpt limited to ~120 words for fair-use compliance. The full article is at GitHub.