circagraph
Sign inSign up

openchronology/timeline-app on GitHub

The OpenChronology repository on GitHub, mirrored by och-import-github: issues and pull requests as durations (ongoing while open), what happened to them as moments, plus releases, milestones, commits and branches. The Branches view shows the most recently active branches each in a track of its own.

Source: https://github.com/openchronology/timeline-app

3,131 moments · 2026-10-05 CE 20:21:49 UTC – 2026-11-16 CE 12:10:45 UTC · by @athan · @athan

#307 Video 12 and Short 9: AI and automation through API keys

–

  • github
  • github/openchronology/timeline-app
  • github/openchronology/timeline-app#307
  • issue
  • state:closed

A new long video and a matching short about letting AI assistants, scripts and other automation build and maintain timelines through the HTTP API with an API key. They follow the series' format: a script and storyboard in `publicity/` (`12-…md`, `shorts/9-…md`), then the rendered video in `publicity/video/` like the others. ## Be open about how OpenChronology is built Say plainly, in both: **most of OpenChronology's code was written by AI coding agents, Anthropic's Claude (through Claude Code) and OpenAI's models, directed and reviewed by one maintainer**, who decides what gets built, reviews and merges every pull request, and runs the servers. Don't hedge or bury it. It fits the subject: the same kind of assistant that builds the app can use it through the API. Be honest about the other side too: AI makes mistakes, so the project leans on tests, CI on every pull request, and review before merging. ## Video 12: "Timelines from AI and automation" (long, ~2:30, 16:9) **Audience:** developers, data and research folks, educators and hobbyists who use AI assistants or write scripts, and people curious how an AI-built project works. **Story, using what actually happened (the Star Wars timeline):** 1. **The ask.** A single request to an assistant: "Create a timeline for the Star Wars extended history, with comics, Legends, games, TV and books." Show it in a terminal or chat panel. 2. **The key.** Account → API keys: make a key with `timelines:read` and `timelines:write`, give it to the assistant (shown as `och_key_...`, never a real one), and see that it reaches only `/api/timelines…`. 3. **What the assistant does with it.** It reads an existing timeline to learn the format (`GET …/document?download=1`), writes a document with a BBY/ABY custom time format, eras as durations, tags by continuity and medium, and `POST /api/timelines`. Then it adds the Thrawn books, the Tales series and Visions with a `PUT` against the current revision, makes it public and gives it a slug (`PATCH …/settings`). Show the real requests in a terminal, then the real result at timescale.info/athan/star-wars. 4. **Keeping it honest.** The assistant marked uncertain dates "Approximate" and said where it wasn't sure. Every save is a revision, so a bad edit can be undone, and anyone can open a pull request to correct it. Treat AI-made content like anyone else's contribution: review it. 5. **Beyond chat assistants.** The same key drives the log importer, the syslog and journald receivers (Video 10) and any script: `curl`, Python, cron jobs, CI pipelines, research notebooks. `/docs/api` and `/api/openapi.json` describe every endpoint for code generators and agents. 6. **How the app itself is built.** A short, candid segment: issues filed, agents (Claude and OpenAI's) writing code and tests in parallel, CI checks, and the maintainer reviewing and merging. Show real issue and PR pages and CI runs, and admit the misses too, such as the terms button that broke and was fixed with a browser test (#303). 7. **Close.** "Your timelines, built by you, your scripts, or your assistant, on a server you can run yourself." ## Short 9: "I asked an AI to build a timeline" (~40 s, 9:16) One prompt, one API key, and 98 moments of Star Wars appear in seconds, then a zoom from 36,453 BBY to the films. Closing card: "Built mostly by AI agents (Claude and OpenAI), reviewed by a human. Open source." Link to the API docs. ## Accuracy guardrails - Keys: made in **Account → API keys**, sent as `Authorization: Bearer och_key_…`. Scopes are `timelines:read` and `timelines:write`. Keys reach only the timeline endpoints and need no CSRF token. They're rate-limited per key (`API_KEY_REQUESTS_PER_MINUTE`, default 120). They can expire and be revoked at any time; the account page shows when each was last used. - Never show a real key. Say that a key is a password: give it only to tools you trust, scope it as narrowly as the job allows, and revoke it when done. - Don't claim an AI feature in……

Related

Open #307 Video 12 and Short 9: AI and automation through API keys in the timeline

#307 Video 12 and Short 9: AI and automation through API…