Refinements can be sourced from anywhere, not only discovered limitations

The NEXUS methodology must not imply or prescribe that
refinements and requirements are only generated by
discovered limitations. Insights that drive methodology
evolution can originate from any source, and NEXUS must
reflect that explicitly.

Why It's Needed

The early framing of the relationship between limitations
and requirements — "limitations lead to requirements" —
was accurate as a description of one pathway but
misleading as a description of the whole. It implies a
reactive model: something breaks or constrains, then
something gets written. In practice, insights emerge
from many sources that have nothing to do with
limitations.

This was identified while building out LOGOS →
Requirements. Several requirements had no limitation
as their source — they came from design principles,
first-principles thinking, and the NEXUS methodology
itself. Forcing them to trace back to a limitation
would have been dishonest.

The Refinement

NEXUS explicitly acknowledges the full range of sources
that can drive methodology evolution and requirement
generation:

• Discovered limitations — a constraint in an
  existing tool or dependency
• Design principles — something that must be true
  for the system to be coherent with its own values
• First-principles reasoning — derived from how
  the system should work, independent of any constraint
• Active use insights — something discovered by
  using the methodology and finding it missing or
  improvable
• Help requests — a user need surfaces something
  unhandled
• Adjacent ideas — something observed elsewhere
  worth bringing in
• Methodology self-reflection — NEXUS examining
  its own assumptions and correcting them

No source is more legitimate than another. Each topic
records its source honestly.

Resolution

Addressed by making source an open field in all
refinement and requirement topics — not constrained
to limitation references. The methodology documentation
should explicitly name the full range of valid sources.

Source

Discovered while building LOGOS → Requirements and
finding that several requirements had no limitation
as their source. This refinement is itself an example
of one sourced from active use insight rather than
a discovered limitation — the methodology correcting
its own implicit framing through use.