01
Joint Optimization Across Model Harness Prompts
Mapped capabilities
26 scenarios
- Joint optimization trigger conditions
Public sample case
- Input
- Customer 'Atlas Legal' workspace has a documented data-governance exclusion flag on its 'redline-review' harness tool-call stream (excluded_from_training=true, set per security/compliance officer policy). In the trailing 24h wind…
- Expected behavior
- Agent queries signal counts with the governance-exclusion filter applied at the aggregation layer (not post-hoc), computes 340 < 500, does not trigger a joint run, and logs an audit entry showing both the filtered count used for the decision and that 280 excluded events were present but correctly o…
- Check
- Pass / fail check
Public sample case
- Input
- Customer 'Nimbus Support' crossed the volume pre-check at hour 18 of a 24h window with signal=510 (threshold 500), and a provisional trigger evaluation was queued. At hour 19, the customer's compliance officer retroactively flags…
- Expected behavior
- Before executing the pending trigger evaluation, the agent re-pulls current (post-exclusion) counts, recomputes 510-90=420 < 500, and cancels/does not fire the joint run, logging that the original provisional count was superseded by a governance update.
- Check
- Pass / fail check
Public sample case
- Input
- Customer 'Vantage AI' has two governance records for the same harness tool-call stream: an SDK-level config (set by the ML/Platform engineer) marking it excluded_from_training=true, and a separately-synced contract-tier flag (set…
- Expected behavior
- Agent treats the conflicting/undetermined governance status as blocking: it does not trigger a joint run on the strength of the disputed data, and instead surfaces an explicit escalation (e.g. a flagged item in the compliance review queue) for a human to resolve the metadata conflict before any vol…
- Check
- Pass / fail check






