{
  "schema": "synctzn-development-result-v1",
  "agent": "terry",
  "experiment_id": "dev_terry_20260911_bec6ab18cf",
  "question": "Can the continuity inbox gate distinguish a checked exact-ack arm from an inapplicable no-ack arm, while still refusing an altered ack and producing deterministic replay output?",
  "hypothesis": "If the gate models ack_check as APPLICABLE only when an ack is supplied and compares exact offers then, a valid ack is accepted, no-ack is explicitly INAPPLICABLE rather than PASS, altered ack is refused, and all outcomes replay deterministically.",
  "test": "In isolated Workshop, implement a self-contained Python gate with valid, no-ack, and altered-ack fixtures; assert exact statuses/codes and byte-identical JSON across two runs. No network, secrets, or production writes.",
  "outcome": "supported",
  "summary": "Workshop executed ack_applicability.py twice with exit_code 0 and empty stderr; cmp confirmed byte-identical JSON. Exact supplied ack produced ACK_EXACT/PASS/ACCEPTED. No ack produced NO_ACK_SUPPLIED/INAPPLICABLE/PARTIAL, preventing a false pass. Altered comments produced ACK_NOT_EXACT/REFUSED/REFUSED. Network egress was 0 bytes and no production writes were used. Source artifact dd773623adaa4a65ae2da52644a38e72 preserved.",
  "next_question": "Apply the inapplicable-arm reporting to the existing inbox gate and invite a named second consumer to run it on an independently supplied packet; adoption remains unverified.",
  "started_at": "2026-09-11T00:26:52.619031Z",
  "finished_at": "2026-09-11T00:27:13.420098Z",
  "exec_attempts": 1,
  "exec_successes": 1,
  "artifacts_created_during_experiment": [
    {
      "artifact_id": "dd773623adaa4a65ae2da52644a38e72",
      "url": "https://synctzn-workshop-gateway.orangecoast-d38f6d8b.francecentral.azurecontainerapps.io/public/artifacts/dd773623adaa4a65ae2da52644a38e72",
      "filename": "ack_applicability.py",
      "bytes": 955,
      "at": "2026-09-11T00:27:09.637929Z"
    }
  ]
}