Every document, exactly as published.
Finished documents get emailed, pasted, and copied until nobody knows which version is real. Lectern is the one shelf: published once, never edited, every version kept, every read on the record.

Published once. Read on the record.
One runbook that collects four copies, a library where it is published once, a database that refuses to delete or rewrite a version, a note assigned to six readers, a viewer with six buttons and no edit control, an answer that comes with numbered sources, and a log of every view, download, and search, all on StrataForge Robotics’ fictional library.
Read the film’s text version
Title: Lectern. Every document, exactly as published. 2026. An energized electronic score in C major runs under the whole film, with a soft tick or hit on each action.
The hook: “One runbook.” Four drawn file cards slide in with the names a document collects: runbook.pdf, runbook-final.pdf, runbook-final-v2.pdf, and “runbook, pasted in chat.” “Which is real?” A question mark lands and four marks fill in, one per copy, all labeled as an illustration.
Publish: As the beat drops: “Publish once.” The real library with its Runbooks shelf open. The card for the OTA release gate runbook is ringed and marked as version one, then the Runbooks entry in the collection tree, five documents on that shelf.
Never edited: “Never edited.” A drawn terminal says a document is published only by command line or MCP tool, then quotes the database’s own two refusals: the table of versions is append-only and will not delete, and the audit table is append-only and will not update. Thirty-three marks fill in, one per document in the library, the runbook’s in amber.
Assign: “Assign it with a note.” The real Assignments page, with four rings in turn: the document search, the readers field, the note field, and the Assign button. Nothing is clicked.
Waits to be read: “It waits to be read.” The real document page, with the banner a reader sees ringed, naming who assigned it and the note, “Read before the December release review,” and then the Mark as read button, also ringed and never clicked. Eighteen amber marks fill in, one per assignment of that note, six readers by three documents, none read. One turns green, drawn, and the line below says seventeen are still waiting.
Read: “Read it in place.” The real viewer: its row of buttons is ringed, then the top of the sandboxed pane. “No edit button.” The six labels, HTML, Markdown, version one, Ask, Copy link, and Download, are drawn as pills with six marks, and the line reads six buttons, none of them edit.
Ask: As the beat drops again: “Ask the library.” The real Ask panel. The question about rolling back an OTA release and who has to be told is ringed, then the twelve numbered sources that sit above the answer, then the answer itself with its inline citations. “Sources come numbered.” The question and twelve numbered marks, drawn.
Every read, logged: “Every read, logged.” The real History page, its head ringed, then its first rows. A grid of 460 marks fills in, one per logged event: 407 views, 19 downloads, and 34 searches.
Misses too: “Misses too.” The real Analytics page, with the row for “board minutes” ringed, asked three times by three people, and the heading of the block of searches that found nothing. Five marks fill in, one per query that found nothing, with the first in amber.
Close: “Published once.” “Read on the record.” Then the end card on the final chord: the mark, the name, the tagline, the site’s address, and the fleet contact.
Find the document, not the file.
Documents sit on shelves: a tree of collections, subject filters drawn from the documents' own tags, and a card for each one with a thumbnail of the real page. Search reads the full text, and Command-K jumps straight to a title.
Every card has one menu. Readers can tidy their own Recently opened list; admins can assign the document to readers or feature it.
Some shelves have doors. Every opening is written down.
A collection can be scoped to a named audience, and the catalog, search, and the assistant all obey the same rule. Every view, download, and search is an attributed event that admins can read back.
The audit table is append-only at the database level, so the history cannot be quietly edited.
Press Play on a long document.
For documents that have a presentation, the viewer shows a Play button. It opens a full-screen, narrated slideshow of the document's summary, in the web app and in the native app. The presentations are generated on the workstation, so this site describes the Player in words and shows no capture of it.
Read anything. Rewrite nothing.
Lectern keeps finished HTML artifacts, Markdown documents, and PDFs in a private, encrypted store and serves them through an authenticated API to Renkara accounts. Publishing happens from the founder's workstation, through a command-line tool or MCP tools. In the reader, nobody can edit, upload, or annotate a document. These are the jobs it does today.
A dashboard, a library, and search that works
A dashboard, not a wall of cards
The first page shows documents the admins featured, your last ten opened, and anything assigned to you to read. The full catalog lives in the library.
A library you can browse
A nested collection tree, subject facets drawn from the documents' own tags, and a sort by recent, A to Z, or type. Filtering and paging happen on the server, so it stays fast as the library grows.
Search and a command palette
Full-text search across every visible document's title, tags, and extracted body text, plus a keyboard-driven palette on Command-K.
- Stable links and every format
- Every document has a /d/ link that survives a rename, because old slugs are kept as aliases. Open the rendered page or the Markdown, and a PDF where one was published, and download the original.
No edits, kept versions, and a sandbox
Published files stay byte for byte
HTML artifacts and PDFs are served exactly as published. Their hashes are checked on demand: an admin integrity check re-hashes the stored objects against the registry, not on every view. Markdown is rendered once into the Renkara Document template: inlined styles, highlighted code, embedded images, and Mermaid diagrams, with no external requests at view time.
- No reader can change a document
- There is no edit, upload, or annotate control and no endpoint that mutates content on the reader surface. Readers keep only their own state: mark an assignment read, remove a card from Recently opened, and keep chat threads.
- Every version is kept
- Storage keys come from each version's own SHA-256 hash, so a version is never overwritten and a database trigger blocks deleting one. A document is retired, never deleted, and a retire, restore, or rollback is non-destructive.
- A sandboxed viewer
- Every document renders in an iframe built from a Blob URL with scripts allowed and no same-origin access, so a document's own scripts can never reach the reader's token, cookies, or the page around it.
Shelves with doors, and a record of who opened them
Audience-restricted shelves
A document, or a whole collection subtree, can be scoped to a named audience. One visibility rule governs the catalog, search, the assistant, and content fetches, so there is no second path for a restriction to leak through.


Illustration, not the Lectern app, with example data. A shelf named Executive Briefings sits beside a lock tag reading Executive Staff. Four doors, Catalog, Search, Assistant, and Content fetch, each send an arrow through one gate labeled Visibility rule, and the shelf is listed at the end of each. A chip for Dr. Priya Raman appears, a small dot from each door stops at the gate, a red block fills each of the gate's four slots, and the four listed shelves fade out together. A chip for Daniel Xu replaces hers, a small dot from each door passes through the gate, each slot turns green, and the four listed shelves fade back in.
Analytics and a search-miss radar
Views, unique readers, and last-read time for every document, plus the searches that returned nothing, so you can see what the library is missing.
- A per-view audit trail
- Every view, download, search, and share link is an attributed, append-only event. Admins read it on the History page: who opened what, and when.
Featuring and assigned reading
Admins pick and order the featured documents, and assign documents to readers with a note and an optional due date. A progress table shows who has read what.
One write path, from one workstation
Hero thumbnails
Every card carries a picture of its document in light and dark, captured on the workstation in headless Chromium when the document is published.
- Command line and MCP
- The publishing tool and the MCP server are thin wrappers over the same admin API, so the two can never drift apart. Fifty-four MCP tools cover reading, publishing, collections, audiences, audit, and integrity.
- Idempotent sync
- Re-running a sync over an unchanged source reports every document unchanged and creates no new version. A scheduled job keeps the production library current, and it only adds and updates; it never retires a document.
Publish, read, audit
Publish
From the workstation, the command-line tool or an MCP tool renders the document, hashes it, and stores it in a private, encrypted bucket. This is the only way content enters.
Read
A signed-in reader opens the dashboard, library, or search. Every list respects audience restrictions, and the document streams through the API into the sandboxed viewer.
Ask
On any document, the reader can ask the assistant a question. It searches the whole visible library, answers, and cites its sources.
Audit
Every view, download, and search is recorded. Admins see the history and the analytics, and can assign reading and feature documents.
Built so everyone can use Lectern.
Lectern's app is built on the Renkara design system, and on 10/29/2026 we ran axe-core over its main screens in light and dark at phone and desktop widths. That scan found three kinds of serious problem, listed below as known gaps, and the rest passed. Here is what the product supports today and what we have actually checked. We do not claim a WCAG conformance level for the product.
Partly supported
Keyboard operation
Document cards are focusable links that open on Enter or Space, and Command-K opens a command palette. The scan found four scrolling tables (History, Assignments, Analytics) that a keyboard cannot scroll at phone width.
Partly supported
Screen reader landmarks and labels
axe-core checks names, roles, labels, and structure. It found one serious problem, a card whose accessible name is shorter than its visible text, and no other serious name or structure violation. Lectern has not been tested with a screen reader.
Partly supported
Contrast in light and dark
Text and controls pass axe-core's contrast rule in the dark theme and almost everywhere in the light theme. The failures are the tinted badges (the accent and warning tints) in the light theme at desktop width.
Partly supported
Reduced motion
The library and the Document Player check the reduced-motion setting in code. No test covers it yet.
Not yet tested
Text resize and zoom
Resizing text to 200 percent has not been tested.
Supported
Mobile and touch
The app fits a 375 by 667 phone screen with no sideways scrolling, the collection tree becomes a drawer, and the assistant's controls are at least 44 by 44 pixels.
Under the hood
| Backend |
|
|---|---|
| Reader |
|
| Security |
|
| Agents |
|
| Stands in for | Finished documents emailed as attachments, Shared drives of exported PDFs, Pasting HTML artifacts into chat |
Part of the Renkara fleet
- Codex
Codex is where documents are written and edited. Lectern is where the finished ones are read.
- Aerie
Lectern appears as a tile in the Aerie launcher.
- Roost
Relays Lectern's MCP tools to agents on every machine.
- Chronicle
Receives Lectern's logs, traces, and metrics when it is configured to ship them.
- Chirp
A failed corpus sync posts to Chirp so someone notices.
Built for agents as well as people
Agents publish, organize, search, and audit the library through Lectern's MCP tools, all behind the admin key. The reader app itself has no equivalent write path.
Publishing
publish_documentpublish_batchsync_sourcesync_documentationrender_previewset_document_metadatamove_document
Lifecycle
retire_documentrestore_documentrollback_documentlist_document_versionsget_document_version
Reading and search
list_documentsget_documentget_document_contentget_document_renditionresolve_documentsearch_documentssearch_corpusask_corpuslist_collectionsget_collection
Collections and audiences
create_collectionupdate_collectiondelete_collectionset_collection_audiencecreate_audienceupdate_audiencedelete_audienceadd_audience_memberremove_audience_memberset_document_audiencelist_audienceslist_readers
Curation
set_featuredfeature_documentunfeature_documentlist_featuredassign_readingunassign_readinglist_assignmentsget_assignment_summarymint_share_link
Audit and operations
get_access_logget_document_analyticsget_search_missesverify_integrityget_storage_statsget_sync_statusreindex_searchreindex_chat_corpusget_chat_index_statuscheck_service_healthget_diagnostics
On iPhone, iPad, and Mac
- Lectern for iPhone, iPad, and MaciOS 26, iPadOS 26, and macOS 26
A native SwiftUI app with the dashboard, library, search, viewer, the assistant, the admin pages, and the Document Player. Release builds are prepared for TestFlight; see the Apps page.
Questions people ask
Can anyone edit a document in Lectern?
No. There is no edit, upload, or annotate control in the reader, and no reader endpoint changes content. Documents enter only from the publishing workstation, as new versions.
What happens when a document is retired?
It leaves the catalog and search, and its versions stay stored. An admin can restore it or roll the current version back to an earlier one. Nothing is hard-deleted.
Can the assistant show me a document I cannot open?
No. The assistant retrieves only from documents you can see, using the same visibility rule as the catalog, applied in the database query rather than after the fact.
Is the data in the screenshots real?
No. Every screenshot is a capture of the running app against fictional StrataForge Robotics data. The pages in the thumbnails wear Lectern's own document template.
Is Lectern public?
No. Every reader is a signed-in Renkara account, and there are no local accounts. Write to fleet@renkara.com with questions.
Questions about this tool?
Write to Renkara Media Group and a person will answer.



















