T-9.1
Instance Isolation
Not yet tested
Hypothesis: Multiple DreamGraph instances running on the same machine maintain strictly isolated graph states with no cross-contamination.
Test: Run two instances simultaneously. Write entity A in instance 1, entity B in instance 2. Verify neither instance can see the other's entities.
Pass: Complete isolation. Zero cross-instance entity leakage.
Fail: Any entity visible across instance boundaries without explicit federation.
T-9.2
Cross-Instance Entity Resolution
Not yet tested
Hypothesis: A federated query can resolve an entity across instances using a namespaced URI scheme.
Test: Instance A defines
feature://auth-module. Instance B queries instanceA://feature://auth-module. Verify resolution returns the correct entity with full metadata.
Pass: Entity resolved correctly. Metadata intact. Latency < 2s for cross-instance query.
Fail: Resolution fails, metadata lost, or latency exceeds 5s.
T-9.3
Archetype Transfer
Not yet tested
Hypothesis: Dream archetypes (learned patterns) can be exported from one instance and imported into another, accelerating the receiving instance's learning.
Test: Instance A dreams for 10 cycles, producing archetypes. Export archetypes. Import into fresh Instance B. Compare Instance B's first dream cycle quality against a control instance with no imported archetypes.
Pass: Instance B's first dream cycle matches or exceeds Instance A's 5th cycle quality.
Fail: Imported archetypes produce no measurable improvement over a fresh start.
T-9.4
Cross-Instance Projection
Not yet tested
Hypothesis: A file can be projected that references entities from multiple instances, with the projection engine combining graph data across boundaries.
Test: Define a module in Instance A that depends on an interface in Instance B. Project the module. Verify the import resolves and the projected file compiles.
Pass: Cross-instance projection compiles. Imports resolve. Type-checking passes.
Fail: Unresolved imports, type errors, or projection engine cannot traverse instance boundaries.
T-9.5
Version-Aware Federation
Not yet tested
Hypothesis: Federated queries can target specific versions of an entity, enabling reproducible cross-instance builds.
Test: Entity evolves through 3 versions in Instance A. Instance B queries version 2 specifically. Verify correct version returned.
Pass: Correct version returned. Projection using pinned version is stable across rebuilds.
Fail: Version pinning not supported, or wrong version returned.
T-9.6
Namespace Collision Handling
Not yet tested
Hypothesis: When two instances define entities with the same name, the federation layer handles namespace collisions gracefully rather than silently merging or overwriting.
Test: Both instances define
feature://logger. Attempt federated query without namespace qualifier. System should return an error or disambiguation prompt.
Pass: Clear error with disambiguation options. No silent merge. Qualified queries resolve correctly.
Fail: Silent merge, arbitrary choice, or crash on collision.