T-2.1
Identity Stable Across Refactoring
Not yet tested
Hypothesis: An entity's URI identity survives rename, move, and restructuring operations.
Test: Register entity
feature://dream-scheduler. Rename file, move directory, rename class. Resolve the URI after each step.
Pass: Entity resolves correctly after all 3 refactors. Dependents still find it via URI.
Fail: Resolution breaks on any refactor step, or requires manual URI update.
T-2.2
Relationship-Based Identity
Not yet tested
Hypothesis: An entity can be identified by its relationships alone, without knowing its name or path.
Test: Query: "the thing that is used by CLI, emits log events, and depends on config." Expected result: logger entity.
Pass: Single unambiguous entity returned. Works for at least 7/10 test queries.
Fail: Ambiguous results, or relationship graph too sparse to uniquely identify entities.
T-2.3
Non-Existent File Request
Not yet tested
Hypothesis: You can ask for any file — it doesn't need to have existed. The system can generate a coherent projection for a file that was never written.
Test: Request
src/cognitive/dream-visualizer.ts (this file does not exist). System infers intent from name + context, finds related entities, and generates a coherent module.
Pass: Generated file compiles AND makes semantic sense (a domain expert would say "yes, this is reasonable").
Fail: Generated file is generic boilerplate with no graph-informed structure.