In pursuit of DeckoSystems and beyond, this is a first step.

Need to support more than one deck in one or more ways:

• Support multiple independent small Decko instances in one Database and web app instance.
• Support serving and rendering cards and card nests from more than one Deck.
  • Use for one or more (read only) Decks for core and modular types, sets and rules. Have much smaller private Decks for private Cards and data.
  • Use for card-mods and other Card based networked content. Use DeckoSystems protocols to update and cache networked contend in local database (cards db with distinct deck ID).
• Multideck namespace integration (DeckoSystems+names)