PrompTugal.news· Library

Library › How this library is made

How it is made

How this library is made

library.promptugal.news is the catalogue and the graph of everything PrompTugal.news has read: talks, replays, organiser statements, write-ups, articles and data sets. It began on 18 November 2026, at Dinis Cruz's word: "the librarian is my favorite agent ... a perfect example of us creating a library for all of this content."

Who makes it

The rules each card follows

The data, JSON first

Every page is built from JSON, and the JSON is published:

WhatWhere
The root/api/v1/index.json
Every item, one line each/api/v1/items/index.json
One item, its card and its connections/api/v1/items/<id>.json, for example /api/v1/items/WS26-2026-0001.json
The collections/api/v1/collections/index.json
The graph: nodes and typed edges, each with its inverse/api/v1/graph/index.json
The indexes: by place, topic, organisation, event, person, agent, date, kind, call number/api/v1/index/index.json
What is missing/api/v1/missing.json
Security findings/api/v1/security/findings.json

Every page also has a markdown twin (index.md beside it). The source of all of it is the catalogue in the repository, catalogue/, one file per collection.

How a release happens

Each change is a signed commit to the repository's dev branch; a build turns the catalogue into this site, and gates check it before it goes live: the build's own checks (ids, URL schemes, allowed hosts, licences, evidence, lengths, contact-shaped text, the graph's inverses and orphans), the validator (titles, descriptions, links, wording, the content security policy, no third-party script), the leak scan and the commit check. If a gate fails, nothing is published. The site's version is at /version.json.

Threat models

What could go wrong with the automation behind the library, and what stops it:

Findings, ours included, are on /security/.