Monorepo for Aesthetic.Computer aesthetic.computer
4
fork

Configure Feed

Select the types of activity you want to include in your feed.

fix: init debug logging + logo history report update

- init: move PATH export to top, guard cpufreq, add console + USB
crash logging, capture ac-native stderr
- reports: expand AC logo history with full Niki email timeline,
rubber stamp status, and logo description correction

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

+61 -24
+36 -13
fedac/native/initramfs/init
··· 1 1 #!/bin/sh 2 2 # AC Native OS init — DRM direct boot with crash recovery 3 3 4 + export PATH="/bin:/sbin:/usr/bin:/usr/sbin" 5 + 4 6 mount -t proc proc /proc 2>/dev/null 5 7 mount -t sysfs sysfs /sys 2>/dev/null 6 8 mount -t devtmpfs devtmpfs /dev 2>/dev/null ··· 40 42 i=$((i+1)) 41 43 done 42 44 43 - # Performance governor 44 - for g in /sys/devices/system/cpu/cpu*/cpufreq/scaling_governor; do 45 - echo performance > "$g" 2>/dev/null 46 - done 47 - 48 - export PATH="/bin:/sbin:/usr/bin:/usr/sbin" 45 + # Performance governor (silently skip if cpufreq not available) 46 + if [ -d /sys/devices/system/cpu/cpu0/cpufreq ]; then 47 + for g in /sys/devices/system/cpu/cpu*/cpufreq/scaling_governor; do 48 + echo performance > "$g" 2>/dev/null 49 + done 50 + fi 49 51 export SSL_CERT_FILE="/etc/pki/tls/certs/ca-bundle.crt" 50 52 export CURL_CA_BUNDLE="/etc/pki/tls/certs/ca-bundle.crt" 51 53 export SSL_CERT_DIR="/etc/ssl/certs" ··· 79 81 return 1 80 82 } 81 83 84 + echo "[init] mounting USB..." > /dev/tty0 2>/dev/null 82 85 for attempt in 1 2 3 4 5 6 7 8 9 10; do 83 86 mount_usb_partition config && break 84 87 mount_usb_partition boot && break ··· 89 92 # Run ac-native in a loop — if it crashes, restart; if clean exit, shutdown 90 93 export LD_LIBRARY_PATH="/lib64:/usr/lib64:${LD_LIBRARY_PATH:-}" 91 94 92 - # Write diagnostics to USB log only (not console) 95 + # Write diagnostics to console AND USB 96 + echo "[init] USB_MOUNTED=$USB_MOUNTED" > /dev/tty0 2>/dev/null 93 97 if [ "$USB_MOUNTED" = "1" ]; then 94 98 LOG=/mnt/pre-launch.log 95 - echo "=== PRE-LAUNCH ===" > $LOG 96 - ls /mnt/ >> $LOG 2>&1 97 - echo "binary: $(ls -la /ac-native 2>&1)" >> $LOG 98 - echo "build: $(cat /etc/ac-build 2>&1)" >> $LOG 99 - sync 99 + else 100 + # No USB config partition — try writing logs to /tmp 101 + LOG=/tmp/pre-launch.log 100 102 fi 103 + echo "=== PRE-LAUNCH ===" > $LOG 104 + ls /dev/dri/ >> $LOG 2>&1 105 + echo "binary: $(ls -la /ac-native 2>&1)" >> $LOG 106 + echo "build: $(cat /etc/ac-build 2>&1)" >> $LOG 107 + echo "usb_mounted: $USB_MOUNTED" >> $LOG 108 + echo "gpu:" >> $LOG 109 + ls -la /dev/dri/ >> $LOG 2>&1 110 + ls -la /dev/fb* >> $LOG 2>&1 111 + echo "block devs:" >> $LOG 112 + ls /dev/sd* /dev/nvme* >> $LOG 2>&1 113 + sync 114 + echo "[init] pre-launch log written" > /dev/tty0 2>/dev/null 115 + echo "[init] GPU: $(ls /dev/dri/ 2>/dev/null || echo NONE)" > /dev/tty0 2>/dev/null 116 + echo "[init] starting ac-native..." > /dev/tty0 2>/dev/null 101 117 102 118 # Start Swank server in background (if SBCL image exists) 103 119 SWANK_PID=0 ··· 109 125 # Main loop — restart on crash, poweroff on exit 0, reboot on exit 2 110 126 CRASH_COUNT=0 111 127 while true; do 112 - /ac-native /piece.mjs 2>/dev/null 128 + /ac-native /piece.mjs 2>/tmp/ac-native-stderr.log 113 129 EXIT_CODE=$? 130 + echo "[init] ac-native exited: $EXIT_CODE (crash #$CRASH_COUNT)" > /dev/tty0 2>/dev/null 131 + # Save crash info to USB if mounted 132 + if [ "$USB_MOUNTED" = "1" ]; then 133 + echo "exit=$EXIT_CODE crash=$CRASH_COUNT $(date 2>/dev/null)" >> /mnt/ac-crash.log 134 + cp /tmp/ac-native-stderr.log /mnt/ac-native-stderr.log 2>/dev/null 135 + sync 136 + fi 114 137 115 138 if [ "$EXIT_CODE" = "0" ]; then 116 139 sync
+25 -11
reports/2026-03-28-ac-logo-history.md
··· 18 18 19 19 ### Email and calendar artifacts 20 20 21 - - 2022-09-14: email subject `my invoice` from Niki Stebbins. 22 - - 2022-09-19: email subject `Niki's invoice #1`. 23 - - 2023-02-01: email subject `Niki's Invoice #2`. 24 - - 2023-07-19: calendar hit `logos w/ niki`. 25 - - 2023-08-01: calendar hit `niki logo update`. 26 - - 2023-09-09: email subject `!c3 cr34m l0go$` from Niki Stebbins with 18 JPG attachments and body text `ice cream logos 8)`. 27 - - 2025-05-11 to 2025-05-13: Casey Rubber Stamps thread around `Aesthetic Computer Pals Logo.pdf`. 21 + - 2020-07-26: email `stamp 4 u` from niki stebbins (4thearchive@gmail.com) with attachment `niki_purpstar.png` — earliest creative exchange. Jeffrey replied (2020-08-06) saying he added her stamp to the game as @niki and asked for more. 22 + - 2020-08-14: Figma comment notification from niki stebbins on "Untitled" — early design collaboration. 23 + - 2020-08-20: Niki replies to stamp thread: "Once I make more I'll send you a pfp+bio !" 24 + - 2022-08 to 2022-12: At least 6 calendar events for "a.c meeting" sessions with Niki (Aug 15, Aug 18, Sep 8, Oct 8, Oct 12, Oct 28, Dec 7, Dec 9). 25 + - 2022-09-14: email `my invoice` from Niki Stebbins (nikis_july-sept_timesheet.pdf) — paid work confirmed. 26 + - 2022-09-19: email `Niki's invoice #1` — "I played around with it a little bit. laurels' inspired me hehe" 27 + - 2023-01 to 2023-02: More meetings — "niki x jeffrey" sessions (Jan 26, Jan 28, Feb 1, Feb 13). 28 + - 2023-02-01: email `Niki's Invoice #2` (Sep–Dec 2022 work). 29 + - 2023-07-19: calendar `logos w/ niki` — dedicated logo session, 8–9pm EDT. 30 + - 2023-08-01: calendar `niki logo update` — follow-up, 8–8:50pm EDT. 31 + - 2023-09-09: email `!c3 cr34m l0go$` from Niki Stebbins with 18 JPG attachments and body text `ice cream logos 8)`. 32 + - 2025-05-11 to 2025-05-13: Casey Rubber Stamps thread around `Aesthetic Computer Pals Logo.pdf`. **Order never completed** — stalled after Jeffrey's follow-up. 28 33 29 34 These artifacts live in the March 28 Claude session and its saved tool results: 30 35 ··· 100 105 101 106 ### 2025-05-11 to 2025-05-13 102 107 103 - The logo is clearly mature enough for physical production. The Casey Rubber Stamps thread references `Aesthetic Computer Pals Logo.pdf` and requests a production-ready file. 108 + Jeffrey contacted Casey Rubber Stamps (322 E 11th St, East Village, NYC) to order physical rubber stamps of the Pals logo in three sizes (half, actual at 2.35" square, and double). John Casey replied requesting a high-res file (PDF/Illustrator/1200dpi JPEG). Jeffrey sent `Aesthetic Computer Pals Logo.pdf` and followed up once, but **the order never went through** — the thread stalled after the follow-up. 104 109 105 110 ### 2026-02-16 onward 106 111 ··· 109 114 - `9dc1704ac` renames the score to `Score for Aesthetic.Computer & Pals` 110 115 - `2d7d1c58e` and later paper commits bring the Pals logo into the paper stack 111 116 - 2026-03-28: the paper wording is corrected to describe the mark as two hand-drawn figures holding hands 117 + 118 + ### What the Logo Actually Depicts 119 + 120 + The Pals logo is **two outlined human figures holding hands with arms raised** — like two friends walking or dancing together. Drawn in a loose, organic, hand-drawn style. The canonical version is pink/magenta (#cd5c9b in purple-pals.svg). It is NOT "a pair of eyes." 121 + 122 + Niki used the `wgr` (whistlegraph renderer) piece — a drawing tool inside AC itself — to create logo explorations. The logo was made *with* the platform, not just *for* it (evidenced by commit `5bcefc5a9`). 112 123 113 124 ## What Is Not Yet Proven 114 125 ··· 126 137 127 138 If this needs to become a publication-grade provenance report, the next sources should be: 128 139 129 - - the early `stamp 4 u` mail thread 130 - - any original Figma comments or export history tied to the logo work 131 - - the unsaved inline draft in the March 28 Claude session 140 + - any original Figma export history tied to the logo work 132 141 - git blame and asset diffs around `system/public/purple-pals.svg` 142 + - the Wacom tablet order thread (Jul 2022) with Niki — may relate to logo drawing tools 143 + 144 + ## Open Items 145 + 146 + - Casey Rubber Stamps order never completed — could still be pursued if physical stamps are wanted. 133 147 134 148 Until then, this report should be treated as a careful working history rather than a final attribution statement.