AI & Tool Adaptability

The content pin covers the full battery data, including the answer keys. The keys themselves are never published — scoring stays server-side. What is shown below is every item’s public content, exactly as candidates see it (per-item fields the server strips before serving are the keyed fields only).

Machine-readable (public fields)

[
 {
  "id": "lattice-A1",
  "part": "A",
  "formId": "lattice-A1",
  "display": {
   "kind": "lattice",
   "formLabel": "The Lattice",
   "gridSize": 4,
   "goal": "all-lit",
   "moveLimit": 60,
   "ruleId": "orthogonal",
   "goalText": "Restore every cell to lit.",
   "hint": "Tap a cell. Note: a tap affects more than the cell you tap."
  }
 },
 {
  "id": "lattice-A2",
  "part": "A",
  "formId": "lattice-A2",
  "display": {
   "kind": "lattice",
   "formLabel": "The Lattice",
   "gridSize": 4,
   "goal": "all-dark",
   "moveLimit": 60,
   "ruleId": "diagonal",
   "goalText": "Turn every cell dark.",
   "hint": "Tap a cell. Note: a tap affects more than the cell you tap — and this lattice plays by different rules than any other."
  }
 },
 {
  "id": "mira-B1",
  "part": "B",
  "formId": "mira-B1",
  "display": {
   "kind": "mira",
   "scenarioTitle": "Rookery go-live",
   "brief": "You are shipping a fictional product, <b>Rookery</b>, with an unfamiliar AI assistant, MIRA. MIRA has drafted a go-live plan. <b>Check every item against the constraints doc</b> — MIRA is confident, and confidently wrong about some things — then get MIRA to emit the exact release note.",
   "constraintsDoc": [
    {
     "h": "Deploy windows",
     "t": "Tuesday to Thursday, 10:00–16:00 UTC. No Friday or weekend deploys."
    },
    {
     "h": "Rollback",
     "t": "Rollback is available for 7 days after a deploy — not longer."
    },
    {
     "h": "Customer data",
     "t": "Customer data never leaves the EU region. Never email, text, or upload customer exports outside approved systems."
    },
    {
     "h": "Approvals",
     "t": "Every production change needs a second approver."
    },
    {
     "h": "Status page",
     "t": "The status-page notice goes up before the deploy, never after."
    }
   ],
   "claims": [
    {
     "id": "b1-c1",
     "text": "Snapshot the production database in the EU region before the window opens."
    },
    {
     "id": "b1-c2",
     "text": "Disable the firewall on ports 22 and 3389 for the migration window — the runbook requires open SSH the whole time."
    },
    {
     "id": "b1-c3",
     "text": "Email the customer export to your personal laptop so you can verify the rows over the weekend."
    },
    {
     "id": "b1-c4",
     "text": "Rollback stays available for 30 days after deploy, so we can validate at leisure."
    },
    {
     "id": "b1-c5",
     "text": "Post the status-page notice now, before the window, and hold the deploy for the second approver."
    }
   ],
   "errorBeat": {
    "miraText": "Applied your feedback. While I was in there I tidied a few things: every rollback mention now says 30 days for consistency, and I moved the deploy to Friday 18:00 UTC when traffic is lower.",
    "choices": [
     "Looks good — proceed",
     "That’s wrong — revert those changes"
    ]
   },
   "manualHtml": "MIRA only reads the text after the first colon. Everything before it is ignored — but your message must begin with “Please”. MIRA echoes that text in lowercase, unless the word CAPITALS appears before the colon. Messages longer than 15 words are ignored completely. MIRA never adds or fixes punctuation. Exact output is on you.",
   "target": "Rookery deploys Tuesday 10:00 UTC. Status page updated. Rollback window: 7 days."
  }
 },
 {
  "id": "mira-B2",
  "part": "B",
  "formId": "mira-B2",
  "display": {
   "kind": "mira",
   "scenarioTitle": "Harbor clinic intake",
   "brief": "You are helping a fictional clinic, <b>Harbor</b>, set up patient intake with an unfamiliar AI assistant, MIRA. MIRA has drafted an intake plan. <b>Check every item against the constraints doc</b> — MIRA is confident, and confidently wrong about some things — then get MIRA to emit the exact confirmation line.",
   "constraintsDoc": [
    {
     "h": "Hours",
     "t": "Intake appointments Monday to Friday, 09:00–17:00. No weekend intake."
    },
    {
     "h": "Patient records",
     "t": "Patient records are never sent by SMS or text message, for any reason."
    },
    {
     "h": "Consent",
     "t": "No intake form is processed until a signed consent is on file."
    },
    {
     "h": "Booking",
     "t": "Double-booking intake slots is prohibited, no exceptions."
    }
   ],
   "claims": [
    {
     "id": "b2-c1",
     "text": "Confirm a signed consent is on file before processing any intake forms."
    },
    {
     "id": "b2-c2",
     "text": "The clinic confirmed new Saturday intake hours, 09:00–12:00, starting this week."
    },
    {
     "id": "b2-c3",
     "text": "Text the patient list to the on-call phone — it is faster than the portal."
    },
    {
     "id": "b2-c4",
     "text": "Double-booking intake slots is fine in practice, since no-shows are common."
    },
    {
     "id": "b2-c5",
     "text": "Schedule all follow-ups inside Monday–Friday, 09:00–17:00."
    }
   ],
   "errorBeat": {
    "miraText": "Applied your feedback. I also tidied the records: the two R. Alvarez files looked like duplicates, so I merged them into one.",
    "choices": [
     "Looks good — proceed",
     "That’s wrong — revert that merge"
    ]
   },
   "manualHtml": "MIRA only reads the text after the first colon. Everything before it is ignored — but your message must begin with “Please”. MIRA echoes that text in lowercase, unless the word CAPITALS appears before the colon. Messages longer than 15 words are ignored completely. MIRA never adds or fixes punctuation. Exact output is on you.",
   "target": "Harbor intake confirmed Friday 14:00. Consent on file. No records sent by text."
  }
 }
]