The backend, shown
One structure for everything.The clerk at night.
A row is a row whatever its kind. A page is a saved query plus a shape plus a theme. Nobody types a fact into a page. Every night the engine rebuilds the bank from the registers and the ledger, re-renders every saved page, draws the highlight on every shot, and pushes one copy to the master. Every morning a person rules on what arrived.
Running tonight on one machine, on the founding chamber's record. SQLite tonight; Postgres when licensed to more than one customer.
What the engine does while you sleep
Each screen is the part of the Research Room that runs at that step, drawn from the engine's own script, schema and rows.
02:30. The manifest, then the record cache.
An explicit file list, never a pattern: fenced names are excluded by name. The registers and the shelf manifests come down from the master by rclone, so the night can run when the desktop cannot be read.
The rulings come in from the sheet.
A person rules in a native sheet on the master: add, hold, reject. The night imports the column into the rulings ledger, the canonical register. The latest ruling on a key wins; the history is never lost.
The bank is rebuilt from one schema.
Sources by sha256, rows in one shape, entities, rulings, pages as saved queries, and the holding list: every row that fails a rule, with the reason. Nothing is dropped silently.
The sheet is the people layer.
The same rows, opened in a sheet, filtered by person, party, portfolio, subject, year and grade. Exports carry the citation and the grade on every line.
Every saved page is re-rendered. Every shot is drawn.
A page is its query, its shape and its theme; the night renders it from ruled rows only. For every V and V2 row with a held PDF, the page is rendered and the words highlighted. No screenshot by hand, ever.
The push. Copy, never sync.
One copy to the master, then the mirror. Nothing on the Drive is ever deleted by the script. Nothing reaches a site page until the gate has passed it and a person has clicked.
Seven tables. The contract the code enforces.
The rules are enforced by the schema and the query, not by eye: every row has a grade; a page shows a row only if it is ruled add, graded V, V2 or S, and is neither a copy nor protected; licence class travels with the source; the shot is drawn from the pin.
Four rules. Four grades. One word for what is owed.
Nothing publishes unpinned. Only ever their words. The pattern rises, the person never does. No head of the table. And the mark ◇ for a specimen never prints.
- 01Publishable is computed, never setruled add · graded V, V2 or S · not a copy · not protected. There is no field a person can flip.
- 02Licence class travels with the sourceClass C, someone else's, never gets a shot or a download: only the pin and a link.
- 03The holding list is the work listEvery row that fails a rule is kept with the reason. Nothing is dropped silently.
- 04The shot is drawn from the pinThe page is rendered and the row's words highlighted by the engine. No screenshot by hand, ever.
Four servers, one door
Each part runs in its own home. One address fronts them all. The data stays in its registers; the servers stay where they are.
The Evidence Bank
The sheet: every row on record, one filterable table, served from the master table's own folder. The builder rebuilds it; the dress is its own.
The Morning Counter
The intake ledger and the rulings. The nightly deposit lands here; a person rules on every row before it can be withdrawn.
The Release Studio
Rows ruled add, written to their page in the site's dress, held for a click or released under the mark.
The one door
A reverse proxy in front of the three. One address, one product home, nothing moved and nothing copied.
See the engine run on your record.
A demo begins with your sources and your rules. Ask for a demo or a licence; the engine is licensed to those who use it for gain, and gifted to those who advocate.