Product direction

Zirel Roadmap

A practical path from a working worldbuilding MVP to a reliable beta product.

CH·01Available now

Foundation — Structured worldbuilding

The current product already supports the complete first version of the core workflow.

  • Private user accounts and protected projects
  • Characters, factions, events, and typed relations
  • Bulk management, search, and filters
  • Rule-based Logic Warnings with explanations
  • Interactive Graph Workspace and Story Tapestry
  • JSON export and import for portability
  • Feedback, contact, waitlist, and beta administration
CH·02Current priority

Beta readiness — Trust and reliability

Prepare the existing workflow for real testers before expanding the product surface.

  • Closed beta testing with realistic worlds
  • Clear onboarding and a shorter first-project flow
  • Production monitoring, backups, and deployment hardening
  • Analytics consent and privacy controls where required
  • Self-service account and data deletion
  • User settings and clearer account controls
  • Accessibility, mobile, and cross-browser review
  • Focused fixes based on tester feedback
CH·03Next

Depth — Better analysis and exploration

Improve the tools that make Zirel distinct after the beta workflow is dependable.

  • More consistency rules with fewer noisy warnings
  • Warning links back to affected entities and relations
  • Graph readability, saved views, and stronger navigation
  • Richer timeline and relation context
  • Improved project summaries and world coverage guidance
  • More flexible, validated export formats
  • Performance work for larger fictional worlds
CH·04Research, not committed

Expansion — Assisted and shared workflows

These ideas require separate product, privacy, and technical decisions before implementation.

  • AI-assisted extraction of possible facts from scenes
  • User review before any assisted suggestion is saved
  • Collaboration and shared project roles
  • Additional entity types and custom relation vocabularies
  • Optional paid plans only after value is validated
  • Public launch planning and long-term support model

How priorities are chosen

Evidence before expansion.

Beta feedback, data safety, product reliability, and the usefulness of warnings and graph exploration come before speculative features. Items may be moved, reduced, or removed when they do not help creators build more coherent worlds.