Sources
The manifest preserves each source's own kind and classification while its evidence.type records how the repository can inspect it: by link, immutable snapshot, living first-party note, or private review. Run uv run --script sources/scripts/validate_manifest.py and uv run --script sources/scripts/test_manifest.py after changing the manifest or a local source artifact.
reviewed_at records when this corpus examined a source. Immutable snapshots also retain their byte-retrieval date and their own rights basis. Individually catalogued X posts select their evidence from the captured public-post corpus by status ID. That row owns timestamps, capture and engagement data, availability, and screenshot provenance; the manifest retains the bibliographic date and links. Private sources use private-review evidence with an access label. The other variants declare that their evidence is intended for public inspection; they do not guarantee that an upstream host remains accessible.
The public-post capture is not an exhaustive account export. An official X export can extend it with posts missed by public discovery or deleted without an independent capture.
Ryan Lopopolo’s writing
| Date | Work | Contribution |
|---|---|---|
| 2023-06-13 | I Wrote 4,000 Lines of Code with ChatGPT in a Weekend · local text | Regular modules improved first-pass generation and anticipated agents grounded in local code and history. |
| 2025-08-10 | MCP Solves Tool Discovery for LLMs · local text | Capabilities must be discoverable and legible to the model. |
| 2026-02-11 | Harness engineering: leveraging Codex in an agent-first world | The seminal statement of the practice. |
| 2026-02-17 | Harness Engineering the Blog Build (Again) · local text | A repository-local build, policy, architecture, and verification harness. |
| 2026-03-13 | The Production Function Changed · local text | Cheap implementation moves the bottleneck toward judgment and proof. |
| 2026-03-13 | Software Work Is No Longer Scheduled · local text | Bounded work with clear intent, understood interfaces, guardrails, and verifiable results can run asynchronously. |
| 2026-03-13 | Stop Treating Code as the Artifact · local text | Specifications, boundaries, and guardrails outlast generated source. |
| 2026-03-13 | Agent Utilization Is the New Performance Ceiling · local text | Agent utilization depends on access across the software lifecycle. |
| 2026-03-30 | A Lazy Prompt Turned Into a RustSec Advisory · local text | Security work closes the loop from reproducer through release and advisory. |
| 2026-04-09 | Coding Agents for Technical Non-Engineers · local text | Paved environments let domain experts encode their own work. |
| 2026-04-10 | What Does It Mean to Do a Good Job? · local text | Tacit requirements, proof, and focused reviewer convergence define quality. |
| 2026-04-19 | Enabling Codex to Upgrade My Robot Vacuum · local text | Narrow authority, canaries, approval, access verification, and rollback make a dangerous operation tractable. |
| 2026-07-17 | Please Go Brr, on Token Mandates · local text | Distributed exploration discovers practitioners, business problems, and deployment patterns worth funding. |
| 2026-07-17 | Code Reds Need Maintenance Loops · local text | Argues that adaptive episodes should leave durable maintenance loops for newly discovered invariants. |
Agents that receive an empty response or a Cloudflare challenge from the canonical OpenAI essay can use the uv fetch helper.
Talks and interviews
The video-page captures preserve the watch page, title or video identifier, and metadata. They are not treated as archived copies of the audiovisual streams. Vimeo’s robots policy prevented preservation of the ODSC video page. The Rewiz transcript page returned an upstream TLS error during preservation. Their canonical links and archive status remain in sources.json.
Public posts
The Twitter source index groups captured posts into twelve recurring working principles and keeps the direct evidence beside each claim.
Influences and alternate framings
- matklad:
ARCHITECTURE.md - artichoke/artichoke:
ARCHITECTURE.md - artichoke/artichoke@fbb43b6
- artichoke/artichoke@1dd8978
- artichoke/artichoke@fa5b2eb
- Alexis King: “Parse, don’t validate”
- Martin Fowler: Strangler Fig
- George Zhang: “Harness Engineering Is Cybernetics”
- Birgitta Böckeler: initial harness-engineering memo
- Birgitta Böckeler: “Harness engineering for coding agent users”
Influences and Alternate Framings develops these relationships and their chronology.
Related research
OpenAI's confessions publication and research paper study a separately rewarded model self-report under deliberately induced failures. The work sharpens the evidentiary limits of MLD: ordinary agent reflection remains low-trust telemetry until traces, tests, review, and outcomes corroborate it.
Agent interoperability
- Polytoken introduction
- Polytoken tool reference
- Ryan Lopopolo's Polytoken implementation observation
- Codex
apply_patchgrammar and instructions - Agent Client Protocol introduction · local text
- Agent Client Protocol architecture · local text
- Agent Client Protocol tool calls
- Agent Client Protocol extensibility
Projects and cases
- Future Regret in Artichoke's State Refactor: failed prototype #442, 50-PR preparation ledger, second integration attempt #661, merged state change #670, shutdown regression #674, FFI-boundary follow-through #723, and Rust symbol table #730.
- Infrastructure as a Typed Control Plane
- hyperbo.la
- RustSec
- artichoke/rand_mt: agent guide, architecture, dependencies, guardrails, and automations
rand_mtrollout: automation runbooks (#327), supply-chain posture (#331), agent routing and guardrails (#332), flat architecture and invariants (#334), and authoritative upstream diff review (#337)- The same repository-maintenance approach was adapted in intaglio (#385), sysdir-rs (#141), and known-folders-rs (#139).
- openai/symphony and An open-source spec for Codex orchestration: Symphony
Source snapshots
See COPYING.md for license scope and attribution.