Monorepo for Aesthetic.Computer
aesthetic.computer
feat: beef up folk songs paper + move build status to bottom of index
Folk songs paper:
- Subtitle now references notepat.com
- Abstract rewritten in first-person with platter cross-refs (whistlegraph, plork, OS)
- Added 4 full NOTE:word encoding examples (Ode to Joy, Amazing Grace, Arirang, Sakura)
- New "Songs as Cards" subsection: cards as printable folk song decks, tappable URLs
- Expanded bare-metal section: classroom scenario (30 laptops, different folk traditions), offline operation (no WiFi needed, songs on boot partition, 89MB OS)
- Added platter references (plork, whistlegraph, pieces papers)
Index: moved build telemetry panel below the colophon, just above the footer.
Caddyfile: updated to match lith server changes (TLS, cache headers).
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
+137
-16
+54
-4
papers/arxiv-folk-songs/folk-songs-cards.tex
+54
-4
papers/arxiv-folk-songs/folk-songs-cards.tex
···
54
54
\href{https://papers.aesthetic.computer}{\includegraphics[height=9em]{pals}}\par\vspace{0.1em}
55
55
{\acbold\fontsize{18pt}{22pt}\selectfont\color{acdark} Playable Folk Songs}\par
56
56
\vspace{0.1em}
57
-
{\fontsize{9pt}{11pt}\selectfont\color{acpink} Oral Tradition Meets the Browser Keyboard}\par
57
+
{\fontsize{9pt}{11pt}\selectfont\color{acpink} Oral Tradition Meets the Browser Keyboard on notepat.com}\par
58
58
\vspace{0.4em}
59
59
{\normalsize\color{cyan!70!blue}\href{https://prompt.ac/@jeffrey}{\textbf{@jeffrey}}}\par
60
60
{\small\color{acgray} Aesthetic.Computer}\par
···
64
64
\vspace{0.15em}
65
65
\colorbox{yellow!60}{\small\color{red!80!black}\textbf{\textit{working draft --- not for citation}}}\par
66
66
\vspace{0.1em}
67
-
{\footnotesize\color{acgray} March 2026 · \href{https://github.com/whistlegraph/aesthetic-computer/commit/809be4868}{809be4868}}\par
67
+
{\footnotesize\color{acgray} March 2026 · \href{https://github.com/whistlegraph/aesthetic-computer/commit/20720999b}{20720999b}}\par
68
68
\vspace{0.1em}
69
69
{\footnotesize\color{acgray}\href{https://papers.aesthetic.computer/folk-songs-26-arxiv-da.pdf}{Dansk} · \href{https://papers.aesthetic.computer/folk-songs-26-arxiv-es.pdf}{Español} · \href{https://papers.aesthetic.computer/folk-songs-26-arxiv-zh.pdf}{{\accjk 中文}}}\par
70
70
\end{center}
···
123
123
124
124
The absence of rhythm information is deliberate. In oral tradition, rhythm belongs to the performer, not the score~\citep{lomax1968folk}. The encoding captures \emph{what} to play; the player decides \emph{how}.
125
125
126
+
\subsection{Extended Examples}
127
+
128
+
\textbf{Ode to Joy} (Beethoven, adapted from folk hymn tradition):
129
+
\begin{lstlisting}[style=notepat]
130
+
E:Freu- E:-de F:schö- G:-ner G:Göt- F:-ter-
131
+
E:fun- D:-ken E:Toch- C:-ter E:aus
132
+
D:E- C:-ly- D:si- E:-um
133
+
\end{lstlisting}
134
+
135
+
\textbf{Amazing Grace} (pentatonic, American):
136
+
\begin{lstlisting}[style=notepat]
137
+
D:A- G:-ma- B:-zing G:grace B:how A:sweet
138
+
G:the B:sound D:that E:saved D:a
139
+
B:wretch G:like B:me
140
+
\end{lstlisting}
141
+
142
+
\textbf{Arirang} (Korean, pentatonic):
143
+
\begin{lstlisting}[style=notepat]
144
+
E:A- G:-ri- A:rang E:a- G:-ri- A:rang
145
+
B:a- A:-ra- G:-ri- E:-yo
146
+
\end{lstlisting}
147
+
148
+
\textbf{Sakura} (Japanese, in mode):
149
+
\begin{lstlisting}[style=notepat]
150
+
E:Sa- E:-ku- F:ra E:sa- E:-ku- F:ra
151
+
A:ya- A:-yo- B:i A:no
152
+
\end{lstlisting}
153
+
154
+
Each encoding fits in a URL. The first four notes of ``Twinkle Twinkle'' are addressable as \texttt{notepat.com?song=C:Twin-\%20C:-kle\%20G:twin-\%20G:-kle}. The song is the address. The address is the score.
155
+
156
+
\subsection{Songs as Cards}
157
+
158
+
The cards format of this paper---4$\times$6 inches, designed for phones---means each encoded melody can appear on a single card, tappable at the bottom URL. A teacher could print a deck of folk song cards, hand one to each student, and the student taps the URL to load the song on their phone or laptop. The card is the program; the URL is the executable; the student is the performer.
159
+
160
+
This connects to the whistlegraph's core property: a score that teaches you how to play it~\citep{scudder2026whistlegraph}. The whistlegraph does this visually (draw the line, sing the note). \np{} does it textually (read the syllable, press the key). Both are self-documenting performance formats that require no teacher beyond the artifact itself.
161
+
126
162
\section{A Catalog of Playable Melodies}
127
163
128
164
We surveyed folk song collections from multiple traditions and selected melodies optimized for \np{}'s two-octave grid. Selection criteria: pitch range $\leq$\,15 semitones, pentatonic or simple diatonic scale, and cultural recognizability.
···
209
245
210
246
\section{The Bare-Metal Folk Instrument}
211
247
212
-
\np{} runs not only in browsers but on bare metal---a 987-line QuickJS port that boots as PID~1 on AC Native OS~\citep{scudder2026os}. A laptop running \np{} on bare metal is, in a literal sense, a folk instrument: a single-purpose device for playing songs, with no operating system, no desktop, no distractions.
248
+
\np{} runs not only in browsers but on bare metal---a 987-line QuickJS port that boots as PID~1 on AC Native OS~\citep{scudder2026os}. A surplus ThinkPad running \np{} on bare metal is, in a literal sense, a folk instrument: a single-purpose device for playing songs, with no desktop environment, no app store, no distractions.
249
+
250
+
The boot sequence: power on, kernel loads (7.3 seconds), the screen says ``hi @alice,'' and \np{} is playing. The student's name is spoken aloud by text-to-speech. The keyboard lights up with the first note of the song. There is nothing else to do, nowhere else to go. The laptop is the instrument.
251
+
252
+
\subsection{Why Bare Metal Matters for Folk Songs}
213
253
214
-
The convergence is complete: folk songs, designed to be played on the simplest available instrument, running on the simplest possible computer---a Linux kernel, a framebuffer, and a keyboard.
254
+
The PLOrk model~\citep{scudder2026plork} required custom hardware: hemispherical speakers, audio interfaces, dedicated laptops. The cost was prohibitive for most schools. AC Native OS inverts this: it runs on surplus commodity hardware---retired corporate laptops available for \$30--80---and transforms them into single-purpose instruments.
255
+
256
+
A classroom of 30 bare-metal \np{} devices, each loaded with a different folk song from a different tradition, is a folk orchestra. Each student learns their song, then the class performs together. The Korean student plays Arirang. The American student plays Amazing Grace. The Japanese student plays Sakura. The instruments are identical; the songs are culturally specific; the ensemble is global.
257
+
258
+
This is the scenario described in the companion paper on laptop orchestras~\citep{scudder2026plork}---but applied specifically to folk music, where the repertoire is public domain, culturally significant, and structurally suited to the instrument.
259
+
260
+
\subsection{Offline Operation}
261
+
262
+
The bare-metal \np{} requires no internet connection. Songs can be pre-loaded on the boot partition in \texttt{config.json}. A teacher prepares a USB drive with a set of folk songs, flashes it onto 30 laptops, and the classroom is ready. No WiFi, no accounts, no cloud services. The song files are kilobytes. The entire OS is 89\,MB.
263
+
264
+
This matters for the contexts where folk music education is most needed: schools without reliable internet, community centers without IT support, rural areas without broadband. The folk song and the folk instrument share a design constraint: they must work with what is available.
215
265
216
266
\section{Future Work}
217
267
+56
-6
papers/arxiv-folk-songs/folk-songs.tex
+56
-6
papers/arxiv-folk-songs/folk-songs.tex
···
94
94
\includegraphics[height=4em]{pals}\par\vspace{0.5em}
95
95
{\acbold\fontsize{22pt}{26pt}\selectfont\color{acdark} Playable Folk Songs}\par
96
96
\vspace{0.2em}
97
-
{\aclight\fontsize{11pt}{13pt}\selectfont\color{acpink} Oral Tradition Meets the Browser Keyboard}\par
97
+
{\aclight\fontsize{11pt}{13pt}\selectfont\color{acpink} Oral Tradition Meets the Browser Keyboard on notepat.com}\par
98
98
\vspace{0.6em}
99
99
{\normalsize\href{https://prompt.ac/@jeffrey}{@jeffrey}}\par
100
100
{\small\color{acgray} Aesthetic.Computer}\par
···
113
113
114
114
\begin{quote}
115
115
\small\noindent\textbf{Abstract.}
116
-
Folk songs evolved to be playable without notation, memorizable without instruments, and forkable without permission. These properties---constrained pitch range, repetitive structure, oral transmissibility---make folk melodies structurally ideal for a browser-based keyboard synthesizer.
116
+
Folk songs evolved to be playable without notation, memorizable without instruments, and forkable without permission. These properties---constrained pitch range, repetitive structure, oral transmissibility---make folk melodies structurally ideal for \np{}.com, a browser-based chromatic keyboard synthesizer built inside \ac{}~\citep{scudder2026ac}.
117
117
118
-
This paper describes the integration of playable folk songs into \np{}.com, a chromatic keyboard instrument that maps QWERTY keys to musical notes. We encode folk melodies in a lightweight \texttt{NOTE:word} format that pairs each pitch with its lyric syllable, creating a guided performance mode where the instrument teaches the song one note at a time.
118
+
I encode folk melodies in a lightweight \texttt{NOTE:word} format that pairs each pitch with its lyric syllable, creating a guided performance mode where the instrument teaches the song one note at a time. The encoding is URL-safe, human-readable, and forkable---copy it, change a note, share a new link. The ``oral tradition'' becomes a tradition of hyperlinks.
119
119
120
-
We survey folk melody collections suitable for this encoding, analyze why folk songs' structural constraints align with keyboard-as-instrument interfaces, and argue that the folk process---variation, selection, oral transmission---has a natural digital analogue in URL-shareable, forkable song encodings.
120
+
I survey folk melody collections from American, European, East Asian, and African traditions, analyze why their structural constraints align with keyboard-as-instrument interfaces~\citep{scudder2026notepat}, and describe how \np{} runs on bare metal via AC Native OS~\citep{scudder2026os}---a surplus laptop that boots directly into a folk instrument. The cards format of this paper (4$\times$6 inch, phone-sized) is itself a playable artifact: each song encoding is a tappable URL.
121
121
\end{quote}
122
122
\vspace{0.5em}
123
123
}]
···
167
167
168
168
The absence of rhythm information is deliberate. In oral tradition, rhythm belongs to the performer, not the score~\citep{lomax1968folk}. The encoding captures \emph{what} to play; the player decides \emph{how}.
169
169
170
+
\subsection{Extended Examples}
171
+
172
+
\textbf{Ode to Joy} (Beethoven, adapted from folk hymn tradition):
173
+
\begin{lstlisting}[style=notepat]
174
+
E:Freu- E:-de F:schö- G:-ner G:Göt- F:-ter-
175
+
E:fun- D:-ken E:Toch- C:-ter E:aus
176
+
D:E- C:-ly- D:si- E:-um
177
+
\end{lstlisting}
178
+
179
+
\textbf{Amazing Grace} (pentatonic, American):
180
+
\begin{lstlisting}[style=notepat]
181
+
D:A- G:-ma- B:-zing G:grace B:how A:sweet
182
+
G:the B:sound D:that E:saved D:a
183
+
B:wretch G:like B:me
184
+
\end{lstlisting}
185
+
186
+
\textbf{Arirang} (Korean, pentatonic):
187
+
\begin{lstlisting}[style=notepat]
188
+
E:A- G:-ri- A:rang E:a- G:-ri- A:rang
189
+
B:a- A:-ra- G:-ri- E:-yo
190
+
\end{lstlisting}
191
+
192
+
\textbf{Sakura} (Japanese, in mode):
193
+
\begin{lstlisting}[style=notepat]
194
+
E:Sa- E:-ku- F:ra E:sa- E:-ku- F:ra
195
+
A:ya- A:-yo- B:i A:no
196
+
\end{lstlisting}
197
+
198
+
Each encoding fits in a URL. The first four notes of ``Twinkle Twinkle'' are addressable as \texttt{notepat.com?song=C:Twin-\%20C:-kle\%20G:twin-\%20G:-kle}. The song is the address. The address is the score.
199
+
200
+
\subsection{Songs as Cards}
201
+
202
+
The cards format of this paper---4$\times$6 inches, designed for phones---means each encoded melody can appear on a single card, tappable at the bottom URL. A teacher could print a deck of folk song cards, hand one to each student, and the student taps the URL to load the song on their phone or laptop. The card is the program; the URL is the executable; the student is the performer.
203
+
204
+
This connects to the whistlegraph's core property: a score that teaches you how to play it~\citep{scudder2026whistlegraph}. The whistlegraph does this visually (draw the line, sing the note). \np{} does it textually (read the syllable, press the key). Both are self-documenting performance formats that require no teacher beyond the artifact itself.
205
+
170
206
\section{A Catalog of Playable Melodies}
171
207
172
208
We surveyed folk song collections from multiple traditions and selected melodies optimized for \np{}'s two-octave grid. Selection criteria: pitch range $\leq$\,15 semitones, pentatonic or simple diatonic scale, and cultural recognizability.
···
253
289
254
290
\section{The Bare-Metal Folk Instrument}
255
291
256
-
\np{} runs not only in browsers but on bare metal---a 987-line QuickJS port that boots as PID~1 on AC Native OS~\citep{scudder2026os}. A laptop running \np{} on bare metal is, in a literal sense, a folk instrument: a single-purpose device for playing songs, with no operating system, no desktop, no distractions.
292
+
\np{} runs not only in browsers but on bare metal---a 987-line QuickJS port that boots as PID~1 on AC Native OS~\citep{scudder2026os}. A surplus ThinkPad running \np{} on bare metal is, in a literal sense, a folk instrument: a single-purpose device for playing songs, with no desktop environment, no app store, no distractions.
293
+
294
+
The boot sequence: power on, kernel loads (7.3 seconds), the screen says ``hi @alice,'' and \np{} is playing. The student's name is spoken aloud by text-to-speech. The keyboard lights up with the first note of the song. There is nothing else to do, nowhere else to go. The laptop is the instrument.
295
+
296
+
\subsection{Why Bare Metal Matters for Folk Songs}
257
297
258
-
The convergence is complete: folk songs, designed to be played on the simplest available instrument, running on the simplest possible computer---a Linux kernel, a framebuffer, and a keyboard.
298
+
The PLOrk model~\citep{scudder2026plork} required custom hardware: hemispherical speakers, audio interfaces, dedicated laptops. The cost was prohibitive for most schools. AC Native OS inverts this: it runs on surplus commodity hardware---retired corporate laptops available for \$30--80---and transforms them into single-purpose instruments.
299
+
300
+
A classroom of 30 bare-metal \np{} devices, each loaded with a different folk song from a different tradition, is a folk orchestra. Each student learns their song, then the class performs together. The Korean student plays Arirang. The American student plays Amazing Grace. The Japanese student plays Sakura. The instruments are identical; the songs are culturally specific; the ensemble is global.
301
+
302
+
This is the scenario described in the companion paper on laptop orchestras~\citep{scudder2026plork}---but applied specifically to folk music, where the repertoire is public domain, culturally significant, and structurally suited to the instrument.
303
+
304
+
\subsection{Offline Operation}
305
+
306
+
The bare-metal \np{} requires no internet connection. Songs can be pre-loaded on the boot partition in \texttt{config.json}. A teacher prepares a USB drive with a set of folk songs, flashes it onto 30 laptops, and the classroom is ready. No WiFi, no accounts, no cloud services. The song files are kilobytes. The entire OS is 89\,MB.
307
+
308
+
This matters for the contexts where folk music education is most needed: schools without reliable internet, community centers without IT support, rural areas without broadband. The folk song and the folk instrument share a design constraint: they must work with what is available.
259
309
260
310
\section{Future Work}
261
311
+21
papers/arxiv-folk-songs/references.bib
+21
papers/arxiv-folk-songs/references.bib
···
105
105
year={2026},
106
106
note={Working draft. \url{https://aesthetic.computer}}
107
107
}
108
+
109
+
@article{scudder2026plork,
110
+
title={PLOrk'ing the Planet: From Ivy League Laptop Orchestra to Kid-Friendly Planetary Organ},
111
+
author={{@jeffrey}},
112
+
year={2026},
113
+
note={Working draft. \url{https://papers.aesthetic.computer}}
114
+
}
115
+
116
+
@article{scudder2026whistlegraph,
117
+
title={Whistlegraph: Drawing, Singing, and the Graphic Score as Viral Form},
118
+
author={{@jeffrey}},
119
+
year={2026},
120
+
note={Working draft. \url{https://papers.aesthetic.computer}}
121
+
}
122
+
123
+
@article{scudder2026pieces,
124
+
title={Pieces Not Programs: The Piece as a Unit of Creative Cognition},
125
+
author={{@jeffrey}},
126
+
year={2026},
127
+
note={Working draft. \url{https://papers.aesthetic.computer}}
128
+
}
+6
-6
system/public/papers.aesthetic.computer/index.html
+6
-6
system/public/papers.aesthetic.computer/index.html
···
638
638
639
639
<!-- papers-end -->
640
640
641
+
<div class="colophon">
642
+
<p>these papers are the research platter for <a href="https://aesthetic.computer">aesthetic computer</a> — a creative computing platform, a bare-metal operating system, a minimal lisp, and whatever else needs writing down. they are working drafts, written in first person, typeset in LaTeX with XeTeX, and compiled by an oven server that polls the git repo every 60 seconds.</p>
643
+
<p>the cards format is a 4×6 inch mobile-friendly version of each paper designed for reading on a phone. every paper is translated into danish, spanish, and chinese. the platter is not a journal submission queue — it is a live notebook that grows alongside the software.</p>
644
+
<p>all papers by <a href="https://prompt.ac/@jeffrey">@jeffrey</a> unless otherwise noted. source at <a href="https://github.com/whistlegraph/aesthetic-computer/tree/main/papers">github.com/whistlegraph/aesthetic-computer/papers</a>.</p>
645
+
</div>
646
+
641
647
<div class="build-status" id="buildStatus">
642
648
<div class="build-header" id="buildHeader">
643
649
<span class="build-dot" id="buildDot"></span>
···
647
653
</div>
648
654
<div class="build-progress"><div class="build-progress-bar" id="buildBar"></div></div>
649
655
<div class="build-logs" id="buildLogs"></div>
650
-
</div>
651
-
652
-
<div class="colophon">
653
-
<p>these papers are the research platter for <a href="https://aesthetic.computer">aesthetic computer</a> — a creative computing platform, a bare-metal operating system, a minimal lisp, and whatever else needs writing down. they are working drafts, written in first person, typeset in LaTeX with XeTeX, and compiled by an oven server that polls the git repo every 60 seconds.</p>
654
-
<p>the cards format is a 4×6 inch mobile-friendly version of each paper designed for reading on a phone. every paper is translated into danish, spanish, and chinese. the platter is not a journal submission queue — it is a live notebook that grows alongside the software.</p>
655
-
<p>all papers by <a href="https://prompt.ac/@jeffrey">@jeffrey</a> unless otherwise noted. source at <a href="https://github.com/whistlegraph/aesthetic-computer/tree/main/papers">github.com/whistlegraph/aesthetic-computer/papers</a>.</p>
656
656
</div>
657
657
658
658
<div class="footer">