rhi

Appearance

CONTEXT.md adoption ​

Project(s) touched: crescent, defocus, interconnect, tiltshift, normalize, reincarnate (have it); all others (don't)

Status: Open — partial adoption, no decision recorded

Surfaced in: session 37565687 (io, 2026-04-27: "what about subagents to seed CONTEXT.md or whatever?"); the improve-codebase-architecture skill (this repo) already assumes CONTEXT.md exists

The question ​

Should CONTEXT.md be a mandatory ecosystem-wide artifact, or remain opt-in per project?

Why this is a registry thread ​

A convention question that affects scaffolding and the propagation toolchain. The improve-codebase-architecture skill depends on it, so the answer also decides whether that skill can be relied on everywhere or only where the file happens to exist.

What's still open ​

  • No decision recorded; ~6 repos have it, the rest don't.
  • If mandatory: a seeding path is needed (subagent-seeded, as floated in 37565687).

Working answer ​

None.