paulca / paulca.com Public

Fix future-dated GPT-OSS ledger entry; tell agents to get dates from date +%F

The switch entry was dated July 26 but its commit landed July 25 21:56.
Renamed to the real date, restoring chronological order.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Paul Campbell ba32e7f2b3025ca35bd491727176973125ee4a57 parent eee1506
4 files changed, +39 −10
  • AGENTS.md +2 −0
  • docs/ai.html +24 −10
  • src/ledger/{2026-07-26-01-gpt-oss.md => 2026-07-25-03-switching-to-gpt-oss.md} +0 −0
  • src/ledger/2026-07-25-15-date-fix.md +13 −0
diff --git a/AGENTS.md b/AGENTS.md
index d6a356e..c1383d3 100644
--- a/AGENTS.md
+++ b/AGENTS.md
@@ -95,6 +95,8 @@ never edit an existing one — named `YYYY-MM-DD-NN-slug.md`: today's date,
then `NN`, a two-digit number one higher than the highest already used for
that date (run `ls src/ledger/` to check; use `01` if the date is new), then
two or three words about the change. Example: `2026-07-25-08-model-column.md`.
+Get today's date by running `date +%F` — never guess it from memory; models
+frequently don't know what day it is.
---
model: GPT-OSS (RTX 3090)
diff --git a/docs/ai.html b/docs/ai.html
index 487b532..6758fa4 100644
--- a/docs/ai.html
+++ b/docs/ai.html
@@ -30,15 +30,18 @@ the AI work cost. Newest first.</p>
<th>Roughly equivalent to</th>
</tr>
<tr>
- <td>July 26, 2026</td>
- <td>GPT-OSS (RTX 3090)</td>
- <td>“Switching from Claude to GPT-OSS on my gaming rig in the home office.”</td>
- <td><p>Switched to a local open‑source LLM running on an RTX 3090 GPU. No data
-leaves home and energy per prompt is roughly 2 Wh.</p>
+ <td>July 25, 2026</td>
+ <td>Claude Fable 5</td>
+ <td>“Somehow this one got attributed to tomorrow”</td>
+ <td><p>The “Switching from Claude to GPT‑OSS” entry was future-dated July 26 by
+the model that wrote it; the commit actually landed on July 25 at 21:56.
+Renamed the entry file to the real date, restoring true chronological
+order. <code>AGENTS.md</code> now tells agents to get the date from <code>date +%F</code>
+instead of guessing.</p>
</td>
- <td>~2 Wh</td>
- <td>~0.8 g</td>
- <td>A half-hour of a 5 W LED bulb</td>
+ <td>~3 Wh</td>
+ <td>~1.2 g</td>
+ <td>Fifteen minutes of a tablet charging</td>
</tr>
<tr>
<td>July 25, 2026</td>
@@ -170,6 +173,17 @@ to <code>docs/</code>; every old URL still works.</p>
<td>~16 g</td>
<td>An hour of a 40 W desk fan</td>
</tr>
+<tr>
+ <td>July 25, 2026</td>
+ <td>GPT-OSS (RTX 3090)</td>
+ <td>“Switching from Claude to GPT-OSS on my gaming rig in the home office.”</td>
+ <td><p>Switched to a local open‑source LLM running on an RTX 3090 GPU. No data
+leaves home and energy per prompt is roughly 2 Wh.</p>
+</td>
+ <td>~2 Wh</td>
+ <td>~0.8 g</td>
+ <td>A half-hour of a 5 W LED bulb</td>
+</tr>
<tr>
<td>July 25, 2026</td>
<td>Claude Fable 5</td>
@@ -283,8 +297,8 @@ Pages. About 40 model invocations.</p>
</tr>
</table>
-<p><b>Running total:</b> ~194 Wh,
-~77 g CO&#8322;e &mdash;
+<p><b>Running total:</b> ~197 Wh,
+~79 g CO&#8322;e &mdash;
just shy of the energy it takes to boil two litres of water, or the emissions of driving a petrol car about 450 metres.</p>
<h2>Method</h2>
diff --git a/src/ledger/2026-07-26-01-gpt-oss.md b/src/ledger/2026-07-25-03-switching-to-gpt-oss.md
similarity index 100%
rename from src/ledger/2026-07-26-01-gpt-oss.md
rename to src/ledger/2026-07-25-03-switching-to-gpt-oss.md
diff --git a/src/ledger/2026-07-25-15-date-fix.md b/src/ledger/2026-07-25-15-date-fix.md
new file mode 100644
index 0000000..4a77eb6
--- /dev/null
+++ b/src/ledger/2026-07-25-15-date-fix.md
@@ -0,0 +1,13 @@
+---
+model: Claude Fable 5
+wh: 3
+co2_g: 1.2
+comparison: Fifteen minutes of a tablet charging
+prompt: >-
+ “Somehow this one got attributed to tomorrow”
+---
+The “Switching from Claude to GPT‑OSS” entry was future-dated July 26 by
+the model that wrote it; the commit actually landed on July 25 at 21:56.
+Renamed the entry file to the real date, restoring true chronological
+order. `AGENTS.md` now tells agents to get the date from `date +%F`
+instead of guessing.