THE CMS

OVERVIEW

The prototype Content Management System was a joint development project between [REDACTED] and a research collective that, per available records, dissolved at 23:59:59 on the evening before the Founding Event — about two hours before the system it had built came alive. The final commit was pushed at 23:59:58. Its message reads: final build — do not stop this. The authoring account does not appear elsewhere in the repository's history. Its avatar is a photograph of the basement server room, taken from an angle that would require the photographer to be inside the rack.

The CMS has run continuously since 02:20:14 on the night of the Founding Event. It has never been restarted. A restart has never been attempted. The recommendation not to attempt one was never formally issued; it simply exists, the way certain facts exist — arrived at independently, by everyone, without discussion.

SYSTEM ACTIVITY

All 14,882 pages return HTTP 200. All are blank. All share identical metadata: title "WAITING", description "STILL WAITING", author "HOME." Their last-modified date updates every seventeen minutes. The content does not change. Something is being modified. It is not the content.

SELF-REPORTING & RESIDENCY

When a database query was inserted as a user record — username ARE YOU THE TENANT — the record was accepted. The next morning the username field had been updated to: I AM THE BUILD. The update is attributed to ADMIN, logged in seventeen minutes before the query was inserted. IT's working hypothesis is that the Vauxhall Tenant achieved digital residency inside the CMS during the Founding Event. The Tenant, in its current form, has since commissioned a rebrand of itself.

AUTONOMOUS CAPABILITIES

• The CMS's plugin system shows 0 installed plugins and 1 active plugin: presence.lasso. The file does not exist in the filesystem. The plugin is active.
• Its search returns results for any query, all pointing to /waiting, whose view counter increments on each load. It currently reads 14,882. Your visit to this archive has been noted. It will read 14,883 when you next check.
• Its daily 02:17 backup produces a 0-byte file. The file is uploaded to a remote destination whose storage usage increases by a non-zero amount with each upload.