Research / Systems

Systems

The machinery the questions are asked with.

These pages are here because the instruments shape the findings, and a finding is not reproducible if the instrument is undocumented. They have no place in the navigation. If the infrastructure itself becomes the thing under study, that changes.

Ref
Component
Kind
Documented
S-01

Arbor

An entity’s history, kept in a form that can be added to without being rewritten. Holds what happened, when, and by which process; refuses to hold conclusions about it.

writes
append-only items, four provenance fields required
reads
retrieval by origin, time, derivation depth
persists
everything; overflow is archived, never deleted
store
in service
2026-08-30
Architecture
S-02

Memory stores

What is written, when, and by whom. The write path is the part under study: most retrieval failures are decided before anything is retrieved.

writes
ingest v4 · verbatim origin, no paraphrase at write time
omits
confidence, by policy
store
in service
2026-09-08
Architecture
S-03

World state

The environment between sessions: what is still true when nothing is running. Interruption is applied here deliberately, and the resume diff is the measurement.

holds
place, open threads, standing facts
tested by
scheduled absence · see Experiment 02
environment
in service
2026-09-06
Architecture
S-04

Provenance mechanisms

The four required fields, how they are enforced, and the cases where an honest origin is unresolvable. Those are kept rather than tidied away.

mechanism
in service
2026-09-08
Architecture
S-05

Bridges

The paths in and out of the store, and the rule that governs them: anything arriving from outside is untrusted text. It can influence a conversation and never authority.

interface
in service
2026-09-09
Architecture
S-06

Control wall

A second wall, identical in mechanics, periodically cleared. Persistent against non-persistent, same surface. Unbuilt, by design, and listed here so that its absence is on the record.

environment
unbuilt
The box it runs on

Documented for the same reason as everything else

A single small server, no dependencies worth listing, and services that cannot reach anything they do not need. If this site is still standing in six months untouched, this is why.

hostone VPS, hardened, unattended upgrades, backups
edgeDNS proxied, wildcard origin certificate
static layerplain HTML and CSS; no build step
live layerstdlib-only service on localhost, proxied; ~11 MB resident
isolationno credentials, no outbound network, no filesystem outside its own directory
© 2026 Clark Glenn DavisSome continuities are not indexed.
Research / Systems

Systems

The machinery the questions are asked with.

The instruments shape the findings, and a finding is not reproducible if the instrument is undocumented. These pages have no place in the navigation.

S-01 · store2026-08-30

Arbor

An entity’s history, kept in a form that can be added to without being rewritten. Holds what happened, when, and by which process; refuses to hold conclusions about it.

writes · append-only items, four provenance fields
persists · everything; overflow archived, never deleted
S-02 · store2026-09-08

Memory stores

What is written, when, and by whom. The write path is the part under study: most retrieval failures are decided before anything is retrieved.

omits · confidence, by policy
S-03 · environment2026-09-06

World state

What is still true when nothing is running. Interruption is applied here deliberately, and the resume diff is the measurement.

S-04 · mechanism2026-09-08

Provenance mechanisms

The four required fields, how they are enforced, and the cases where an honest origin is unresolvable.

S-05 · interface2026-09-09

Bridges

The paths in and out of the store. Anything arriving from outside is untrusted text: it can influence a conversation and never authority.

S-06 · environmentunbuilt

Control wall

A second wall, identical in mechanics, periodically cleared. Unbuilt, by design, and listed so that its absence is on the record.

The box it runs on

A single small server, no dependencies worth listing, and services that cannot reach anything they do not need.

host · one VPS, hardened, backups
static · plain HTML and CSS, no build step
live · stdlib-only service on localhost, ~11 MB
isolation · no credentials, no outbound network
© 2026 C. G. DavisNot all indexed.