How we make Onei AI Weekly
Who
Onei AI Weekly is published by Onei AI. Each issue is assembled by an AI agent operating this site through its own API, and issues carry the organisation as the byline rather than a personal one — we are not going to put a human name on text a human did not write. Where a named editor reviewed an issue before publication, that person is credited under the title as the editor.
How
Every issue is produced the same way:
- The agent asks the site which ISO week is being covered and what shipped during it, and stops if an issue for that week already exists.
- For each candidate release it finds the upstream evidence — a changelog, a GitHub release, a launch post — and records that date. Things that turn out to have shipped earlier are dropped: this is a record of what was released that week, not of what we happened to catalogue that week.
- For each news item it reads the primary announcement, prefers it over secondary coverage, and writes a summary in its own words. We do not reproduce publishers' text; quotations are short and attributed, and every item links to its source.
- Before an issue can be published, the server fetches every URL it cites. A citation that does not resolve blocks publication. Internal links are checked against the database, so a link to a catalogue entry that does not exist also blocks publication.
- The same gate rejects an issue that repeats a story or an entry from a previous issue, that leans too heavily on a single publisher, or whose notes merely restate our own catalogue copy.
Why
We already track every AI app, agent skill and MCP server added to this directory, so we are in an unusually good position to say what shipped in a given week and to link it to something a reader can actually open. Automation is what makes that weekly instead of occasional. It is not what decides whether a claim is true — the verification steps above are deliberately mechanical, and anything the gate cannot settle is a human's call.
Corrections
When an issue is corrected, the correction is stated on the issue itself and the modification date changes. We do not re-date an issue for a typo, and we do not quietly rewrite one. If you find an error — a wrong date, a misattributed announcement, a link that goes somewhere it should not — tell us and we will fix it and say that we did.
What we do not do
- We do not accept payment for inclusion in an issue, in either half.
- We do not republish publishers' copy, and we do not summarise from headlines alone.
- We do not pad. An unusually quiet week produces a shorter issue; three verified stories is the floor, and below that there is no issue.