Tuesday
Dispatch / Publishing schedule
We publish the work after the evidence.
Each week, we choose a change worth explaining. We show what happened, what we learned, and where the result has limits.
- Source Repository
- Lesson One per week
- Claim Evidence-gated
Working rhythm
One lesson, carried across the right formats.
We share updates on LinkedIn, demonstrate a full workflow on YouTube twice a month, and send selected lessons by email.
Thursday
Alternate Thursdays
YouTube
A complete 5–8 minute workflow walkthrough.Friday
X / Instagram
A technical adaptation or an existing demonstration clip.Up to twice monthly
Current editorial queue
Four questions from work already in the repository.
These dates are plans. We publish only after reviewing the supporting evidence and checking what can be shared.
01
Week of September 7, 2026
Can an operator see what an agent changed?
Inspectable canvas changes. Source: Draw semantic composition and scoped production tools.
- Evidence
- Public-safe canvas walkthrough with one bounded change
- Channels
- LinkedIn · YouTube · X · Instagram
- State
- evidence review
02
Week of September 14, 2026
How do you check a code claim before repeating it?
Verification before claims. Source: Ground calibration and release verification.
- Evidence
- One reproducible check with the exact result and limit
- Channels
- LinkedIn · X
- State
- evidence review
03
Week of September 21, 2026
Does done mean prepared, approved, executed, or verified?
A receipt must name the state. Source: Workflow receipt history and the existing field note.
- Evidence
- Synthetic workflow from request through wait, stop, and receipt
- Channels
- LinkedIn · YouTube · Email · X
- State
- evidence review
04
Week of September 28, 2026
What should remain when the agent leaves?
The next operator needs a usable handoff. Source: Atlas/Substrate operating loop and Agent Foundation handoff.
- Evidence
- Public-safe map with owner, boundary, proof, and recovery
- Channels
- LinkedIn · X · Instagram
- State
- evidence review
Publication boundary
A commit is the start of the story.
Git establishes what changed; a merge does not establish live behavior.
The agent wiki helps locate the operating lesson; its source artifacts remain authoritative.
CTX can explain earlier reasoning; current source, tests, and live behavior gate the claim.
Every public example names what the evidence proves and what remains unknown.
Client-private records and access changes do not become public stories.
Bring the next workflow
Show us the handoff your team still rebuilds by hand.
We’ll look at the task, tools, approvals, and expected result before proposing a build.
- Owner
- Workflow owner
- Authority
- Human approval
- Proof
- Map + evidence plan
- State
- ready