auto: 2026-04-29T01:17:30Z [skip ci]

content/colophon.md

@@ -1,7 +1,7 @@
 ---
 title: Colophon
 date: 2026-03-21
-modified: 2026-04-12
+modified: 2026-04-27
 status: "Durable"
 confidence: 93
 tags: [meta]
@@ -50,6 +50,8 @@ This is a [Static Website](https://en.wikipedia.org/wiki/Static_web_page). For t
 
 The [AST](https://en.wikipedia.org/wiki/Abstract_syntax_tree) we use is heavily customized and modified. The chain is roughly markdown -> pandoc -> citations -> wikilinks -> preprocessing -> sidenotes -> smallcaps and dropcaps -> links -> images -> math. Mathematics with LaTeX requires a second pass and is rendered at build-time with KaTeX - no math rendering occurs in your browser. Samples from music are displayed as SVGs, generally typeset with Lilypond through some helper scripts I wrote to automate the process.
 
+Not all content on this site is markdown. A handful of pages — the [[Library]], the [[Commonplace]], and [[Current]] — are driven instead by YAML files under `data/`, rendered through dedicated Haskell modules that parse the schema, apply a sort or filter discipline particular to the surface, and emit the rendered HTML directly into a template. The split is deliberate: prose belongs in markdown, where the discipline is rhetorical; curated lists belong in YAML, where the discipline is editorial. The Current page, for instance, ladders entries by status (*in-review* → *revising* → *drafting* → *building*) before falling back to recency, and stamps each entry with its own "last updated" date — features that would be tedious to maintain in markdown but trivial to express in a small declarative schema.
+
 The semantic search model is a particularly intriguing aspect of the website. The model used is self-hosted, with weights served from the same origin. There are NO external API calls when you use this, in contrast to just about every other similar feature on other websites. This is essential for the privacy model that this site strives to achieve - see **Design Decisions** for more.
 
 A full accounting of what this build process has actually produced is available at the [[Build]] page. It is generated automatically at each compile: corpus word counts, length distributions, tag frequencies, link analysis, epistemic coverage, repository metrics, and build timing — all computed from the same source tree that produces the content. Think of it as the build system reporting on itself.
@@ -143,6 +145,8 @@ Every essay and post on this site carries an **epistemic footer** — a structur
 
 The version history block, directly above the epistemic footer, uses a three-tier fallback: authored `history:` notes when they exist (written by me when the git log alone would not convey what changed), then the raw git log, then the `date:` frontmatter field as a creation record. `make build` auto-commits any changed content files before the Hakyll compilation runs, so the git log is always current.
 
+The [[Current]] page extends this premise from essays to ongoing work. Every research project listed there carries its own `updated:` timestamp and a status drawn from a controlled vocabulary — *in-review*, *revising*, *drafting*, *building*, *early-stage*, *paused* — and the page itself wears a masthead "last updated" date as its thesis. The page has no epistemic footer because it isn't an argument; it is, rather, the closest thing this site has to a publication, and yet by design it is the part of the site most committed to being out of date the moment you finish reading it.
+
 The point of all this is simple: when you read something on this site, you should know what kind of claim I am making. The date a document was last modified is not decorative. A 40% confidence rating is not self-deprecation. The system is an attempt to make explicit something that most writing leaves implicit — where the author actually stands.
 
 ---

content/drafts/essays/specification_dilemma.md

@@ -25,3 +25,4 @@ The second is a starkly different picture: the human, who only has a vague idea
 These two represent diverging definitions of *intelligence*, both for the models and for their users, or, if you prefer, their collaborators. The first is a definition of intelligence that depends both on what one has the capacity to specify and what one has the capacity to see through. The latter depends wholly on what one has the capacity to see through, and places even more emphasize on this metric than the first, for the amount of recalibration and prompt adjustment necessary to build a specification continuously throughout the duration of a task is always greater than paying the upfront cost of developing a strong specification from the onset. [We the programmers have known this for years](https://en.wikipedia.org/wiki/Hofstadter%27s_law). The first future is chiefly preferable, and the second, which seems to be the unfortunate reality we are racing towards, is not only a realization of the worst affect that AI could have on our cognition, but may also unnecessarily constrain the breadth of intelligence that AGI can achieve.
 
 ## Compression *is* Intelligence
+How many bits constitute a project? The question is impossible to answer.

content/drafts/essays/university_care.md

@@ -0,0 +1,47 @@
+---
+title: "Universities Should Care"
+date: 2026-04-28          # required; used for ordering, feed, and display
+abstract: >               # optional; shown in the metadata block and link previews
+  As Students should be more than a mere statistic to the Universities at which they study. I critique Brown University, my undergraduate institution, in this regard. The degradation of students to treatment as if they are a mere statistic is potentially a major reason for the decline in postsecondary education in the modern United States. 
+tags:                     # optional; see Tags section
+  - ai
+  - tech
+
+# Epistemic profile — all optional; the entire section is hidden unless `status` is set
+status: "Draft"   # Draft | Working model | Durable | Refined | Superseded | Deprecated
+confidence: 85           # 0–100 integer (%)
+importance: 4         # 1–5 integer (rendered as filled/empty dots ●●●○○)
+evidence: 5              # 1–5 integer (same)
+scope: broad            # personal | local | average | broad | civilizational
+novelty: moderate         # conventional | moderate | idiosyncratic | innovative
+practicality: high    # abstract | low | moderate | high | exceptional
+confidence-history:       # list of integers; trend arrow derived from last two entries
+---
+
+
+
+
+
+--- 
+Planning: List of grievances
+
+COMPUTER SCIENCE
+  - TA System section.
+  - 
+
+RES LIFE
+  - Obviously: repeated requests for discussion and process for moving out in Fall '23.
+  - Unable to control heat
+  - Lack of bathrooms.
+  - Lack of kitchens
+    
+DINING
+  - Let's run through some calculations to see the actual cost of every meal averaged across a semester.
+  - No real late night options.
+  - Poor optimization of queues / high demand items like grilled cheese.
+  - Inconsistent pricing for the same items across locations.
+
+SECURITY
+  
+  
+EFFECTS ON THE CULTURE

content/index.md

@@ -20,4 +20,3 @@ This website is *not* an academic homepage, nor a blog, nor a portfolio — thou
 <div class="hp-curiosity-row">
 <a href="/memento-mori.html">Memento Mori</a><span class="hp-sep" aria-hidden="true">·</span><a href="/commonplace.html">Commonplace</a><span class="hp-sep" aria-hidden="true">·</span><a href="/colophon.html">Colophon</a><span class="hp-sep" aria-hidden="true">·</span><a href="/build/">Build</a><span class="hp-sep" aria-hidden="true">·</span><a href="#" data-random>Random</a>
 </div>
-

content/photography/index.md

@@ -0,0 +1,7 @@
+---
+title: Photography
+abstract: A working portfolio of photographs.
+tags: [photography]
+---
+
+A working portfolio of photographs from travel, study, and the everyday. Nothing here yet.

content/tag-meta/photography.md

@@ -0,0 +1,3 @@
+---
+tooltip: "photographs from travel and the everyday"
+---