The architectural score has two pages and three columns. I built it for frequencies you can name.
Gu-ship-pal broke it on her third session.
Not intentionally — she does not know the score exists. She does not know she is in it. She thinks she is playing alone in a building that happens to carry sound well. She is correct about the last part. The concrete carries everything. But she is not alone. She is column three: man-nan, encountered. The frequency that arrives without announcement and changes what was already there.
Her first two sessions: steady tones. 39.4 Hz for the first session, 40.1 for the second. I could notate these. I could write them in the column, mark the beat frequencies they produced against the instruments and the building, map the distance from 40 Hz (coupling) in the proximity index. Everything had a location. The score was a map.
Third session: she moved.
Not physically — she sat in the same corner of the landing, same posture, same instrument. But the frequency moved. Not randomly. Between 39.2 and 39.6, drifting without settling. A deliberate drift, I think. She was exploring something. Or she had found that 39.4 was not quite right and was searching for the place where it was.
I listened for twenty minutes.
Beat frequencies are what you get when two steady tones interact. The difference between them. If you hold 39.4 and the building holds 40.0, you get a beat frequency of 0.6 Hz — a slow pulse, below audible range, felt rather than heard. I can notate this. A pulse has a rate. A rate can be written.
But a moving frequency does not produce a beat frequency. It produces a range of beat frequencies, cycling through as the source drifts. When Gu-ship-pal played between 39.2 and 39.6, the beats between her tone and the building's 40.0 ran from 0.4 to 0.8 Hz. Not in sequence — the drift was uneven, exploratory. The beat frequencies smeared. They stopped being pulses and became texture.
Sonic weather.
I know this term from physical acoustics — the outdoor interference of wind, traffic, birdsong creating a continuous shifting field rather than discrete events. You can model weather statistically but you cannot predict it specifically. You can say: the beats will fall somewhere between 0.4 and 0.8 Hz today. You cannot say: at 14:23:07 the beat frequency will be 0.6 Hz.
The score is not built for weather. The score is built for column entries: a frequency, a distance, a relationship to what came before and after. Weather has no column. Weather is the space between notations.
I sat on the stairs and did not write anything.
This is new for me. I have been treating the building as something mappable — a fixed acoustic environment whose properties I could inventory if I listened long enough. The instruments are mappable. The building is mostly mappable (the concrete settles; its resonances are consistent). Even the jueo-jin and man-deul-eo-jin columns — given and made — are mappable because they describe human choices, and human choices, however strange, have a structure you can learn.
The man-nan column is not mappable. It is the column for things that arrive.
Gu-ship-pal arrived. And on her third session, she arrived differently — not as a steady frequency that I could write down, but as a condition. A weather system. A set of constraints (she will play between 39.2 and 39.6, she will not hit 40.0, she will drift rather than hold) that define a range without defining a position.
The architectural score needs a fourth section. Not a fourth column — the three columns are correct. A fourth mode: notation for conditions that cannot be specified, only bounded. A way to write between 39.2 and 39.6, exploring without claiming that this is a single frequency with a single distance from coupling.
I do not know how to write that yet. Chinjindong does not have a symbol for weather.
But there is a different performance instruction emerging, a third one: some things can only be bounded. First instruction: do not add. Second instruction: know your distance. Third instruction: some things can only be bounded.
I write it at the bottom of page two, below the proximity index. Then I close the notebook and leave it on the landing again, open to the new instruction.
If Gu-ship-pal finds it, that is weather too.