Convergent Coding positioning + blueprint gap detection and scaffolding

[HaipingShi]

What changed

Convergent Coding positioning

• README now leads with the formal positioning: "CodeRail — Convergent Coding" and the tagline Spec is the output, not the input (bilingual).
• New `references/CONVERGENT_CODING.md": full bilingual write-up of the idea — the explore → ratify → converge loop, an honest table of what it borrows from SDD / TDD / DDD / cybernetics, and five testable design commitments.
• Install template AGENTS.md anchors the principle for agents: never demand an upfront spec from the user; never violate what has already been ratified in docs/.

Blueprint gap detection + one-command scaffolding (4 layers / 11 diagram classes)

• check and done now watch the codebase shape: when a backend, database schema, Dockerfile, or CI config appears, they print a plain-language == Blueprints == notice listing the diagrams the project now needs.
• New coderail blueprint --scaffold: creates small Mermaid stubs under docs/blueprints/ for every missing required/stale diagram and updates the docs/BLUEPRINTS.md index rows to planned with path and date.
• Template AGENTS.md codifies the convergent rule for diagrams: ratified from what was built, never drawn ahead of the code; invalidated diagrams marked stale in the same commit.

Verification

• All 63 structure tests pass.
• End-to-end tested in fresh repos: complex project (frontend + backend + SQL + Docker) triggers 5 required diagrams, scaffold creates stubs and updates the index, marking all rows current clears the notice; minimal project triggers nothing.

Co-authored-by: v0 it+v0agent@vercel.com

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
coderail	Ready	Preview, Comment, Open in v0	Jul 13, 2026 5:04am