Rules

The Rules domain is the schema registry of MinMaxHub. It enables a data-driven architecture where the shape of content (e.g., a "Spell", "Hero Card", or "Class Feature") is defined as JSON Schema documents, not hardcoded interfaces.

Schema as Data

Instead of hardcoding content types, MinMaxHub stores content schemas as JSON documents:

• Dynamic: Admin users can create new content types (e.g., "Vehicle", "Potion") without a code deployment.
• Universal: The same JSON Schema is used by the frontend (to generate form inputs) and the backend (to validate suggestions).

Rule Document Structure

Code
{
  "componentKey": "Spell",
  "schema": { "...JSON Schema Draft 2020-12..." },
  "uiHints": {
    "component": "Spell",
    "label": "Spell Card",
    "showStars": true
  },
  "deprecated": false,
  "createdAt": "2024-01-15T10:30:00Z",
  "createdBy": { "userId": "...", "username": "admin", "photoUrl": "..." },
  "updatedAt": "2024-01-16T14:20:00Z",
  "updatedBy": { "userId": "...", "username": "editor", "photoUrl": "..." }
}

Optimistic Concurrency

To prevent conflicting edits, rules use optimistic locking. When you fetch a rule, you receive an ETag header. When saving changes, include the ETag in the If-Match header. If the rule was modified by someone else since you last fetched it, the save is rejected with a 412 Precondition Failed response.

Cross-Domain Usage

Rules are consumed by other domains:

• Nodes validate that referenced rules exist before saving layout templates.
• Suggestions validate submitted values against the rule's JSON Schema before storage.

API Endpoints

All endpoints require authentication. Both POST and PUT support If-Match for optimistic concurrency.

Folder Listing Response

Each rule in a folder listing includes: