Boundary Flow To Compute

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": "seed",
      "value": {
        "type": "integer",
        "value": "15"
      }
    },
    {
      "name": "scenario",
      "value": {
        "type": "text",
        "value": "boundary-flow-to-compute"
      }
    }
  ],
  "type": "record"
}

{
  "code": "ZL-DOMAIN-0004",
  "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_integration_flow_to_compute_14;

public value Boundary {
    public compiled compute message target(type: Class<Self>, input: Int64)
        -> Int64 effects { compute } { return input + 1; }
    // FAIL-CLOSED: flow->compute requires recorded-activity; this direct call
    // deliberately exercises ZL-DOMAIN-0004 until that boundary has source syntax.
    public compiled flow message source(type: Class<Self>, input: Int64)
        -> Int64 effects { flow, compute } {
        return Boundary.target(input);
    }
}

Execution contract

artifact-roundtrip

Selector

benchmark_integration_flow_to_compute_14.Boundary.source

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"
  }
]