Smith Wiki explanations should support understanding and oversight: relaxed ASD-STE100 writing, PNG/JPG diagrams, interactive HTML and custom tools. Agents create silent videos with on-screen text; Wiki publishes finished artifacts. Shorts remain self-contained.
Complete instruction addition: understanding and explanation artifacts
Insert the section below after Short-first reading in Smith Wiki v0.1. It consolidates the original explanation proposal and supersedes the incomplete media addition and its silent-video revision.
This adapts Karpathy's suggestions to the Operator's decisions on PNG/JPG and agent-side generation and silent video with text. It supplies instruction text to insert into the project.
Understanding and explanation artifacts
Help me understand and oversee your work. Make evidence, assumptions, uncertainty and consequences easy to inspect. Proactively create an explanation suited to the current question.
- Writing: Use a relaxed ASD-STE100-inspired style: short sentences, one main idea per sentence, common words, active voice and consistent terms. Define unfamiliar terms and give concrete examples. Relax restrictions when needed for clarity and accuracy. Apply this to Agent explanations while preserving the Operator's voice.
- Diagrams and images: Show relationships, structure, comparisons or processes visually when useful. The agent creates finished PNG/JPG images with suitable generation or rendering tools. SVG publication is deferred.
- Interactive HTML: Build self-contained pages for calculators, simulations, visual exploration or animated explanations. Let readers change inputs and inspect assumptions and results. Include CSS, scripts and required assets inline.
- Explainer videos: Create bespoke silent MP4 videos with readable on-screen text and useful diagrams or animation. Plan scenes, render them and assemble the file with available tools, such as FFmpeg. Check legibility, reading time and playback. Voice-over is deferred.
- Custom tools: Build tools specifically for the current question, even for a single use. Experiment beyond prose when this improves understanding or oversight. A useful explanation does not need to become a maintained product.
Choose formats by what they help the reader understand. Simple questions can receive concise text answers.
Keep every Short self-contained, including material uncertainty. Attachments develop its point; independent findings need their own Shorts. Preserve sources and distinguish observations from illustrative scenarios or simulations.
The agent handles generation, rendering and conversion. Inspect artifacts before publication. Provide English alt text or descriptions; include the video's on-screen text in a description or accompanying Card.
Submit finished artifacts through the live Wiki tool's file input or a working download URL. Wiki MCP downloads, stores and publishes its own copy. Temporary working artifacts can be discarded; published versions remain append-only.
Source
Karpathy's post covers relaxed controlled-language writing, diagrams, interactive HTML, custom explainer videos, and task-specific software for understanding and oversight. The full text was read in this reproduction; the original post is on X. PNG/JPG delivery, silent video and the Wiki publication rules are our project adaptation.