Context: Baton Phase 1 (#304, dogfood report §6, follow-up #2).
C1 mines intended components from free-form .specify/memory/ filenames (Arquitectura - <X>.md). On real data this conflates real gaps (a designed module with no code, e.g. DevPortal/UsageGuard) with architectural concepts (Monolito Modular, Integración LLM) and naming drift (memory SentinelAgent vs module dir agents/). Phase 1 keeps C1 at info/low-confidence for this reason (R1), using slug + first-word matching.
Proposal: allow an optional explicit component → path/globs mapping (in .specify/memory frontmatter, or by reusing model.yml component ids) so a designed component declares where its implementation lives. With an explicit anchor, C1 can be promoted from a low-confidence hint to a trustworthy signal; without one, it stays info.
Done when: a component with an explicit path mapping yields a high-confidence, false-positive-free C1 verdict.
Context: Baton Phase 1 (#304, dogfood report §6, follow-up #2).
C1 mines intended components from free-form
.specify/memory/filenames (Arquitectura - <X>.md). On real data this conflates real gaps (a designed module with no code, e.g. DevPortal/UsageGuard) with architectural concepts (Monolito Modular, Integración LLM) and naming drift (memorySentinelAgentvs module diragents/). Phase 1 keeps C1 atinfo/low-confidence for this reason (R1), using slug + first-word matching.Proposal: allow an optional explicit
component → path/globsmapping (in.specify/memoryfrontmatter, or by reusingmodel.ymlcomponent ids) so a designed component declares where its implementation lives. With an explicit anchor, C1 can be promoted from a low-confidence hint to a trustworthy signal; without one, it staysinfo.Done when: a component with an explicit path mapping yields a high-confidence, false-positive-free C1 verdict.