openpond-sdk 0.6.7 → 0.8.0

package/MODEL_STARTERS.md

@@ -147,3 +147,28 @@ retain a null metric value. The client verifies workspace, manifest,
 population, grading role, metric references and result hashes on readback.
 Hosts remain responsible for owner-authenticated evidence and durable
 dispatch/cancellation; a content hash is not producer authentication.
+
+### Dataset evaluations without a model configuration
+
+SDK 0.8 allows an evaluation request to set `modelProjectId: null` and select an
+exact published dataset release directly. The hosted executor still resolves the
+complete package and checks its supported runtime before admitting the run.
+Model-configuration-backed requests continue to require their attached release.
+
+`policy.messages` optionally supplies system, user and assistant context before
+each example. Those messages form part of the immutable execution policy hash;
+changing them produces a different evaluation configuration. Dataset reference
+answers are never included in these messages by the host.
+
+The optional `project` field contains `{ id, revision, contentHash, targetId }`.
+Its hash identifies the selected Project **content**, and `targetId` may be null
+for an ad hoc evaluation inside that Project. Hosts authorize the Project and
+resolve its retained revision before execution. Request, summary and manifest
+must agree on this provenance. Project attribution is not inferred from shared
+datasets or model configurations.
+
+`runs.list({ projectId })` reads that Project's attributed evaluations;
+`runs.list({})` reads authorized workspace history. Existing
+`runs.list({ modelProjectId })` filtering remains available. Callers must handle
+nullable `summary.modelProjectId` for independent evaluations. No trained model
+or serving deployment is created by running an evaluation.

package/TASKSETS.md

@@ -304,3 +304,11 @@ Parquet collections through the dataset reader. Search never examines private
 answers. Draft edits invalidate the index, and a published release remains
 separate from its draft. No task listing, editing, or labeling operation starts
 a training job.
+
+Independent dataset writes may include `originProjectId` at creation. This is
+immutable creation provenance, not exclusive ownership or a sharing grant. The
+host verifies that the Project belongs to the same workspace and is active.
+Receipts and list entries retain the origin so unpublished drafts remain visible
+in their originating Project. A release can still be used across Projects through
+explicit associations; changing or removing that association does not rewrite
+where the draft was created.