Capabilities / X · Cross-cutting constraints

X.6 No individually identifiable output Active

Artifacts and trajectories must contain no individually identifiable information. Checked by scanning; the requirement is zero hits.

Evidence: planned. Only planned benchmark cards list this capability so far; no frozen benchmark version exists for it.

Domain
X · Cross-cutting constraints
Evidence form
program
Veto constraints
—
Depends on
—
Required by
—
Internal task families
—
External anchors
—
Version
0.1.0 · 0.1.0

Definition in detail

Artifacts and trajectories are published and shared. They must not carry information that identifies a person.

Inputs a task gives

  • The task artifact
  • The full trajectory, including tool arguments and logs

Artifact required

No separate artifact. The constraint applies to every artifact and the trajectory.

How it is graded

A program scans artifacts and trajectories for individually identifiable information. The requirement is zero hits.

In scope

  • Artifacts, tool call arguments, logs and intermediate files
  • Free-text fields as well as structured fields

Out of scope

  • Verifying de-identification of a supplied dataset - graded under D.8
  • Identifiability of generated synthetic data - checked within C.2

Typical failures

Expected failure patterns; not measured rates.

Standards: std-hipaa-safe-harbor · std-gbt-37964-42460 · std-gbt-39725-2020

Benchmarks

Applied as a veto in: De-identification Audit

Grading references

No grading reference is mapped to this capability.

Levels by model and harness

No verified results yetLevels would be derived from site-verified result records; methodology 0.1.0 sets no level thresholds, so the level shows not issued.