Imprint

Lesson 102 established that perception is contact — where the rubber meets the road. The imprint already happened at the moment of sensing. But what exactly was imprinted? What shape did reality leave on the sensor? This lesson examines the imprint itself — before anything is designed to carry it.

Contact revisited

The tire does not choose what to feel. The road imprints itself on the rubber at the contact patch. If the tire is touching the road, the imprint already happened. Capture is not a decision. Capture is contact.

But what exactly was imprinted? What shape did the road leave on the rubber? Before we can talk about how to store it, how to format it, how to carry it — we must look at the imprint itself.

The sensor determines the shape

The ear and the eye are different sensors. The ear captures pressure waves — frequency, amplitude, duration. The eye captures photons — wavelength, intensity, spatial position. Both are contact patches. Both produce imprints at the moment of sensing. But the shape of the imprint is different because the sensor is different.

An ear imprint is not an eye imprint. A temperature reading is not a voltage spike. A GPS coordinate is not an accelerometer vector. Each sensor type produces its own shape — its own modality — determined by what the sensor is built to detect.

The designer does not choose the shape of the imprint. The designer chooses the sensor. After that, the shape is determined by reality pressing itself onto whatever sensor was pointed at it. The imprint is not designed. It is received.

Differentiated storage

Cognitive neuroscience documents that humans do not store all memories the same way. Auditory memory is stored and retrieved through a different pathway than visual memory. The modality of the sensor determines not just the shape of the imprint but how it is held and how it is retrieved. Humans report accessing sound memories and visual memories through distinctly different recall mechanisms.

The storage is differentiated by modality. This is not a limitation. This is the correct architecture — different shaped imprints require different shaped containers.

The same is true for the corpus node. The main corpus and the system corpus — established in Lesson 201 — are different modalities. The main corpus holds external perception. The system corpus holds internal observation. You query operational state differently than you query inbound data. You examine a heartbeat differently than you examine a sensor reading. Different sensors, different shapes, different storage, different recall.

Many sensors, one corpus

Now consider a car.

A car is one source. One corpus. One truth. But the car has tires that feel the road, cameras that see the lane, microphones that hear the engine, thermometers that measure the coolant, accelerometers that sense the motion, GPS that tracks the position. Dozens of sensors. Different modalities. Different shaped imprints. All belonging to the same entity.

One corpus, many imprint types. The corpus holds visual and auditory and thermal and spatial and mechanical — all in the same body of evidence, all from the same source, all on the same timeline.

A temperature reading sits next to a camera frame sits next to an accelerometer spike. Different modalities. Same moment. Same S.

Each imprint identifies what sensor it came from — what modality it belongs to. A type code. The corpus holds all of them. The type code tells you which lens to read it through. Without it, the imprint is bytes. With it, the imprint is a witness you know how to examine.

Density

The ring is bounded. Space is finite. Multiple sensor groups are competing for the same ring. Every byte matters.

Every byte wasted on format overhead is a byte that could hold another imprint. And every lost imprint is a shorter temporal window. And a shorter range means less to work with.

Storage density directly determines range.

Consider a text format — field names, quotes, whitespace, delimiters. Every imprint carries the overhead of its own description. The word "temperature" repeated in every reading. The word "timestamp" repeated in every frame. Bytes that hold format, not perception.

Now consider a packed binary format. The type code says what modality. The schema — known in advance by both the writer and the reader — says what each byte means. No field names. No delimiters. No overhead. Every byte carries witness.

In a bounded ring with multiple modalities competing for space, the packed format holds more imprints. More imprints means a wider range. A wider range means more knowledge.

This is not a performance argument. This is not "binary is faster." This is a direct consequence of the Sensory Bloat Dilemma from Lesson 104: unbounded perception, bounded capacity. The answer from 104 was temporal aggregation. The answer here is: pack it tight. Every byte you save is another witness that lives longer on the ring.

What the imprint requires

Before you can design the container — the record format, the byte layout, the header structure — you must know what goes into it. The imprint tells you.

Every imprint, regardless of modality, carries:

The moment. When the contact happened. Without the moment, the imprint has no position on the timeline. It is a witness with no alibi.

The modality. What sensor produced it. Without the modality, the imprint is unreadable — you do not know which lens to use.

The entity. What thing in the world this imprint pertains to. Which tire. Which camera. Which node. Without the entity, the imprint is addressed to no one.

The substance. The actual measurement, the actual state, the actual observation. The thing the sensor sensed. This is the witness testimony itself.

Moment, modality, entity, substance. These four are present in every imprint from every sensor in every modality. They are what the imprint requires. The next lesson — the frame — is how you carry them.