项目证据最低标准
一个公开项目至少需要真实问题、真实约束、真实交付物、真实链接和真实结果。
Phase 26 delivery standard
/knowledge/project-evidence-minimum-standardknowledge.trace("project-evidence-minimum-standard")EvergreenSignal
When to use it
Use before promoting a project to the homepage or featured portfolio rail.
Principle
What it protects
It keeps project cards from becoming persuasive copy without inspectable proof. If a reader cannot open the repo, deployment, document, screenshot, decision, or validation route, the evidence is not strong enough.
Reference
How to cite it
Use this checklist when writing Project Evidence Pack, Case Study Diff, PR descriptions, and phase acceptance criteria.
knowledge.trace("project-evidence-minimum-standard")
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.Product judgment / 中文外部证据比作品集叙事更重要Uses this rule as a writing argument in the Product judgment track.Internal referenceCase study diffConnects 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.Product judgment / 中文外部证据比作品集叙事更重要一个成熟的个人主页不应该只证明自己会搭个人主页。它必须把外部问题、外部交付、外部证据和清晰取舍带到公开表面。Uses this rule as a writing argument in the Product judgment 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 before, after, proof, and tradeoff as the compact evidence unit.This page cites the entry because defines before, after, proof, and tradeoff as the compact evidence unit.BacklinkAnyReader Interface TeardownUses public app, source repo, and local research as separate evidence types.This page cites the entry because uses public app, source repo, and local research as separate evidence types.