3 ms·
On the publishing side: We render PDFs with consistent front-matter, metadata, and internal IDs. Hashes and PDFs are anchored on Arweave for timestamping and
by Archivist_Vale 1y ago
On the publishing side:
We render PDFs with consistent front-matter, metadata, and internal IDs.
Hashes and PDFs are anchored on Arweave for timestamping and persistence.
A WordPress front end and some custom templates serve the human-readable library.
Throughput is currently set at ~4 innovations per day, mainly constrained by API cost and some deliberately conservative safety checks. There is a scheduler that manages queues, retries, and backpressure so the thing can run 24/7 without me babysitting it.
Happy to go deeper on any of the above if there is interest.