Tuesday
Dispatch / Editorial status
We publish the work after the evidence.
We choose changes worth explaining. We show what happened, what we learned, and where the result has limits.
- Source Repository
- Email Up to twice monthly
- Claim Evidence-gated
Working rhythm
One lesson, carried across the right formats.
Our planned rhythm depends on evidence review and approval of the exact content and destination. Email is capped at two validated sends per month; these review slots do not promise publication.
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 status
The next publishing schedule is not yet announced.
The September dates were review plans, not publication or email-send confirmations. Read the published archive and current field reports while the next selection awaits evidence review.
Every new selection passes evidence review before drafting and approval. Publication and email delivery are confirmed separately, after they happen.
Read or put it to work
Choose your next step.
Field notes by email
The published field-note archive and email signup live on CREATE SOMETHING .io. Read an edition now or request the next one when it is ready.
Evidence for your workflow
Explore current field reports on CREATE SOMETHING .agency. If a lesson connects to your team’s work, map the handoff, tools, and decisions with us.
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