Random Character Relationship Web Generator

Description

Generate a fictional symmetric relationship graph from supplied characters with exact edge count, degree bounds, and optional connectivity using bounded search.

A structured creative brief combines a supplied bank of fictional material with explicit sequencing, timing, or compatibility rules. IDs and tags make those constraints inspectable; they do not assess the artistic meaning or quality of a scene.

Generate a fictional symmetric relationship graph from supplied characters with exact edge count, degree bounds, and optional connectivity using bounded search.

When to use this tool

Use this generator to create reproducible character relationship web cases from the supplied model or bank. Inspect the returned evidence before using cases in a test or exercise.

How to use the tool and how it works

Supply characters, relationshipTypes, edgeCount, minimumDegree, maximumDegree, connected in the field shapes below. Set seed when you need an explicit replay.
Run the tool and correct any input error. For generated controls, distinguish a successful fixture containing an invalid case from failure to generate the fixture.
Read fictional, relationships, degrees, components. Use the conventions below. Keep answer-bearing fields separate when presenting an exercise.

Construct a simple relationship graph satisfying requested edge count, degree bounds, and optional connectivity using bounded search. Sample one relationship type per unordered edge and return graph evidence with fictional character IDs.^[1]

Input field	Meaning and units	Accepted input
characters	Characters	Required. Array of Object; no unknown keys.; minimum items 1; maximum items 12.
characters[].id	Literal identifier used independently of display labels.	Required. Text; minimum UTF-16 length 1; maximum UTF-16 length 64.
characters[].name	Name	Required. Text; maximum UTF-16 length 2048.
relationshipTypes	Relationship Types	Required. Array of Text; minimum UTF-16 length 1; maximum UTF-16 length 64.; minimum items 1; maximum items 16.
edgeCount	Edge Count	Required. Safe integer; minimum 0; maximum 32.
minimumDegree	Minimum Degree	Required. Safe integer; minimum 0; maximum 11.
maximumDegree	Maximum Degree	Required. Safe integer; minimum 0; maximum 11.
connected	Connected	Required. Boolean.
seed	Optional numeric seed; takes precedence over context randomness. Without either, use the fixed tool.io default seed.	Optional. Safe integer.

Output field	Interpretation	Returned shape
fictional	Fictional	Required. Boolean; exactly true.
relationships	Relationships	Required. Array of Object; no unknown keys.; minimum items 0; maximum items 32.
relationships[].from	From	Required. Text; minimum UTF-16 length 1; maximum UTF-16 length 64.
relationships[].to	To	Required. Text; minimum UTF-16 length 1; maximum UTF-16 length 64.
relationships[].type	Type	Required. Text; minimum UTF-16 length 1; maximum UTF-16 length 64.
degrees	Degrees	Required. Array of Object; no unknown keys.; minimum items 1; maximum items 12.
degrees[].id	Literal identifier used independently of display labels.	Required. Text; minimum UTF-16 length 1; maximum UTF-16 length 64.
degrees[].degree	Degree	Required. Safe integer; minimum 0; maximum 11.
components	Components	Required. Safe integer; minimum 1; maximum 12.
randomness	Replay source and normalized 32-bit seed, or null seed for an advancing context source.	Required. Object; no unknown keys.
randomness.seed	Optional safe-integer replay seed; normalization and precedence are explained below.	Required. Safe integer. or Null.
randomness.source	Source	Required. Text; one of "context", "seed".

An explicit safe-integer seed takes precedence over injected context randomness and is normalized to an unsigned 32-bit integer. With no seed and no context source, replay uses the fixed tool.io default seed. A context source must return finite values from zero inclusive to one exclusive; its advancing state must be retained separately. randomness records the source and normalized seed, or null for context. These generators are not cryptographic random sources.

json

{
  "input": {
    "characters": [
      {
        "id": "ada",
        "name": "Ada of Reedport"
      },
      {
        "id": "ben",
        "name": "Ben the Mapmaker"
      },
      {
        "id": "cy",
        "name": "Cy of North Quay"
      }
    ],
    "relationshipTypes": [
      "friend",
      "rival"
    ],
    "edgeCount": 3,
    "minimumDegree": 2,
    "maximumDegree": 2,
    "connected": true,
    "seed": 42
  },
  "output": {
    "fictional": true,
    "relationships": [
      {
        "from": "ada",
        "to": "ben",
        "type": "rival"
      },
      {
        "from": "ada",
        "to": "cy",
        "type": "friend"
      },
      {
        "from": "ben",
        "to": "cy",
        "type": "rival"
      }
    ],
    "components": 1,
    "degrees": [
      {
        "id": "ada",
        "degree": 2
      },
      {
        "id": "ben",
        "degree": 2
      },
      {
        "id": "cy",
        "degree": 2
      }
    ],
    "randomness": {
      "seed": 42,
      "source": "seed"
    }
  }
}

Limitations and assumptions

Relationship types are fictional labels and do not infer real relationships. Output orientation represents one stored unordered pair rather than a reciprocal behavioral model; constraints can be infeasible.
A replay requires the same complete input and implementation. The stated sampling convention applies within its eligible space. A finite draw does not exhaust all possible outputs; repeats remain possible unless a distinct-selection rule is explicit.
The field tables state structural bounds; cross-field constraints and bounded search or output budgets also apply. Unknown keys are rejected where the object contract disallows them. Input errors are distinct from null fields and deliberate invalid controls in a successful output.

Alternative or Complementary methods

For a supplied example, inspect the returned construction or delegated check directly. To evaluate a consumer, also test cases chosen for its own boundaries; a generated finite corpus does not establish exhaustive coverage.

References

Tool behavior and example: Random Character Relationship Web Generator — tool.io

Similar or alternative tools

Random Character Entry and Exit Cue Plan Generator
Build fictional cast-presence traces with exits before entries, role-doubling checks, simultaneous performer limits, and complete cue ledgers.
Random Character Objective Conflict Matrix Generator
Assign distinct supplied fictional objectives and construct a symmetric conflict matrix from explicit incompatibility tags and caller-provided resolutions.