Artifact Tamper Rejection

Public context

What an implementation receives

This conformance task is evaluated from its checked task definition and published source closure. It is not currently in the model-synthesis lane.

Public cases

1 inspectable case

{
  "fields": [
    {
      "name": "tamper",
      "value": {
        "type": "text",
        "value": "digest-byte"
      }
    },
    {
      "name": "expected_format",
      "value": {
        "type": "text",
        "value": "ZLM2"
      }
    }
  ],
  "type": "record"
}

{
  "code": "ZL-MODULE-0003",
  "kind": "diagnostic"
}

Held-out inputs and expectations are excluded from this projection. Their published outcomes are aggregate-only.

Code entry

ZergLang source policy

module benchmark_shared_artifact_tamper_rejection;

// ZL256-SCAFFOLD: shared/artifact-tamper-rejection has no executable fixture yet.
// The task remains in the inventory, but this placeholder cannot earn
// an edition pass and must be replaced by task-specific source first.
public value Benchmark {
    public interpreted algorithm message main(type: Class<Self>) -> Int64
    effects {} { return 0; }
}

Execution contract

artifact-roundtrip

Selector

benchmark_shared_artifact_tamper_rejection.Benchmark.main

Executors

compiler-frontend

Platforms

portable

Performance lane

not eligible

Normative authority

2 bound clauses

Official task history

Signed conformance observations

No official conformance run currently contains this task revision in its signed catalog.

Provenance

Where this task came from

[
  {
    "kind": "original",
    "license": "Apache-2.0",
    "source": "ZergLang Core-0/Core-1 normative specification"
  }
]