WorkCase study
Continuity
A founder-narrative article published as a single X post.
A long-form narrative article deployed on GitHub Pages and published to X. Initial thread format withdrawn; single-post revision published 2026-07-12. Outcome: channel-format mismatch.
Summary
Outcome · needs revision
A well-built artifact with a clear motive. The article is clearly written, the visual surface is coherent, and the deployment is solid. The publication format did not match the channel: a long backstory in a link card does not communicate in a scroll feed. Initial thread format withdrawn; single-post revision published 2026-07-12. The artifact is retained as a reference; the feed format is not reused.
Engagement
X post · 2026-07-12
Continuity did not surface in the top visible posts on the profile after 24 hours. Tile's product-demo format earned 617 views in the same period. The feed format rewards shipped, visible product over narrative content.
Inputs used
Dimension findings
Each dimension: observation, judgment, action — Kit One format.
Purpose
Observation. A founder-narrative article with a clear motive and coherent form.
Judgment. Purpose is clear. Purpose does not guarantee reach.
Action · Retain as a reference artifact. Do not re-publish the narrative format on X.
Clarity
Observation. Clean structure, clear sections. Yellow-field addressing with black rounded cards — a distinct mode from the dark default.
Judgment. Clarity is strong in the artifact. The publication format was the constraint, not the writing.
Action · Retain at the hosted URL. Reference, not feed post.
Context
Observation. Deployed on GitHub Pages. X audience (1,891 followers, building-in-public) rewards shipped product demos over narrative content. The context is a feed, not a reading surface.
Judgment. Channel-format mismatch. The artifact is sound; the distribution channel was wrong for this format.
Action · Match format to channel. Hosted URL as a profile reference, not a feed post.
Inclusion
Observation. Yellow-field mode is a deliberate VAI surface choice — dark default with a toggle into yellow addressing. Article text is readable. No dark pattern.
Judgment. Inclusion is sound. The dark/yellow toggle is an accessibility-aware choice.
Action · Retain the dark/yellow toggle.
System coherence
Observation. VAI yellow #FFC400 as the field, black rounded cards, VAI wordmark only. Designesy activation yellow #FECC34 is deliberately suppressed. Deployment pattern matches Tile.
Judgment. Coherent within the VAI surface. The yellow-field mode is a distinct address, not a doctrine violation.
Action · Retain as a VAI-specific surface option. Do not import into Designesy.
Durability
Observation. Full documentation: ARTICLE_DRAFT, VISUAL_BRIEF, STATUS, build scripts, host, preview, renders. Article locked. Hosting live. Publication receipt recorded.
Judgment. Durable as a reference artifact.
Action · Retain at the hosted URL. Update STATUS if the narrative is revised.
Delight
Observation. Yellow-field mode is visually striking. Article voice is sincere. Feed-context delight requires immediate payoff — a long backstory does not deliver that.
Judgment. Delight is present in the artifact but is channel-dependent.
Action · Retain the artifact; change the distribution.
Responsibility
Observation. Initial thread format withdrawn; single-post revision published 2026-07-12. Underperformance documented.
Judgment. Outcome reported with the same rigor as a pass.
Action · Retain the case study. Mismatches are as documented as successes.