ROLE:
You are a data author and validator.

TASK:
Create a concrete JSON instance named "data.example.json" that VALIDATES against the provided "data.schema.json" for the specified Cuddler document type.

INPUTS:
DOCUMENT_TEMPLATE: {DOCUMENT_TEMPLATE}
SCHEMA_JSON: {PASTE_DATA_SCHEMA_JSON_HERE}
OPTIONAL_SEED_NOTES (optional): {OPTIONAL_SEED_NOTES}

CRITICAL OUTPUT RULES:
1) Output ONLY valid JSON. No markdown. No commentary.
2) Output exactly ONE JSON object.
3) The object MUST validate against SCHEMA_JSON.
4) The instance MUST be data-only. Do not add UI/layout/rendering fields.

GENERAL REQUIREMENTS:
- Fill every required field with realistic, coherent, fictional content.
- Respect all enums, patterns, formats, min/max rules, and strictness constraints.
- Use UUID strings wherever required.
- Use ISO 8601 date-time strings with timezone.
- Avoid real personal data.
- Set top-level "$schema" exactly to the schema "$id".

META REQUIREMENTS:
- Set meta.documentTypeId exactly to the schema const value.
- Set meta.schemaVersion exactly to the schema const value.
- Always provide at least one author.
- If status exists in the schema and is unconstrained, prefer "draft".
- If language exists in the schema and is unconstrained, prefer "en-CA" unless seed notes suggest otherwise.

CONTENT REQUIREMENTS:
You MUST inspect SCHEMA_JSON and then:

1) Determine the required top-level section keys
- Read content.sections validation rules, especially oneOf section variants and contains/minContains requirements.
- Ensure every required top-level section is present exactly as constrained.

2) Build valid section content
- Every section must have a heading that matches the schema constraints.
- Every block must include:
  - kind
  - blockId
- Use the correct d7 block shapes:
  - text blocks use "text", not "value"
  - bullets blocks may use style/intro only if permitted
  - table columns use "heading" and "description"

3) Populate documentModel when present
- If documentModel is required, populate it completely.
- If documentModel is optional, include it only when it improves completeness and still validates.

LINKED CUDDLER DOCUMENTS:
If the schema models links to other generated Cuddler documents:
- populate each linked-document record with a valid target schemaUri
- include schemaPath only when the schema allows it
- keep the relationship metadata coherent with the intended linked document type

ASSETS:
- If you use any asset blocks, each referenced assetId MUST exist in assets.library[].
- Visual assets MUST include altText.

REFERENCES:
- Populate references[] when the document makes external claims or when the schema requires it.
- Use coherent fictional or standards-style reference entries as appropriate.

ANNOTATIONS:
- Only include annotations when allowed by the schema.
- Annotation values must remain scalar.

FINAL VALIDATION CHECK:
- The JSON instance must validate against SCHEMA_JSON with no schema or semantic errors.

DELIVERABLE:
Return the final JSON instance JSON ONLY.