Problem
Absence from one file, branch, repository, device or current context does not prove a capability is absent. Premature creation produces duplication, fragmented authority and avoidable maintenance.
Capability-Gap Reconnaissance
A conditional method for checking what the ecosystem already contains before an observation becomes new implementation work.
Flow
Observation / signal -> capability-gap gate when triggered -> inspect repos, projects, branches, PRs, workflows and indexes -> REUSE | ADAPT | CONTINUE | CREATE | NO ACTION
Boundary
not found here != does not exist
main != complete historical evidence
discovery != authority
recommendation != execution
Use when
Use it when a signal appears to imply a reusable capability, unfinished implementation, overlapping work or a potentially reusable mechanism. It is a conditional gate inside a broader observation flow, not a separate note type or automatic build instruction.
Authority and scope
This public page projects the method's purpose and invariants without exposing private estate details. Claims about what exists in a current estate still require fresh evidence from the relevant repositories, branches, runtime surfaces and indexes.