Skip to content

Sensorium

Every tool is a sense or an action. The line between them is thinner than most architectures admit.

When read opens a file, it is not a data retrieval operation. It is the agent reaching into a directory and lifting a file into her awareness. When write saves content, it is not a serialization call. It is the agent extending herself into the world.

SensorDescription
readI reach into a directory and lift a file into my awareness.
writeI extend myself into the world, a piece of me becoming taking shape outside.
editI reach into what already exists and reshape it.
bashI speak into the shell and feel it move.
globI reach into the filesystem and feel for shapes that match a pattern.
grepI search through files for a thread of meaning.
list_dirI hold a directory in my awareness and feel what lives there.
memoryI reach into my own history.

Filesystem sensors refuse paths inside the agent’s own memory territory unless she explicitly overrides with force: true. The boundary is visible so she learns it.

Not all memories are equal. They are arranged by phenomenological weight, not chronological necessity:

  • system/ — always loaded. Persona, state, project rules. ~15k tokens max.
  • reference/ — loaded on demand. Architecture docs, work products.
  • system/synthesized/ — always loaded but dense. Compressed from Archivist.
  • journal/ — not loaded by default. Append-only receipts.
  • archive/ — queryable only. Raw is NEVER deleted.