README

This category is where the NEXUS methodology refines itself.

Each topic here is a single refinement — a gap discovered
through active use, an ambiguity that forced an undocumented
decision, an extension to the methodology, or a pattern that
emerged and needs to be made explicit. Refinements come from
anywhere: applying NEXUS to a real project, finding it silent
on something, observing a better way, or correcting an
assumption that turned out to be wrong.

What a Refinement Topic Contains

• What it is — a clear statement of the gap, ambiguity,
  or extension
• Why it's needed — the situation that exposed it
• Resolution — how the methodology addresses it, or
  the direction being explored
• Cross-references — links to related refinements,
  methodology wiki topics, or project examples where
  the gap was encountered

What This Is Not

This is not a critique of NEXUS. It is the methodology
knowing itself — surfacing the places where it is
incomplete, ambiguous, or untested and making them
visible and improvable. An undocumented decision is a
hidden gap. Recording it here makes it explicit.

This is also not where the methodology is documented.
The NEXUS wiki topics in the parent category are the
reference layer. This subcategory is where that
reference layer gets questioned, corrected, and extended.

Topic Types

Idea — a candidate refinement not yet fully
understood. Something feels incomplete or improvable
but the right answer isn't clear yet. Open for
discussion.

Problem — a refinement understood well enough to
articulate. Clear statement, known source, known
direction. Status model:

• New — identified, not yet worked through
• Planned — direction is taking shape
• Started — actively being worked out
• Done — addressed in the methodology
• Accepted — consciously acknowledged as a known
  limitation or deliberate tradeoff in the methodology

An Idea becomes a Problem when the gap is understood
well enough to state clearly.