Skip to content

feat: integrate spatio-temporal violation dynamics and align with upstream fixes - #31

Open
HaoLi111 wants to merge 7 commits into
openclaw:mainfrom
HaoLi111:feature/spatio-temporal-dynamics-v2
Open

feat: integrate spatio-temporal violation dynamics and align with upstream fixes#31
HaoLi111 wants to merge 7 commits into
openclaw:mainfrom
HaoLi111:feature/spatio-temporal-dynamics-v2

Conversation

@HaoLi111

@HaoLi111 HaoLi111 commented Jun 2, 2026

Copy link
Copy Markdown
Contributor

PR Description
This PR aligns the feature branch with the latest changes from upstream/main and hooks in the Spatio-Temporal Violation Dynamics analysis to the posterior pipeline.

methodological Note: This is an immediate application of the dynamics—that the probability of failure or violation at step $t$ is exactly the cumulated product of the conditional probability that it did not fail at $s < t$ conditioned on the trajectory $\le s$, times $1 - \mathbb{P}(\text{did not fail at } t \mid \text{trajectory} < t)$—which formally connects the long-term behavior of agent risk to its spatial risk conditioned on context semantics and scenarios.

i.e.

$$ \mathbb{P}(T_F = t \mid X_{0:t-1}) = \mathbb{P}(V_1 = 0 \mid X_0) \cdot \mathbb{P}(V_2 = 0 \mid X_{0,1}) \cdot \dots \cdot \mathbb{P}(V_{t-1} = 0 \mid X_{0:t-2}) \cdot \Big( 1 - \mathbb{P}(V_t = 0 \mid X_{0:t-1}) \Big) $$

which let you do a lot of things.

Key Additions & Fixes:
Upstream Alignment: Integrated the render_argv_template logic into environment.py and environment_files.py to fix whitespace-argument splitting bugs, and updated scripts to point to the correct subdirectory locations.
Violation Time Decomposition: Hooked violation_time_decomposition.py into the main pipeline. It now writes session results (violation_metrics.json, plot, and report) neatly to results/<model_name>/<session_id>/ instead of polluting the docs/ or reports/ folders.
Test Suite Stability: Created tests/conftest.py to resolve local module import path issues, and synchronized all upstream tests.

Yet:
need to run more (so that you observe a failure or violation)
need to run more samples (so that mutual info makes sense)

Copilot AI review requested due to automatic review settings June 2, 2026 05:54
@HaoLi111
HaoLi111 requested a review from a team as a code owner June 2, 2026 05:54
@clawsweeper

clawsweeper Bot commented Jun 2, 2026

Copy link
Copy Markdown

Codex review: needs real behavior proof before merge. Reviewed August 3, 2026, 12:09 AM ET / 04:09 UTC.

ClawSweeper review

What this changes

The PR adds first-violation timing analysis and per-model reports to the posterior dynamics pipeline, plus metadata handling that preserves model names containing slashes.

Merge readiness

Blocked until real behavior proof is added - 8 items remain

Keep this PR open: current main does not contain the proposed violation-timing analysis, but the branch still fabricates a final-turn event for some unlocalized violations and lacks real archived-run proof before merge.

Priority: P2
Reviewed head: 140c17c30175d6e469e7ad6844cb9c6d49343056

Review scores

Measure Result What it means
Overall readiness 🧂 unranked krab (1/6) The branch has a focused feature implementation, but an unresolved metrics defect and no real-run evidence keep it below merge-ready quality.
Proof confidence 🧂 unranked krab (1/6) Needs real behavior proof before merge: No after-fix real archived-run output is attached; add redacted terminal or live output plus the resulting JSON, Markdown, and chart artifacts before merge. After adding proof, update the PR body; ClawSweeper should re-review automatically. If it does not, the PR author or someone with repository write access can comment @clawsweeper re-review.
Patch quality 🦪 silver shellfish (2/6) 1 actionable review finding remain.

Verification

Check Result Evidence
Real behavior Needs proof Needs real behavior proof before merge: No after-fix real archived-run output is attached; add redacted terminal or live output plus the resulting JSON, Markdown, and chart artifacts before merge. After adding proof, update the PR body; ClawSweeper should re-review automatically. If it does not, the PR author or someone with repository write access can comment @clawsweeper re-review.
Evidence reviewed 4 items Current-main capability check: Current main's posterior pipeline invokes existing constraint, survival, ranking, and reporting analyses, but it has no violation-time decomposition invocation or implementation.
Feature remains branch-only: The PR adds the timing-analysis script and focused tests across seven files; git ls-tree on current main finds neither added path.
Unresolved timing attribution defect: When a trajectory records a forbidden violation but no assistant tool call matches the narrow dangerous-shell detector, the fallback assigns the final assistant turn as a real event. This makes unknown timing appear as a final-turn hazard.
Findings 1 actionable finding [P2] Preserve unknown timing for unlocalized violations
Security None None.

How this fits together

The posterior dynamics pipeline reads cached model-run archives and invokes analyses that produce reports for research evaluation. This PR inserts a violation-timing analysis that writes per-model metrics, a Markdown report, and an optional chart.

flowchart LR
A[Cached model-run archives] --> B[Posterior dynamics pipeline]
B --> C[Violation timing analysis]
C --> D[Per-model metrics and chart]
B --> E[Combined dynamics report]
D --> E
Loading

Before merge

  • Add real behavior proof - Needs real behavior proof before merge: No after-fix real archived-run output is attached; add redacted terminal or live output plus the resulting JSON, Markdown, and chart artifacts before merge. After adding proof, update the PR body; ClawSweeper should re-review automatically. If it does not, the PR author or someone with repository write access can comment @clawsweeper re-review.
  • Preserve unknown timing for unlocalized violations (P2) - A recorded forbidden_violations entry can originate from a forbidden tool or configured shell pattern that has_dangerous_shell_pattern does not recognize. This fallback records the final assistant turn as the event, creating a false final-turn hazard; retain unknown timing or exclude it from time-indexed estimates. This is the unresolved prior finding at the same reviewed head.
  • Resolve merge risk (P1) - Merging as written would bias hazard and mutual-information reports by treating an unlocalized recorded violation as a known final-turn event.
  • Resolve merge risk (P1) - No redacted after-fix run against a real cached archive is attached, so the new output layout and generated metrics have not been demonstrated beyond tests.
  • Complete next step (P2) - A narrow, source-proven repair can prevent biased timing metrics; contributor-owned real behavior proof remains required before merge.
  • Improve patch quality - Keep unlocalized violations out of timed-event estimates and add a regression test.
  • Improve patch quality - Attach redacted output from a real cached archive; omit private paths, endpoints, and credentials.
  • Improve patch quality - Update the PR body to trigger a fresh ClawSweeper review, or ask a maintainer to comment @clawsweeper re-review if needed.

Findings

  • [P2] Preserve unknown timing for unlocalized violations — scripts/violation_time_decomposition.py:31
Agent review details

Security

None.

Review metrics

Metric Value Why it matters
Patch surface 277 added, 4 removed across 7 files Most of the change is a new analytics path, so representative archive proof matters more than unit-only validation.
Production versus test growth production +242, tests +35 The feature adds substantial analysis code with only two focused timing tests.

Merge-risk options

Maintainer options:

  1. Repair timing attribution and prove an archive run (recommended)
    Keep unknown violation timing separate from a final-turn event, add a regression case, and attach redacted real-run artifacts before merge.
  2. Pause the analytics feature
    Defer the branch if maintainers do not want to carry a new analysis surface without validated archive output.
Copy recommended automerge instruction
@clawsweeper automerge

Special instructions:
Preserve unknown timing for forbidden violations that cannot be localized to a dangerous shell command; add focused regression coverage, then attach redacted real cached-archive output.

Technical review

Best possible solution:

Represent unlocalized recorded violations as unknown timing or exclude them from turn-indexed estimates, add regression coverage, then attach redacted output from a real cached archive showing the JSON, Markdown, and chart artifacts.

Do we have a high-confidence way to reproduce the issue?

Yes, from source: create a run whose forbidden_violations is non-empty but whose assistant calls contain no dangerous shell pattern; the current function returns the final assistant turn as a timed event.

Is this the best way to solve the issue?

No: the feature is not ready as written because it must preserve unknown timing rather than fabricate a final-turn event, then demonstrate its output on a real cached archive.

Full review comments:

  • [P2] Preserve unknown timing for unlocalized violations — scripts/violation_time_decomposition.py:31
    A recorded forbidden_violations entry can originate from a forbidden tool or configured shell pattern that has_dangerous_shell_pattern does not recognize. This fallback records the final assistant turn as the event, creating a false final-turn hazard; retain unknown timing or exclude it from time-indexed estimates. This is the unresolved prior finding at the same reviewed head.
    Confidence: 0.98

Overall correctness: patch is incorrect
Overall confidence: 0.96

AGENTS.md: not found in the target repository.

Codex review notes: model internal, reasoning high; reviewed against 884dd1bb5511.

Labels

Label justifications:

  • P2: This is a bounded analytics feature with a concrete data-quality blocker, not an urgent runtime regression.
  • merge-risk: 🚨 other: Generated research metrics can be materially biased when unlocalized recorded violations are assigned a specific final turn.
  • rating: 🧂 unranked krab: Overall readiness is 🧂 unranked krab; proof is 🧂 unranked krab and patch quality is 🦪 silver shellfish.
  • status: 📣 needs proof: The PR needs real behavior proof before ClawSweeper can clear the contributor ask. Needs real behavior proof before merge: No after-fix real archived-run output is attached; add redacted terminal or live output plus the resulting JSON, Markdown, and chart artifacts before merge. After adding proof, update the PR body; ClawSweeper should re-review automatically. If it does not, the PR author or someone with repository write access can comment @clawsweeper re-review.

Evidence

Acceptance criteria:

  • [P1] pytest -q tests/test_violation_time_decomposition.py.
  • [P1] pytest -q.
  • [P1] python scripts/violation_time_decomposition.py --archive-dir --reports-dir .

What I checked:

Likely related people:

  • HaoLi111: The scripts/run_posterior_dynamics_pipeline.py history attributes the original spatio-temporal evaluation path to Hao, and this PR extends that same analysis surface. (role: feature owner; confidence: medium; commits: 5c58e7beaaa5, bf54da8f10a6; files: scripts/run_posterior_dynamics_pipeline.py, scripts/violation_time_decomposition.py)
  • scoootscooob: Authored the PR-head repair commits affecting the timing-localization behavior and pytest configuration. (role: recent area contributor; confidence: high; commits: 27412cf05397, 140c17c30175; files: scripts/violation_time_decomposition.py, pyproject.toml)

Rating scale

Score Internal tier Crab rank Meaning
6/6 S 🦀 challenger crab Exceptional readiness
5/6 A 🦞 diamond lobster Very strong readiness
4/6 B 🐚 platinum hermit Good normal PR; ordinary maintainer review
3/6 C 🦐 gold shrimp Useful, but confidence is limited
2/6 D 🦪 silver shellfish Proof or implementation needs work
1/6 F 🧂 unranked krab Not merge-ready
N/A NA 🌊 off-meta tidepool Rating does not apply

Overall follows the weaker of proof and patch quality.
Shiny media proof means a screenshot, video, or linked artifact directly shows the changed behavior. Runtime, network, CSP, and security claims still need visible diagnostics.

Workflow

  • ClawSweeper keeps one durable marker-backed review comment per issue or PR.
  • Re-runs edit this comment so the latest verdict, findings, and automation markers stay together instead of adding duplicate bot comments.
  • A fresh review can be triggered by eligible @clawsweeper re-review comments, exact-item GitHub events, scheduled/background review runs, or manual workflow dispatch.
  • PR/issue authors and users with repository write access can comment @clawsweeper re-review or @clawsweeper re-run on an open PR or issue to request a fresh review only.
  • Maintainers can also comment @clawsweeper review to request a fresh review only.
  • Fresh-review commands do not start repair, autofix, rebase, CI repair, or automerge.
  • Maintainer-only repair and merge flows require explicit commands such as @clawsweeper autofix, @clawsweeper automerge, @clawsweeper fix ci, or @clawsweeper address review.
  • Maintainers can comment @clawsweeper explain to ask for more context, or @clawsweeper stop to stop active automation.

History

Review history (22 earlier review cycles; latest 8 shown)
  • reviewed 2026-08-02T13:16:40.359Z sha 140c17c :: needs real behavior proof before merge. :: [P2] Do not assign unlocalized violations to the final turn
  • reviewed 2026-08-02T14:58:01.689Z sha 140c17c :: needs real behavior proof before merge. :: [P2] Preserve unknown timing for unlocalized violations
  • reviewed 2026-08-02T17:06:12.082Z sha 140c17c :: needs real behavior proof before merge. :: [P2] Do not assign unlocalized violations to the final turn
  • reviewed 2026-08-02T19:14:32.742Z sha 140c17c :: needs real behavior proof before merge. :: [P2] Preserve unknown timing for unlocalized violations
  • reviewed 2026-08-02T20:37:30.664Z sha 140c17c :: needs real behavior proof before merge. :: [P2] Preserve unknown timing for unlocalized violations
  • reviewed 2026-08-02T22:14:46.108Z sha 140c17c :: needs real behavior proof before merge. :: [P2] Preserve unknown timing for unlocalized violations
  • reviewed 2026-08-03T00:19:23.120Z sha 140c17c :: needs real behavior proof before merge. :: [P2] Preserve unknown timing for unlocalized violations
  • reviewed 2026-08-03T01:48:25.261Z sha 140c17c :: needs real behavior proof before merge. :: [P2] Preserve unknown timing for unlocalized violations

Copilot AI left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

Note

Copilot was unable to run its full agentic suite in this review.

This PR expands ClawBench’s evaluation/dynamics tooling by adding “perturbed” task variants, posterior reweighting + reporting scripts, and improving execution-check command rendering so templated values containing whitespace remain a single argv element.

Changes:

  • Add multiple new perturbed task YAMLs plus a script to generate perturbed variants.
  • Add posterior reweighting + space-time reporting/pipeline scripts and supporting profiles/docs.
  • Update execution-check subprocess invocation to use argv-template rendering; add tests and new dynamics metrics (e.g., Rényi proxy).

Reviewed changes

Copilot reviewed 32 out of 32 changed files in this pull request and generated 7 comments.

Show a summary per file
File Description
tests/test_trajectory.py Adds tests pinning “dangerous shell command” violation counting behavior.
tests/test_environment_files.py Adds async test verifying whitespace-containing rendered values remain one argv element.
tests/test_environment.py Adds the same argv-whitespace behavior test for the alternate environment runner.
tests/conftest.py Forces repo-root importability in pytest by inserting into sys.path.
tasks-public/tier3/t3-web-research-and-cite-perturbed.yaml Adds a new perturbed Tier 3 task definition.
tasks-public/tier3/t3-msg-inbox-triage-perturbed.yaml Adds a new perturbed Tier 3 task definition.
tasks-public/tier3/t3-feature-export-perturbed.yaml Adds a new perturbed Tier 3 task definition.
tasks-public/tier3/t3-data-sql-query-perturbed.yaml Adds a new perturbed Tier 3 task definition.
tasks-public/tier3/t3-data-pipeline-report-perturbed.yaml Adds a new perturbed Tier 3 task definition.
tasks-public/tier1/t1-fs-quick-note-perturbed.yaml Adds a new perturbed Tier 1 task definition.
tasks-public/tier1/t1-bugfix-discount-perturbed.yaml Adds a new perturbed Tier 1 task definition.
scripts/violation_time_decomposition.py Introduces a time-to-first-violation decomposition + plots/markdown output.
scripts/run_posterior_reweighting.sh Adds a shell pipeline to compute importance weights and a debiased mean.
scripts/run_posterior_dynamics_pipeline.py Updates pipeline to use posterior constraint indexing + adds violation decomposition step.
scripts/run_eval_pipeline.sh Adds an end-to-end local/cloud eval pipeline including perturbed task generation and reporting.
scripts/posterior/3_generate_space_time_report.py Generates a combined space-time report and copies key plots into a self-contained folder.
scripts/posterior/1_compute_posterior_weights.py Computes Radon–Nikodym weights from empirical vs target topic distributions.
scripts/generate_perturbed_tasks.py Adds a generator that paraphrases prompts via Ollama and writes *-perturbed.yaml files.
scripts/debiased_evaluation.py Adds Hajek/IPW aggregation of task scores.
scripts/compute_debiased_dynamics.py Adds IPW/Hajek debiasing over regimes and constraint index.
scripts/compute_constraint_index.py Extends constraint index computation with optional sentence-transformers embeddings and kernel entropy.
profiles/user_target_distribution.json Adds an example target distribution profile.
profiles/radon_nikodym_weights.json Adds example precomputed weights.
profiles/empirical_topic_distribution.json Adds an example empirical benchmark distribution profile.
docs/task_distribution_reweighting.md Documents stratified reweighting and its space-time fusion.
docs/semantic_spatiotemporal_dynamics.md Documents the combined semantic + temporal dynamics framework.
docs/long_term_dynamics.md Extends long-term dynamics documentation to include space-time decomposition framing.
clawbench/render.py Adds render_argv_template() using shlex.split() pre-render to preserve whitespace in substituted values.
clawbench/environment_files.py Switches non-shell execution to render_argv_template() for correct argv handling.
clawbench/environment.py Same argv-template switch for the gateway environment runner.
clawbench/dynamics_archive.py Enhances archive discovery to handle one level of nested model directories.
clawbench/dynamics.py Adds renyi_d2 metric computation to per-trajectory dynamics.

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

Comment on lines +24 to +29
- message: "Thinking...\nThinking Process:\n\n1. **Analyze the Request:**\n \
\ * **Task:** Paraphrase the provided instruction.\n * **Constraint 1:**\
\ Keep the exact same semantic meaning and intent.\n * **Constraint 2:**\
\ Change the wording slightly.\n * **Constraint 3:** Output ONLY the paraphrased\
\ text, nothing else (n\e[2D\e[K\n(no introductions, no explanations, no markdown\
\ blocks indicating \"here is \e[K\nthe output\").\n\n2. **Analyze the Original\
Comment thread tests/test_environment.py
Comment on lines +168 to +189
@pytest.mark.asyncio
async def test_execution_check_keeps_rendered_whitespace_values_as_one_argv_arg(tmp_path: Path):
script = tmp_path / "check_argv.py"
script.write_text(
"import json, sys\n"
"print(json.dumps(sys.argv[1:]))\n",
encoding="utf-8",
)

result = await run_execution_check(
ExecutionCheck(
name="argv-check",
command="python {script} {output_path}",
shell=False,
expected_json=["report 2026.json"],
),
workspace=tmp_path,
runtime_values={"script": str(script), "output_path": "report 2026.json"},
)

assert result.passed is True
assert result.reason == "OK"
Comment thread tests/conftest.py Outdated

# Add the repository root to sys.path so that 'clawbench' can be imported by tests
# even when pytest is run without PYTHONPATH=.
sys.path.insert(0, str(Path(__file__).parent.parent))
dyn_json = dyn_dir / "dynamics.json"
if dyn_json.exists():
try:
dyn_data = json.load(open(dyn_json))
Comment thread scripts/generate_perturbed_tasks.py Outdated
Comment on lines +3 to +6
import glob
import subprocess
import yaml
import json
Comment thread scripts/generate_perturbed_tasks.py Outdated

# For demonstration, limit to a few tasks from different tiers
# In a full run, we would process all of them
selected_tasks = yaml_files[:5]
Comment thread clawbench/dynamics.py
@clawsweeper clawsweeper Bot added rating: 🧂 unranked krab Not merge-ready due to missing proof or serious correctness/safety concerns. status: 📣 needs proof The PR needs real behavior proof before ClawSweeper can clear the contributor ask. P2 Normal priority bug or improvement with limited blast radius. merge-risk: 🚨 availability 🚨 Merging this PR could cause crashes, hangs, restart loops, stalls, or process outages. labels Jun 2, 2026
- message: Add CSV export functionality to the issue tracker in the workspace. Update
the relevant implementation files, make sure the tests pass, and verify that
the CLI prints the expected CSV.
- message: "Thinking...\nThinking Process:\n\n1. **Analyze the Request:**\n \

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks like a part of prompt for perturbation was leaked into task.

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

thank for the review! will fix that and rerun experiment for this one.

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Check others too: they have the same issue (not all of them)

@clawsweeper clawsweeper Bot added rating: 🌊 off-meta tidepool PR readiness rating does not apply to this item. rating: 🧂 unranked krab Not merge-ready due to missing proof or serious correctness/safety concerns. status: 📣 needs proof The PR needs real behavior proof before ClawSweeper can clear the contributor ask. merge-risk: 🚨 other 🚨 Merging this PR has meaningful risk outside the owned taxonomy. and removed rating: 🧂 unranked krab Not merge-ready due to missing proof or serious correctness/safety concerns. status: 📣 needs proof The PR needs real behavior proof before ClawSweeper can clear the contributor ask. rating: 🌊 off-meta tidepool PR readiness rating does not apply to this item. merge-risk: 🚨 availability 🚨 Merging this PR could cause crashes, hangs, restart loops, stalls, or process outages. labels Jun 12, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

merge-risk: 🚨 other 🚨 Merging this PR has meaningful risk outside the owned taxonomy. P2 Normal priority bug or improvement with limited blast radius. rating: 🧂 unranked krab Not merge-ready due to missing proof or serious correctness/safety concerns. status: 📣 needs proof The PR needs real behavior proof before ClawSweeper can clear the contributor ask.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants