M-2: Create Multiverse

[spuentesp]

Category: manage | Epic: 1 | Priority: high

Summary

Create a new Multiverse node under the Omniverse. A Multiverse groups related
Universes that share a game system or thematic connection. Each Multiverse
can have its own rule system (D&D 5e, Pathfinder, etc.).

Acceptance Criteria

• neo4j_create_multiverse creates node with required fields
• Multiverse is linked to Omniverse via CONTAINS relationship
• Name validation prevents duplicates within Omniverse
• System name is stored for rule system reference
• CLI provides both interactive and flag-based creation
• Success confirmation displays multiverse_id
• Unit tests cover success and validation failures

Dependencies

This use case depends on:

• DL-1
• M-1

Blocks

This use case blocks:

• M-4

Implementation

Layer: 3

Files to create:

• packages/cli/src/monitor_cli/commands/manage/multiverse.py
  Files to modify:
• packages/cli/src/monitor_cli/commands/manage/__init__.py

NEO4J Operations:

• neo4j_create_multiverse (authority: CanonKeeper)

Notes:

• System name helps link to RS-* (Rules System) use cases
• Consider adding system validation against known systems

Testing Requirements

Minimum coverage: 80%

Unit tests:

• test_create_multiverse_success: valid params creates node
• test_create_multiverse_duplicate: duplicate name fails
• test_create_multiverse_missing_omniverse: fails gracefully
• test_create_multiverse_validation: invalid params rejected

Integration tests:

• test_multiverse_lifecycle: create and verify in database
• test_multiverse_cli: CLI command works correctly

References

Documentation:

• docs/ontology/ONTOLOGY.md#21-world-structure
• docs/USE_CASES.md#m-2-create-multiverse
  Code:
• packages/data-layer/src/monitor_data/tools/neo4j_tools.py
• packages/data-layer/src/monitor_data/schemas/universe.py

---

Generated from /home/sebas/monitor2/docs/use-cases/manage/M-2.yml