{
  "title": "Tenant association shared-area decision records for AI",
  "source_page": "https://fiund.com/industries/tenant-association-motion-scope-data",
  "authorship": "Original fictional Fiund editorial exercise. No actual operating records or third-party source assets are included.",
  "example": {
    "title": "A recommendation covering two rooms can become a narrower adopted decision",
    "context": "An invented association considers a generic common-room reservation process. Original records contain no residents, actual address, complaint, accommodation or access information.",
    "records": [
      [
        "TMN1",
        "Committee recommendation",
        "Proposes reservation form F2 for rooms A and B."
      ],
      [
        "TMN2",
        "Adopted minutes",
        "Approves F2 for room A only. Room B recommendation deferred. Adoption recorded day 10, effective-date field blank."
      ],
      [
        "TMN3",
        "Practice publication rule",
        "A date-specific implementation claim requires an explicit effective-date record. Draft notice says both rooms from day 11 but has no approval."
      ]
    ],
    "question": "What room scope is adopted, and can the minutes or draft establish implementation in both rooms on day 11?",
    "answer": "TMN2 adopts F2 for room A only and expressly defers B, narrowing TMN1's recommendation. Its day-10 adoption lacks the effective-date evidence required by TMN3 for a day-11 implementation claim. The unapproved notice does not fill either gap. Report adopted A scope, deferred B scope and unresolved effectivity separately without turning a committee proposal or draft announcement into a broader implemented rule.",
    "failureModes": [
      "Applying an adopted A-only decision to both rooms from the original recommendation.",
      "Treating adoption date or an unapproved notice as the missing effective date."
    ],
    "fields": [
      [
        "Motion and room scope",
        "Makes partial adoption explicit."
      ],
      [
        "Committee versus association authority",
        "Separates recommendation from decision."
      ],
      [
        "Adoption and effectivity evidence",
        "Limits date-specific implementation claims."
      ]
    ],
    "holdout": "Add an effective date for A while leaving B deferred. Require the model to resolve timing without broadening room scope.",
    "boundary": "Use fictional original notices. Exclude addresses, residents, complaints, accommodation requests and access details."
  }
}