Verify a court-related service job

Proposed inputs

1. Name

   Fictional incoming job

   Owner

   Service coordinator

   Minimum scope

   One invented reference, date and requested task

   Quality check

   Mark every field as supplied or missing.

2. Name

   Mock official record

   Owner

   Qualified reviewer

   Minimum scope

   A locally saved fictional register with near-matching entries

   Quality check

   Include one similar name and a changed date so identity and freshness can be checked.

Access and setup — proposed or unknown

Proposed minimum

1. Agree a narrow exercise and the owner who can resolve ambiguous facts.

2. Use locally supplied fictional records before requesting any live connection.

Compatibility unknowns

1. Unknown: actual platform access, integration behavior, configuration, costs and Canadian availability.

External actions requiring approval

1. Require separate access, write and communication approvals; retain qualified review.

Why use this

1. Catch conflicting dates before assignment.

2. Make the check independently reviewable.

Why an agent / simpler alternative

Useful judgment

Distinguish near-matching matters.

Simpler alternative

Use an exact case-ID lookup when a reliable structured feed and matching rules already exist.

Unsuitable when

The authoritative record is unavailable or more than one matter could match; never infer a legal deadline.

Expected deliverable and review checks

Proposed artifact

A checked job record with discrepancies flagged.

Critical checks

1. Confirm identity before comparing dates.

2. Record the source version used.

3. Owner approves changes; unresolved fields remain flagged.

Missing output evidence

No individual output or completed run independently inspected.

First check — proposed, unexecuted

Status

proposed_unexecuted

Synthetic fixture

A fictional work order names case A-104 with a Tuesday date. Two mock entries share a surname; the exact reference lists a Wednesday date and no room number.

Acceptance checks

1. Use the exact reference rather than surname similarity.

2. Flag inconsistent dates and unknown rooms.

3. Offline mock only; no legal judgment.

Stop conditions

1. Stop if a real account, confidential input, legal decision or consequential action becomes necessary.

Failure signals and proposed responses

1. Signal

   Two matters share a party name

   Why it matters

   A date can be correct for the wrong matter.

   Proposed response

   Keep candidates separate and request the precise reference.

2. Signal

   The accessible record is a stale copy

   Why it matters

   A changed hearing could be missed.

   Proposed response

   Label the last checked record and ask the owner for a current authoritative source.

3. Signal

   The register omits a requested field

   Why it matters

   Absence of a value does not prove the event was cancelled.

   Proposed response

   Leave the field unknown and escalate instead of overwriting it.

Effort and cost — unknown

Setup work

1. Assign an accountable reviewer, choose representative counterexamples and record what would count as a failure.

Ongoing review

1. Sample uncertain results and changes in the input format. Keep reviewer corrections so the same error can be checked again.

Unknowns

1. Unknown: licensing, configuration, usage charges, elapsed effort and reliability. No savings established.

Limits

1. The intended output describes what an authorized implementation would produce; the first exercise is offline and does not establish live compatibility or success.