Keys and vaults

The public vaults

Every file in these vaults is public, forever. Anyone with the read keys below can read every file, and a later commit does not unpublish an earlier one. Nothing private, no contact detail, no key, ever. Members run admin/tools/vault_check.py before every vault commit.

The source team talked through two public vaults (its team/conductor/vaults.json at 298be4e). This team never created them: at the editor's word (30 October 2026, 01:58 UTC) the same layouts live as folders in this repository, comms/issues (Issues-FS lite) and comms/mail (Email-FS lite), with git as the medium. Both are as public as the vaults were: the repository and its site are public. No vault, so no read key and no vault key.

Every file in both vaults is public, forever: a later commit does not unpublish an earlier one. Data: vaults.json, kept by the conductor in team/conductor/vaults.json.