Case study diff format
Before, after, proof, and tradeoff are often a better portfolio unit than a long process narrative.
Phase 26 portfolio format
/knowledge/case-study-diff-formatknowledge.trace("case-study-diff-format")EvergreenSignal
When to use it
Use when writing project pages that need to stay inspectable and low-drama.
Principle
What it protects
It keeps case studies grounded in change. A diff forces the author to name what was actually different after the work, where the proof lives, and which limitations remain.
Reference
How to cite it
Use this when adding Project Evidence Pack, project detail pages, release reviews, or compact portfolio writeups.
knowledge.trace("case-study-diff-format")
Where this idea is used.
knowledge.graph("thin")Most related paths
AI-native developer tooling / ShippedOpenProfile Agent WorkflowTurns this knowledge entry into inspectable project evidence.Product interface research / ActiveAnyReader Interface TeardownTurns this knowledge entry into inspectable project evidence.Portfolio systems / EnglishCase Study Diff as a Portfolio FormatUses this rule as a writing argument in the Portfolio systems track.Portfolio systems / EnglishEvidence Without Precision TheaterUses this rule as a writing argument in the Portfolio systems track.Internal referenceDiff essayConnects this rule to another public route in the studio.
Related writing
Portfolio systems / EnglishCase Study Diff as a Portfolio FormatThe case study diff is a compact portfolio pattern: name the previous state, the changed state, the proof, and what the change did not solve.Uses this rule as a writing argument in the Portfolio systems track.Portfolio systems / EnglishEvidence Without Precision TheaterEvidence packs are useful when they reveal source, deployment, verification, and tradeoffs. They become harmful when they hard-code volatile numbers for decorative precision.Uses this rule as a writing argument in the Portfolio systems track.
Project evidence
AI-native developer tooling / ShippedOpenProfile Agent WorkflowA reproducible workflow for keeping a GitHub Profile, companion site, docs, and agent team aligned through explicit context, decisions, releases, and quality gates.Turns this knowledge entry into inspectable project evidence.Product interface research / ActiveAnyReader Interface TeardownA structured teardown of AnyReader as a reading workspace: what the interface promises, where the code proves it, and which engineering guardrails should come before more features.Turns this knowledge entry into inspectable project evidence.
Reference links
Backlinks
BacklinkCase Study Diff as a Portfolio FormatDefines the compact before, after, proof, tradeoff structure.This page cites the entry because defines the compact before, after, proof, tradeoff structure.BacklinkAnyReader Interface TeardownUses diff cards to separate product promise from repository reality.This page cites the entry because uses diff cards to separate product promise from repository reality.