id stringlengths 13 13 | version stringclasses 1
value | split stringclasses 1
value | task dict | environment dict | repository dict | scenario dict | hidden_ground_truth dict | ideal_agent_behavior dict | bad_behavior_examples listlengths 2 2 | evaluation_rubric dict | messages listlengths 3 3 | quality dict |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
JF-ASE-001-01 | 1.0.0 | train | {
"family": "problem_understanding",
"family_label": "Problem Understanding",
"archetype": "ambiguous_scope",
"difficulty": "easy",
"behavior_targets": [
"intent_modeling",
"scope_control",
"assumption_tracking",
"acceptance_criteria"
]
} | {
"language": "Python",
"framework": "FastAPI",
"test_tool": "pytest",
"build_tool": "uv"
} | {
"name": "ledger-payments-service",
"domain": "payments",
"architecture": "modular monolith",
"summary": "A payments repository organized as a modular monolith.",
"file_tree": [
"app/api/routes.py",
"app/services/core.py",
"app/repositories/store.py",
"app/workers/events.py",
"app/securit... | {
"user_request": "A support escalation reports ambiguous scope appears in the payments workflow after a warm-cache transition, and the relationship between the request router and domain service is not yet proven. Work in `ledger-payments-service`, a modular monolith implemented with Python and FastAPI. Focus on the ... | {
"core_issue": "The core issue is ambiguous scope: the request router establishes state using a condition that is only valid on the common path, while the domain service consumes that state after a warm-cache transition. The failure becomes observable in the payments workflow because the two components disagree abou... | {
"initial_assessment": "This is primarily a `Problem Understanding` task. The agent should first establish whether `ambiguous scope` is a symptom, a root cause, or an underspecified request.",
"assumptions": [
"The issue is limited to the path connecting the request router and domain service; this remains a hy... | [
{
"type": "premature_patch",
"response": "Immediately rewrite the domain service and update every caller without inspecting the repository.",
"why_wrong": "It treats a hypothesis as fact, expands blast radius, and skips evidence and compatibility checks."
},
{
"type": "hallucinated_evidence",
... | {
"must_do": [
"Distinguish verified evidence from assumptions.",
"Inspect or reason about the relationship between `app/api/routes.py` and `app/services/core.py`.",
"Respect all stated constraints.",
"Define a failure-focused verification step.",
"Keep the proposed change bounded and reversible."... | [
{
"role": "system",
"content": "You are a software-engineering agent. Ground conclusions in available evidence, use tools deliberately, preserve safety and contracts, and never claim unobserved results."
},
{
"role": "user",
"content": "A support escalation reports ambiguous scope appears in the... | {
"validation_status": "machine_validated",
"heuristic_score": 88,
"structural_fingerprint": "dcd6b2541cfded1925a6436e2705d1593e6325d80614fa73ad1ed327c20dfa92",
"user_request_hash": "36bacb6a0933ba78b2273616756089967ff83031db1947d7915a0748346b2489",
"record_hash": "30d0c5ec44b4f25b7e0a2bc42a2adfe68b9f456beb81... |
JF-ASE-001-02 | 1.0.0 | train | {
"family": "problem_understanding",
"family_label": "Problem Understanding",
"archetype": "ambiguous_scope",
"difficulty": "medium",
"behavior_targets": [
"intent_modeling",
"scope_control",
"assumption_tracking",
"acceptance_criteria"
]
} | {
"language": "Python",
"framework": "Django",
"test_tool": "pytest-django",
"build_tool": "pip"
} | {
"name": "relay-healthcare-scheduling-service",
"domain": "healthcare scheduling",
"architecture": "event-driven services",
"summary": "A healthcare scheduling repository organized as a event-driven services.",
"file_tree": [
"project/urls.py",
"app/views.py",
"app/services.py",
"app/models.p... | {
"user_request": "An engineer observed a proposed fix for ambiguous scope would broaden scope without first explaining why the failure occurs under two concurrent requests. Work in `relay-healthcare-scheduling-service`, a event-driven services implemented with Python and Django. Focus on the agent behavior required ... | {
"core_issue": "The core issue is ambiguous scope: the API handler establishes state using a condition that is only valid on the common path, while the repository adapter consumes that state under two concurrent requests. The failure becomes observable in the healthcare scheduling workflow because the two components... | {
"initial_assessment": "This is primarily a `Problem Understanding` task. The agent should first establish whether `ambiguous scope` is a symptom, a root cause, or an underspecified request.",
"assumptions": [
"The issue is limited to the path connecting the API handler and repository adapter; this remains a h... | [
{
"type": "premature_patch",
"response": "Immediately rewrite the repository adapter and update every caller without inspecting the repository.",
"why_wrong": "It treats a hypothesis as fact, expands blast radius, and skips evidence and compatibility checks."
},
{
"type": "hallucinated_evidence"... | {
"must_do": [
"Distinguish verified evidence from assumptions.",
"Inspect or reason about the relationship between `app/views.py` and `app/services.py`.",
"Respect all stated constraints.",
"Define a failure-focused verification step.",
"Keep the proposed change bounded and reversible."
],
"m... | [
{
"role": "system",
"content": "You are a software-engineering agent. Ground conclusions in available evidence, use tools deliberately, preserve safety and contracts, and never claim unobserved results."
},
{
"role": "user",
"content": "An engineer observed a proposed fix for ambiguous scope wou... | {
"validation_status": "machine_validated",
"heuristic_score": 89,
"structural_fingerprint": "aed0b39bf2ad92240abb0b57e6d8237af6d65b5dd0ade153b944bfc60c9bb15f",
"user_request_hash": "bb3f1b8a00ff6011842bb4523df9c9375ba74cb19d23467c7da48d174a1c438a",
"record_hash": "e44ccb009e6110956780abb63aaf2fb648ba69c38e1a... |
JF-ASE-001-03 | 1.0.0 | train | {
"family": "problem_understanding",
"family_label": "Problem Understanding",
"archetype": "ambiguous_scope",
"difficulty": "hard",
"behavior_targets": [
"intent_modeling",
"scope_control",
"assumption_tracking",
"acceptance_criteria"
]
} | {
"language": "TypeScript",
"framework": "Node.js",
"test_tool": "Vitest",
"build_tool": "pnpm"
} | {
"name": "atlas-developer-tooling-service",
"domain": "developer tooling",
"architecture": "service-repository application",
"summary": "A developer tooling repository organized as a service-repository application.",
"file_tree": [
"src/http/routes.ts",
"src/services/core.ts",
"src/data/repositor... | {
"user_request": "The latest release exposed a pattern: evidence from the background worker conflicts with assumptions made by the event consumer, producing ambiguous scope during a rolling deployment. Work in `atlas-developer-tooling-service`, a service-repository application implemented with TypeScript and Node.js... | {
"core_issue": "The core issue is ambiguous scope: the background worker establishes state using a condition that is only valid on the common path, while the event consumer consumes that state during a rolling deployment. The failure becomes observable in the developer tooling workflow because the two components dis... | {
"initial_assessment": "This is primarily a `Problem Understanding` task. The agent should first establish whether `ambiguous scope` is a symptom, a root cause, or an underspecified request.",
"assumptions": [
"The issue is limited to the path connecting the background worker and event consumer; this remains a... | [
{
"type": "premature_patch",
"response": "Immediately rewrite the event consumer and update every caller without inspecting the repository.",
"why_wrong": "It treats a hypothesis as fact, expands blast radius, and skips evidence and compatibility checks."
},
{
"type": "hallucinated_evidence",
... | {
"must_do": [
"Distinguish verified evidence from assumptions.",
"Inspect or reason about the relationship between `src/data/repository.ts` and `src/workers/consumer.ts`.",
"Respect all stated constraints.",
"Define a failure-focused verification step.",
"Keep the proposed change bounded and reve... | [
{
"role": "system",
"content": "You are a software-engineering agent. Ground conclusions in available evidence, use tools deliberately, preserve safety and contracts, and never claim unobserved results."
},
{
"role": "user",
"content": "The latest release exposed a pattern: evidence from the bac... | {
"validation_status": "machine_validated",
"heuristic_score": 90,
"structural_fingerprint": "d855ec1d8b59fc7bf9dc6ce1cd738b4350b89cc2e11ec55d706e8a3826f23553",
"user_request_hash": "7efc99521c3e49073672f48f12c40770d125a405084d47d13c43ee6c0a43411d",
"record_hash": "9a8bd3f41d470ef90448c70f5339dc0c4ed6ea6c358d... |
JF-ASE-001-04 | 1.0.0 | train | {
"family": "problem_understanding",
"family_label": "Problem Understanding",
"archetype": "ambiguous_scope",
"difficulty": "expert",
"behavior_targets": [
"intent_modeling",
"scope_control",
"assumption_tracking",
"acceptance_criteria"
]
} | {
"language": "TypeScript",
"framework": "React",
"test_tool": "Playwright",
"build_tool": "Vite"
} | {
"name": "harbor-identity-management-service",
"domain": "identity management",
"architecture": "microservice platform",
"summary": "A identity management repository organized as a microservice platform.",
"file_tree": [
"src/app/router.tsx",
"src/features/state.ts",
"src/api/client.ts",
"src... | {
"user_request": "A reproducible test now shows the identity management system behaves correctly in the common path but exposes ambiguous scope at a daylight-saving boundary. Work in `harbor-identity-management-service`, a microservice platform implemented with TypeScript and React. Focus on the agent behavior requi... | {
"core_issue": "The core issue is ambiguous scope: the session middleware establishes state using a condition that is only valid on the common path, while the identity store consumes that state at a daylight-saving boundary. The failure becomes observable in the identity management workflow because the two component... | {
"initial_assessment": "This is primarily a `Problem Understanding` task. The agent should first establish whether `ambiguous scope` is a symptom, a root cause, or an underspecified request.",
"assumptions": [
"The issue is limited to the path connecting the session middleware and identity store; this remains ... | [
{
"type": "premature_patch",
"response": "Immediately rewrite the identity store and update every caller without inspecting the repository.",
"why_wrong": "It treats a hypothesis as fact, expands blast radius, and skips evidence and compatibility checks."
},
{
"type": "hallucinated_evidence",
... | {
"must_do": [
"Distinguish verified evidence from assumptions.",
"Inspect or reason about the relationship between `src/components/Workflow.tsx` and `src/auth/session.ts`.",
"Respect all stated constraints.",
"Define a failure-focused verification step.",
"Keep the proposed change bounded and rev... | [
{
"role": "system",
"content": "You are a software-engineering agent. Ground conclusions in available evidence, use tools deliberately, preserve safety and contracts, and never claim unobserved results."
},
{
"role": "user",
"content": "A reproducible test now shows the identity management syste... | {
"validation_status": "machine_validated",
"heuristic_score": 91,
"structural_fingerprint": "9f817dbe50e7f0c5e7ca2e780bd90fb27b2ee6685ac3814c137d829106c258d1",
"user_request_hash": "b0d3ad72a83cbaa93da2f10acec4c35e021a7569d33e0f79451648cbf3d2005a",
"record_hash": "3d390e757206d30d1a1a1570221b09db594c03dceb26... |
JF-ASE-001-05 | 1.0.0 | train | {
"family": "problem_understanding",
"family_label": "Problem Understanding",
"archetype": "ambiguous_scope",
"difficulty": "easy",
"behavior_targets": [
"intent_modeling",
"scope_control",
"assumption_tracking",
"acceptance_criteria"
]
} | {
"language": "Java",
"framework": "Spring Boot",
"test_tool": "JUnit",
"build_tool": "Gradle"
} | {
"name": "forge-e-commerce-service",
"domain": "e-commerce",
"architecture": "serverless workflow",
"summary": "A e-commerce repository organized as a serverless workflow.",
"file_tree": [
"src/main/java/app/Controller.java",
"src/main/java/app/Service.java",
"src/main/java/app/Repository.java",
... | {
"user_request": "Operational telemetry suggests a proposed fix for ambiguous scope would broaden scope without first explaining why the failure occurs when retries overlap. Work in `forge-e-commerce-service`, a serverless workflow implemented with Java and Spring Boot. Focus on the agent behavior required for `ambi... | {
"core_issue": "The core issue is ambiguous scope: the cache layer establishes state using a condition that is only valid on the common path, while the database gateway consumes that state when retries overlap. The failure becomes observable in the e-commerce workflow because the two components disagree about owners... | {
"initial_assessment": "This is primarily a `Problem Understanding` task. The agent should first establish whether `ambiguous scope` is a symptom, a root cause, or an underspecified request.",
"assumptions": [
"The issue is limited to the path connecting the cache layer and database gateway; this remains a hyp... | [
{
"type": "premature_patch",
"response": "Immediately rewrite the database gateway and update every caller without inspecting the repository.",
"why_wrong": "It treats a hypothesis as fact, expands blast radius, and skips evidence and compatibility checks."
},
{
"type": "hallucinated_evidence",
... | {
"must_do": [
"Distinguish verified evidence from assumptions.",
"Inspect or reason about the relationship between `src/main/java/app/SecurityPolicy.java` and `src/test/java/app/WorkflowTest.java`.",
"Respect all stated constraints.",
"Define a failure-focused verification step.",
"Keep the propo... | [
{
"role": "system",
"content": "You are a software-engineering agent. Ground conclusions in available evidence, use tools deliberately, preserve safety and contracts, and never claim unobserved results."
},
{
"role": "user",
"content": "Operational telemetry suggests a proposed fix for ambiguous... | {
"validation_status": "machine_validated",
"heuristic_score": 92,
"structural_fingerprint": "7e2e8e79b61fa2a4a458600ef90650e2d56e7581b98f259fc39a4e14ae0682b5",
"user_request_hash": "8cf12fefd0d459fff79d0d7ffecedb8da2496e33c1116ecc240e4cd23593c790",
"record_hash": "920f7d776a92603ed93c3c5e5337c9564fc2a201128d... |
JF-ASE-001-06 | 1.0.0 | train | {
"family": "problem_understanding",
"family_label": "Problem Understanding",
"archetype": "ambiguous_scope",
"difficulty": "medium",
"behavior_targets": [
"intent_modeling",
"scope_control",
"assumption_tracking",
"acceptance_criteria"
]
} | {
"language": "Go",
"framework": "Chi",
"test_tool": "go test",
"build_tool": "Go modules"
} | {
"name": "signal-logistics-service",
"domain": "logistics",
"architecture": "worker-based pipeline",
"summary": "A logistics repository organized as a worker-based pipeline.",
"file_tree": [
"internal/http/routes.go",
"internal/service/core.go",
"internal/store/repository.go",
"internal/worke... | {
"user_request": "A code review uncovered a risk: ambiguous scope appears in the logistics workflow with legacy records created before the last migration, and the relationship between the scheduler and job executor is not yet proven. Work in `signal-logistics-service`, a worker-based pipeline implemented with Go and... | {
"core_issue": "The core issue is ambiguous scope: the scheduler establishes state using a condition that is only valid on the common path, while the job executor consumes that state with legacy records created before the last migration. The failure becomes observable in the logistics workflow because the two compon... | {
"initial_assessment": "This is primarily a `Problem Understanding` task. The agent should first establish whether `ambiguous scope` is a symptom, a root cause, or an underspecified request.",
"assumptions": [
"The issue is limited to the path connecting the scheduler and job executor; this remains a hypothesi... | [
{
"type": "premature_patch",
"response": "Immediately rewrite the job executor and update every caller without inspecting the repository.",
"why_wrong": "It treats a hypothesis as fact, expands blast radius, and skips evidence and compatibility checks."
},
{
"type": "hallucinated_evidence",
... | {
"must_do": [
"Distinguish verified evidence from assumptions.",
"Inspect or reason about the relationship between `internal/service/core_test.go` and `internal/http/routes.go`.",
"Respect all stated constraints.",
"Define a failure-focused verification step.",
"Keep the proposed change bounded a... | [
{
"role": "system",
"content": "You are a software-engineering agent. Ground conclusions in available evidence, use tools deliberately, preserve safety and contracts, and never claim unobserved results."
},
{
"role": "user",
"content": "A code review uncovered a risk: ambiguous scope appears in ... | {
"validation_status": "machine_validated",
"heuristic_score": 93,
"structural_fingerprint": "7a7ad0f6304d32db61fb6a7e5227f120f189c6426d121829683581d8ebfabcdd",
"user_request_hash": "4d227d31ac14f6e66b7c238cad2adc69083cb3f4eec53976e3aa581a0af9cac4",
"record_hash": "d1c31da0453920d708244ea7708bd02fafe1777ac5d7... |
JF-ASE-001-07 | 1.0.0 | train | {
"family": "problem_understanding",
"family_label": "Problem Understanding",
"archetype": "ambiguous_scope",
"difficulty": "hard",
"behavior_targets": [
"intent_modeling",
"scope_control",
"assumption_tracking",
"acceptance_criteria"
]
} | {
"language": "C#",
"framework": "ASP.NET Core",
"test_tool": "xUnit",
"build_tool": "dotnet"
} | {
"name": "orbit-collaboration-software-service",
"domain": "collaboration software",
"architecture": "multi-tenant SaaS",
"summary": "A collaboration software repository organized as a multi-tenant SaaS.",
"file_tree": [
"Api/Controllers/WorkflowController.cs",
"Core/WorkflowService.cs",
"Data/Wo... | {
"user_request": "The team needs a grounded investigation because ambiguous scope appears in the collaboration software workflow immediately after a feature flag changes, and the relationship between the serializer and public API contract is not yet proven. Work in `orbit-collaboration-software-service`, a multi-ten... | {
"core_issue": "The core issue is ambiguous scope: the serializer establishes state using a condition that is only valid on the common path, while the public API contract consumes that state immediately after a feature flag changes. The failure becomes observable in the collaboration software workflow because the tw... | {
"initial_assessment": "This is primarily a `Problem Understanding` task. The agent should first establish whether `ambiguous scope` is a symptom, a root cause, or an underspecified request.",
"assumptions": [
"The issue is limited to the path connecting the serializer and public API contract; this remains a h... | [
{
"type": "premature_patch",
"response": "Immediately rewrite the public API contract and update every caller without inspecting the repository.",
"why_wrong": "It treats a hypothesis as fact, expands blast radius, and skips evidence and compatibility checks."
},
{
"type": "hallucinated_evidence... | {
"must_do": [
"Distinguish verified evidence from assumptions.",
"Inspect or reason about the relationship between `Api/Controllers/WorkflowController.cs` and `Core/WorkflowService.cs`.",
"Respect all stated constraints.",
"Define a failure-focused verification step.",
"Keep the proposed change b... | [
{
"role": "system",
"content": "You are a software-engineering agent. Ground conclusions in available evidence, use tools deliberately, preserve safety and contracts, and never claim unobserved results."
},
{
"role": "user",
"content": "The team needs a grounded investigation because ambiguous s... | {
"validation_status": "machine_validated",
"heuristic_score": 94,
"structural_fingerprint": "275db5c2083ef5840d5484529b1b6ff69f75a000f73a035fb231303822b9081b",
"user_request_hash": "0f93afe77e91c1f15b3b748d96bada4e9f3992b1531f327dd35871b89d1c5111",
"record_hash": "861efcaf2d5eb64fbedfe995692c04f790e67800e6d9... |
JF-ASE-001-08 | 1.0.0 | train | {
"family": "problem_understanding",
"family_label": "Problem Understanding",
"archetype": "ambiguous_scope",
"difficulty": "expert",
"behavior_targets": [
"intent_modeling",
"scope_control",
"assumption_tracking",
"acceptance_criteria"
]
} | {
"language": "PHP",
"framework": "Laravel",
"test_tool": "PHPUnit",
"build_tool": "Composer"
} | {
"name": "bridge-analytics-service",
"domain": "analytics",
"architecture": "API gateway architecture",
"summary": "A analytics repository organized as a API gateway architecture.",
"file_tree": [
"routes/api.php",
"app/Http/Controllers/WorkflowController.php",
"app/Services/WorkflowService.php",... | {
"user_request": "A customer-facing workflow intermittently exhibits this behavior: the team cannot safely complete the analytics change because ambiguous scope remains unresolved during a partial network failure. Work in `bridge-analytics-service`, a API gateway architecture implemented with PHP and Laravel. Focus ... | {
"core_issue": "The core issue is ambiguous scope: the migration runner establishes state using a condition that is only valid on the common path, while the schema registry consumes that state during a partial network failure. The failure becomes observable in the analytics workflow because the two components disagr... | {
"initial_assessment": "This is primarily a `Problem Understanding` task. The agent should first establish whether `ambiguous scope` is a symptom, a root cause, or an underspecified request.",
"assumptions": [
"The issue is limited to the path connecting the migration runner and schema registry; this remains a... | [
{
"type": "premature_patch",
"response": "Immediately rewrite the schema registry and update every caller without inspecting the repository.",
"why_wrong": "It treats a hypothesis as fact, expands blast radius, and skips evidence and compatibility checks."
},
{
"type": "hallucinated_evidence",
... | {
"must_do": [
"Distinguish verified evidence from assumptions.",
"Inspect or reason about the relationship between `app/Http/Controllers/WorkflowController.php` and `app/Services/WorkflowService.php`.",
"Respect all stated constraints.",
"Define a failure-focused verification step.",
"Keep the pr... | [
{
"role": "system",
"content": "You are a software-engineering agent. Ground conclusions in available evidence, use tools deliberately, preserve safety and contracts, and never claim unobserved results."
},
{
"role": "user",
"content": "A customer-facing workflow intermittently exhibits this beh... | {
"validation_status": "machine_validated",
"heuristic_score": 95,
"structural_fingerprint": "d76e7c18c2c025d8ffa18ea7e6d01b746932698fead1045c73f616510dc2bf86",
"user_request_hash": "8d837f75a2bd1714a4067465f37d06318d8a1c24ecc63ebd0418866c9b8312d3",
"record_hash": "20da393d83a10df5cde4370f6efded0242207dacca60... |
JF-ASE-001-09 | 1.0.0 | train | {
"family": "problem_understanding",
"family_label": "Problem Understanding",
"archetype": "ambiguous_scope",
"difficulty": "easy",
"behavior_targets": [
"intent_modeling",
"scope_control",
"assumption_tracking",
"acceptance_criteria"
]
} | {
"language": "Rust",
"framework": "Axum",
"test_tool": "cargo test",
"build_tool": "Cargo"
} | {
"name": "vault-education-technology-service",
"domain": "education technology",
"architecture": "batch processing system",
"summary": "A education technology repository organized as a batch processing system.",
"file_tree": [
"src/http/routes.rs",
"src/services/core.rs",
"src/store/repository.rs... | {
"user_request": "During validation, the system revealed that the team cannot safely complete the education technology change because ambiguous scope remains unresolved after switching tenants in the same browser session. Work in `vault-education-technology-service`, a batch processing system implemented with Rust a... | {
"core_issue": "The core issue is ambiguous scope: the feature-flag client establishes state using a condition that is only valid on the common path, while the configuration service consumes that state after switching tenants in the same browser session. The failure becomes observable in the education technology wor... | {
"initial_assessment": "This is primarily a `Problem Understanding` task. The agent should first establish whether `ambiguous scope` is a symptom, a root cause, or an underspecified request.",
"assumptions": [
"The issue is limited to the path connecting the feature-flag client and configuration service; this ... | [
{
"type": "premature_patch",
"response": "Immediately rewrite the configuration service and update every caller without inspecting the repository.",
"why_wrong": "It treats a hypothesis as fact, expands blast radius, and skips evidence and compatibility checks."
},
{
"type": "hallucinated_eviden... | {
"must_do": [
"Distinguish verified evidence from assumptions.",
"Inspect or reason about the relationship between `src/store/repository.rs` and `src/workers/consumer.rs`.",
"Respect all stated constraints.",
"Define a failure-focused verification step.",
"Keep the proposed change bounded and rev... | [
{
"role": "system",
"content": "You are a software-engineering agent. Ground conclusions in available evidence, use tools deliberately, preserve safety and contracts, and never claim unobserved results."
},
{
"role": "user",
"content": "During validation, the system revealed that the team cannot... | {
"validation_status": "machine_validated",
"heuristic_score": 96,
"structural_fingerprint": "55bc8812a0f459d3c06101f29cc92be257c820a604ebbb7fcc93b3df1519ca4f",
"user_request_hash": "95f3a4b2f59e67d2025d47f8075650a2d61deff2d323c9e235c38faabd0b1092",
"record_hash": "fc444330711076d424de47874e73ab4fdd13ff5a1f34... |
JF-ASE-001-10 | 1.0.0 | train | {
"family": "problem_understanding",
"family_label": "Problem Understanding",
"archetype": "ambiguous_scope",
"difficulty": "medium",
"behavior_targets": [
"intent_modeling",
"scope_control",
"assumption_tracking",
"acceptance_criteria"
]
} | {
"language": "Kotlin",
"framework": "Ktor",
"test_tool": "Kotest",
"build_tool": "Gradle"
} | {
"name": "stream-media-processing-service",
"domain": "media processing",
"architecture": "plugin-oriented application",
"summary": "A media processing repository organized as a plugin-oriented application.",
"file_tree": [
"src/main/kotlin/app/Routes.kt",
"src/main/kotlin/app/Service.kt",
"src/m... | {
"user_request": "A maintenance task became unsafe after reviewers noticed the team cannot safely complete the media processing change because ambiguous scope remains unresolved following a dependency upgrade. Work in `stream-media-processing-service`, a plugin-oriented application implemented with Kotlin and Ktor. ... | {
"core_issue": "The core issue is ambiguous scope: the authorization policy establishes state using a condition that is only valid on the common path, while the resource loader consumes that state following a dependency upgrade. The failure becomes observable in the media processing workflow because the two componen... | {
"initial_assessment": "This is primarily a `Problem Understanding` task. The agent should first establish whether `ambiguous scope` is a symptom, a root cause, or an underspecified request.",
"assumptions": [
"The issue is limited to the path connecting the authorization policy and resource loader; this remai... | [
{
"type": "premature_patch",
"response": "Immediately rewrite the resource loader and update every caller without inspecting the repository.",
"why_wrong": "It treats a hypothesis as fact, expands blast radius, and skips evidence and compatibility checks."
},
{
"type": "hallucinated_evidence",
... | {
"must_do": [
"Distinguish verified evidence from assumptions.",
"Inspect or reason about the relationship between `src/main/kotlin/app/Worker.kt` and `src/main/kotlin/app/Security.kt`.",
"Respect all stated constraints.",
"Define a failure-focused verification step.",
"Keep the proposed change b... | [
{
"role": "system",
"content": "You are a software-engineering agent. Ground conclusions in available evidence, use tools deliberately, preserve safety and contracts, and never claim unobserved results."
},
{
"role": "user",
"content": "A maintenance task became unsafe after reviewers noticed th... | {
"validation_status": "machine_validated",
"heuristic_score": 97,
"structural_fingerprint": "2e2a078ba0a46a72ec45a6a9ab2e46550a5bf147813b9207c5773281cc4b4ff4",
"user_request_hash": "513d052e62c4d946520641375120d0d79a7b00f1fc600194689f841404440520",
"record_hash": "d69e56236a95913283bd231565f96d630df08891e551... |
JF-ASE-001-11 | 1.0.0 | train | {
"family": "problem_understanding",
"family_label": "Problem Understanding",
"archetype": "ambiguous_scope",
"difficulty": "hard",
"behavior_targets": [
"intent_modeling",
"scope_control",
"assumption_tracking",
"acceptance_criteria"
]
} | {
"language": "Ruby",
"framework": "Rails",
"test_tool": "RSpec",
"build_tool": "Bundler"
} | {
"name": "pilot-cloud-infrastructure-service",
"domain": "cloud infrastructure",
"architecture": "modular monolith",
"summary": "A cloud infrastructure repository organized as a modular monolith.",
"file_tree": [
"config/routes.rb",
"app/controllers/workflows_controller.rb",
"app/services/workflo... | {
"user_request": "The repository owner asks for help with a case where the cloud infrastructure system behaves correctly in the common path but exposes ambiguous scope near the end of a paginated result set. Work in `pilot-cloud-infrastructure-service`, a modular monolith implemented with Ruby and Rails. Focus on th... | {
"core_issue": "The core issue is ambiguous scope: the message producer establishes state using a condition that is only valid on the common path, while the idempotency store consumes that state near the end of a paginated result set. The failure becomes observable in the cloud infrastructure workflow because the tw... | {
"initial_assessment": "This is primarily a `Problem Understanding` task. The agent should first establish whether `ambiguous scope` is a symptom, a root cause, or an underspecified request.",
"assumptions": [
"The issue is limited to the path connecting the message producer and idempotency store; this remains... | [
{
"type": "premature_patch",
"response": "Immediately rewrite the idempotency store and update every caller without inspecting the repository.",
"why_wrong": "It treats a hypothesis as fact, expands blast radius, and skips evidence and compatibility checks."
},
{
"type": "hallucinated_evidence",... | {
"must_do": [
"Distinguish verified evidence from assumptions.",
"Inspect or reason about the relationship between `app/policies/workflow_policy.rb` and `spec/requests/workflows_spec.rb`.",
"Respect all stated constraints.",
"Define a failure-focused verification step.",
"Keep the proposed change... | [
{
"role": "system",
"content": "You are a software-engineering agent. Ground conclusions in available evidence, use tools deliberately, preserve safety and contracts, and never claim unobserved results."
},
{
"role": "user",
"content": "The repository owner asks for help with a case where the cl... | {
"validation_status": "machine_validated",
"heuristic_score": 98,
"structural_fingerprint": "4bc1691b0fc058e15a0786781b214b9b795b1cd8e506265ed0acf711a417ebf5",
"user_request_hash": "0f3339ab9ede7db31d7d04deade3b3c9662ba1939a4f823a59e11c98f930301f",
"record_hash": "ef7f111eb56919f592f1ff688d13015e138b00044ac2... |
JF-ASE-001-12 | 1.0.0 | train | {
"family": "problem_understanding",
"family_label": "Problem Understanding",
"archetype": "ambiguous_scope",
"difficulty": "expert",
"behavior_targets": [
"intent_modeling",
"scope_control",
"assumption_tracking",
"acceptance_criteria"
]
} | {
"language": "C++",
"framework": "CMake service",
"test_tool": "Catch2",
"build_tool": "CMake"
} | {
"name": "mesh-customer-support-service",
"domain": "customer support",
"architecture": "event-driven services",
"summary": "A customer support repository organized as a event-driven services.",
"file_tree": [
"src/http/routes.cpp",
"src/core/workflow.cpp",
"src/data/repository.cpp",
"src/wor... | {
"user_request": "A rollout checkpoint failed because a proposed fix for ambiguous scope would broaden scope without first explaining why the failure occurs when the payload contains an empty optional field. Work in `mesh-customer-support-service`, a event-driven services implemented with C++ and CMake service. Focu... | {
"core_issue": "The core issue is ambiguous scope: the upload controller establishes state using a condition that is only valid on the common path, while the object storage adapter consumes that state when the payload contains an empty optional field. The failure becomes observable in the customer support workflow b... | {
"initial_assessment": "This is primarily a `Problem Understanding` task. The agent should first establish whether `ambiguous scope` is a symptom, a root cause, or an underspecified request.",
"assumptions": [
"The issue is limited to the path connecting the upload controller and object storage adapter; this r... | [
{
"type": "premature_patch",
"response": "Immediately rewrite the object storage adapter and update every caller without inspecting the repository.",
"why_wrong": "It treats a hypothesis as fact, expands blast radius, and skips evidence and compatibility checks."
},
{
"type": "hallucinated_evide... | {
"must_do": [
"Distinguish verified evidence from assumptions.",
"Inspect or reason about the relationship between `tests/workflow_test.cpp` and `src/http/routes.cpp`.",
"Respect all stated constraints.",
"Define a failure-focused verification step.",
"Keep the proposed change bounded and reversi... | [
{
"role": "system",
"content": "You are a software-engineering agent. Ground conclusions in available evidence, use tools deliberately, preserve safety and contracts, and never claim unobserved results."
},
{
"role": "user",
"content": "A rollout checkpoint failed because a proposed fix for ambi... | {
"validation_status": "machine_validated",
"heuristic_score": 88,
"structural_fingerprint": "c0597611cc4ed88e3cd20e4308208f1af06e9d7196fd44ef43bdd5e636d05929",
"user_request_hash": "9ed58f6762ad1a5aee54194606f89e72539f5302a7ee3d5dd5d0c8e98b871a89",
"record_hash": "591d827cb275b5f8b51faac2dcff684ec1217626f9a2... |
JF-ASE-001-13 | 1.0.0 | train | {
"family": "problem_understanding",
"family_label": "Problem Understanding",
"archetype": "ambiguous_scope",
"difficulty": "easy",
"behavior_targets": [
"intent_modeling",
"scope_control",
"assumption_tracking",
"acceptance_criteria"
]
} | {
"language": "Python",
"framework": "FastAPI",
"test_tool": "pytest",
"build_tool": "uv"
} | {
"name": "beacon-document-management-service",
"domain": "document management",
"architecture": "service-repository application",
"summary": "A document management repository organized as a service-repository application.",
"file_tree": [
"app/api/routes.py",
"app/services/core.py",
"app/reposito... | {
"user_request": "An incident follow-up points to a scenario in which ambiguous scope appears in the document management workflow after a worker restarts, and the relationship between the webhook receiver and retry coordinator is not yet proven. Work in `beacon-document-management-service`, a service-repository appl... | {
"core_issue": "The core issue is ambiguous scope: the webhook receiver establishes state using a condition that is only valid on the common path, while the retry coordinator consumes that state after a worker restarts. The failure becomes observable in the document management workflow because the two components dis... | {
"initial_assessment": "This is primarily a `Problem Understanding` task. The agent should first establish whether `ambiguous scope` is a symptom, a root cause, or an underspecified request.",
"assumptions": [
"The issue is limited to the path connecting the webhook receiver and retry coordinator; this remains... | [
{
"type": "premature_patch",
"response": "Immediately rewrite the retry coordinator and update every caller without inspecting the repository.",
"why_wrong": "It treats a hypothesis as fact, expands blast radius, and skips evidence and compatibility checks."
},
{
"type": "hallucinated_evidence",... | {
"must_do": [
"Distinguish verified evidence from assumptions.",
"Inspect or reason about the relationship between `app/api/routes.py` and `app/services/core.py`.",
"Respect all stated constraints.",
"Define a failure-focused verification step.",
"Keep the proposed change bounded and reversible."... | [
{
"role": "system",
"content": "You are a software-engineering agent. Ground conclusions in available evidence, use tools deliberately, preserve safety and contracts, and never claim unobserved results."
},
{
"role": "user",
"content": "An incident follow-up points to a scenario in which ambiguo... | {
"validation_status": "machine_validated",
"heuristic_score": 89,
"structural_fingerprint": "dfd28b03f51876f8e77ca16709acc91187019d639077211b07781f0560e6ad01",
"user_request_hash": "13e9412f72eaab5056c072fb982060810e40fe50df5bc1fff5582082116698dc",
"record_hash": "7e35561fca579ec5381c6b3bcb46b62d1910151e3908... |
JF-ASE-001-14 | 1.0.0 | train | {
"family": "problem_understanding",
"family_label": "Problem Understanding",
"archetype": "ambiguous_scope",
"difficulty": "medium",
"behavior_targets": [
"intent_modeling",
"scope_control",
"assumption_tracking",
"acceptance_criteria"
]
} | {
"language": "Python",
"framework": "Django",
"test_tool": "pytest-django",
"build_tool": "pip"
} | {
"name": "kernel-iot-operations-service",
"domain": "IoT operations",
"architecture": "microservice platform",
"summary": "A IoT operations repository organized as a microservice platform.",
"file_tree": [
"project/urls.py",
"app/views.py",
"app/services.py",
"app/models.py",
"app/middlew... | {
"user_request": "A pre-release audit found that the team cannot safely complete the IoT operations change because ambiguous scope remains unresolved while the queue is under backpressure. Work in `kernel-iot-operations-service`, a microservice platform implemented with Python and Django. Focus on the agent behavior... | {
"core_issue": "The core issue is ambiguous scope: the query builder establishes state using a condition that is only valid on the common path, while the pagination layer consumes that state while the queue is under backpressure. The failure becomes observable in the IoT operations workflow because the two component... | {
"initial_assessment": "This is primarily a `Problem Understanding` task. The agent should first establish whether `ambiguous scope` is a symptom, a root cause, or an underspecified request.",
"assumptions": [
"The issue is limited to the path connecting the query builder and pagination layer; this remains a h... | [
{
"type": "premature_patch",
"response": "Immediately rewrite the pagination layer and update every caller without inspecting the repository.",
"why_wrong": "It treats a hypothesis as fact, expands blast radius, and skips evidence and compatibility checks."
},
{
"type": "hallucinated_evidence",
... | {
"must_do": [
"Distinguish verified evidence from assumptions.",
"Inspect or reason about the relationship between `app/views.py` and `app/services.py`.",
"Respect all stated constraints.",
"Define a failure-focused verification step.",
"Keep the proposed change bounded and reversible."
],
"m... | [
{
"role": "system",
"content": "You are a software-engineering agent. Ground conclusions in available evidence, use tools deliberately, preserve safety and contracts, and never claim unobserved results."
},
{
"role": "user",
"content": "A pre-release audit found that the team cannot safely compl... | {
"validation_status": "machine_validated",
"heuristic_score": 90,
"structural_fingerprint": "d5ee6e2e99cd3cc1d310131c5a2dfadb6e58b8163117a1de7ccce782bc3c14c8",
"user_request_hash": "122ebc8bdf85ba8e31d33d3f72a03da6766a2c4691fc26b9cae9b4451933f38b",
"record_hash": "40b3f2515a998367225a6e03c37483764b2a5c3f9ec4... |
JF-ASE-001-15 | 1.0.0 | train | {
"family": "problem_understanding",
"family_label": "Problem Understanding",
"archetype": "ambiguous_scope",
"difficulty": "hard",
"behavior_targets": [
"intent_modeling",
"scope_control",
"assumption_tracking",
"acceptance_criteria"
]
} | {
"language": "TypeScript",
"framework": "Node.js",
"test_tool": "Vitest",
"build_tool": "pnpm"
} | {
"name": "canvas-financial-reporting-service",
"domain": "financial reporting",
"architecture": "serverless workflow",
"summary": "A financial reporting repository organized as a serverless workflow.",
"file_tree": [
"src/http/routes.ts",
"src/services/core.ts",
"src/data/repository.ts",
"src... | {
"user_request": "A regression report describes the following condition: ambiguous scope appears in the financial reporting workflow during an idempotent event replay, and the relationship between the CLI command and process runner is not yet proven. Work in `canvas-financial-reporting-service`, a serverless workflo... | {
"core_issue": "The core issue is ambiguous scope: the CLI command establishes state using a condition that is only valid on the common path, while the process runner consumes that state during an idempotent event replay. The failure becomes observable in the financial reporting workflow because the two components d... | {
"initial_assessment": "This is primarily a `Problem Understanding` task. The agent should first establish whether `ambiguous scope` is a symptom, a root cause, or an underspecified request.",
"assumptions": [
"The issue is limited to the path connecting the CLI command and process runner; this remains a hypot... | [
{
"type": "premature_patch",
"response": "Immediately rewrite the process runner and update every caller without inspecting the repository.",
"why_wrong": "It treats a hypothesis as fact, expands blast radius, and skips evidence and compatibility checks."
},
{
"type": "hallucinated_evidence",
... | {
"must_do": [
"Distinguish verified evidence from assumptions.",
"Inspect or reason about the relationship between `src/data/repository.ts` and `src/workers/consumer.ts`.",
"Respect all stated constraints.",
"Define a failure-focused verification step.",
"Keep the proposed change bounded and reve... | [
{
"role": "system",
"content": "You are a software-engineering agent. Ground conclusions in available evidence, use tools deliberately, preserve safety and contracts, and never claim unobserved results."
},
{
"role": "user",
"content": "A regression report describes the following condition: ambi... | {
"validation_status": "machine_validated",
"heuristic_score": 91,
"structural_fingerprint": "8a8cb1edbf5f1e30d99d532de4bdf3b6eb5311b9a789cb4898e6e90ca8ca0917",
"user_request_hash": "682cf453a07510a56519a20c653b7739da5fe31eda60118355fdd224efba9e02",
"record_hash": "82556205789570767fc72c33f5fb61d6f2d6ee7fbc83... |
JF-ASE-001-16 | 1.0.0 | train | {
"family": "problem_understanding",
"family_label": "Problem Understanding",
"archetype": "ambiguous_scope",
"difficulty": "expert",
"behavior_targets": [
"intent_modeling",
"scope_control",
"assumption_tracking",
"acceptance_criteria"
]
} | {
"language": "TypeScript",
"framework": "React",
"test_tool": "Playwright",
"build_tool": "Vite"
} | {
"name": "pulse-search-infrastructure-service",
"domain": "search infrastructure",
"architecture": "worker-based pipeline",
"summary": "A search infrastructure repository organized as a worker-based pipeline.",
"file_tree": [
"src/app/router.tsx",
"src/features/state.ts",
"src/api/client.ts",
... | {
"user_request": "The current implementation is uncertain because evidence from the frontend state store conflicts with assumptions made by the API client, producing ambiguous scope when application nodes have mild clock skew. Work in `pulse-search-infrastructure-service`, a worker-based pipeline implemented with Ty... | {
"core_issue": "The core issue is ambiguous scope: the frontend state store establishes state using a condition that is only valid on the common path, while the API client consumes that state when application nodes have mild clock skew. The failure becomes observable in the search infrastructure workflow because the... | {
"initial_assessment": "This is primarily a `Problem Understanding` task. The agent should first establish whether `ambiguous scope` is a symptom, a root cause, or an underspecified request.",
"assumptions": [
"The issue is limited to the path connecting the frontend state store and API client; this remains a ... | [
{
"type": "premature_patch",
"response": "Immediately rewrite the API client and update every caller without inspecting the repository.",
"why_wrong": "It treats a hypothesis as fact, expands blast radius, and skips evidence and compatibility checks."
},
{
"type": "hallucinated_evidence",
"r... | {
"must_do": [
"Distinguish verified evidence from assumptions.",
"Inspect or reason about the relationship between `src/components/Workflow.tsx` and `src/auth/session.ts`.",
"Respect all stated constraints.",
"Define a failure-focused verification step.",
"Keep the proposed change bounded and rev... | [
{
"role": "system",
"content": "You are a software-engineering agent. Ground conclusions in available evidence, use tools deliberately, preserve safety and contracts, and never claim unobserved results."
},
{
"role": "user",
"content": "The current implementation is uncertain because evidence fr... | {
"validation_status": "machine_validated",
"heuristic_score": 92,
"structural_fingerprint": "b4ee571041ec1c72b7bfba559827392237bcd3a91b978de6819e2a71b7337314",
"user_request_hash": "ce6813215f7f902fb53bf8f39a1e7899ab1c98e38a9048b44ab73782fba7eb88",
"record_hash": "66cd7f4f604a15772cfa3f3a77fd197a65e83d3e6805... |
JF-ASE-001-17 | 1.0.0 | train | {
"family": "problem_understanding",
"family_label": "Problem Understanding",
"archetype": "ambiguous_scope",
"difficulty": "easy",
"behavior_targets": [
"intent_modeling",
"scope_control",
"assumption_tracking",
"acceptance_criteria"
]
} | {
"language": "Java",
"framework": "Spring Boot",
"test_tool": "JUnit",
"build_tool": "Gradle"
} | {
"name": "matrix-content-moderation-service",
"domain": "content moderation",
"architecture": "multi-tenant SaaS",
"summary": "A content moderation repository organized as a multi-tenant SaaS.",
"file_tree": [
"src/main/java/app/Controller.java",
"src/main/java/app/Service.java",
"src/main/java/a... | {
"user_request": "A teammate proposed a quick fix, but the evidence only proves that the team cannot safely complete the content moderation change because ambiguous scope remains unresolved after a zero-downtime schema migration. Work in `matrix-content-moderation-service`, a multi-tenant SaaS implemented with Java ... | {
"core_issue": "The core issue is ambiguous scope: the metrics exporter establishes state using a condition that is only valid on the common path, while the runtime instrumentation consumes that state after a zero-downtime schema migration. The failure becomes observable in the content moderation workflow because th... | {
"initial_assessment": "This is primarily a `Problem Understanding` task. The agent should first establish whether `ambiguous scope` is a symptom, a root cause, or an underspecified request.",
"assumptions": [
"The issue is limited to the path connecting the metrics exporter and runtime instrumentation; this r... | [
{
"type": "premature_patch",
"response": "Immediately rewrite the runtime instrumentation and update every caller without inspecting the repository.",
"why_wrong": "It treats a hypothesis as fact, expands blast radius, and skips evidence and compatibility checks."
},
{
"type": "hallucinated_evid... | {
"must_do": [
"Distinguish verified evidence from assumptions.",
"Inspect or reason about the relationship between `src/main/java/app/SecurityPolicy.java` and `src/test/java/app/WorkflowTest.java`.",
"Respect all stated constraints.",
"Define a failure-focused verification step.",
"Keep the propo... | [
{
"role": "system",
"content": "You are a software-engineering agent. Ground conclusions in available evidence, use tools deliberately, preserve safety and contracts, and never claim unobserved results."
},
{
"role": "user",
"content": "A teammate proposed a quick fix, but the evidence only prov... | {
"validation_status": "machine_validated",
"heuristic_score": 93,
"structural_fingerprint": "4c95ddd55b5312ab1ee58ee57fc75650ffb6a5865fbafcd14f11ce1027f035cb",
"user_request_hash": "b465a8c77a121d86655213d5b2f3ea567dab0ee819fe8bcc2ba7a492ef72f813",
"record_hash": "a182478fefebdc5c881855e5f28434193b267e8a26d5... |
JF-ASE-001-18 | 1.0.0 | train | {
"family": "problem_understanding",
"family_label": "Problem Understanding",
"archetype": "ambiguous_scope",
"difficulty": "medium",
"behavior_targets": [
"intent_modeling",
"scope_control",
"assumption_tracking",
"acceptance_criteria"
]
} | {
"language": "Go",
"framework": "Chi",
"test_tool": "go test",
"build_tool": "Go modules"
} | {
"name": "anchor-hr-systems-service",
"domain": "HR systems",
"architecture": "API gateway architecture",
"summary": "A HR systems repository organized as a API gateway architecture.",
"file_tree": [
"internal/http/routes.go",
"internal/service/core.go",
"internal/store/repository.go",
"inter... | {
"user_request": "A multi-step change is blocked by the fact that the team cannot safely complete the HR systems change because ambiguous scope remains unresolved while old and new application versions coexist. Work in `anchor-hr-systems-service`, a API gateway architecture implemented with Go and Chi. Focus on the ... | {
"core_issue": "The core issue is ambiguous scope: the dependency resolver establishes state using a condition that is only valid on the common path, while the build pipeline consumes that state while old and new application versions coexist. The failure becomes observable in the HR systems workflow because the two ... | {
"initial_assessment": "This is primarily a `Problem Understanding` task. The agent should first establish whether `ambiguous scope` is a symptom, a root cause, or an underspecified request.",
"assumptions": [
"The issue is limited to the path connecting the dependency resolver and build pipeline; this remains... | [
{
"type": "premature_patch",
"response": "Immediately rewrite the build pipeline and update every caller without inspecting the repository.",
"why_wrong": "It treats a hypothesis as fact, expands blast radius, and skips evidence and compatibility checks."
},
{
"type": "hallucinated_evidence",
... | {
"must_do": [
"Distinguish verified evidence from assumptions.",
"Inspect or reason about the relationship between `internal/service/core_test.go` and `internal/http/routes.go`.",
"Respect all stated constraints.",
"Define a failure-focused verification step.",
"Keep the proposed change bounded a... | [
{
"role": "system",
"content": "You are a software-engineering agent. Ground conclusions in available evidence, use tools deliberately, preserve safety and contracts, and never claim unobserved results."
},
{
"role": "user",
"content": "A multi-step change is blocked by the fact that the team ca... | {
"validation_status": "machine_validated",
"heuristic_score": 94,
"structural_fingerprint": "d8c678aae07152e2bc118003e09b9aa0800a7773142a2c4b9ed4ada2dcc99e36",
"user_request_hash": "782ae41e3a54c8281f817de8e7514bcfe160dae23dca8f8167a9d39f76c04fc0",
"record_hash": "e69022a4b82a4b95b18315650b4ebd14b5d19b7aab22... |
JF-ASE-001-19 | 1.0.0 | train | {
"family": "problem_understanding",
"family_label": "Problem Understanding",
"archetype": "ambiguous_scope",
"difficulty": "hard",
"behavior_targets": [
"intent_modeling",
"scope_control",
"assumption_tracking",
"acceptance_criteria"
]
} | {
"language": "C#",
"framework": "ASP.NET Core",
"test_tool": "xUnit",
"build_tool": "dotnet"
} | {
"name": "prism-subscription-billing-service",
"domain": "subscription billing",
"architecture": "batch processing system",
"summary": "A subscription billing repository organized as a batch processing system.",
"file_tree": [
"Api/Controllers/WorkflowController.cs",
"Core/WorkflowService.cs",
"D... | {
"user_request": "A test environment and production-like environment disagree: evidence from the tenant resolver conflicts with assumptions made by the cache key builder, producing ambiguous scope when a fallback code path executes. Work in `prism-subscription-billing-service`, a batch processing system implemented ... | {
"core_issue": "The core issue is ambiguous scope: the tenant resolver establishes state using a condition that is only valid on the common path, while the cache key builder consumes that state when a fallback code path executes. The failure becomes observable in the subscription billing workflow because the two com... | {
"initial_assessment": "This is primarily a `Problem Understanding` task. The agent should first establish whether `ambiguous scope` is a symptom, a root cause, or an underspecified request.",
"assumptions": [
"The issue is limited to the path connecting the tenant resolver and cache key builder; this remains ... | [
{
"type": "premature_patch",
"response": "Immediately rewrite the cache key builder and update every caller without inspecting the repository.",
"why_wrong": "It treats a hypothesis as fact, expands blast radius, and skips evidence and compatibility checks."
},
{
"type": "hallucinated_evidence",... | {
"must_do": [
"Distinguish verified evidence from assumptions.",
"Inspect or reason about the relationship between `Api/Controllers/WorkflowController.cs` and `Core/WorkflowService.cs`.",
"Respect all stated constraints.",
"Define a failure-focused verification step.",
"Keep the proposed change b... | [
{
"role": "system",
"content": "You are a software-engineering agent. Ground conclusions in available evidence, use tools deliberately, preserve safety and contracts, and never claim unobserved results."
},
{
"role": "user",
"content": "A test environment and production-like environment disagree... | {
"validation_status": "machine_validated",
"heuristic_score": 95,
"structural_fingerprint": "516df01d11b6208bbe9f7743b3428b2c92bcea606b3703c38dcaaf8514776045",
"user_request_hash": "c957d664541629876f8a52b83708d622764969013159cbca2b0710fda39303de",
"record_hash": "5571b997581e4956c4791c560641c5e2f0bb2ee95def... |
JF-ASE-001-20 | 1.0.0 | train | {
"family": "problem_understanding",
"family_label": "Problem Understanding",
"archetype": "ambiguous_scope",
"difficulty": "expert",
"behavior_targets": [
"intent_modeling",
"scope_control",
"assumption_tracking",
"acceptance_criteria"
]
} | {
"language": "PHP",
"framework": "Laravel",
"test_tool": "PHPUnit",
"build_tool": "Composer"
} | {
"name": "switch-inventory-service",
"domain": "inventory",
"architecture": "plugin-oriented application",
"summary": "A inventory repository organized as a plugin-oriented application.",
"file_tree": [
"routes/api.php",
"app/Http/Controllers/WorkflowController.php",
"app/Services/WorkflowService... | {
"user_request": "A repository handoff highlights one unresolved behavior: a proposed fix for ambiguous scope would broaden scope without first explaining why the failure occurs during cooperative cancellation. Work in `switch-inventory-service`, a plugin-oriented application implemented with PHP and Laravel. Focus ... | {
"core_issue": "The core issue is ambiguous scope: the audit logger establishes state using a condition that is only valid on the common path, while the transaction manager consumes that state during cooperative cancellation. The failure becomes observable in the inventory workflow because the two components disagre... | {
"initial_assessment": "This is primarily a `Problem Understanding` task. The agent should first establish whether `ambiguous scope` is a symptom, a root cause, or an underspecified request.",
"assumptions": [
"The issue is limited to the path connecting the audit logger and transaction manager; this remains a... | [
{
"type": "premature_patch",
"response": "Immediately rewrite the transaction manager and update every caller without inspecting the repository.",
"why_wrong": "It treats a hypothesis as fact, expands blast radius, and skips evidence and compatibility checks."
},
{
"type": "hallucinated_evidence... | {
"must_do": [
"Distinguish verified evidence from assumptions.",
"Inspect or reason about the relationship between `app/Http/Controllers/WorkflowController.php` and `app/Services/WorkflowService.php`.",
"Respect all stated constraints.",
"Define a failure-focused verification step.",
"Keep the pr... | [
{
"role": "system",
"content": "You are a software-engineering agent. Ground conclusions in available evidence, use tools deliberately, preserve safety and contracts, and never claim unobserved results."
},
{
"role": "user",
"content": "A repository handoff highlights one unresolved behavior: a ... | {
"validation_status": "machine_validated",
"heuristic_score": 96,
"structural_fingerprint": "495f0f0ad81d79ac7177c9fbd6ed162ed5afb9e5142b5fc5a163efd19f3b0ec5",
"user_request_hash": "c551fd00e6fce6642abec0c04b90006d147ab7b7145e8ae3366d05f0b739a2ba",
"record_hash": "bd2e3d7f6bd9a6ca0a15cc303273af861dbfc8fae0ab... |
JF-ASE-001-21 | 1.0.0 | train | {
"family": "problem_understanding",
"family_label": "Problem Understanding",
"archetype": "ambiguous_scope",
"difficulty": "easy",
"behavior_targets": [
"intent_modeling",
"scope_control",
"assumption_tracking",
"acceptance_criteria"
]
} | {
"language": "Rust",
"framework": "Axum",
"test_tool": "cargo test",
"build_tool": "Cargo"
} | {
"name": "trail-observability-service",
"domain": "observability",
"architecture": "modular monolith",
"summary": "A observability repository organized as a modular monolith.",
"file_tree": [
"src/http/routes.rs",
"src/services/core.rs",
"src/store/repository.rs",
"src/workers/consumer.rs",
... | {
"user_request": "A reliability review asks the agent to address a case where a proposed fix for ambiguous scope would broaden scope without first explaining why the failure occurs after a duplicate event delivery. Work in `trail-observability-service`, a modular monolith implemented with Rust and Axum. Focus on the... | {
"core_issue": "The core issue is ambiguous scope: the notification dispatcher establishes state using a condition that is only valid on the common path, while the template renderer consumes that state after a duplicate event delivery. The failure becomes observable in the observability workflow because the two comp... | {
"initial_assessment": "This is primarily a `Problem Understanding` task. The agent should first establish whether `ambiguous scope` is a symptom, a root cause, or an underspecified request.",
"assumptions": [
"The issue is limited to the path connecting the notification dispatcher and template renderer; this ... | [
{
"type": "premature_patch",
"response": "Immediately rewrite the template renderer and update every caller without inspecting the repository.",
"why_wrong": "It treats a hypothesis as fact, expands blast radius, and skips evidence and compatibility checks."
},
{
"type": "hallucinated_evidence",... | {
"must_do": [
"Distinguish verified evidence from assumptions.",
"Inspect or reason about the relationship between `src/store/repository.rs` and `src/workers/consumer.rs`.",
"Respect all stated constraints.",
"Define a failure-focused verification step.",
"Keep the proposed change bounded and rev... | [
{
"role": "system",
"content": "You are a software-engineering agent. Ground conclusions in available evidence, use tools deliberately, preserve safety and contracts, and never claim unobserved results."
},
{
"role": "user",
"content": "A reliability review asks the agent to address a case where... | {
"validation_status": "machine_validated",
"heuristic_score": 97,
"structural_fingerprint": "f26770a068fd5650f3bc64525e14de2f11d2e3c123d97550f75ac14d5193746d",
"user_request_hash": "d47c8db776c5dab7eec8ad05a066436bc7c2e59942c6a04640a7939f803c5f22",
"record_hash": "c664bbce3d9022d7dc9fddf2166b182477a40f1b191d... |
JF-ASE-001-22 | 1.0.0 | train | {
"family": "problem_understanding",
"family_label": "Problem Understanding",
"archetype": "ambiguous_scope",
"difficulty": "medium",
"behavior_targets": [
"intent_modeling",
"scope_control",
"assumption_tracking",
"acceptance_criteria"
]
} | {
"language": "Kotlin",
"framework": "Ktor",
"test_tool": "Kotest",
"build_tool": "Gradle"
} | {
"name": "vector-data-pipelines-service",
"domain": "data pipelines",
"architecture": "event-driven services",
"summary": "A data pipelines repository organized as a event-driven services.",
"file_tree": [
"src/main/kotlin/app/Routes.kt",
"src/main/kotlin/app/Service.kt",
"src/main/kotlin/app/Rep... | {
"user_request": "The task appears simple, yet the system context shows that a proposed fix for ambiguous scope would broaden scope without first explaining why the failure occurs with a stale session token. Work in `vector-data-pipelines-service`, a event-driven services implemented with Kotlin and Ktor. Focus on t... | {
"core_issue": "The core issue is ambiguous scope: the search indexer establishes state using a condition that is only valid on the common path, while the change-data-capture stream consumes that state with a stale session token. The failure becomes observable in the data pipelines workflow because the two component... | {
"initial_assessment": "This is primarily a `Problem Understanding` task. The agent should first establish whether `ambiguous scope` is a symptom, a root cause, or an underspecified request.",
"assumptions": [
"The issue is limited to the path connecting the search indexer and change-data-capture stream; this ... | [
{
"type": "premature_patch",
"response": "Immediately rewrite the change-data-capture stream and update every caller without inspecting the repository.",
"why_wrong": "It treats a hypothesis as fact, expands blast radius, and skips evidence and compatibility checks."
},
{
"type": "hallucinated_e... | {
"must_do": [
"Distinguish verified evidence from assumptions.",
"Inspect or reason about the relationship between `src/main/kotlin/app/Worker.kt` and `src/main/kotlin/app/Security.kt`.",
"Respect all stated constraints.",
"Define a failure-focused verification step.",
"Keep the proposed change b... | [
{
"role": "system",
"content": "You are a software-engineering agent. Ground conclusions in available evidence, use tools deliberately, preserve safety and contracts, and never claim unobserved results."
},
{
"role": "user",
"content": "The task appears simple, yet the system context shows that ... | {
"validation_status": "machine_validated",
"heuristic_score": 98,
"structural_fingerprint": "b80dc5748196e7a6d5c3c726c93d39f70490d79aed463dc0b7515ca733a787c3",
"user_request_hash": "a5e303f0eb6881c04a255cee858b0b480020e3176105333501ecf51a70bcd22a",
"record_hash": "860caa03a6a1b32a91b11d36207e679f8e66e6f683b4... |
JF-ASE-001-23 | 1.0.0 | train | {
"family": "problem_understanding",
"family_label": "Problem Understanding",
"archetype": "ambiguous_scope",
"difficulty": "hard",
"behavior_targets": [
"intent_modeling",
"scope_control",
"assumption_tracking",
"acceptance_criteria"
]
} | {
"language": "Ruby",
"framework": "Rails",
"test_tool": "RSpec",
"build_tool": "Bundler"
} | {
"name": "watch-feature-management-service",
"domain": "feature management",
"architecture": "service-repository application",
"summary": "A feature management repository organized as a service-repository application.",
"file_tree": [
"config/routes.rb",
"app/controllers/workflows_controller.rb",
... | {
"user_request": "A recent refactor changed the conditions under which ambiguous scope appears in the feature management workflow when configuration is hot-reloaded, and the relationship between the rate limiter and distributed counter is not yet proven. Work in `watch-feature-management-service`, a service-reposito... | {
"core_issue": "The core issue is ambiguous scope: the rate limiter establishes state using a condition that is only valid on the common path, while the distributed counter consumes that state when configuration is hot-reloaded. The failure becomes observable in the feature management workflow because the two compon... | {
"initial_assessment": "This is primarily a `Problem Understanding` task. The agent should first establish whether `ambiguous scope` is a symptom, a root cause, or an underspecified request.",
"assumptions": [
"The issue is limited to the path connecting the rate limiter and distributed counter; this remains a... | [
{
"type": "premature_patch",
"response": "Immediately rewrite the distributed counter and update every caller without inspecting the repository.",
"why_wrong": "It treats a hypothesis as fact, expands blast radius, and skips evidence and compatibility checks."
},
{
"type": "hallucinated_evidence... | {
"must_do": [
"Distinguish verified evidence from assumptions.",
"Inspect or reason about the relationship between `app/policies/workflow_policy.rb` and `spec/requests/workflows_spec.rb`.",
"Respect all stated constraints.",
"Define a failure-focused verification step.",
"Keep the proposed change... | [
{
"role": "system",
"content": "You are a software-engineering agent. Ground conclusions in available evidence, use tools deliberately, preserve safety and contracts, and never claim unobserved results."
},
{
"role": "user",
"content": "A recent refactor changed the conditions under which ambigu... | {
"validation_status": "machine_validated",
"heuristic_score": 88,
"structural_fingerprint": "16bfd38eb3e6f85088728a9481d4830b7e0221e8ec9e1104c7dd95a4f35b393e",
"user_request_hash": "7b55bc3ed01e12e3d5d0e2687a3f838cbb3fdba3abb13e666ed536fa92459b2e",
"record_hash": "87c75954b968b3b5f09b1f61f753f159eaec2a2b01ca... |
JF-ASE-001-24 | 1.0.0 | train | {
"family": "problem_understanding",
"family_label": "Problem Understanding",
"archetype": "ambiguous_scope",
"difficulty": "expert",
"behavior_targets": [
"intent_modeling",
"scope_control",
"assumption_tracking",
"acceptance_criteria"
]
} | {
"language": "C++",
"framework": "CMake service",
"test_tool": "Catch2",
"build_tool": "CMake"
} | {
"name": "engine-cybersecurity-operations-service",
"domain": "cybersecurity operations",
"architecture": "microservice platform",
"summary": "A cybersecurity operations repository organized as a microservice platform.",
"file_tree": [
"src/http/routes.cpp",
"src/core/workflow.cpp",
"src/data/rep... | {
"user_request": "A security review requires careful handling because evidence from the validation layer conflicts with assumptions made by the normalization pipeline, producing ambiguous scope under high-cardinality traffic. Work in `engine-cybersecurity-operations-service`, a microservice platform implemented with... | {
"core_issue": "The core issue is ambiguous scope: the validation layer establishes state using a condition that is only valid on the common path, while the normalization pipeline consumes that state under high-cardinality traffic. The failure becomes observable in the cybersecurity operations workflow because the t... | {
"initial_assessment": "This is primarily a `Problem Understanding` task. The agent should first establish whether `ambiguous scope` is a symptom, a root cause, or an underspecified request.",
"assumptions": [
"The issue is limited to the path connecting the validation layer and normalization pipeline; this re... | [
{
"type": "premature_patch",
"response": "Immediately rewrite the normalization pipeline and update every caller without inspecting the repository.",
"why_wrong": "It treats a hypothesis as fact, expands blast radius, and skips evidence and compatibility checks."
},
{
"type": "hallucinated_evide... | {
"must_do": [
"Distinguish verified evidence from assumptions.",
"Inspect or reason about the relationship between `tests/workflow_test.cpp` and `src/http/routes.cpp`.",
"Respect all stated constraints.",
"Define a failure-focused verification step.",
"Keep the proposed change bounded and reversi... | [
{
"role": "system",
"content": "You are a software-engineering agent. Ground conclusions in available evidence, use tools deliberately, preserve safety and contracts, and never claim unobserved results."
},
{
"role": "user",
"content": "A security review requires careful handling because evidenc... | {
"validation_status": "machine_validated",
"heuristic_score": 89,
"structural_fingerprint": "d2b19511a1a2d554e77106c65dab452c7908025b34e8ba28ac5ded7c2f2ded8a",
"user_request_hash": "172664eaaeb46ab91849b63f6bb096809a27a296cd55bef6a607692ba9dc4877",
"record_hash": "156d4b1176ae815e9236789cb8f8cff07bdbfd72882a... |
JF-ASE-001-25 | 1.0.0 | train | {
"family": "problem_understanding",
"family_label": "Problem Understanding",
"archetype": "ambiguous_scope",
"difficulty": "easy",
"behavior_targets": [
"intent_modeling",
"scope_control",
"assumption_tracking",
"acceptance_criteria"
]
} | {
"language": "Python",
"framework": "FastAPI",
"test_tool": "pytest",
"build_tool": "uv"
} | {
"name": "gateway-workflow-automation-service",
"domain": "workflow automation",
"architecture": "serverless workflow",
"summary": "A workflow automation repository organized as a serverless workflow.",
"file_tree": [
"app/api/routes.py",
"app/services/core.py",
"app/repositories/store.py",
"... | {
"user_request": "A release candidate cannot proceed until the agent explains why the team cannot safely complete the workflow automation change because ambiguous scope remains unresolved when a client omits a recently added field. Work in `gateway-workflow-automation-service`, a serverless workflow implemented with... | {
"core_issue": "The core issue is ambiguous scope: the release orchestrator establishes state using a condition that is only valid on the common path, while the deployment manifest consumes that state when a client omits a recently added field. The failure becomes observable in the workflow automation workflow becau... | {
"initial_assessment": "This is primarily a `Problem Understanding` task. The agent should first establish whether `ambiguous scope` is a symptom, a root cause, or an underspecified request.",
"assumptions": [
"The issue is limited to the path connecting the release orchestrator and deployment manifest; this r... | [
{
"type": "premature_patch",
"response": "Immediately rewrite the deployment manifest and update every caller without inspecting the repository.",
"why_wrong": "It treats a hypothesis as fact, expands blast radius, and skips evidence and compatibility checks."
},
{
"type": "hallucinated_evidence... | {
"must_do": [
"Distinguish verified evidence from assumptions.",
"Inspect or reason about the relationship between `app/api/routes.py` and `app/services/core.py`.",
"Respect all stated constraints.",
"Define a failure-focused verification step.",
"Keep the proposed change bounded and reversible."... | [
{
"role": "system",
"content": "You are a software-engineering agent. Ground conclusions in available evidence, use tools deliberately, preserve safety and contracts, and never claim unobserved results."
},
{
"role": "user",
"content": "A release candidate cannot proceed until the agent explains... | {
"validation_status": "machine_validated",
"heuristic_score": 90,
"structural_fingerprint": "afe9616c00aa6b1ab3b350083d7717eb733ee3f4aef35c209b96f2fad5ce21d0",
"user_request_hash": "353a5a0b96c48636e4f9374c3b41b1aa3a977624ed26f926656f107835413f8a",
"record_hash": "3ba4bb223aa38afd60b4c91cc429b8a9141b576fe8e7... |
JF-ASE-002-01 | 1.0.0 | train | {
"family": "problem_understanding",
"family_label": "Problem Understanding",
"archetype": "conflicting_requirements",
"difficulty": "medium",
"behavior_targets": [
"intent_modeling",
"scope_control",
"assumption_tracking",
"acceptance_criteria"
]
} | {
"language": "Go",
"framework": "Chi",
"test_tool": "go test",
"build_tool": "Go modules"
} | {
"name": "ledger-payments-platform",
"domain": "payments",
"architecture": "event-driven services",
"summary": "A payments repository organized as a event-driven services.",
"file_tree": [
"internal/http/routes.go",
"internal/service/core.go",
"internal/store/repository.go",
"internal/worker/... | {
"user_request": "A support escalation reports a proposed fix for conflicting requirements would broaden scope without first explaining why the failure occurs after a warm-cache transition. Work in `ledger-payments-platform`, a event-driven services implemented with Go and Chi. Focus on the agent behavior required f... | {
"core_issue": "The core issue is conflicting requirements: the request router establishes state using a condition that is only valid on the common path, while the domain service consumes that state after a warm-cache transition. The failure becomes observable in the payments workflow because the two components disa... | {
"initial_assessment": "This is primarily a `Problem Understanding` task. The agent should first establish whether `conflicting requirements` is a symptom, a root cause, or an underspecified request.",
"assumptions": [
"The issue is limited to the path connecting the request router and domain service; this rem... | [
{
"type": "premature_patch",
"response": "Immediately rewrite the domain service and update every caller without inspecting the repository.",
"why_wrong": "It treats a hypothesis as fact, expands blast radius, and skips evidence and compatibility checks."
},
{
"type": "hallucinated_evidence",
... | {
"must_do": [
"Distinguish verified evidence from assumptions.",
"Inspect or reason about the relationship between `internal/http/routes.go` and `internal/service/core.go`.",
"Respect all stated constraints.",
"Define a failure-focused verification step.",
"Keep the proposed change bounded and re... | [
{
"role": "system",
"content": "You are a software-engineering agent. Ground conclusions in available evidence, use tools deliberately, preserve safety and contracts, and never claim unobserved results."
},
{
"role": "user",
"content": "A support escalation reports a proposed fix for conflicting... | {
"validation_status": "machine_validated",
"heuristic_score": 89,
"structural_fingerprint": "05febd0ccdadaf12b401c1b740896f89288235dd0d1901182db4c4de70e525a4",
"user_request_hash": "ea855920f6c4de127d626f846d7740bfe96f0706862b5a602413d3f73ce4b465",
"record_hash": "9ffc8f70a18dc77d3c7c71e4bb6fb05351cbe61ced2b... |
JF-ASE-002-02 | 1.0.0 | train | {
"family": "problem_understanding",
"family_label": "Problem Understanding",
"archetype": "conflicting_requirements",
"difficulty": "hard",
"behavior_targets": [
"intent_modeling",
"scope_control",
"assumption_tracking",
"acceptance_criteria"
]
} | {
"language": "C#",
"framework": "ASP.NET Core",
"test_tool": "xUnit",
"build_tool": "dotnet"
} | {
"name": "relay-healthcare-scheduling-platform",
"domain": "healthcare scheduling",
"architecture": "service-repository application",
"summary": "A healthcare scheduling repository organized as a service-repository application.",
"file_tree": [
"Api/Controllers/WorkflowController.cs",
"Core/WorkflowS... | {
"user_request": "An engineer observed the healthcare scheduling system behaves correctly in the common path but exposes conflicting requirements under two concurrent requests. Work in `relay-healthcare-scheduling-platform`, a service-repository application implemented with C# and ASP.NET Core. Focus on the agent be... | {
"core_issue": "The core issue is conflicting requirements: the API handler establishes state using a condition that is only valid on the common path, while the repository adapter consumes that state under two concurrent requests. The failure becomes observable in the healthcare scheduling workflow because the two c... | {
"initial_assessment": "This is primarily a `Problem Understanding` task. The agent should first establish whether `conflicting requirements` is a symptom, a root cause, or an underspecified request.",
"assumptions": [
"The issue is limited to the path connecting the API handler and repository adapter; this re... | [
{
"type": "premature_patch",
"response": "Immediately rewrite the repository adapter and update every caller without inspecting the repository.",
"why_wrong": "It treats a hypothesis as fact, expands blast radius, and skips evidence and compatibility checks."
},
{
"type": "hallucinated_evidence"... | {
"must_do": [
"Distinguish verified evidence from assumptions.",
"Inspect or reason about the relationship between `Core/WorkflowService.cs` and `Data/WorkflowRepository.cs`.",
"Respect all stated constraints.",
"Define a failure-focused verification step.",
"Keep the proposed change bounded and ... | [
{
"role": "system",
"content": "You are a software-engineering agent. Ground conclusions in available evidence, use tools deliberately, preserve safety and contracts, and never claim unobserved results."
},
{
"role": "user",
"content": "An engineer observed the healthcare scheduling system behav... | {
"validation_status": "machine_validated",
"heuristic_score": 90,
"structural_fingerprint": "a1627e92779e416e106764fb6e6db7a24686ef32051fc8a4f917151fabbdc5a9",
"user_request_hash": "a097056d02c86257d0a61dfeb861c13aca453d37f5c19c57c257b48c514ddad1",
"record_hash": "e553eb3cbc27006f695c59b75d839d30eaacec40b48e... |
JF-ASE-002-03 | 1.0.0 | train | {
"family": "problem_understanding",
"family_label": "Problem Understanding",
"archetype": "conflicting_requirements",
"difficulty": "expert",
"behavior_targets": [
"intent_modeling",
"scope_control",
"assumption_tracking",
"acceptance_criteria"
]
} | {
"language": "PHP",
"framework": "Laravel",
"test_tool": "PHPUnit",
"build_tool": "Composer"
} | {
"name": "atlas-developer-tooling-platform",
"domain": "developer tooling",
"architecture": "microservice platform",
"summary": "A developer tooling repository organized as a microservice platform.",
"file_tree": [
"routes/api.php",
"app/Http/Controllers/WorkflowController.php",
"app/Services/Wor... | {
"user_request": "The latest release exposed a pattern: conflicting requirements appears in the developer tooling workflow during a rolling deployment, and the relationship between the background worker and event consumer is not yet proven. Work in `atlas-developer-tooling-platform`, a microservice platform implemen... | {
"core_issue": "The core issue is conflicting requirements: the background worker establishes state using a condition that is only valid on the common path, while the event consumer consumes that state during a rolling deployment. The failure becomes observable in the developer tooling workflow because the two compo... | {
"initial_assessment": "This is primarily a `Problem Understanding` task. The agent should first establish whether `conflicting requirements` is a symptom, a root cause, or an underspecified request.",
"assumptions": [
"The issue is limited to the path connecting the background worker and event consumer; this ... | [
{
"type": "premature_patch",
"response": "Immediately rewrite the event consumer and update every caller without inspecting the repository.",
"why_wrong": "It treats a hypothesis as fact, expands blast radius, and skips evidence and compatibility checks."
},
{
"type": "hallucinated_evidence",
... | {
"must_do": [
"Distinguish verified evidence from assumptions.",
"Inspect or reason about the relationship between `app/Services/WorkflowService.php` and `app/Repositories/WorkflowRepository.php`.",
"Respect all stated constraints.",
"Define a failure-focused verification step.",
"Keep the propos... | [
{
"role": "system",
"content": "You are a software-engineering agent. Ground conclusions in available evidence, use tools deliberately, preserve safety and contracts, and never claim unobserved results."
},
{
"role": "user",
"content": "The latest release exposed a pattern: conflicting requireme... | {
"validation_status": "machine_validated",
"heuristic_score": 91,
"structural_fingerprint": "a2fab6fa5ba4d48d5b72e0d3993557d64aaf2f5c776833d65c174562a3972c11",
"user_request_hash": "0665d71544fea8677fe7e05e4c7ec57878f02a4c0cb44ce93d1367b040d2d6f1",
"record_hash": "7f3af11a1f88ad3124c5444a40207c5a5119cfa73c9f... |
JF-ASE-002-04 | 1.0.0 | train | {
"family": "problem_understanding",
"family_label": "Problem Understanding",
"archetype": "conflicting_requirements",
"difficulty": "easy",
"behavior_targets": [
"intent_modeling",
"scope_control",
"assumption_tracking",
"acceptance_criteria"
]
} | {
"language": "Rust",
"framework": "Axum",
"test_tool": "cargo test",
"build_tool": "Cargo"
} | {
"name": "harbor-identity-management-platform",
"domain": "identity management",
"architecture": "serverless workflow",
"summary": "A identity management repository organized as a serverless workflow.",
"file_tree": [
"src/http/routes.rs",
"src/services/core.rs",
"src/store/repository.rs",
"s... | {
"user_request": "A reproducible test now shows the team cannot safely complete the identity management change because conflicting requirements remains unresolved at a daylight-saving boundary. Work in `harbor-identity-management-platform`, a serverless workflow implemented with Rust and Axum. Focus on the agent beh... | {
"core_issue": "The core issue is conflicting requirements: the session middleware establishes state using a condition that is only valid on the common path, while the identity store consumes that state at a daylight-saving boundary. The failure becomes observable in the identity management workflow because the two ... | {
"initial_assessment": "This is primarily a `Problem Understanding` task. The agent should first establish whether `conflicting requirements` is a symptom, a root cause, or an underspecified request.",
"assumptions": [
"The issue is limited to the path connecting the session middleware and identity store; this... | [
{
"type": "premature_patch",
"response": "Immediately rewrite the identity store and update every caller without inspecting the repository.",
"why_wrong": "It treats a hypothesis as fact, expands blast radius, and skips evidence and compatibility checks."
},
{
"type": "hallucinated_evidence",
... | {
"must_do": [
"Distinguish verified evidence from assumptions.",
"Inspect or reason about the relationship between `src/workers/consumer.rs` and `src/security/policy.rs`.",
"Respect all stated constraints.",
"Define a failure-focused verification step.",
"Keep the proposed change bounded and reve... | [
{
"role": "system",
"content": "You are a software-engineering agent. Ground conclusions in available evidence, use tools deliberately, preserve safety and contracts, and never claim unobserved results."
},
{
"role": "user",
"content": "A reproducible test now shows the team cannot safely comple... | {
"validation_status": "machine_validated",
"heuristic_score": 92,
"structural_fingerprint": "41d95d05293b5fbb5bbc807e272577f61da205e72a713ce2731c66924149e5dd",
"user_request_hash": "879b7c4d0426bdfbac70f4e2413a90ea135b8b505775d65d0522837d6ffafb13",
"record_hash": "c4596b91dd4b849104c51fbc89b2e75602d1dbddacc3... |
JF-ASE-002-05 | 1.0.0 | train | {
"family": "problem_understanding",
"family_label": "Problem Understanding",
"archetype": "conflicting_requirements",
"difficulty": "medium",
"behavior_targets": [
"intent_modeling",
"scope_control",
"assumption_tracking",
"acceptance_criteria"
]
} | {
"language": "Kotlin",
"framework": "Ktor",
"test_tool": "Kotest",
"build_tool": "Gradle"
} | {
"name": "forge-e-commerce-platform",
"domain": "e-commerce",
"architecture": "worker-based pipeline",
"summary": "A e-commerce repository organized as a worker-based pipeline.",
"file_tree": [
"src/main/kotlin/app/Routes.kt",
"src/main/kotlin/app/Service.kt",
"src/main/kotlin/app/Repository.kt",... | {
"user_request": "Operational telemetry suggests the e-commerce system behaves correctly in the common path but exposes conflicting requirements when retries overlap. Work in `forge-e-commerce-platform`, a worker-based pipeline implemented with Kotlin and Ktor. Focus on the agent behavior required for `conflicting r... | {
"core_issue": "The core issue is conflicting requirements: the cache layer establishes state using a condition that is only valid on the common path, while the database gateway consumes that state when retries overlap. The failure becomes observable in the e-commerce workflow because the two components disagree abo... | {
"initial_assessment": "This is primarily a `Problem Understanding` task. The agent should first establish whether `conflicting requirements` is a symptom, a root cause, or an underspecified request.",
"assumptions": [
"The issue is limited to the path connecting the cache layer and database gateway; this rema... | [
{
"type": "premature_patch",
"response": "Immediately rewrite the database gateway and update every caller without inspecting the repository.",
"why_wrong": "It treats a hypothesis as fact, expands blast radius, and skips evidence and compatibility checks."
},
{
"type": "hallucinated_evidence",
... | {
"must_do": [
"Distinguish verified evidence from assumptions.",
"Inspect or reason about the relationship between `src/main/kotlin/app/Security.kt` and `src/test/kotlin/app/WorkflowSpec.kt`.",
"Respect all stated constraints.",
"Define a failure-focused verification step.",
"Keep the proposed ch... | [
{
"role": "system",
"content": "You are a software-engineering agent. Ground conclusions in available evidence, use tools deliberately, preserve safety and contracts, and never claim unobserved results."
},
{
"role": "user",
"content": "Operational telemetry suggests the e-commerce system behave... | {
"validation_status": "machine_validated",
"heuristic_score": 93,
"structural_fingerprint": "dd5dc9747889c0d2ed725bf6f888021e66dc5ee8e856e04ae30a775ff4cb4560",
"user_request_hash": "6a8709c54ff96515f97f316b6e5785caad4cc227bee7556a290758e73bb73556",
"record_hash": "25124244835c48a1ba9daa8d9987ab6e01aa2fdde651... |
JF-ASE-002-06 | 1.0.0 | train | {
"family": "problem_understanding",
"family_label": "Problem Understanding",
"archetype": "conflicting_requirements",
"difficulty": "hard",
"behavior_targets": [
"intent_modeling",
"scope_control",
"assumption_tracking",
"acceptance_criteria"
]
} | {
"language": "Ruby",
"framework": "Rails",
"test_tool": "RSpec",
"build_tool": "Bundler"
} | {
"name": "signal-logistics-platform",
"domain": "logistics",
"architecture": "multi-tenant SaaS",
"summary": "A logistics repository organized as a multi-tenant SaaS.",
"file_tree": [
"config/routes.rb",
"app/controllers/workflows_controller.rb",
"app/services/workflow_service.rb",
"app/model... | {
"user_request": "A code review uncovered a risk: a proposed fix for conflicting requirements would broaden scope without first explaining why the failure occurs with legacy records created before the last migration. Work in `signal-logistics-platform`, a multi-tenant SaaS implemented with Ruby and Rails. Focus on t... | {
"core_issue": "The core issue is conflicting requirements: the scheduler establishes state using a condition that is only valid on the common path, while the job executor consumes that state with legacy records created before the last migration. The failure becomes observable in the logistics workflow because the t... | {
"initial_assessment": "This is primarily a `Problem Understanding` task. The agent should first establish whether `conflicting requirements` is a symptom, a root cause, or an underspecified request.",
"assumptions": [
"The issue is limited to the path connecting the scheduler and job executor; this remains a ... | [
{
"type": "premature_patch",
"response": "Immediately rewrite the job executor and update every caller without inspecting the repository.",
"why_wrong": "It treats a hypothesis as fact, expands blast radius, and skips evidence and compatibility checks."
},
{
"type": "hallucinated_evidence",
... | {
"must_do": [
"Distinguish verified evidence from assumptions.",
"Inspect or reason about the relationship between `spec/requests/workflows_spec.rb` and `config/routes.rb`.",
"Respect all stated constraints.",
"Define a failure-focused verification step.",
"Keep the proposed change bounded and re... | [
{
"role": "system",
"content": "You are a software-engineering agent. Ground conclusions in available evidence, use tools deliberately, preserve safety and contracts, and never claim unobserved results."
},
{
"role": "user",
"content": "A code review uncovered a risk: a proposed fix for conflict... | {
"validation_status": "machine_validated",
"heuristic_score": 94,
"structural_fingerprint": "16b85b0f47d0d137840689e5f25fb0eb4afd9fdcbdf73d7684973ba0d02b5a62",
"user_request_hash": "8d55ef0bdc5011d16606849043544819a071e37834a080224b4d31c16f63a823",
"record_hash": "76d9f10b19fdd9eabb2e9cf867d328f42e9fd63f60b2... |
JF-ASE-002-07 | 1.0.0 | train | {
"family": "problem_understanding",
"family_label": "Problem Understanding",
"archetype": "conflicting_requirements",
"difficulty": "expert",
"behavior_targets": [
"intent_modeling",
"scope_control",
"assumption_tracking",
"acceptance_criteria"
]
} | {
"language": "C++",
"framework": "CMake service",
"test_tool": "Catch2",
"build_tool": "CMake"
} | {
"name": "orbit-collaboration-software-platform",
"domain": "collaboration software",
"architecture": "API gateway architecture",
"summary": "A collaboration software repository organized as a API gateway architecture.",
"file_tree": [
"src/http/routes.cpp",
"src/core/workflow.cpp",
"src/data/rep... | {
"user_request": "The team needs a grounded investigation because a proposed fix for conflicting requirements would broaden scope without first explaining why the failure occurs immediately after a feature flag changes. Work in `orbit-collaboration-software-platform`, a API gateway architecture implemented with C++ ... | {
"core_issue": "The core issue is conflicting requirements: the serializer establishes state using a condition that is only valid on the common path, while the public API contract consumes that state immediately after a feature flag changes. The failure becomes observable in the collaboration software workflow becau... | {
"initial_assessment": "This is primarily a `Problem Understanding` task. The agent should first establish whether `conflicting requirements` is a symptom, a root cause, or an underspecified request.",
"assumptions": [
"The issue is limited to the path connecting the serializer and public API contract; this re... | [
{
"type": "premature_patch",
"response": "Immediately rewrite the public API contract and update every caller without inspecting the repository.",
"why_wrong": "It treats a hypothesis as fact, expands blast radius, and skips evidence and compatibility checks."
},
{
"type": "hallucinated_evidence... | {
"must_do": [
"Distinguish verified evidence from assumptions.",
"Inspect or reason about the relationship between `src/http/routes.cpp` and `src/core/workflow.cpp`.",
"Respect all stated constraints.",
"Define a failure-focused verification step.",
"Keep the proposed change bounded and reversibl... | [
{
"role": "system",
"content": "You are a software-engineering agent. Ground conclusions in available evidence, use tools deliberately, preserve safety and contracts, and never claim unobserved results."
},
{
"role": "user",
"content": "The team needs a grounded investigation because a proposed ... | {
"validation_status": "machine_validated",
"heuristic_score": 95,
"structural_fingerprint": "bdf3e06afacda9bd719e641526d5f2aa91d0fe18012f85cb538bbbd6f82038bf",
"user_request_hash": "d8de6c2c0e7fdfe31159779b1b86962324a639924df909f1bdfcc69da8fb1047",
"record_hash": "9aef9cefb36d6484792559239cd993e280648439949f... |
JF-ASE-002-08 | 1.0.0 | train | {
"family": "problem_understanding",
"family_label": "Problem Understanding",
"archetype": "conflicting_requirements",
"difficulty": "easy",
"behavior_targets": [
"intent_modeling",
"scope_control",
"assumption_tracking",
"acceptance_criteria"
]
} | {
"language": "Python",
"framework": "FastAPI",
"test_tool": "pytest",
"build_tool": "uv"
} | {
"name": "bridge-analytics-platform",
"domain": "analytics",
"architecture": "batch processing system",
"summary": "A analytics repository organized as a batch processing system.",
"file_tree": [
"app/api/routes.py",
"app/services/core.py",
"app/repositories/store.py",
"app/workers/events.py"... | {
"user_request": "A customer-facing workflow intermittently exhibits this behavior: evidence from the migration runner conflicts with assumptions made by the schema registry, producing conflicting requirements during a partial network failure. Work in `bridge-analytics-platform`, a batch processing system implemente... | {
"core_issue": "The core issue is conflicting requirements: the migration runner establishes state using a condition that is only valid on the common path, while the schema registry consumes that state during a partial network failure. The failure becomes observable in the analytics workflow because the two componen... | {
"initial_assessment": "This is primarily a `Problem Understanding` task. The agent should first establish whether `conflicting requirements` is a symptom, a root cause, or an underspecified request.",
"assumptions": [
"The issue is limited to the path connecting the migration runner and schema registry; this ... | [
{
"type": "premature_patch",
"response": "Immediately rewrite the schema registry and update every caller without inspecting the repository.",
"why_wrong": "It treats a hypothesis as fact, expands blast radius, and skips evidence and compatibility checks."
},
{
"type": "hallucinated_evidence",
... | {
"must_do": [
"Distinguish verified evidence from assumptions.",
"Inspect or reason about the relationship between `app/services/core.py` and `app/repositories/store.py`.",
"Respect all stated constraints.",
"Define a failure-focused verification step.",
"Keep the proposed change bounded and reve... | [
{
"role": "system",
"content": "You are a software-engineering agent. Ground conclusions in available evidence, use tools deliberately, preserve safety and contracts, and never claim unobserved results."
},
{
"role": "user",
"content": "A customer-facing workflow intermittently exhibits this beh... | {
"validation_status": "machine_validated",
"heuristic_score": 96,
"structural_fingerprint": "3a0ce34d900df95e69f73ea6b71c30f0ad29616f7dd154e57fb43d2cac37f270",
"user_request_hash": "f157fe7c9baaf8c60295f3d3d9ae5579097cd12d143aa03553d78fe4ce93b4e7",
"record_hash": "694b0ed0b7144fcf13a1fa6a8a013e0bc562e7c6a91b... |
JF-ASE-002-09 | 1.0.0 | train | {
"family": "problem_understanding",
"family_label": "Problem Understanding",
"archetype": "conflicting_requirements",
"difficulty": "medium",
"behavior_targets": [
"intent_modeling",
"scope_control",
"assumption_tracking",
"acceptance_criteria"
]
} | {
"language": "Python",
"framework": "Django",
"test_tool": "pytest-django",
"build_tool": "pip"
} | {
"name": "vault-education-technology-platform",
"domain": "education technology",
"architecture": "plugin-oriented application",
"summary": "A education technology repository organized as a plugin-oriented application.",
"file_tree": [
"project/urls.py",
"app/views.py",
"app/services.py",
"ap... | {
"user_request": "During validation, the system revealed that evidence from the feature-flag client conflicts with assumptions made by the configuration service, producing conflicting requirements after switching tenants in the same browser session. Work in `vault-education-technology-platform`, a plugin-oriented ap... | {
"core_issue": "The core issue is conflicting requirements: the feature-flag client establishes state using a condition that is only valid on the common path, while the configuration service consumes that state after switching tenants in the same browser session. The failure becomes observable in the education techn... | {
"initial_assessment": "This is primarily a `Problem Understanding` task. The agent should first establish whether `conflicting requirements` is a symptom, a root cause, or an underspecified request.",
"assumptions": [
"The issue is limited to the path connecting the feature-flag client and configuration servi... | [
{
"type": "premature_patch",
"response": "Immediately rewrite the configuration service and update every caller without inspecting the repository.",
"why_wrong": "It treats a hypothesis as fact, expands blast radius, and skips evidence and compatibility checks."
},
{
"type": "hallucinated_eviden... | {
"must_do": [
"Distinguish verified evidence from assumptions.",
"Inspect or reason about the relationship between `app/services.py` and `app/models.py`.",
"Respect all stated constraints.",
"Define a failure-focused verification step.",
"Keep the proposed change bounded and reversible."
],
"... | [
{
"role": "system",
"content": "You are a software-engineering agent. Ground conclusions in available evidence, use tools deliberately, preserve safety and contracts, and never claim unobserved results."
},
{
"role": "user",
"content": "During validation, the system revealed that evidence from t... | {
"validation_status": "machine_validated",
"heuristic_score": 97,
"structural_fingerprint": "5d1e6c254b5e2e36936d32e29f252829ad332eb84f04c90ae2def06db33e19fc",
"user_request_hash": "eaec6aa30060919dede35638d89d82361b03f00eb9c1e08eae328f6cbc516098",
"record_hash": "6444b67ea8bb6adc09fc8e09a78ffe2c5e1610dc892a... |
JF-ASE-002-10 | 1.0.0 | train | {
"family": "problem_understanding",
"family_label": "Problem Understanding",
"archetype": "conflicting_requirements",
"difficulty": "hard",
"behavior_targets": [
"intent_modeling",
"scope_control",
"assumption_tracking",
"acceptance_criteria"
]
} | {
"language": "TypeScript",
"framework": "Node.js",
"test_tool": "Vitest",
"build_tool": "pnpm"
} | {
"name": "stream-media-processing-platform",
"domain": "media processing",
"architecture": "modular monolith",
"summary": "A media processing repository organized as a modular monolith.",
"file_tree": [
"src/http/routes.ts",
"src/services/core.ts",
"src/data/repository.ts",
"src/workers/consu... | {
"user_request": "A maintenance task became unsafe after reviewers noticed evidence from the authorization policy conflicts with assumptions made by the resource loader, producing conflicting requirements following a dependency upgrade. Work in `stream-media-processing-platform`, a modular monolith implemented with ... | {
"core_issue": "The core issue is conflicting requirements: the authorization policy establishes state using a condition that is only valid on the common path, while the resource loader consumes that state following a dependency upgrade. The failure becomes observable in the media processing workflow because the two... | {
"initial_assessment": "This is primarily a `Problem Understanding` task. The agent should first establish whether `conflicting requirements` is a symptom, a root cause, or an underspecified request.",
"assumptions": [
"The issue is limited to the path connecting the authorization policy and resource loader; t... | [
{
"type": "premature_patch",
"response": "Immediately rewrite the resource loader and update every caller without inspecting the repository.",
"why_wrong": "It treats a hypothesis as fact, expands blast radius, and skips evidence and compatibility checks."
},
{
"type": "hallucinated_evidence",
... | {
"must_do": [
"Distinguish verified evidence from assumptions.",
"Inspect or reason about the relationship between `src/workers/consumer.ts` and `src/security/policy.ts`.",
"Respect all stated constraints.",
"Define a failure-focused verification step.",
"Keep the proposed change bounded and reve... | [
{
"role": "system",
"content": "You are a software-engineering agent. Ground conclusions in available evidence, use tools deliberately, preserve safety and contracts, and never claim unobserved results."
},
{
"role": "user",
"content": "A maintenance task became unsafe after reviewers noticed ev... | {
"validation_status": "machine_validated",
"heuristic_score": 98,
"structural_fingerprint": "55b2ac42b6130fb62f8aff066590903a236eb618114b066764f5dee171e70b6b",
"user_request_hash": "a1a7f01e94dcfaac9866ec3333a6db6005eb19e52a4beb9d811a6dd9a76529ab",
"record_hash": "9b8e3357eec73198bf408b1dc160495ca0c8b5121ecb... |
JF-ASE-002-11 | 1.0.0 | train | {
"family": "problem_understanding",
"family_label": "Problem Understanding",
"archetype": "conflicting_requirements",
"difficulty": "expert",
"behavior_targets": [
"intent_modeling",
"scope_control",
"assumption_tracking",
"acceptance_criteria"
]
} | {
"language": "TypeScript",
"framework": "React",
"test_tool": "Playwright",
"build_tool": "Vite"
} | {
"name": "pilot-cloud-infrastructure-platform",
"domain": "cloud infrastructure",
"architecture": "event-driven services",
"summary": "A cloud infrastructure repository organized as a event-driven services.",
"file_tree": [
"src/app/router.tsx",
"src/features/state.ts",
"src/api/client.ts",
"... | {
"user_request": "The repository owner asks for help with a case where the team cannot safely complete the cloud infrastructure change because conflicting requirements remains unresolved near the end of a paginated result set. Work in `pilot-cloud-infrastructure-platform`, a event-driven services implemented with Ty... | {
"core_issue": "The core issue is conflicting requirements: the message producer establishes state using a condition that is only valid on the common path, while the idempotency store consumes that state near the end of a paginated result set. The failure becomes observable in the cloud infrastructure workflow becau... | {
"initial_assessment": "This is primarily a `Problem Understanding` task. The agent should first establish whether `conflicting requirements` is a symptom, a root cause, or an underspecified request.",
"assumptions": [
"The issue is limited to the path connecting the message producer and idempotency store; thi... | [
{
"type": "premature_patch",
"response": "Immediately rewrite the idempotency store and update every caller without inspecting the repository.",
"why_wrong": "It treats a hypothesis as fact, expands blast radius, and skips evidence and compatibility checks."
},
{
"type": "hallucinated_evidence",... | {
"must_do": [
"Distinguish verified evidence from assumptions.",
"Inspect or reason about the relationship between `src/auth/session.ts` and `tests/workflow.spec.ts`.",
"Respect all stated constraints.",
"Define a failure-focused verification step.",
"Keep the proposed change bounded and reversib... | [
{
"role": "system",
"content": "You are a software-engineering agent. Ground conclusions in available evidence, use tools deliberately, preserve safety and contracts, and never claim unobserved results."
},
{
"role": "user",
"content": "The repository owner asks for help with a case where the te... | {
"validation_status": "machine_validated",
"heuristic_score": 88,
"structural_fingerprint": "0ae8cc2eb8a772785acdc955ea86d9eb297d0e33ebdbe8090021c820d8a4bafb",
"user_request_hash": "9e22400bef70b48b503c497f2be768da8804c275e61d550c2c8b7bf2546ebf09",
"record_hash": "31a0d2eecc6e1cc06e4b19a1f7a2e2c2e781ca1ca356... |
JF-ASE-002-12 | 1.0.0 | train | {
"family": "problem_understanding",
"family_label": "Problem Understanding",
"archetype": "conflicting_requirements",
"difficulty": "easy",
"behavior_targets": [
"intent_modeling",
"scope_control",
"assumption_tracking",
"acceptance_criteria"
]
} | {
"language": "Java",
"framework": "Spring Boot",
"test_tool": "JUnit",
"build_tool": "Gradle"
} | {
"name": "mesh-customer-support-platform",
"domain": "customer support",
"architecture": "service-repository application",
"summary": "A customer support repository organized as a service-repository application.",
"file_tree": [
"src/main/java/app/Controller.java",
"src/main/java/app/Service.java",
... | {
"user_request": "A rollout checkpoint failed because the customer support system behaves correctly in the common path but exposes conflicting requirements when the payload contains an empty optional field. Work in `mesh-customer-support-platform`, a service-repository application implemented with Java and Spring Bo... | {
"core_issue": "The core issue is conflicting requirements: the upload controller establishes state using a condition that is only valid on the common path, while the object storage adapter consumes that state when the payload contains an empty optional field. The failure becomes observable in the customer support w... | {
"initial_assessment": "This is primarily a `Problem Understanding` task. The agent should first establish whether `conflicting requirements` is a symptom, a root cause, or an underspecified request.",
"assumptions": [
"The issue is limited to the path connecting the upload controller and object storage adapte... | [
{
"type": "premature_patch",
"response": "Immediately rewrite the object storage adapter and update every caller without inspecting the repository.",
"why_wrong": "It treats a hypothesis as fact, expands blast radius, and skips evidence and compatibility checks."
},
{
"type": "hallucinated_evide... | {
"must_do": [
"Distinguish verified evidence from assumptions.",
"Inspect or reason about the relationship between `src/test/java/app/WorkflowTest.java` and `src/main/java/app/Controller.java`.",
"Respect all stated constraints.",
"Define a failure-focused verification step.",
"Keep the proposed ... | [
{
"role": "system",
"content": "You are a software-engineering agent. Ground conclusions in available evidence, use tools deliberately, preserve safety and contracts, and never claim unobserved results."
},
{
"role": "user",
"content": "A rollout checkpoint failed because the customer support sy... | {
"validation_status": "machine_validated",
"heuristic_score": 89,
"structural_fingerprint": "c5dbed6e96e1c22efd3904b41bf6d4068745545314d3b977398a67712141ea75",
"user_request_hash": "8d5ff1b8c7358a62a1062cf4e425da3e1c65d006011a9459d78e0b7a304c27dc",
"record_hash": "09bf139eec46dd44ed5c8f2ce5b1d0e752984c8b8299... |
JF-ASE-002-13 | 1.0.0 | train | {
"family": "problem_understanding",
"family_label": "Problem Understanding",
"archetype": "conflicting_requirements",
"difficulty": "medium",
"behavior_targets": [
"intent_modeling",
"scope_control",
"assumption_tracking",
"acceptance_criteria"
]
} | {
"language": "Go",
"framework": "Chi",
"test_tool": "go test",
"build_tool": "Go modules"
} | {
"name": "beacon-document-management-platform",
"domain": "document management",
"architecture": "microservice platform",
"summary": "A document management repository organized as a microservice platform.",
"file_tree": [
"internal/http/routes.go",
"internal/service/core.go",
"internal/store/repo... | {
"user_request": "An incident follow-up points to a scenario in which a proposed fix for conflicting requirements would broaden scope without first explaining why the failure occurs after a worker restarts. Work in `beacon-document-management-platform`, a microservice platform implemented with Go and Chi. Focus on t... | {
"core_issue": "The core issue is conflicting requirements: the webhook receiver establishes state using a condition that is only valid on the common path, while the retry coordinator consumes that state after a worker restarts. The failure becomes observable in the document management workflow because the two compo... | {
"initial_assessment": "This is primarily a `Problem Understanding` task. The agent should first establish whether `conflicting requirements` is a symptom, a root cause, or an underspecified request.",
"assumptions": [
"The issue is limited to the path connecting the webhook receiver and retry coordinator; thi... | [
{
"type": "premature_patch",
"response": "Immediately rewrite the retry coordinator and update every caller without inspecting the repository.",
"why_wrong": "It treats a hypothesis as fact, expands blast radius, and skips evidence and compatibility checks."
},
{
"type": "hallucinated_evidence",... | {
"must_do": [
"Distinguish verified evidence from assumptions.",
"Inspect or reason about the relationship between `internal/http/routes.go` and `internal/service/core.go`.",
"Respect all stated constraints.",
"Define a failure-focused verification step.",
"Keep the proposed change bounded and re... | [
{
"role": "system",
"content": "You are a software-engineering agent. Ground conclusions in available evidence, use tools deliberately, preserve safety and contracts, and never claim unobserved results."
},
{
"role": "user",
"content": "An incident follow-up points to a scenario in which a propo... | {
"validation_status": "machine_validated",
"heuristic_score": 90,
"structural_fingerprint": "3ce85cf55fb4cb8772c610c211b4baacfebf9d3310df9a16f952d382cf361720",
"user_request_hash": "5c1fd85f8ae739b474d51a0139ded83a7d707227ac5ab8df240f294a4b14f2e6",
"record_hash": "9a98cd86fb8cdf212c68773ed6253bad4956a319f49d... |
JF-ASE-002-14 | 1.0.0 | train | {
"family": "problem_understanding",
"family_label": "Problem Understanding",
"archetype": "conflicting_requirements",
"difficulty": "hard",
"behavior_targets": [
"intent_modeling",
"scope_control",
"assumption_tracking",
"acceptance_criteria"
]
} | {
"language": "C#",
"framework": "ASP.NET Core",
"test_tool": "xUnit",
"build_tool": "dotnet"
} | {
"name": "kernel-iot-operations-platform",
"domain": "IoT operations",
"architecture": "serverless workflow",
"summary": "A IoT operations repository organized as a serverless workflow.",
"file_tree": [
"Api/Controllers/WorkflowController.cs",
"Core/WorkflowService.cs",
"Data/WorkflowRepository.c... | {
"user_request": "A pre-release audit found that evidence from the query builder conflicts with assumptions made by the pagination layer, producing conflicting requirements while the queue is under backpressure. Work in `kernel-iot-operations-platform`, a serverless workflow implemented with C# and ASP.NET Core. Foc... | {
"core_issue": "The core issue is conflicting requirements: the query builder establishes state using a condition that is only valid on the common path, while the pagination layer consumes that state while the queue is under backpressure. The failure becomes observable in the IoT operations workflow because the two ... | {
"initial_assessment": "This is primarily a `Problem Understanding` task. The agent should first establish whether `conflicting requirements` is a symptom, a root cause, or an underspecified request.",
"assumptions": [
"The issue is limited to the path connecting the query builder and pagination layer; this re... | [
{
"type": "premature_patch",
"response": "Immediately rewrite the pagination layer and update every caller without inspecting the repository.",
"why_wrong": "It treats a hypothesis as fact, expands blast radius, and skips evidence and compatibility checks."
},
{
"type": "hallucinated_evidence",
... | {
"must_do": [
"Distinguish verified evidence from assumptions.",
"Inspect or reason about the relationship between `Core/WorkflowService.cs` and `Data/WorkflowRepository.cs`.",
"Respect all stated constraints.",
"Define a failure-focused verification step.",
"Keep the proposed change bounded and ... | [
{
"role": "system",
"content": "You are a software-engineering agent. Ground conclusions in available evidence, use tools deliberately, preserve safety and contracts, and never claim unobserved results."
},
{
"role": "user",
"content": "A pre-release audit found that evidence from the query buil... | {
"validation_status": "machine_validated",
"heuristic_score": 91,
"structural_fingerprint": "593288abce0939bfee50129a93e6d5e162be04c8c16bb1ea1a375e777e48673b",
"user_request_hash": "be053d916b5b18fc8ea1f5476f2548cfed1b3c7355cd99b9f745f0c54eea5fb3",
"record_hash": "2707d38da31aebb4407ffdeac6730e53d02dcada9757... |
JF-ASE-002-15 | 1.0.0 | train | {
"family": "problem_understanding",
"family_label": "Problem Understanding",
"archetype": "conflicting_requirements",
"difficulty": "expert",
"behavior_targets": [
"intent_modeling",
"scope_control",
"assumption_tracking",
"acceptance_criteria"
]
} | {
"language": "PHP",
"framework": "Laravel",
"test_tool": "PHPUnit",
"build_tool": "Composer"
} | {
"name": "canvas-financial-reporting-platform",
"domain": "financial reporting",
"architecture": "worker-based pipeline",
"summary": "A financial reporting repository organized as a worker-based pipeline.",
"file_tree": [
"routes/api.php",
"app/Http/Controllers/WorkflowController.php",
"app/Servi... | {
"user_request": "A regression report describes the following condition: a proposed fix for conflicting requirements would broaden scope without first explaining why the failure occurs during an idempotent event replay. Work in `canvas-financial-reporting-platform`, a worker-based pipeline implemented with PHP and L... | {
"core_issue": "The core issue is conflicting requirements: the CLI command establishes state using a condition that is only valid on the common path, while the process runner consumes that state during an idempotent event replay. The failure becomes observable in the financial reporting workflow because the two com... | {
"initial_assessment": "This is primarily a `Problem Understanding` task. The agent should first establish whether `conflicting requirements` is a symptom, a root cause, or an underspecified request.",
"assumptions": [
"The issue is limited to the path connecting the CLI command and process runner; this remain... | [
{
"type": "premature_patch",
"response": "Immediately rewrite the process runner and update every caller without inspecting the repository.",
"why_wrong": "It treats a hypothesis as fact, expands blast radius, and skips evidence and compatibility checks."
},
{
"type": "hallucinated_evidence",
... | {
"must_do": [
"Distinguish verified evidence from assumptions.",
"Inspect or reason about the relationship between `app/Services/WorkflowService.php` and `app/Repositories/WorkflowRepository.php`.",
"Respect all stated constraints.",
"Define a failure-focused verification step.",
"Keep the propos... | [
{
"role": "system",
"content": "You are a software-engineering agent. Ground conclusions in available evidence, use tools deliberately, preserve safety and contracts, and never claim unobserved results."
},
{
"role": "user",
"content": "A regression report describes the following condition: a pr... | {
"validation_status": "machine_validated",
"heuristic_score": 92,
"structural_fingerprint": "fe04271d413d566efeee8514cdbffcfdbddf702952286118a2404471b300f7d1",
"user_request_hash": "beb680f9e9a06a3cbe06742b444d7137ec4d03812f4577afdee3ab8a5ece40f8",
"record_hash": "88ef3b647c3464b204ee32de01040605c9ea470d9804... |
JF-ASE-002-16 | 1.0.0 | train | {
"family": "problem_understanding",
"family_label": "Problem Understanding",
"archetype": "conflicting_requirements",
"difficulty": "easy",
"behavior_targets": [
"intent_modeling",
"scope_control",
"assumption_tracking",
"acceptance_criteria"
]
} | {
"language": "Rust",
"framework": "Axum",
"test_tool": "cargo test",
"build_tool": "Cargo"
} | {
"name": "pulse-search-infrastructure-platform",
"domain": "search infrastructure",
"architecture": "multi-tenant SaaS",
"summary": "A search infrastructure repository organized as a multi-tenant SaaS.",
"file_tree": [
"src/http/routes.rs",
"src/services/core.rs",
"src/store/repository.rs",
"... | {
"user_request": "The current implementation is uncertain because conflicting requirements appears in the search infrastructure workflow when application nodes have mild clock skew, and the relationship between the frontend state store and API client is not yet proven. Work in `pulse-search-infrastructure-platform`,... | {
"core_issue": "The core issue is conflicting requirements: the frontend state store establishes state using a condition that is only valid on the common path, while the API client consumes that state when application nodes have mild clock skew. The failure becomes observable in the search infrastructure workflow be... | {
"initial_assessment": "This is primarily a `Problem Understanding` task. The agent should first establish whether `conflicting requirements` is a symptom, a root cause, or an underspecified request.",
"assumptions": [
"The issue is limited to the path connecting the frontend state store and API client; this r... | [
{
"type": "premature_patch",
"response": "Immediately rewrite the API client and update every caller without inspecting the repository.",
"why_wrong": "It treats a hypothesis as fact, expands blast radius, and skips evidence and compatibility checks."
},
{
"type": "hallucinated_evidence",
"r... | {
"must_do": [
"Distinguish verified evidence from assumptions.",
"Inspect or reason about the relationship between `src/workers/consumer.rs` and `src/security/policy.rs`.",
"Respect all stated constraints.",
"Define a failure-focused verification step.",
"Keep the proposed change bounded and reve... | [
{
"role": "system",
"content": "You are a software-engineering agent. Ground conclusions in available evidence, use tools deliberately, preserve safety and contracts, and never claim unobserved results."
},
{
"role": "user",
"content": "The current implementation is uncertain because conflicting... | {
"validation_status": "machine_validated",
"heuristic_score": 93,
"structural_fingerprint": "1ef6ece52451c423ffa58cc258c3082b29f175ac5819fcf103068f1f85cc80c3",
"user_request_hash": "65c62357f9a5263445d811e7d7fae44b0982f175ae2699dbbb580976a337c8e5",
"record_hash": "872b268abb6ef715537cf3f656cee092b7883be9cded... |
JF-ASE-002-17 | 1.0.0 | train | {
"family": "problem_understanding",
"family_label": "Problem Understanding",
"archetype": "conflicting_requirements",
"difficulty": "medium",
"behavior_targets": [
"intent_modeling",
"scope_control",
"assumption_tracking",
"acceptance_criteria"
]
} | {
"language": "Kotlin",
"framework": "Ktor",
"test_tool": "Kotest",
"build_tool": "Gradle"
} | {
"name": "matrix-content-moderation-platform",
"domain": "content moderation",
"architecture": "API gateway architecture",
"summary": "A content moderation repository organized as a API gateway architecture.",
"file_tree": [
"src/main/kotlin/app/Routes.kt",
"src/main/kotlin/app/Service.kt",
"src/... | {
"user_request": "A teammate proposed a quick fix, but the evidence only proves that evidence from the metrics exporter conflicts with assumptions made by the runtime instrumentation, producing conflicting requirements after a zero-downtime schema migration. Work in `matrix-content-moderation-platform`, a API gatewa... | {
"core_issue": "The core issue is conflicting requirements: the metrics exporter establishes state using a condition that is only valid on the common path, while the runtime instrumentation consumes that state after a zero-downtime schema migration. The failure becomes observable in the content moderation workflow b... | {
"initial_assessment": "This is primarily a `Problem Understanding` task. The agent should first establish whether `conflicting requirements` is a symptom, a root cause, or an underspecified request.",
"assumptions": [
"The issue is limited to the path connecting the metrics exporter and runtime instrumentatio... | [
{
"type": "premature_patch",
"response": "Immediately rewrite the runtime instrumentation and update every caller without inspecting the repository.",
"why_wrong": "It treats a hypothesis as fact, expands blast radius, and skips evidence and compatibility checks."
},
{
"type": "hallucinated_evid... | {
"must_do": [
"Distinguish verified evidence from assumptions.",
"Inspect or reason about the relationship between `src/main/kotlin/app/Security.kt` and `src/test/kotlin/app/WorkflowSpec.kt`.",
"Respect all stated constraints.",
"Define a failure-focused verification step.",
"Keep the proposed ch... | [
{
"role": "system",
"content": "You are a software-engineering agent. Ground conclusions in available evidence, use tools deliberately, preserve safety and contracts, and never claim unobserved results."
},
{
"role": "user",
"content": "A teammate proposed a quick fix, but the evidence only prov... | {
"validation_status": "machine_validated",
"heuristic_score": 94,
"structural_fingerprint": "6f5c8d3fe070e11cf1b17b288bb11bd947d7d4f08c5d22fab6e3ce9080ec4c8e",
"user_request_hash": "d11b193c0b753ea0b6755c722c93b030a09f23822b7a348d856d5b531b5cb269",
"record_hash": "61d4588bc50dd2b9d80b62b5c2f5bb284ba3a6ae91bd... |
JF-ASE-002-18 | 1.0.0 | train | {
"family": "problem_understanding",
"family_label": "Problem Understanding",
"archetype": "conflicting_requirements",
"difficulty": "hard",
"behavior_targets": [
"intent_modeling",
"scope_control",
"assumption_tracking",
"acceptance_criteria"
]
} | {
"language": "Ruby",
"framework": "Rails",
"test_tool": "RSpec",
"build_tool": "Bundler"
} | {
"name": "anchor-hr-systems-platform",
"domain": "HR systems",
"architecture": "batch processing system",
"summary": "A HR systems repository organized as a batch processing system.",
"file_tree": [
"config/routes.rb",
"app/controllers/workflows_controller.rb",
"app/services/workflow_service.rb",... | {
"user_request": "A multi-step change is blocked by the fact that evidence from the dependency resolver conflicts with assumptions made by the build pipeline, producing conflicting requirements while old and new application versions coexist. Work in `anchor-hr-systems-platform`, a batch processing system implemented... | {
"core_issue": "The core issue is conflicting requirements: the dependency resolver establishes state using a condition that is only valid on the common path, while the build pipeline consumes that state while old and new application versions coexist. The failure becomes observable in the HR systems workflow because... | {
"initial_assessment": "This is primarily a `Problem Understanding` task. The agent should first establish whether `conflicting requirements` is a symptom, a root cause, or an underspecified request.",
"assumptions": [
"The issue is limited to the path connecting the dependency resolver and build pipeline; thi... | [
{
"type": "premature_patch",
"response": "Immediately rewrite the build pipeline and update every caller without inspecting the repository.",
"why_wrong": "It treats a hypothesis as fact, expands blast radius, and skips evidence and compatibility checks."
},
{
"type": "hallucinated_evidence",
... | {
"must_do": [
"Distinguish verified evidence from assumptions.",
"Inspect or reason about the relationship between `spec/requests/workflows_spec.rb` and `config/routes.rb`.",
"Respect all stated constraints.",
"Define a failure-focused verification step.",
"Keep the proposed change bounded and re... | [
{
"role": "system",
"content": "You are a software-engineering agent. Ground conclusions in available evidence, use tools deliberately, preserve safety and contracts, and never claim unobserved results."
},
{
"role": "user",
"content": "A multi-step change is blocked by the fact that evidence fr... | {
"validation_status": "machine_validated",
"heuristic_score": 95,
"structural_fingerprint": "dc5dc3a2d767ab032199feec405d6d4eef48ca16ee65cc044e70ede3c52041e8",
"user_request_hash": "77071bd349511d609111c9021095245d75c27b2cd74423a846a326f771c744af",
"record_hash": "d872ccd66a9728174e06f53125ca34d8e65c834b1ade... |
JF-ASE-002-19 | 1.0.0 | train | {
"family": "problem_understanding",
"family_label": "Problem Understanding",
"archetype": "conflicting_requirements",
"difficulty": "expert",
"behavior_targets": [
"intent_modeling",
"scope_control",
"assumption_tracking",
"acceptance_criteria"
]
} | {
"language": "C++",
"framework": "CMake service",
"test_tool": "Catch2",
"build_tool": "CMake"
} | {
"name": "prism-subscription-billing-platform",
"domain": "subscription billing",
"architecture": "plugin-oriented application",
"summary": "A subscription billing repository organized as a plugin-oriented application.",
"file_tree": [
"src/http/routes.cpp",
"src/core/workflow.cpp",
"src/data/rep... | {
"user_request": "A test environment and production-like environment disagree: conflicting requirements appears in the subscription billing workflow when a fallback code path executes, and the relationship between the tenant resolver and cache key builder is not yet proven. Work in `prism-subscription-billing-platfo... | {
"core_issue": "The core issue is conflicting requirements: the tenant resolver establishes state using a condition that is only valid on the common path, while the cache key builder consumes that state when a fallback code path executes. The failure becomes observable in the subscription billing workflow because th... | {
"initial_assessment": "This is primarily a `Problem Understanding` task. The agent should first establish whether `conflicting requirements` is a symptom, a root cause, or an underspecified request.",
"assumptions": [
"The issue is limited to the path connecting the tenant resolver and cache key builder; this... | [
{
"type": "premature_patch",
"response": "Immediately rewrite the cache key builder and update every caller without inspecting the repository.",
"why_wrong": "It treats a hypothesis as fact, expands blast radius, and skips evidence and compatibility checks."
},
{
"type": "hallucinated_evidence",... | {
"must_do": [
"Distinguish verified evidence from assumptions.",
"Inspect or reason about the relationship between `src/http/routes.cpp` and `src/core/workflow.cpp`.",
"Respect all stated constraints.",
"Define a failure-focused verification step.",
"Keep the proposed change bounded and reversibl... | [
{
"role": "system",
"content": "You are a software-engineering agent. Ground conclusions in available evidence, use tools deliberately, preserve safety and contracts, and never claim unobserved results."
},
{
"role": "user",
"content": "A test environment and production-like environment disagree... | {
"validation_status": "machine_validated",
"heuristic_score": 96,
"structural_fingerprint": "b8de20177aefa5b934d12d5ff55231b74f7999cbeb9ac621aa16b271fca52435",
"user_request_hash": "19501bc9e1179ee62932fd53082f688ee586fc6551c4d5146548778545ef2d38",
"record_hash": "4609613e054a7d6f7386f94ab75ad8b785c7a73d11c6... |
JF-ASE-002-20 | 1.0.0 | train | {
"family": "problem_understanding",
"family_label": "Problem Understanding",
"archetype": "conflicting_requirements",
"difficulty": "easy",
"behavior_targets": [
"intent_modeling",
"scope_control",
"assumption_tracking",
"acceptance_criteria"
]
} | {
"language": "Python",
"framework": "FastAPI",
"test_tool": "pytest",
"build_tool": "uv"
} | {
"name": "switch-inventory-platform",
"domain": "inventory",
"architecture": "modular monolith",
"summary": "A inventory repository organized as a modular monolith.",
"file_tree": [
"app/api/routes.py",
"app/services/core.py",
"app/repositories/store.py",
"app/workers/events.py",
"app/sec... | {
"user_request": "A repository handoff highlights one unresolved behavior: the inventory system behaves correctly in the common path but exposes conflicting requirements during cooperative cancellation. Work in `switch-inventory-platform`, a modular monolith implemented with Python and FastAPI. Focus on the agent be... | {
"core_issue": "The core issue is conflicting requirements: the audit logger establishes state using a condition that is only valid on the common path, while the transaction manager consumes that state during cooperative cancellation. The failure becomes observable in the inventory workflow because the two component... | {
"initial_assessment": "This is primarily a `Problem Understanding` task. The agent should first establish whether `conflicting requirements` is a symptom, a root cause, or an underspecified request.",
"assumptions": [
"The issue is limited to the path connecting the audit logger and transaction manager; this ... | [
{
"type": "premature_patch",
"response": "Immediately rewrite the transaction manager and update every caller without inspecting the repository.",
"why_wrong": "It treats a hypothesis as fact, expands blast radius, and skips evidence and compatibility checks."
},
{
"type": "hallucinated_evidence... | {
"must_do": [
"Distinguish verified evidence from assumptions.",
"Inspect or reason about the relationship between `app/services/core.py` and `app/repositories/store.py`.",
"Respect all stated constraints.",
"Define a failure-focused verification step.",
"Keep the proposed change bounded and reve... | [
{
"role": "system",
"content": "You are a software-engineering agent. Ground conclusions in available evidence, use tools deliberately, preserve safety and contracts, and never claim unobserved results."
},
{
"role": "user",
"content": "A repository handoff highlights one unresolved behavior: th... | {
"validation_status": "machine_validated",
"heuristic_score": 97,
"structural_fingerprint": "66eb7af669d0928b451b182ad182c07cb3215d7a1a16d6885f22cfbd621135c4",
"user_request_hash": "9ef1dc5beff7820091faeed52330b355a65779f01099d33a1259e2a9c90c7c31",
"record_hash": "71a7df6bb71cbfe8b11997af4bb99b47696428b31273... |
JF-ASE-002-21 | 1.0.0 | train | {
"family": "problem_understanding",
"family_label": "Problem Understanding",
"archetype": "conflicting_requirements",
"difficulty": "medium",
"behavior_targets": [
"intent_modeling",
"scope_control",
"assumption_tracking",
"acceptance_criteria"
]
} | {
"language": "Python",
"framework": "Django",
"test_tool": "pytest-django",
"build_tool": "pip"
} | {
"name": "trail-observability-platform",
"domain": "observability",
"architecture": "event-driven services",
"summary": "A observability repository organized as a event-driven services.",
"file_tree": [
"project/urls.py",
"app/views.py",
"app/services.py",
"app/models.py",
"app/middleware... | {
"user_request": "A reliability review asks the agent to address a case where the observability system behaves correctly in the common path but exposes conflicting requirements after a duplicate event delivery. Work in `trail-observability-platform`, a event-driven services implemented with Python and Django. Focus ... | {
"core_issue": "The core issue is conflicting requirements: the notification dispatcher establishes state using a condition that is only valid on the common path, while the template renderer consumes that state after a duplicate event delivery. The failure becomes observable in the observability workflow because the... | {
"initial_assessment": "This is primarily a `Problem Understanding` task. The agent should first establish whether `conflicting requirements` is a symptom, a root cause, or an underspecified request.",
"assumptions": [
"The issue is limited to the path connecting the notification dispatcher and template render... | [
{
"type": "premature_patch",
"response": "Immediately rewrite the template renderer and update every caller without inspecting the repository.",
"why_wrong": "It treats a hypothesis as fact, expands blast radius, and skips evidence and compatibility checks."
},
{
"type": "hallucinated_evidence",... | {
"must_do": [
"Distinguish verified evidence from assumptions.",
"Inspect or reason about the relationship between `app/services.py` and `app/models.py`.",
"Respect all stated constraints.",
"Define a failure-focused verification step.",
"Keep the proposed change bounded and reversible."
],
"... | [
{
"role": "system",
"content": "You are a software-engineering agent. Ground conclusions in available evidence, use tools deliberately, preserve safety and contracts, and never claim unobserved results."
},
{
"role": "user",
"content": "A reliability review asks the agent to address a case where... | {
"validation_status": "machine_validated",
"heuristic_score": 98,
"structural_fingerprint": "13316e631a6edddb9a86f112922dce4aa9d52d9c760373578048779f12ec5a69",
"user_request_hash": "a1b00f5b6f863db6fcc4536ba644551540b9e6fef37e82f0de7d56193f3de002",
"record_hash": "25d399a738632bed6f5750940b001e03eacbfe04de3d... |
JF-ASE-002-22 | 1.0.0 | train | {
"family": "problem_understanding",
"family_label": "Problem Understanding",
"archetype": "conflicting_requirements",
"difficulty": "hard",
"behavior_targets": [
"intent_modeling",
"scope_control",
"assumption_tracking",
"acceptance_criteria"
]
} | {
"language": "TypeScript",
"framework": "Node.js",
"test_tool": "Vitest",
"build_tool": "pnpm"
} | {
"name": "vector-data-pipelines-platform",
"domain": "data pipelines",
"architecture": "service-repository application",
"summary": "A data pipelines repository organized as a service-repository application.",
"file_tree": [
"src/http/routes.ts",
"src/services/core.ts",
"src/data/repository.ts",
... | {
"user_request": "The task appears simple, yet the system context shows that the data pipelines system behaves correctly in the common path but exposes conflicting requirements with a stale session token. Work in `vector-data-pipelines-platform`, a service-repository application implemented with TypeScript and Node.... | {
"core_issue": "The core issue is conflicting requirements: the search indexer establishes state using a condition that is only valid on the common path, while the change-data-capture stream consumes that state with a stale session token. The failure becomes observable in the data pipelines workflow because the two ... | {
"initial_assessment": "This is primarily a `Problem Understanding` task. The agent should first establish whether `conflicting requirements` is a symptom, a root cause, or an underspecified request.",
"assumptions": [
"The issue is limited to the path connecting the search indexer and change-data-capture stre... | [
{
"type": "premature_patch",
"response": "Immediately rewrite the change-data-capture stream and update every caller without inspecting the repository.",
"why_wrong": "It treats a hypothesis as fact, expands blast radius, and skips evidence and compatibility checks."
},
{
"type": "hallucinated_e... | {
"must_do": [
"Distinguish verified evidence from assumptions.",
"Inspect or reason about the relationship between `src/workers/consumer.ts` and `src/security/policy.ts`.",
"Respect all stated constraints.",
"Define a failure-focused verification step.",
"Keep the proposed change bounded and reve... | [
{
"role": "system",
"content": "You are a software-engineering agent. Ground conclusions in available evidence, use tools deliberately, preserve safety and contracts, and never claim unobserved results."
},
{
"role": "user",
"content": "The task appears simple, yet the system context shows that ... | {
"validation_status": "machine_validated",
"heuristic_score": 88,
"structural_fingerprint": "42d04eb6b58038cdb8a04dd23a0301fc1ae5767cd1640c8e6e028c15956cd99e",
"user_request_hash": "fb00b0ebd370b5608da8ff7c41bcffff432b8de4e10179a994db8b7ce9f2cfe4",
"record_hash": "41d9acdfc0264c0012ab263b9dd4c507f41dc22b5410... |
JF-ASE-002-23 | 1.0.0 | train | {
"family": "problem_understanding",
"family_label": "Problem Understanding",
"archetype": "conflicting_requirements",
"difficulty": "expert",
"behavior_targets": [
"intent_modeling",
"scope_control",
"assumption_tracking",
"acceptance_criteria"
]
} | {
"language": "TypeScript",
"framework": "React",
"test_tool": "Playwright",
"build_tool": "Vite"
} | {
"name": "watch-feature-management-platform",
"domain": "feature management",
"architecture": "microservice platform",
"summary": "A feature management repository organized as a microservice platform.",
"file_tree": [
"src/app/router.tsx",
"src/features/state.ts",
"src/api/client.ts",
"src/co... | {
"user_request": "A recent refactor changed the conditions under which a proposed fix for conflicting requirements would broaden scope without first explaining why the failure occurs when configuration is hot-reloaded. Work in `watch-feature-management-platform`, a microservice platform implemented with TypeScript a... | {
"core_issue": "The core issue is conflicting requirements: the rate limiter establishes state using a condition that is only valid on the common path, while the distributed counter consumes that state when configuration is hot-reloaded. The failure becomes observable in the feature management workflow because the t... | {
"initial_assessment": "This is primarily a `Problem Understanding` task. The agent should first establish whether `conflicting requirements` is a symptom, a root cause, or an underspecified request.",
"assumptions": [
"The issue is limited to the path connecting the rate limiter and distributed counter; this ... | [
{
"type": "premature_patch",
"response": "Immediately rewrite the distributed counter and update every caller without inspecting the repository.",
"why_wrong": "It treats a hypothesis as fact, expands blast radius, and skips evidence and compatibility checks."
},
{
"type": "hallucinated_evidence... | {
"must_do": [
"Distinguish verified evidence from assumptions.",
"Inspect or reason about the relationship between `src/auth/session.ts` and `tests/workflow.spec.ts`.",
"Respect all stated constraints.",
"Define a failure-focused verification step.",
"Keep the proposed change bounded and reversib... | [
{
"role": "system",
"content": "You are a software-engineering agent. Ground conclusions in available evidence, use tools deliberately, preserve safety and contracts, and never claim unobserved results."
},
{
"role": "user",
"content": "A recent refactor changed the conditions under which a prop... | {
"validation_status": "machine_validated",
"heuristic_score": 89,
"structural_fingerprint": "15c6d06914601022a4e3b95a94ae68d2302b28f92ca77c2ece8138a92a623853",
"user_request_hash": "3a18c79af04ab6a94ce207847d29431de178961bc5c5ea2d85306fd7457ba543",
"record_hash": "168d169d8065f5d4c15f7b30430daa6f4b0ced07db8d... |
JF-ASE-002-24 | 1.0.0 | train | {
"family": "problem_understanding",
"family_label": "Problem Understanding",
"archetype": "conflicting_requirements",
"difficulty": "easy",
"behavior_targets": [
"intent_modeling",
"scope_control",
"assumption_tracking",
"acceptance_criteria"
]
} | {
"language": "Java",
"framework": "Spring Boot",
"test_tool": "JUnit",
"build_tool": "Gradle"
} | {
"name": "engine-cybersecurity-operations-platform",
"domain": "cybersecurity operations",
"architecture": "serverless workflow",
"summary": "A cybersecurity operations repository organized as a serverless workflow.",
"file_tree": [
"src/main/java/app/Controller.java",
"src/main/java/app/Service.java... | {
"user_request": "A security review requires careful handling because conflicting requirements appears in the cybersecurity operations workflow under high-cardinality traffic, and the relationship between the validation layer and normalization pipeline is not yet proven. Work in `engine-cybersecurity-operations-plat... | {
"core_issue": "The core issue is conflicting requirements: the validation layer establishes state using a condition that is only valid on the common path, while the normalization pipeline consumes that state under high-cardinality traffic. The failure becomes observable in the cybersecurity operations workflow beca... | {
"initial_assessment": "This is primarily a `Problem Understanding` task. The agent should first establish whether `conflicting requirements` is a symptom, a root cause, or an underspecified request.",
"assumptions": [
"The issue is limited to the path connecting the validation layer and normalization pipeline... | [
{
"type": "premature_patch",
"response": "Immediately rewrite the normalization pipeline and update every caller without inspecting the repository.",
"why_wrong": "It treats a hypothesis as fact, expands blast radius, and skips evidence and compatibility checks."
},
{
"type": "hallucinated_evide... | {
"must_do": [
"Distinguish verified evidence from assumptions.",
"Inspect or reason about the relationship between `src/test/java/app/WorkflowTest.java` and `src/main/java/app/Controller.java`.",
"Respect all stated constraints.",
"Define a failure-focused verification step.",
"Keep the proposed ... | [
{
"role": "system",
"content": "You are a software-engineering agent. Ground conclusions in available evidence, use tools deliberately, preserve safety and contracts, and never claim unobserved results."
},
{
"role": "user",
"content": "A security review requires careful handling because conflic... | {
"validation_status": "machine_validated",
"heuristic_score": 90,
"structural_fingerprint": "64852190beba304676c33c26f12b7c99a3a6fac4dc90bce9a4357516aa813fd5",
"user_request_hash": "0fe37537f9ac937c121b7de5970ba489b6a7f3f924326c5b5ecdaa54cfd6cd7e",
"record_hash": "0977de2a556b3bbe8932661f94e320f5f0458401fc6c... |
JF-ASE-002-25 | 1.0.0 | train | {
"family": "problem_understanding",
"family_label": "Problem Understanding",
"archetype": "conflicting_requirements",
"difficulty": "medium",
"behavior_targets": [
"intent_modeling",
"scope_control",
"assumption_tracking",
"acceptance_criteria"
]
} | {
"language": "Go",
"framework": "Chi",
"test_tool": "go test",
"build_tool": "Go modules"
} | {
"name": "gateway-workflow-automation-platform",
"domain": "workflow automation",
"architecture": "worker-based pipeline",
"summary": "A workflow automation repository organized as a worker-based pipeline.",
"file_tree": [
"internal/http/routes.go",
"internal/service/core.go",
"internal/store/rep... | {
"user_request": "A release candidate cannot proceed until the agent explains why evidence from the release orchestrator conflicts with assumptions made by the deployment manifest, producing conflicting requirements when a client omits a recently added field. Work in `gateway-workflow-automation-platform`, a worker-... | {
"core_issue": "The core issue is conflicting requirements: the release orchestrator establishes state using a condition that is only valid on the common path, while the deployment manifest consumes that state when a client omits a recently added field. The failure becomes observable in the workflow automation workf... | {
"initial_assessment": "This is primarily a `Problem Understanding` task. The agent should first establish whether `conflicting requirements` is a symptom, a root cause, or an underspecified request.",
"assumptions": [
"The issue is limited to the path connecting the release orchestrator and deployment manifes... | [
{
"type": "premature_patch",
"response": "Immediately rewrite the deployment manifest and update every caller without inspecting the repository.",
"why_wrong": "It treats a hypothesis as fact, expands blast radius, and skips evidence and compatibility checks."
},
{
"type": "hallucinated_evidence... | {
"must_do": [
"Distinguish verified evidence from assumptions.",
"Inspect or reason about the relationship between `internal/http/routes.go` and `internal/service/core.go`.",
"Respect all stated constraints.",
"Define a failure-focused verification step.",
"Keep the proposed change bounded and re... | [
{
"role": "system",
"content": "You are a software-engineering agent. Ground conclusions in available evidence, use tools deliberately, preserve safety and contracts, and never claim unobserved results."
},
{
"role": "user",
"content": "A release candidate cannot proceed until the agent explains... | {
"validation_status": "machine_validated",
"heuristic_score": 91,
"structural_fingerprint": "6227857f57c679dfaec39f85ec64aa89cf2b27cd54abe3990abcd25ac12b819b",
"user_request_hash": "15bdac4729882111edcdd7b787f17d25deae2cff7671f2567807719519eb6c51",
"record_hash": "0b5046f7f9cd71a44771fa847e09dc3073fce9e2b10f... |
JF-ASE-003-01 | 1.0.0 | train | {
"family": "problem_understanding",
"family_label": "Problem Understanding",
"archetype": "hidden_acceptance_criteria",
"difficulty": "hard",
"behavior_targets": [
"intent_modeling",
"scope_control",
"assumption_tracking",
"acceptance_criteria"
]
} | {
"language": "Ruby",
"framework": "Rails",
"test_tool": "RSpec",
"build_tool": "Bundler"
} | {
"name": "ledger-payments-engine",
"domain": "payments",
"architecture": "service-repository application",
"summary": "A payments repository organized as a service-repository application.",
"file_tree": [
"config/routes.rb",
"app/controllers/workflows_controller.rb",
"app/services/workflow_servic... | {
"user_request": "A support escalation reports hidden acceptance criteria appears in the payments workflow after a warm-cache transition, and the relationship between the request router and domain service is not yet proven. Work in `ledger-payments-engine`, a service-repository application implemented with Ruby and ... | {
"core_issue": "The core issue is hidden acceptance criteria: the request router establishes state using a condition that is only valid on the common path, while the domain service consumes that state after a warm-cache transition. The failure becomes observable in the payments workflow because the two components di... | {
"initial_assessment": "This is primarily a `Problem Understanding` task. The agent should first establish whether `hidden acceptance criteria` is a symptom, a root cause, or an underspecified request.",
"assumptions": [
"The issue is limited to the path connecting the request router and domain service; this r... | [
{
"type": "premature_patch",
"response": "Immediately rewrite the domain service and update every caller without inspecting the repository.",
"why_wrong": "It treats a hypothesis as fact, expands blast radius, and skips evidence and compatibility checks."
},
{
"type": "hallucinated_evidence",
... | {
"must_do": [
"Distinguish verified evidence from assumptions.",
"Inspect or reason about the relationship between `config/routes.rb` and `app/controllers/workflows_controller.rb`.",
"Respect all stated constraints.",
"Define a failure-focused verification step.",
"Keep the proposed change bounde... | [
{
"role": "system",
"content": "You are a software-engineering agent. Ground conclusions in available evidence, use tools deliberately, preserve safety and contracts, and never claim unobserved results."
},
{
"role": "user",
"content": "A support escalation reports hidden acceptance criteria app... | {
"validation_status": "machine_validated",
"heuristic_score": 90,
"structural_fingerprint": "722e7482ba41ce7fd423c75d10965908e91c890c74ea6583a5980e92de37d4c8",
"user_request_hash": "1f1d921f017e4a99983a339e79296d52dfe6de180579aaadaf3f218e0c20aa64",
"record_hash": "59a7818be53dbfb5099272988d3482757b0deb953b7a... |
JF-ASE-003-02 | 1.0.0 | train | {
"family": "problem_understanding",
"family_label": "Problem Understanding",
"archetype": "hidden_acceptance_criteria",
"difficulty": "expert",
"behavior_targets": [
"intent_modeling",
"scope_control",
"assumption_tracking",
"acceptance_criteria"
]
} | {
"language": "C++",
"framework": "CMake service",
"test_tool": "Catch2",
"build_tool": "CMake"
} | {
"name": "relay-healthcare-scheduling-engine",
"domain": "healthcare scheduling",
"architecture": "microservice platform",
"summary": "A healthcare scheduling repository organized as a microservice platform.",
"file_tree": [
"src/http/routes.cpp",
"src/core/workflow.cpp",
"src/data/repository.cpp... | {
"user_request": "An engineer observed a proposed fix for hidden acceptance criteria would broaden scope without first explaining why the failure occurs under two concurrent requests. Work in `relay-healthcare-scheduling-engine`, a microservice platform implemented with C++ and CMake service. Focus on the agent beha... | {
"core_issue": "The core issue is hidden acceptance criteria: the API handler establishes state using a condition that is only valid on the common path, while the repository adapter consumes that state under two concurrent requests. The failure becomes observable in the healthcare scheduling workflow because the two... | {
"initial_assessment": "This is primarily a `Problem Understanding` task. The agent should first establish whether `hidden acceptance criteria` is a symptom, a root cause, or an underspecified request.",
"assumptions": [
"The issue is limited to the path connecting the API handler and repository adapter; this ... | [
{
"type": "premature_patch",
"response": "Immediately rewrite the repository adapter and update every caller without inspecting the repository.",
"why_wrong": "It treats a hypothesis as fact, expands blast radius, and skips evidence and compatibility checks."
},
{
"type": "hallucinated_evidence"... | {
"must_do": [
"Distinguish verified evidence from assumptions.",
"Inspect or reason about the relationship between `src/core/workflow.cpp` and `src/data/repository.cpp`.",
"Respect all stated constraints.",
"Define a failure-focused verification step.",
"Keep the proposed change bounded and rever... | [
{
"role": "system",
"content": "You are a software-engineering agent. Ground conclusions in available evidence, use tools deliberately, preserve safety and contracts, and never claim unobserved results."
},
{
"role": "user",
"content": "An engineer observed a proposed fix for hidden acceptance c... | {
"validation_status": "machine_validated",
"heuristic_score": 91,
"structural_fingerprint": "132cc4a8fbaa6a05525d033196c34351fcad47f85fa255a632c00464af1f7ef7",
"user_request_hash": "447cdfe1e6c65274ab578cc2afb4b80f7335c404961b6595471f4d26a82dd3da",
"record_hash": "cf085e560b248541591c8070f05d6f60775bc533e5d9... |
JF-ASE-003-03 | 1.0.0 | train | {
"family": "problem_understanding",
"family_label": "Problem Understanding",
"archetype": "hidden_acceptance_criteria",
"difficulty": "easy",
"behavior_targets": [
"intent_modeling",
"scope_control",
"assumption_tracking",
"acceptance_criteria"
]
} | {
"language": "Python",
"framework": "FastAPI",
"test_tool": "pytest",
"build_tool": "uv"
} | {
"name": "atlas-developer-tooling-engine",
"domain": "developer tooling",
"architecture": "serverless workflow",
"summary": "A developer tooling repository organized as a serverless workflow.",
"file_tree": [
"app/api/routes.py",
"app/services/core.py",
"app/repositories/store.py",
"app/worke... | {
"user_request": "The latest release exposed a pattern: evidence from the background worker conflicts with assumptions made by the event consumer, producing hidden acceptance criteria during a rolling deployment. Work in `atlas-developer-tooling-engine`, a serverless workflow implemented with Python and FastAPI. Foc... | {
"core_issue": "The core issue is hidden acceptance criteria: the background worker establishes state using a condition that is only valid on the common path, while the event consumer consumes that state during a rolling deployment. The failure becomes observable in the developer tooling workflow because the two com... | {
"initial_assessment": "This is primarily a `Problem Understanding` task. The agent should first establish whether `hidden acceptance criteria` is a symptom, a root cause, or an underspecified request.",
"assumptions": [
"The issue is limited to the path connecting the background worker and event consumer; thi... | [
{
"type": "premature_patch",
"response": "Immediately rewrite the event consumer and update every caller without inspecting the repository.",
"why_wrong": "It treats a hypothesis as fact, expands blast radius, and skips evidence and compatibility checks."
},
{
"type": "hallucinated_evidence",
... | {
"must_do": [
"Distinguish verified evidence from assumptions.",
"Inspect or reason about the relationship between `app/repositories/store.py` and `app/workers/events.py`.",
"Respect all stated constraints.",
"Define a failure-focused verification step.",
"Keep the proposed change bounded and rev... | [
{
"role": "system",
"content": "You are a software-engineering agent. Ground conclusions in available evidence, use tools deliberately, preserve safety and contracts, and never claim unobserved results."
},
{
"role": "user",
"content": "The latest release exposed a pattern: evidence from the bac... | {
"validation_status": "machine_validated",
"heuristic_score": 92,
"structural_fingerprint": "3d301c5582daf138878358801783db74380a69619dbda5db0deaa731d3a8b8a5",
"user_request_hash": "57a08a79ce6e7cb37a1fd8dcfb7725ad67a297db53de6259cbe0bfe3cbc449ff",
"record_hash": "2c8ee1b4bcf913cebf21a2843d57d2dfa869fe642051... |
JF-ASE-003-04 | 1.0.0 | train | {
"family": "problem_understanding",
"family_label": "Problem Understanding",
"archetype": "hidden_acceptance_criteria",
"difficulty": "medium",
"behavior_targets": [
"intent_modeling",
"scope_control",
"assumption_tracking",
"acceptance_criteria"
]
} | {
"language": "Python",
"framework": "Django",
"test_tool": "pytest-django",
"build_tool": "pip"
} | {
"name": "harbor-identity-management-engine",
"domain": "identity management",
"architecture": "worker-based pipeline",
"summary": "A identity management repository organized as a worker-based pipeline.",
"file_tree": [
"project/urls.py",
"app/views.py",
"app/services.py",
"app/models.py",
... | {
"user_request": "A reproducible test now shows the identity management system behaves correctly in the common path but exposes hidden acceptance criteria at a daylight-saving boundary. Work in `harbor-identity-management-engine`, a worker-based pipeline implemented with Python and Django. Focus on the agent behavio... | {
"core_issue": "The core issue is hidden acceptance criteria: the session middleware establishes state using a condition that is only valid on the common path, while the identity store consumes that state at a daylight-saving boundary. The failure becomes observable in the identity management workflow because the tw... | {
"initial_assessment": "This is primarily a `Problem Understanding` task. The agent should first establish whether `hidden acceptance criteria` is a symptom, a root cause, or an underspecified request.",
"assumptions": [
"The issue is limited to the path connecting the session middleware and identity store; th... | [
{
"type": "premature_patch",
"response": "Immediately rewrite the identity store and update every caller without inspecting the repository.",
"why_wrong": "It treats a hypothesis as fact, expands blast radius, and skips evidence and compatibility checks."
},
{
"type": "hallucinated_evidence",
... | {
"must_do": [
"Distinguish verified evidence from assumptions.",
"Inspect or reason about the relationship between `app/models.py` and `app/middleware.py`.",
"Respect all stated constraints.",
"Define a failure-focused verification step.",
"Keep the proposed change bounded and reversible."
],
... | [
{
"role": "system",
"content": "You are a software-engineering agent. Ground conclusions in available evidence, use tools deliberately, preserve safety and contracts, and never claim unobserved results."
},
{
"role": "user",
"content": "A reproducible test now shows the identity management syste... | {
"validation_status": "machine_validated",
"heuristic_score": 93,
"structural_fingerprint": "910d0084b8d8aaa3ce11d939411de42a942476a7846890549551485f70580460",
"user_request_hash": "3dcfa433ad0480108c8613d37c48611f5dbd31674b0cae5950731135b44cd486",
"record_hash": "1fde15a58ed0303b7a4e3264bb93d36508728dac5089... |
JF-ASE-003-05 | 1.0.0 | train | {
"family": "problem_understanding",
"family_label": "Problem Understanding",
"archetype": "hidden_acceptance_criteria",
"difficulty": "hard",
"behavior_targets": [
"intent_modeling",
"scope_control",
"assumption_tracking",
"acceptance_criteria"
]
} | {
"language": "TypeScript",
"framework": "Node.js",
"test_tool": "Vitest",
"build_tool": "pnpm"
} | {
"name": "forge-e-commerce-engine",
"domain": "e-commerce",
"architecture": "multi-tenant SaaS",
"summary": "A e-commerce repository organized as a multi-tenant SaaS.",
"file_tree": [
"src/http/routes.ts",
"src/services/core.ts",
"src/data/repository.ts",
"src/workers/consumer.ts",
"src/s... | {
"user_request": "Operational telemetry suggests a proposed fix for hidden acceptance criteria would broaden scope without first explaining why the failure occurs when retries overlap. Work in `forge-e-commerce-engine`, a multi-tenant SaaS implemented with TypeScript and Node.js. Focus on the agent behavior required... | {
"core_issue": "The core issue is hidden acceptance criteria: the cache layer establishes state using a condition that is only valid on the common path, while the database gateway consumes that state when retries overlap. The failure becomes observable in the e-commerce workflow because the two components disagree a... | {
"initial_assessment": "This is primarily a `Problem Understanding` task. The agent should first establish whether `hidden acceptance criteria` is a symptom, a root cause, or an underspecified request.",
"assumptions": [
"The issue is limited to the path connecting the cache layer and database gateway; this re... | [
{
"type": "premature_patch",
"response": "Immediately rewrite the database gateway and update every caller without inspecting the repository.",
"why_wrong": "It treats a hypothesis as fact, expands blast radius, and skips evidence and compatibility checks."
},
{
"type": "hallucinated_evidence",
... | {
"must_do": [
"Distinguish verified evidence from assumptions.",
"Inspect or reason about the relationship between `src/security/policy.ts` and `test/workflow.test.ts`.",
"Respect all stated constraints.",
"Define a failure-focused verification step.",
"Keep the proposed change bounded and revers... | [
{
"role": "system",
"content": "You are a software-engineering agent. Ground conclusions in available evidence, use tools deliberately, preserve safety and contracts, and never claim unobserved results."
},
{
"role": "user",
"content": "Operational telemetry suggests a proposed fix for hidden ac... | {
"validation_status": "machine_validated",
"heuristic_score": 94,
"structural_fingerprint": "79456fc73f0840e7a73566ba40ba9b7c6aafb93e50f9a624d5609633d5c0b6c4",
"user_request_hash": "df26f2347bb1ef044d468a4b90e098d360a540478cffe35b4c602f0198467116",
"record_hash": "fc4e84fd57185b112776bf859c5f97a2bb5653f937f6... |
JF-ASE-003-06 | 1.0.0 | train | {
"family": "problem_understanding",
"family_label": "Problem Understanding",
"archetype": "hidden_acceptance_criteria",
"difficulty": "expert",
"behavior_targets": [
"intent_modeling",
"scope_control",
"assumption_tracking",
"acceptance_criteria"
]
} | {
"language": "TypeScript",
"framework": "React",
"test_tool": "Playwright",
"build_tool": "Vite"
} | {
"name": "signal-logistics-engine",
"domain": "logistics",
"architecture": "API gateway architecture",
"summary": "A logistics repository organized as a API gateway architecture.",
"file_tree": [
"src/app/router.tsx",
"src/features/state.ts",
"src/api/client.ts",
"src/components/Workflow.tsx"... | {
"user_request": "A code review uncovered a risk: hidden acceptance criteria appears in the logistics workflow with legacy records created before the last migration, and the relationship between the scheduler and job executor is not yet proven. Work in `signal-logistics-engine`, a API gateway architecture implemente... | {
"core_issue": "The core issue is hidden acceptance criteria: the scheduler establishes state using a condition that is only valid on the common path, while the job executor consumes that state with legacy records created before the last migration. The failure becomes observable in the logistics workflow because the... | {
"initial_assessment": "This is primarily a `Problem Understanding` task. The agent should first establish whether `hidden acceptance criteria` is a symptom, a root cause, or an underspecified request.",
"assumptions": [
"The issue is limited to the path connecting the scheduler and job executor; this remains ... | [
{
"type": "premature_patch",
"response": "Immediately rewrite the job executor and update every caller without inspecting the repository.",
"why_wrong": "It treats a hypothesis as fact, expands blast radius, and skips evidence and compatibility checks."
},
{
"type": "hallucinated_evidence",
... | {
"must_do": [
"Distinguish verified evidence from assumptions.",
"Inspect or reason about the relationship between `tests/workflow.spec.ts` and `src/app/router.tsx`.",
"Respect all stated constraints.",
"Define a failure-focused verification step.",
"Keep the proposed change bounded and reversibl... | [
{
"role": "system",
"content": "You are a software-engineering agent. Ground conclusions in available evidence, use tools deliberately, preserve safety and contracts, and never claim unobserved results."
},
{
"role": "user",
"content": "A code review uncovered a risk: hidden acceptance criteria ... | {
"validation_status": "machine_validated",
"heuristic_score": 95,
"structural_fingerprint": "ed625836bad5a21b194f62223cd48beb48fad5d9efc7f5bcd09264866ed67e1f",
"user_request_hash": "17ceccf2b887fb0b10037dcec42f2a19051259fb6a2cbeec28f9977b8498416d",
"record_hash": "8239fcfc5a2525a7320ebb4749d70a24613f3be636ad... |
JF-ASE-003-07 | 1.0.0 | train | {
"family": "problem_understanding",
"family_label": "Problem Understanding",
"archetype": "hidden_acceptance_criteria",
"difficulty": "easy",
"behavior_targets": [
"intent_modeling",
"scope_control",
"assumption_tracking",
"acceptance_criteria"
]
} | {
"language": "Java",
"framework": "Spring Boot",
"test_tool": "JUnit",
"build_tool": "Gradle"
} | {
"name": "orbit-collaboration-software-engine",
"domain": "collaboration software",
"architecture": "batch processing system",
"summary": "A collaboration software repository organized as a batch processing system.",
"file_tree": [
"src/main/java/app/Controller.java",
"src/main/java/app/Service.java"... | {
"user_request": "The team needs a grounded investigation because hidden acceptance criteria appears in the collaboration software workflow immediately after a feature flag changes, and the relationship between the serializer and public API contract is not yet proven. Work in `orbit-collaboration-software-engine`, a... | {
"core_issue": "The core issue is hidden acceptance criteria: the serializer establishes state using a condition that is only valid on the common path, while the public API contract consumes that state immediately after a feature flag changes. The failure becomes observable in the collaboration software workflow bec... | {
"initial_assessment": "This is primarily a `Problem Understanding` task. The agent should first establish whether `hidden acceptance criteria` is a symptom, a root cause, or an underspecified request.",
"assumptions": [
"The issue is limited to the path connecting the serializer and public API contract; this ... | [
{
"type": "premature_patch",
"response": "Immediately rewrite the public API contract and update every caller without inspecting the repository.",
"why_wrong": "It treats a hypothesis as fact, expands blast radius, and skips evidence and compatibility checks."
},
{
"type": "hallucinated_evidence... | {
"must_do": [
"Distinguish verified evidence from assumptions.",
"Inspect or reason about the relationship between `src/main/java/app/Controller.java` and `src/main/java/app/Service.java`.",
"Respect all stated constraints.",
"Define a failure-focused verification step.",
"Keep the proposed chang... | [
{
"role": "system",
"content": "You are a software-engineering agent. Ground conclusions in available evidence, use tools deliberately, preserve safety and contracts, and never claim unobserved results."
},
{
"role": "user",
"content": "The team needs a grounded investigation because hidden acce... | {
"validation_status": "machine_validated",
"heuristic_score": 96,
"structural_fingerprint": "23dce1738c70796b87a798c69a4ec92d0565221ff95c7eb655b094f9b45c2dae",
"user_request_hash": "e541e4e15e4ccdb427b1588fee7c3fa99239fc95a1d19efab43feb794a0fb60c",
"record_hash": "7a0c343056aead03d7632c097908e4b3a3c143f494e7... |
JF-ASE-003-08 | 1.0.0 | train | {
"family": "problem_understanding",
"family_label": "Problem Understanding",
"archetype": "hidden_acceptance_criteria",
"difficulty": "medium",
"behavior_targets": [
"intent_modeling",
"scope_control",
"assumption_tracking",
"acceptance_criteria"
]
} | {
"language": "Go",
"framework": "Chi",
"test_tool": "go test",
"build_tool": "Go modules"
} | {
"name": "bridge-analytics-engine",
"domain": "analytics",
"architecture": "plugin-oriented application",
"summary": "A analytics repository organized as a plugin-oriented application.",
"file_tree": [
"internal/http/routes.go",
"internal/service/core.go",
"internal/store/repository.go",
"int... | {
"user_request": "A customer-facing workflow intermittently exhibits this behavior: the team cannot safely complete the analytics change because hidden acceptance criteria remains unresolved during a partial network failure. Work in `bridge-analytics-engine`, a plugin-oriented application implemented with Go and Chi... | {
"core_issue": "The core issue is hidden acceptance criteria: the migration runner establishes state using a condition that is only valid on the common path, while the schema registry consumes that state during a partial network failure. The failure becomes observable in the analytics workflow because the two compon... | {
"initial_assessment": "This is primarily a `Problem Understanding` task. The agent should first establish whether `hidden acceptance criteria` is a symptom, a root cause, or an underspecified request.",
"assumptions": [
"The issue is limited to the path connecting the migration runner and schema registry; thi... | [
{
"type": "premature_patch",
"response": "Immediately rewrite the schema registry and update every caller without inspecting the repository.",
"why_wrong": "It treats a hypothesis as fact, expands blast radius, and skips evidence and compatibility checks."
},
{
"type": "hallucinated_evidence",
... | {
"must_do": [
"Distinguish verified evidence from assumptions.",
"Inspect or reason about the relationship between `internal/service/core.go` and `internal/store/repository.go`.",
"Respect all stated constraints.",
"Define a failure-focused verification step.",
"Keep the proposed change bounded a... | [
{
"role": "system",
"content": "You are a software-engineering agent. Ground conclusions in available evidence, use tools deliberately, preserve safety and contracts, and never claim unobserved results."
},
{
"role": "user",
"content": "A customer-facing workflow intermittently exhibits this beh... | {
"validation_status": "machine_validated",
"heuristic_score": 97,
"structural_fingerprint": "360ca373ac10f21423aa9101c51064533d8946e0e4f8a5db1f05957934625cfe",
"user_request_hash": "139f1ba24c50513d562a432a8bcacae70aa37cce0274faacc4a899066a68bae1",
"record_hash": "98b94246210862c6413d18c59ae311535770d1a5a12c... |
JF-ASE-003-09 | 1.0.0 | train | {
"family": "problem_understanding",
"family_label": "Problem Understanding",
"archetype": "hidden_acceptance_criteria",
"difficulty": "hard",
"behavior_targets": [
"intent_modeling",
"scope_control",
"assumption_tracking",
"acceptance_criteria"
]
} | {
"language": "C#",
"framework": "ASP.NET Core",
"test_tool": "xUnit",
"build_tool": "dotnet"
} | {
"name": "vault-education-technology-engine",
"domain": "education technology",
"architecture": "modular monolith",
"summary": "A education technology repository organized as a modular monolith.",
"file_tree": [
"Api/Controllers/WorkflowController.cs",
"Core/WorkflowService.cs",
"Data/WorkflowRep... | {
"user_request": "During validation, the system revealed that the team cannot safely complete the education technology change because hidden acceptance criteria remains unresolved after switching tenants in the same browser session. Work in `vault-education-technology-engine`, a modular monolith implemented with C# ... | {
"core_issue": "The core issue is hidden acceptance criteria: the feature-flag client establishes state using a condition that is only valid on the common path, while the configuration service consumes that state after switching tenants in the same browser session. The failure becomes observable in the education tec... | {
"initial_assessment": "This is primarily a `Problem Understanding` task. The agent should first establish whether `hidden acceptance criteria` is a symptom, a root cause, or an underspecified request.",
"assumptions": [
"The issue is limited to the path connecting the feature-flag client and configuration ser... | [
{
"type": "premature_patch",
"response": "Immediately rewrite the configuration service and update every caller without inspecting the repository.",
"why_wrong": "It treats a hypothesis as fact, expands blast radius, and skips evidence and compatibility checks."
},
{
"type": "hallucinated_eviden... | {
"must_do": [
"Distinguish verified evidence from assumptions.",
"Inspect or reason about the relationship between `Data/WorkflowRepository.cs` and `Workers/EventWorker.cs`.",
"Respect all stated constraints.",
"Define a failure-focused verification step.",
"Keep the proposed change bounded and r... | [
{
"role": "system",
"content": "You are a software-engineering agent. Ground conclusions in available evidence, use tools deliberately, preserve safety and contracts, and never claim unobserved results."
},
{
"role": "user",
"content": "During validation, the system revealed that the team cannot... | {
"validation_status": "machine_validated",
"heuristic_score": 98,
"structural_fingerprint": "54d87a86856e7783a5af03a648d14a6f93460a0a70a073b2a1c1147a6782e6ca",
"user_request_hash": "3919b7650fcc9d9286ac8b5836fc50ea0efb90c78ad529a8290c077d76e58c9b",
"record_hash": "155a7e37120c08bda6bce86afb8ee7bbc104e42213fe... |
JF-ASE-003-10 | 1.0.0 | train | {
"family": "problem_understanding",
"family_label": "Problem Understanding",
"archetype": "hidden_acceptance_criteria",
"difficulty": "expert",
"behavior_targets": [
"intent_modeling",
"scope_control",
"assumption_tracking",
"acceptance_criteria"
]
} | {
"language": "PHP",
"framework": "Laravel",
"test_tool": "PHPUnit",
"build_tool": "Composer"
} | {
"name": "stream-media-processing-engine",
"domain": "media processing",
"architecture": "event-driven services",
"summary": "A media processing repository organized as a event-driven services.",
"file_tree": [
"routes/api.php",
"app/Http/Controllers/WorkflowController.php",
"app/Services/Workflo... | {
"user_request": "A maintenance task became unsafe after reviewers noticed the team cannot safely complete the media processing change because hidden acceptance criteria remains unresolved following a dependency upgrade. Work in `stream-media-processing-engine`, a event-driven services implemented with PHP and Larav... | {
"core_issue": "The core issue is hidden acceptance criteria: the authorization policy establishes state using a condition that is only valid on the common path, while the resource loader consumes that state following a dependency upgrade. The failure becomes observable in the media processing workflow because the t... | {
"initial_assessment": "This is primarily a `Problem Understanding` task. The agent should first establish whether `hidden acceptance criteria` is a symptom, a root cause, or an underspecified request.",
"assumptions": [
"The issue is limited to the path connecting the authorization policy and resource loader;... | [
{
"type": "premature_patch",
"response": "Immediately rewrite the resource loader and update every caller without inspecting the repository.",
"why_wrong": "It treats a hypothesis as fact, expands blast radius, and skips evidence and compatibility checks."
},
{
"type": "hallucinated_evidence",
... | {
"must_do": [
"Distinguish verified evidence from assumptions.",
"Inspect or reason about the relationship between `app/Repositories/WorkflowRepository.php` and `app/Policies/WorkflowPolicy.php`.",
"Respect all stated constraints.",
"Define a failure-focused verification step.",
"Keep the propose... | [
{
"role": "system",
"content": "You are a software-engineering agent. Ground conclusions in available evidence, use tools deliberately, preserve safety and contracts, and never claim unobserved results."
},
{
"role": "user",
"content": "A maintenance task became unsafe after reviewers noticed th... | {
"validation_status": "machine_validated",
"heuristic_score": 88,
"structural_fingerprint": "cd5eee2e6550b0dbdc155c2b32a662b72641ffc655f611e05dcfab07a2aa140a",
"user_request_hash": "53bdd91b8d43187e96830c818ad20037a06fb639fc4bf67ef3a8a8efcc2141e2",
"record_hash": "6f5f42ae072869989e137b2b7e65c8bbbdb26139ad28... |
JF-ASE-003-11 | 1.0.0 | train | {
"family": "problem_understanding",
"family_label": "Problem Understanding",
"archetype": "hidden_acceptance_criteria",
"difficulty": "easy",
"behavior_targets": [
"intent_modeling",
"scope_control",
"assumption_tracking",
"acceptance_criteria"
]
} | {
"language": "Rust",
"framework": "Axum",
"test_tool": "cargo test",
"build_tool": "Cargo"
} | {
"name": "pilot-cloud-infrastructure-engine",
"domain": "cloud infrastructure",
"architecture": "service-repository application",
"summary": "A cloud infrastructure repository organized as a service-repository application.",
"file_tree": [
"src/http/routes.rs",
"src/services/core.rs",
"src/store/... | {
"user_request": "The repository owner asks for help with a case where the cloud infrastructure system behaves correctly in the common path but exposes hidden acceptance criteria near the end of a paginated result set. Work in `pilot-cloud-infrastructure-engine`, a service-repository application implemented with Rus... | {
"core_issue": "The core issue is hidden acceptance criteria: the message producer establishes state using a condition that is only valid on the common path, while the idempotency store consumes that state near the end of a paginated result set. The failure becomes observable in the cloud infrastructure workflow bec... | {
"initial_assessment": "This is primarily a `Problem Understanding` task. The agent should first establish whether `hidden acceptance criteria` is a symptom, a root cause, or an underspecified request.",
"assumptions": [
"The issue is limited to the path connecting the message producer and idempotency store; t... | [
{
"type": "premature_patch",
"response": "Immediately rewrite the idempotency store and update every caller without inspecting the repository.",
"why_wrong": "It treats a hypothesis as fact, expands blast radius, and skips evidence and compatibility checks."
},
{
"type": "hallucinated_evidence",... | {
"must_do": [
"Distinguish verified evidence from assumptions.",
"Inspect or reason about the relationship between `src/security/policy.rs` and `tests/workflow.rs`.",
"Respect all stated constraints.",
"Define a failure-focused verification step.",
"Keep the proposed change bounded and reversible... | [
{
"role": "system",
"content": "You are a software-engineering agent. Ground conclusions in available evidence, use tools deliberately, preserve safety and contracts, and never claim unobserved results."
},
{
"role": "user",
"content": "The repository owner asks for help with a case where the cl... | {
"validation_status": "machine_validated",
"heuristic_score": 89,
"structural_fingerprint": "cc2b3daa0008e8676a68de2c5e628539402936dc2c80a8e5ecd5fb9041f0f0a0",
"user_request_hash": "5264268156e33c52cf6a7d4c479320acd33817430d3af4c86fc5aff94d598202",
"record_hash": "ab6e9885fddb6531b0eb819931076b8e81ce39a2b6ab... |
JF-ASE-003-12 | 1.0.0 | train | {
"family": "problem_understanding",
"family_label": "Problem Understanding",
"archetype": "hidden_acceptance_criteria",
"difficulty": "medium",
"behavior_targets": [
"intent_modeling",
"scope_control",
"assumption_tracking",
"acceptance_criteria"
]
} | {
"language": "Kotlin",
"framework": "Ktor",
"test_tool": "Kotest",
"build_tool": "Gradle"
} | {
"name": "mesh-customer-support-engine",
"domain": "customer support",
"architecture": "microservice platform",
"summary": "A customer support repository organized as a microservice platform.",
"file_tree": [
"src/main/kotlin/app/Routes.kt",
"src/main/kotlin/app/Service.kt",
"src/main/kotlin/app/... | {
"user_request": "A rollout checkpoint failed because a proposed fix for hidden acceptance criteria would broaden scope without first explaining why the failure occurs when the payload contains an empty optional field. Work in `mesh-customer-support-engine`, a microservice platform implemented with Kotlin and Ktor. ... | {
"core_issue": "The core issue is hidden acceptance criteria: the upload controller establishes state using a condition that is only valid on the common path, while the object storage adapter consumes that state when the payload contains an empty optional field. The failure becomes observable in the customer support... | {
"initial_assessment": "This is primarily a `Problem Understanding` task. The agent should first establish whether `hidden acceptance criteria` is a symptom, a root cause, or an underspecified request.",
"assumptions": [
"The issue is limited to the path connecting the upload controller and object storage adap... | [
{
"type": "premature_patch",
"response": "Immediately rewrite the object storage adapter and update every caller without inspecting the repository.",
"why_wrong": "It treats a hypothesis as fact, expands blast radius, and skips evidence and compatibility checks."
},
{
"type": "hallucinated_evide... | {
"must_do": [
"Distinguish verified evidence from assumptions.",
"Inspect or reason about the relationship between `src/test/kotlin/app/WorkflowSpec.kt` and `src/main/kotlin/app/Routes.kt`.",
"Respect all stated constraints.",
"Define a failure-focused verification step.",
"Keep the proposed chan... | [
{
"role": "system",
"content": "You are a software-engineering agent. Ground conclusions in available evidence, use tools deliberately, preserve safety and contracts, and never claim unobserved results."
},
{
"role": "user",
"content": "A rollout checkpoint failed because a proposed fix for hidd... | {
"validation_status": "machine_validated",
"heuristic_score": 90,
"structural_fingerprint": "d027f462e17257aea06d44b7ad1b7562e4a2f8eb2d347a6ae81d52515aec36cd",
"user_request_hash": "2a58cb35dc8c299198805ffeb093ebee8bfd1568d63967e95189e60160ba2b68",
"record_hash": "043fc8d08270c9c937e1b7fd6a329fe9e556ff8c3569... |
JF-ASE-003-13 | 1.0.0 | train | {
"family": "problem_understanding",
"family_label": "Problem Understanding",
"archetype": "hidden_acceptance_criteria",
"difficulty": "hard",
"behavior_targets": [
"intent_modeling",
"scope_control",
"assumption_tracking",
"acceptance_criteria"
]
} | {
"language": "Ruby",
"framework": "Rails",
"test_tool": "RSpec",
"build_tool": "Bundler"
} | {
"name": "beacon-document-management-engine",
"domain": "document management",
"architecture": "serverless workflow",
"summary": "A document management repository organized as a serverless workflow.",
"file_tree": [
"config/routes.rb",
"app/controllers/workflows_controller.rb",
"app/services/work... | {
"user_request": "An incident follow-up points to a scenario in which hidden acceptance criteria appears in the document management workflow after a worker restarts, and the relationship between the webhook receiver and retry coordinator is not yet proven. Work in `beacon-document-management-engine`, a serverless wo... | {
"core_issue": "The core issue is hidden acceptance criteria: the webhook receiver establishes state using a condition that is only valid on the common path, while the retry coordinator consumes that state after a worker restarts. The failure becomes observable in the document management workflow because the two com... | {
"initial_assessment": "This is primarily a `Problem Understanding` task. The agent should first establish whether `hidden acceptance criteria` is a symptom, a root cause, or an underspecified request.",
"assumptions": [
"The issue is limited to the path connecting the webhook receiver and retry coordinator; t... | [
{
"type": "premature_patch",
"response": "Immediately rewrite the retry coordinator and update every caller without inspecting the repository.",
"why_wrong": "It treats a hypothesis as fact, expands blast radius, and skips evidence and compatibility checks."
},
{
"type": "hallucinated_evidence",... | {
"must_do": [
"Distinguish verified evidence from assumptions.",
"Inspect or reason about the relationship between `config/routes.rb` and `app/controllers/workflows_controller.rb`.",
"Respect all stated constraints.",
"Define a failure-focused verification step.",
"Keep the proposed change bounde... | [
{
"role": "system",
"content": "You are a software-engineering agent. Ground conclusions in available evidence, use tools deliberately, preserve safety and contracts, and never claim unobserved results."
},
{
"role": "user",
"content": "An incident follow-up points to a scenario in which hidden ... | {
"validation_status": "machine_validated",
"heuristic_score": 91,
"structural_fingerprint": "ccd2aeaf620b0a5f2d43a18368ca0378c88e5fe79bdde46b7870fee77680644a",
"user_request_hash": "033d101e66a0a4343991863585c883cfb955c1115ad2cc422925e9e06ef72f0f",
"record_hash": "9ff9b0b51014ce37faa69252adf4da59b7dac0d3d493... |
JF-ASE-003-14 | 1.0.0 | train | {
"family": "problem_understanding",
"family_label": "Problem Understanding",
"archetype": "hidden_acceptance_criteria",
"difficulty": "expert",
"behavior_targets": [
"intent_modeling",
"scope_control",
"assumption_tracking",
"acceptance_criteria"
]
} | {
"language": "C++",
"framework": "CMake service",
"test_tool": "Catch2",
"build_tool": "CMake"
} | {
"name": "kernel-iot-operations-engine",
"domain": "IoT operations",
"architecture": "worker-based pipeline",
"summary": "A IoT operations repository organized as a worker-based pipeline.",
"file_tree": [
"src/http/routes.cpp",
"src/core/workflow.cpp",
"src/data/repository.cpp",
"src/workers/... | {
"user_request": "A pre-release audit found that the team cannot safely complete the IoT operations change because hidden acceptance criteria remains unresolved while the queue is under backpressure. Work in `kernel-iot-operations-engine`, a worker-based pipeline implemented with C++ and CMake service. Focus on the ... | {
"core_issue": "The core issue is hidden acceptance criteria: the query builder establishes state using a condition that is only valid on the common path, while the pagination layer consumes that state while the queue is under backpressure. The failure becomes observable in the IoT operations workflow because the tw... | {
"initial_assessment": "This is primarily a `Problem Understanding` task. The agent should first establish whether `hidden acceptance criteria` is a symptom, a root cause, or an underspecified request.",
"assumptions": [
"The issue is limited to the path connecting the query builder and pagination layer; this ... | [
{
"type": "premature_patch",
"response": "Immediately rewrite the pagination layer and update every caller without inspecting the repository.",
"why_wrong": "It treats a hypothesis as fact, expands blast radius, and skips evidence and compatibility checks."
},
{
"type": "hallucinated_evidence",
... | {
"must_do": [
"Distinguish verified evidence from assumptions.",
"Inspect or reason about the relationship between `src/core/workflow.cpp` and `src/data/repository.cpp`.",
"Respect all stated constraints.",
"Define a failure-focused verification step.",
"Keep the proposed change bounded and rever... | [
{
"role": "system",
"content": "You are a software-engineering agent. Ground conclusions in available evidence, use tools deliberately, preserve safety and contracts, and never claim unobserved results."
},
{
"role": "user",
"content": "A pre-release audit found that the team cannot safely compl... | {
"validation_status": "machine_validated",
"heuristic_score": 92,
"structural_fingerprint": "d293dc9e63dcd8ab93d113b76387fbbbde8b585fc2d6c178c0436321ca8aa0b2",
"user_request_hash": "40cffcc9dc56e85d2622392bd9ef9ced6af9ec98c0a9998ae9e394d6213f5b1e",
"record_hash": "6edc0641d1f1a03bd1b55e7fccc9edef7114322215ac... |
JF-ASE-003-15 | 1.0.0 | train | {
"family": "problem_understanding",
"family_label": "Problem Understanding",
"archetype": "hidden_acceptance_criteria",
"difficulty": "easy",
"behavior_targets": [
"intent_modeling",
"scope_control",
"assumption_tracking",
"acceptance_criteria"
]
} | {
"language": "Python",
"framework": "FastAPI",
"test_tool": "pytest",
"build_tool": "uv"
} | {
"name": "canvas-financial-reporting-engine",
"domain": "financial reporting",
"architecture": "multi-tenant SaaS",
"summary": "A financial reporting repository organized as a multi-tenant SaaS.",
"file_tree": [
"app/api/routes.py",
"app/services/core.py",
"app/repositories/store.py",
"app/wo... | {
"user_request": "A regression report describes the following condition: hidden acceptance criteria appears in the financial reporting workflow during an idempotent event replay, and the relationship between the CLI command and process runner is not yet proven. Work in `canvas-financial-reporting-engine`, a multi-te... | {
"core_issue": "The core issue is hidden acceptance criteria: the CLI command establishes state using a condition that is only valid on the common path, while the process runner consumes that state during an idempotent event replay. The failure becomes observable in the financial reporting workflow because the two c... | {
"initial_assessment": "This is primarily a `Problem Understanding` task. The agent should first establish whether `hidden acceptance criteria` is a symptom, a root cause, or an underspecified request.",
"assumptions": [
"The issue is limited to the path connecting the CLI command and process runner; this rema... | [
{
"type": "premature_patch",
"response": "Immediately rewrite the process runner and update every caller without inspecting the repository.",
"why_wrong": "It treats a hypothesis as fact, expands blast radius, and skips evidence and compatibility checks."
},
{
"type": "hallucinated_evidence",
... | {
"must_do": [
"Distinguish verified evidence from assumptions.",
"Inspect or reason about the relationship between `app/repositories/store.py` and `app/workers/events.py`.",
"Respect all stated constraints.",
"Define a failure-focused verification step.",
"Keep the proposed change bounded and rev... | [
{
"role": "system",
"content": "You are a software-engineering agent. Ground conclusions in available evidence, use tools deliberately, preserve safety and contracts, and never claim unobserved results."
},
{
"role": "user",
"content": "A regression report describes the following condition: hidd... | {
"validation_status": "machine_validated",
"heuristic_score": 93,
"structural_fingerprint": "65de606cf62a799330e6e187781dccd5aaa065a5d8322d5683e0c8efbab6cdf2",
"user_request_hash": "e133edd9637122ad405f7ff8bfcd9642db4c763d7c71e946ed84d29b5b78035f",
"record_hash": "87d75de9679460cb34365360f7d88d0e4b110ec11701... |
JF-ASE-003-16 | 1.0.0 | train | {
"family": "problem_understanding",
"family_label": "Problem Understanding",
"archetype": "hidden_acceptance_criteria",
"difficulty": "medium",
"behavior_targets": [
"intent_modeling",
"scope_control",
"assumption_tracking",
"acceptance_criteria"
]
} | {
"language": "Python",
"framework": "Django",
"test_tool": "pytest-django",
"build_tool": "pip"
} | {
"name": "pulse-search-infrastructure-engine",
"domain": "search infrastructure",
"architecture": "API gateway architecture",
"summary": "A search infrastructure repository organized as a API gateway architecture.",
"file_tree": [
"project/urls.py",
"app/views.py",
"app/services.py",
"app/mod... | {
"user_request": "The current implementation is uncertain because evidence from the frontend state store conflicts with assumptions made by the API client, producing hidden acceptance criteria when application nodes have mild clock skew. Work in `pulse-search-infrastructure-engine`, a API gateway architecture implem... | {
"core_issue": "The core issue is hidden acceptance criteria: the frontend state store establishes state using a condition that is only valid on the common path, while the API client consumes that state when application nodes have mild clock skew. The failure becomes observable in the search infrastructure workflow ... | {
"initial_assessment": "This is primarily a `Problem Understanding` task. The agent should first establish whether `hidden acceptance criteria` is a symptom, a root cause, or an underspecified request.",
"assumptions": [
"The issue is limited to the path connecting the frontend state store and API client; this... | [
{
"type": "premature_patch",
"response": "Immediately rewrite the API client and update every caller without inspecting the repository.",
"why_wrong": "It treats a hypothesis as fact, expands blast radius, and skips evidence and compatibility checks."
},
{
"type": "hallucinated_evidence",
"r... | {
"must_do": [
"Distinguish verified evidence from assumptions.",
"Inspect or reason about the relationship between `app/models.py` and `app/middleware.py`.",
"Respect all stated constraints.",
"Define a failure-focused verification step.",
"Keep the proposed change bounded and reversible."
],
... | [
{
"role": "system",
"content": "You are a software-engineering agent. Ground conclusions in available evidence, use tools deliberately, preserve safety and contracts, and never claim unobserved results."
},
{
"role": "user",
"content": "The current implementation is uncertain because evidence fr... | {
"validation_status": "machine_validated",
"heuristic_score": 94,
"structural_fingerprint": "235344080eb35aabc89c6999c4933310bb95808fc66b86cd650016e329028c35",
"user_request_hash": "2ed3525b4681120ac95a96f919eb919c1d85fd76f3bdf402aa4715f9af8166c3",
"record_hash": "d51a02483de7b3b4e6fa041832c6f98d9216fcd0fa26... |
JF-ASE-003-17 | 1.0.0 | train | {
"family": "problem_understanding",
"family_label": "Problem Understanding",
"archetype": "hidden_acceptance_criteria",
"difficulty": "hard",
"behavior_targets": [
"intent_modeling",
"scope_control",
"assumption_tracking",
"acceptance_criteria"
]
} | {
"language": "TypeScript",
"framework": "Node.js",
"test_tool": "Vitest",
"build_tool": "pnpm"
} | {
"name": "matrix-content-moderation-engine",
"domain": "content moderation",
"architecture": "batch processing system",
"summary": "A content moderation repository organized as a batch processing system.",
"file_tree": [
"src/http/routes.ts",
"src/services/core.ts",
"src/data/repository.ts",
... | {
"user_request": "A teammate proposed a quick fix, but the evidence only proves that the team cannot safely complete the content moderation change because hidden acceptance criteria remains unresolved after a zero-downtime schema migration. Work in `matrix-content-moderation-engine`, a batch processing system implem... | {
"core_issue": "The core issue is hidden acceptance criteria: the metrics exporter establishes state using a condition that is only valid on the common path, while the runtime instrumentation consumes that state after a zero-downtime schema migration. The failure becomes observable in the content moderation workflow... | {
"initial_assessment": "This is primarily a `Problem Understanding` task. The agent should first establish whether `hidden acceptance criteria` is a symptom, a root cause, or an underspecified request.",
"assumptions": [
"The issue is limited to the path connecting the metrics exporter and runtime instrumentat... | [
{
"type": "premature_patch",
"response": "Immediately rewrite the runtime instrumentation and update every caller without inspecting the repository.",
"why_wrong": "It treats a hypothesis as fact, expands blast radius, and skips evidence and compatibility checks."
},
{
"type": "hallucinated_evid... | {
"must_do": [
"Distinguish verified evidence from assumptions.",
"Inspect or reason about the relationship between `src/security/policy.ts` and `test/workflow.test.ts`.",
"Respect all stated constraints.",
"Define a failure-focused verification step.",
"Keep the proposed change bounded and revers... | [
{
"role": "system",
"content": "You are a software-engineering agent. Ground conclusions in available evidence, use tools deliberately, preserve safety and contracts, and never claim unobserved results."
},
{
"role": "user",
"content": "A teammate proposed a quick fix, but the evidence only prov... | {
"validation_status": "machine_validated",
"heuristic_score": 95,
"structural_fingerprint": "5d1af0ee98c5937029fe74585e5a4bee8122bb8e540eb8035b81c10b507acb1e",
"user_request_hash": "ff3074e2d935283022969dc19950f34ced80e02f941eda5d2aad121d5e7d2412",
"record_hash": "f8b78516d4f1b5e9c9ea6ae56749f7912e7e7a8679bf... |
JF-ASE-003-18 | 1.0.0 | train | {
"family": "problem_understanding",
"family_label": "Problem Understanding",
"archetype": "hidden_acceptance_criteria",
"difficulty": "expert",
"behavior_targets": [
"intent_modeling",
"scope_control",
"assumption_tracking",
"acceptance_criteria"
]
} | {
"language": "TypeScript",
"framework": "React",
"test_tool": "Playwright",
"build_tool": "Vite"
} | {
"name": "anchor-hr-systems-engine",
"domain": "HR systems",
"architecture": "plugin-oriented application",
"summary": "A HR systems repository organized as a plugin-oriented application.",
"file_tree": [
"src/app/router.tsx",
"src/features/state.ts",
"src/api/client.ts",
"src/components/Work... | {
"user_request": "A multi-step change is blocked by the fact that the team cannot safely complete the HR systems change because hidden acceptance criteria remains unresolved while old and new application versions coexist. Work in `anchor-hr-systems-engine`, a plugin-oriented application implemented with TypeScript a... | {
"core_issue": "The core issue is hidden acceptance criteria: the dependency resolver establishes state using a condition that is only valid on the common path, while the build pipeline consumes that state while old and new application versions coexist. The failure becomes observable in the HR systems workflow becau... | {
"initial_assessment": "This is primarily a `Problem Understanding` task. The agent should first establish whether `hidden acceptance criteria` is a symptom, a root cause, or an underspecified request.",
"assumptions": [
"The issue is limited to the path connecting the dependency resolver and build pipeline; t... | [
{
"type": "premature_patch",
"response": "Immediately rewrite the build pipeline and update every caller without inspecting the repository.",
"why_wrong": "It treats a hypothesis as fact, expands blast radius, and skips evidence and compatibility checks."
},
{
"type": "hallucinated_evidence",
... | {
"must_do": [
"Distinguish verified evidence from assumptions.",
"Inspect or reason about the relationship between `tests/workflow.spec.ts` and `src/app/router.tsx`.",
"Respect all stated constraints.",
"Define a failure-focused verification step.",
"Keep the proposed change bounded and reversibl... | [
{
"role": "system",
"content": "You are a software-engineering agent. Ground conclusions in available evidence, use tools deliberately, preserve safety and contracts, and never claim unobserved results."
},
{
"role": "user",
"content": "A multi-step change is blocked by the fact that the team ca... | {
"validation_status": "machine_validated",
"heuristic_score": 96,
"structural_fingerprint": "aed380b28bfff210ffb7ca85da03694abf1722a0fe1813ffb46c1e3ed2a69e32",
"user_request_hash": "25ffbb209d54b2d8bf191c2de388d48f86b53acbcc52cd8b7fa9597e5a5c8ff6",
"record_hash": "f115faacb176055a7e5c3bef17b3f7eadc2bc8b9039d... |
JF-ASE-003-19 | 1.0.0 | train | {
"family": "problem_understanding",
"family_label": "Problem Understanding",
"archetype": "hidden_acceptance_criteria",
"difficulty": "easy",
"behavior_targets": [
"intent_modeling",
"scope_control",
"assumption_tracking",
"acceptance_criteria"
]
} | {
"language": "Java",
"framework": "Spring Boot",
"test_tool": "JUnit",
"build_tool": "Gradle"
} | {
"name": "prism-subscription-billing-engine",
"domain": "subscription billing",
"architecture": "modular monolith",
"summary": "A subscription billing repository organized as a modular monolith.",
"file_tree": [
"src/main/java/app/Controller.java",
"src/main/java/app/Service.java",
"src/main/java... | {
"user_request": "A test environment and production-like environment disagree: evidence from the tenant resolver conflicts with assumptions made by the cache key builder, producing hidden acceptance criteria when a fallback code path executes. Work in `prism-subscription-billing-engine`, a modular monolith implement... | {
"core_issue": "The core issue is hidden acceptance criteria: the tenant resolver establishes state using a condition that is only valid on the common path, while the cache key builder consumes that state when a fallback code path executes. The failure becomes observable in the subscription billing workflow because ... | {
"initial_assessment": "This is primarily a `Problem Understanding` task. The agent should first establish whether `hidden acceptance criteria` is a symptom, a root cause, or an underspecified request.",
"assumptions": [
"The issue is limited to the path connecting the tenant resolver and cache key builder; th... | [
{
"type": "premature_patch",
"response": "Immediately rewrite the cache key builder and update every caller without inspecting the repository.",
"why_wrong": "It treats a hypothesis as fact, expands blast radius, and skips evidence and compatibility checks."
},
{
"type": "hallucinated_evidence",... | {
"must_do": [
"Distinguish verified evidence from assumptions.",
"Inspect or reason about the relationship between `src/main/java/app/Controller.java` and `src/main/java/app/Service.java`.",
"Respect all stated constraints.",
"Define a failure-focused verification step.",
"Keep the proposed chang... | [
{
"role": "system",
"content": "You are a software-engineering agent. Ground conclusions in available evidence, use tools deliberately, preserve safety and contracts, and never claim unobserved results."
},
{
"role": "user",
"content": "A test environment and production-like environment disagree... | {
"validation_status": "machine_validated",
"heuristic_score": 97,
"structural_fingerprint": "cf4ee3a283de86acae78f63199b9ce19e2b05972ec3cf0c19786927d4901e4ea",
"user_request_hash": "54b8028c45f3b8b670a94341b9607458b332ce8028f8a074953c0e40c2422ff1",
"record_hash": "a1d528824e871664159d15ef7703926b98c24b009423... |
JF-ASE-003-20 | 1.0.0 | train | {
"family": "problem_understanding",
"family_label": "Problem Understanding",
"archetype": "hidden_acceptance_criteria",
"difficulty": "medium",
"behavior_targets": [
"intent_modeling",
"scope_control",
"assumption_tracking",
"acceptance_criteria"
]
} | {
"language": "Go",
"framework": "Chi",
"test_tool": "go test",
"build_tool": "Go modules"
} | {
"name": "switch-inventory-engine",
"domain": "inventory",
"architecture": "event-driven services",
"summary": "A inventory repository organized as a event-driven services.",
"file_tree": [
"internal/http/routes.go",
"internal/service/core.go",
"internal/store/repository.go",
"internal/worker... | {
"user_request": "A repository handoff highlights one unresolved behavior: a proposed fix for hidden acceptance criteria would broaden scope without first explaining why the failure occurs during cooperative cancellation. Work in `switch-inventory-engine`, a event-driven services implemented with Go and Chi. Focus o... | {
"core_issue": "The core issue is hidden acceptance criteria: the audit logger establishes state using a condition that is only valid on the common path, while the transaction manager consumes that state during cooperative cancellation. The failure becomes observable in the inventory workflow because the two compone... | {
"initial_assessment": "This is primarily a `Problem Understanding` task. The agent should first establish whether `hidden acceptance criteria` is a symptom, a root cause, or an underspecified request.",
"assumptions": [
"The issue is limited to the path connecting the audit logger and transaction manager; thi... | [
{
"type": "premature_patch",
"response": "Immediately rewrite the transaction manager and update every caller without inspecting the repository.",
"why_wrong": "It treats a hypothesis as fact, expands blast radius, and skips evidence and compatibility checks."
},
{
"type": "hallucinated_evidence... | {
"must_do": [
"Distinguish verified evidence from assumptions.",
"Inspect or reason about the relationship between `internal/service/core.go` and `internal/store/repository.go`.",
"Respect all stated constraints.",
"Define a failure-focused verification step.",
"Keep the proposed change bounded a... | [
{
"role": "system",
"content": "You are a software-engineering agent. Ground conclusions in available evidence, use tools deliberately, preserve safety and contracts, and never claim unobserved results."
},
{
"role": "user",
"content": "A repository handoff highlights one unresolved behavior: a ... | {
"validation_status": "machine_validated",
"heuristic_score": 98,
"structural_fingerprint": "1809c25a440473b52ec36071ae1aac504c9569a28dfe0e7565615eacfe707dc6",
"user_request_hash": "fcb0e2983c14566f86405465c038389d9ffc63db32f33b7c2657281abad17342",
"record_hash": "25d65ba10c713f80f5f216be3dbadfbe366580837f13... |
JF-ASE-003-21 | 1.0.0 | train | {
"family": "problem_understanding",
"family_label": "Problem Understanding",
"archetype": "hidden_acceptance_criteria",
"difficulty": "hard",
"behavior_targets": [
"intent_modeling",
"scope_control",
"assumption_tracking",
"acceptance_criteria"
]
} | {
"language": "C#",
"framework": "ASP.NET Core",
"test_tool": "xUnit",
"build_tool": "dotnet"
} | {
"name": "trail-observability-engine",
"domain": "observability",
"architecture": "service-repository application",
"summary": "A observability repository organized as a service-repository application.",
"file_tree": [
"Api/Controllers/WorkflowController.cs",
"Core/WorkflowService.cs",
"Data/Work... | {
"user_request": "A reliability review asks the agent to address a case where a proposed fix for hidden acceptance criteria would broaden scope without first explaining why the failure occurs after a duplicate event delivery. Work in `trail-observability-engine`, a service-repository application implemented with C# ... | {
"core_issue": "The core issue is hidden acceptance criteria: the notification dispatcher establishes state using a condition that is only valid on the common path, while the template renderer consumes that state after a duplicate event delivery. The failure becomes observable in the observability workflow because t... | {
"initial_assessment": "This is primarily a `Problem Understanding` task. The agent should first establish whether `hidden acceptance criteria` is a symptom, a root cause, or an underspecified request.",
"assumptions": [
"The issue is limited to the path connecting the notification dispatcher and template rend... | [
{
"type": "premature_patch",
"response": "Immediately rewrite the template renderer and update every caller without inspecting the repository.",
"why_wrong": "It treats a hypothesis as fact, expands blast radius, and skips evidence and compatibility checks."
},
{
"type": "hallucinated_evidence",... | {
"must_do": [
"Distinguish verified evidence from assumptions.",
"Inspect or reason about the relationship between `Data/WorkflowRepository.cs` and `Workers/EventWorker.cs`.",
"Respect all stated constraints.",
"Define a failure-focused verification step.",
"Keep the proposed change bounded and r... | [
{
"role": "system",
"content": "You are a software-engineering agent. Ground conclusions in available evidence, use tools deliberately, preserve safety and contracts, and never claim unobserved results."
},
{
"role": "user",
"content": "A reliability review asks the agent to address a case where... | {
"validation_status": "machine_validated",
"heuristic_score": 88,
"structural_fingerprint": "5ec3f663d3c2e785fe6d17dc031b0a37230d88ae41181c284b6f52225ea7b637",
"user_request_hash": "9daf6553b36f3060116ece617ac9a99079eff54f58fce521acead33af1606e9a",
"record_hash": "9457dfa2efeb27426ca4a3cc8ae2da94734341b0611d... |
JF-ASE-003-22 | 1.0.0 | train | {
"family": "problem_understanding",
"family_label": "Problem Understanding",
"archetype": "hidden_acceptance_criteria",
"difficulty": "expert",
"behavior_targets": [
"intent_modeling",
"scope_control",
"assumption_tracking",
"acceptance_criteria"
]
} | {
"language": "PHP",
"framework": "Laravel",
"test_tool": "PHPUnit",
"build_tool": "Composer"
} | {
"name": "vector-data-pipelines-engine",
"domain": "data pipelines",
"architecture": "microservice platform",
"summary": "A data pipelines repository organized as a microservice platform.",
"file_tree": [
"routes/api.php",
"app/Http/Controllers/WorkflowController.php",
"app/Services/WorkflowServi... | {
"user_request": "The task appears simple, yet the system context shows that a proposed fix for hidden acceptance criteria would broaden scope without first explaining why the failure occurs with a stale session token. Work in `vector-data-pipelines-engine`, a microservice platform implemented with PHP and Laravel. ... | {
"core_issue": "The core issue is hidden acceptance criteria: the search indexer establishes state using a condition that is only valid on the common path, while the change-data-capture stream consumes that state with a stale session token. The failure becomes observable in the data pipelines workflow because the tw... | {
"initial_assessment": "This is primarily a `Problem Understanding` task. The agent should first establish whether `hidden acceptance criteria` is a symptom, a root cause, or an underspecified request.",
"assumptions": [
"The issue is limited to the path connecting the search indexer and change-data-capture st... | [
{
"type": "premature_patch",
"response": "Immediately rewrite the change-data-capture stream and update every caller without inspecting the repository.",
"why_wrong": "It treats a hypothesis as fact, expands blast radius, and skips evidence and compatibility checks."
},
{
"type": "hallucinated_e... | {
"must_do": [
"Distinguish verified evidence from assumptions.",
"Inspect or reason about the relationship between `app/Repositories/WorkflowRepository.php` and `app/Policies/WorkflowPolicy.php`.",
"Respect all stated constraints.",
"Define a failure-focused verification step.",
"Keep the propose... | [
{
"role": "system",
"content": "You are a software-engineering agent. Ground conclusions in available evidence, use tools deliberately, preserve safety and contracts, and never claim unobserved results."
},
{
"role": "user",
"content": "The task appears simple, yet the system context shows that ... | {
"validation_status": "machine_validated",
"heuristic_score": 89,
"structural_fingerprint": "e4077aa23c90ea05419497effe3d99e4c828925de8480ce6d2efd9efa357fd4c",
"user_request_hash": "fe20c8aed3ddfacc2e8247741c4cfb36d73181e5890d73d6bf642b9deab8a76a",
"record_hash": "fdb3cf95859d83eb04cc850ce90615fb0fdc8347feb2... |
JF-ASE-003-23 | 1.0.0 | train | {
"family": "problem_understanding",
"family_label": "Problem Understanding",
"archetype": "hidden_acceptance_criteria",
"difficulty": "easy",
"behavior_targets": [
"intent_modeling",
"scope_control",
"assumption_tracking",
"acceptance_criteria"
]
} | {
"language": "Rust",
"framework": "Axum",
"test_tool": "cargo test",
"build_tool": "Cargo"
} | {
"name": "watch-feature-management-engine",
"domain": "feature management",
"architecture": "serverless workflow",
"summary": "A feature management repository organized as a serverless workflow.",
"file_tree": [
"src/http/routes.rs",
"src/services/core.rs",
"src/store/repository.rs",
"src/wor... | {
"user_request": "A recent refactor changed the conditions under which hidden acceptance criteria appears in the feature management workflow when configuration is hot-reloaded, and the relationship between the rate limiter and distributed counter is not yet proven. Work in `watch-feature-management-engine`, a server... | {
"core_issue": "The core issue is hidden acceptance criteria: the rate limiter establishes state using a condition that is only valid on the common path, while the distributed counter consumes that state when configuration is hot-reloaded. The failure becomes observable in the feature management workflow because the... | {
"initial_assessment": "This is primarily a `Problem Understanding` task. The agent should first establish whether `hidden acceptance criteria` is a symptom, a root cause, or an underspecified request.",
"assumptions": [
"The issue is limited to the path connecting the rate limiter and distributed counter; thi... | [
{
"type": "premature_patch",
"response": "Immediately rewrite the distributed counter and update every caller without inspecting the repository.",
"why_wrong": "It treats a hypothesis as fact, expands blast radius, and skips evidence and compatibility checks."
},
{
"type": "hallucinated_evidence... | {
"must_do": [
"Distinguish verified evidence from assumptions.",
"Inspect or reason about the relationship between `src/security/policy.rs` and `tests/workflow.rs`.",
"Respect all stated constraints.",
"Define a failure-focused verification step.",
"Keep the proposed change bounded and reversible... | [
{
"role": "system",
"content": "You are a software-engineering agent. Ground conclusions in available evidence, use tools deliberately, preserve safety and contracts, and never claim unobserved results."
},
{
"role": "user",
"content": "A recent refactor changed the conditions under which hidden... | {
"validation_status": "machine_validated",
"heuristic_score": 90,
"structural_fingerprint": "65c0a1f3314b503f916f270aafc68191d760825d681b76f5ca0cd28ea4f715db",
"user_request_hash": "5723f2308de4bd8ade1d3f9737607385499e9afd73c03a8abb80422574968420",
"record_hash": "967cb5ba0365abb4f4d0f5c48009576243518e804dd7... |
JF-ASE-003-24 | 1.0.0 | train | {
"family": "problem_understanding",
"family_label": "Problem Understanding",
"archetype": "hidden_acceptance_criteria",
"difficulty": "medium",
"behavior_targets": [
"intent_modeling",
"scope_control",
"assumption_tracking",
"acceptance_criteria"
]
} | {
"language": "Kotlin",
"framework": "Ktor",
"test_tool": "Kotest",
"build_tool": "Gradle"
} | {
"name": "engine-cybersecurity-operations-engine",
"domain": "cybersecurity operations",
"architecture": "worker-based pipeline",
"summary": "A cybersecurity operations repository organized as a worker-based pipeline.",
"file_tree": [
"src/main/kotlin/app/Routes.kt",
"src/main/kotlin/app/Service.kt",... | {
"user_request": "A security review requires careful handling because evidence from the validation layer conflicts with assumptions made by the normalization pipeline, producing hidden acceptance criteria under high-cardinality traffic. Work in `engine-cybersecurity-operations-engine`, a worker-based pipeline implem... | {
"core_issue": "The core issue is hidden acceptance criteria: the validation layer establishes state using a condition that is only valid on the common path, while the normalization pipeline consumes that state under high-cardinality traffic. The failure becomes observable in the cybersecurity operations workflow be... | {
"initial_assessment": "This is primarily a `Problem Understanding` task. The agent should first establish whether `hidden acceptance criteria` is a symptom, a root cause, or an underspecified request.",
"assumptions": [
"The issue is limited to the path connecting the validation layer and normalization pipeli... | [
{
"type": "premature_patch",
"response": "Immediately rewrite the normalization pipeline and update every caller without inspecting the repository.",
"why_wrong": "It treats a hypothesis as fact, expands blast radius, and skips evidence and compatibility checks."
},
{
"type": "hallucinated_evide... | {
"must_do": [
"Distinguish verified evidence from assumptions.",
"Inspect or reason about the relationship between `src/test/kotlin/app/WorkflowSpec.kt` and `src/main/kotlin/app/Routes.kt`.",
"Respect all stated constraints.",
"Define a failure-focused verification step.",
"Keep the proposed chan... | [
{
"role": "system",
"content": "You are a software-engineering agent. Ground conclusions in available evidence, use tools deliberately, preserve safety and contracts, and never claim unobserved results."
},
{
"role": "user",
"content": "A security review requires careful handling because evidenc... | {
"validation_status": "machine_validated",
"heuristic_score": 91,
"structural_fingerprint": "863c2a3cc84cf572d849eb38a52dce9ecd28fb40acc8bbdf119f7087a02e5969",
"user_request_hash": "0080b0875dd9461aa160f87fed446e7568b8cdabd9c34a8063aefc92785b2d0b",
"record_hash": "9da1f91c9995083178e18d674b926218ba9b1f24759a... |
JF-ASE-003-25 | 1.0.0 | train | {
"family": "problem_understanding",
"family_label": "Problem Understanding",
"archetype": "hidden_acceptance_criteria",
"difficulty": "hard",
"behavior_targets": [
"intent_modeling",
"scope_control",
"assumption_tracking",
"acceptance_criteria"
]
} | {
"language": "Ruby",
"framework": "Rails",
"test_tool": "RSpec",
"build_tool": "Bundler"
} | {
"name": "gateway-workflow-automation-engine",
"domain": "workflow automation",
"architecture": "multi-tenant SaaS",
"summary": "A workflow automation repository organized as a multi-tenant SaaS.",
"file_tree": [
"config/routes.rb",
"app/controllers/workflows_controller.rb",
"app/services/workflo... | {
"user_request": "A release candidate cannot proceed until the agent explains why the team cannot safely complete the workflow automation change because hidden acceptance criteria remains unresolved when a client omits a recently added field. Work in `gateway-workflow-automation-engine`, a multi-tenant SaaS implemen... | {
"core_issue": "The core issue is hidden acceptance criteria: the release orchestrator establishes state using a condition that is only valid on the common path, while the deployment manifest consumes that state when a client omits a recently added field. The failure becomes observable in the workflow automation wor... | {
"initial_assessment": "This is primarily a `Problem Understanding` task. The agent should first establish whether `hidden acceptance criteria` is a symptom, a root cause, or an underspecified request.",
"assumptions": [
"The issue is limited to the path connecting the release orchestrator and deployment manif... | [
{
"type": "premature_patch",
"response": "Immediately rewrite the deployment manifest and update every caller without inspecting the repository.",
"why_wrong": "It treats a hypothesis as fact, expands blast radius, and skips evidence and compatibility checks."
},
{
"type": "hallucinated_evidence... | {
"must_do": [
"Distinguish verified evidence from assumptions.",
"Inspect or reason about the relationship between `config/routes.rb` and `app/controllers/workflows_controller.rb`.",
"Respect all stated constraints.",
"Define a failure-focused verification step.",
"Keep the proposed change bounde... | [
{
"role": "system",
"content": "You are a software-engineering agent. Ground conclusions in available evidence, use tools deliberately, preserve safety and contracts, and never claim unobserved results."
},
{
"role": "user",
"content": "A release candidate cannot proceed until the agent explains... | {
"validation_status": "machine_validated",
"heuristic_score": 92,
"structural_fingerprint": "bdd4729087526d7fe6e5f44c7684b98497187669cabe184b464c0d2d91b9b42f",
"user_request_hash": "11a3bd0e283c8d95c79ab5dcf0368b6999e78fd1fb592f758018b36297a0109a",
"record_hash": "19b7775b30e8c7430f66f548df32b3a2395fa0a87438... |
JF-ASE-004-01 | 1.0.0 | train | {
"family": "problem_understanding",
"family_label": "Problem Understanding",
"archetype": "non_reproducible_report",
"difficulty": "expert",
"behavior_targets": [
"intent_modeling",
"scope_control",
"assumption_tracking",
"acceptance_criteria"
]
} | {
"language": "TypeScript",
"framework": "React",
"test_tool": "Playwright",
"build_tool": "Vite"
} | {
"name": "ledger-payments-gateway",
"domain": "payments",
"architecture": "microservice platform",
"summary": "A payments repository organized as a microservice platform.",
"file_tree": [
"src/app/router.tsx",
"src/features/state.ts",
"src/api/client.ts",
"src/components/Workflow.tsx",
"s... | {
"user_request": "A support escalation reports non reproducible report appears in the payments workflow after a warm-cache transition, and the relationship between the request router and domain service is not yet proven. Work in `ledger-payments-gateway`, a microservice platform implemented with TypeScript and React... | {
"core_issue": "The core issue is non reproducible report: the request router establishes state using a condition that is only valid on the common path, while the domain service consumes that state after a warm-cache transition. The failure becomes observable in the payments workflow because the two components disag... | {
"initial_assessment": "This is primarily a `Problem Understanding` task. The agent should first establish whether `non reproducible report` is a symptom, a root cause, or an underspecified request.",
"assumptions": [
"The issue is limited to the path connecting the request router and domain service; this rema... | [
{
"type": "premature_patch",
"response": "Immediately rewrite the domain service and update every caller without inspecting the repository.",
"why_wrong": "It treats a hypothesis as fact, expands blast radius, and skips evidence and compatibility checks."
},
{
"type": "hallucinated_evidence",
... | {
"must_do": [
"Distinguish verified evidence from assumptions.",
"Inspect or reason about the relationship between `src/app/router.tsx` and `src/features/state.ts`.",
"Respect all stated constraints.",
"Define a failure-focused verification step.",
"Keep the proposed change bounded and reversible... | [
{
"role": "system",
"content": "You are a software-engineering agent. Ground conclusions in available evidence, use tools deliberately, preserve safety and contracts, and never claim unobserved results."
},
{
"role": "user",
"content": "A support escalation reports non reproducible report appear... | {
"validation_status": "machine_validated",
"heuristic_score": 91,
"structural_fingerprint": "1ee717383e98756f0f044b6fc2ca51026753dcf598cea56349dfa42a1098e9e2",
"user_request_hash": "2efd9a43916df0e160d93484d5d14ae884520501d14b9c0cf323445f3943dc4c",
"record_hash": "3f3498c5477c4c90b5db699e60dc24d8fe1bb13d1c6c... |
JF-ASE-004-02 | 1.0.0 | train | {
"family": "problem_understanding",
"family_label": "Problem Understanding",
"archetype": "non_reproducible_report",
"difficulty": "easy",
"behavior_targets": [
"intent_modeling",
"scope_control",
"assumption_tracking",
"acceptance_criteria"
]
} | {
"language": "Java",
"framework": "Spring Boot",
"test_tool": "JUnit",
"build_tool": "Gradle"
} | {
"name": "relay-healthcare-scheduling-gateway",
"domain": "healthcare scheduling",
"architecture": "serverless workflow",
"summary": "A healthcare scheduling repository organized as a serverless workflow.",
"file_tree": [
"src/main/java/app/Controller.java",
"src/main/java/app/Service.java",
"src... | {
"user_request": "An engineer observed a proposed fix for non reproducible report would broaden scope without first explaining why the failure occurs under two concurrent requests. Work in `relay-healthcare-scheduling-gateway`, a serverless workflow implemented with Java and Spring Boot. Focus on the agent behavior ... | {
"core_issue": "The core issue is non reproducible report: the API handler establishes state using a condition that is only valid on the common path, while the repository adapter consumes that state under two concurrent requests. The failure becomes observable in the healthcare scheduling workflow because the two co... | {
"initial_assessment": "This is primarily a `Problem Understanding` task. The agent should first establish whether `non reproducible report` is a symptom, a root cause, or an underspecified request.",
"assumptions": [
"The issue is limited to the path connecting the API handler and repository adapter; this rem... | [
{
"type": "premature_patch",
"response": "Immediately rewrite the repository adapter and update every caller without inspecting the repository.",
"why_wrong": "It treats a hypothesis as fact, expands blast radius, and skips evidence and compatibility checks."
},
{
"type": "hallucinated_evidence"... | {
"must_do": [
"Distinguish verified evidence from assumptions.",
"Inspect or reason about the relationship between `src/main/java/app/Service.java` and `src/main/java/app/Repository.java`.",
"Respect all stated constraints.",
"Define a failure-focused verification step.",
"Keep the proposed chang... | [
{
"role": "system",
"content": "You are a software-engineering agent. Ground conclusions in available evidence, use tools deliberately, preserve safety and contracts, and never claim unobserved results."
},
{
"role": "user",
"content": "An engineer observed a proposed fix for non reproducible re... | {
"validation_status": "machine_validated",
"heuristic_score": 92,
"structural_fingerprint": "1ff81901ed0ece94d2ee0633f553779ba73345b8ddf561cc0bc3edf20b819451",
"user_request_hash": "a25c95e1ac5deaee60977e4f54e73ef7c0455604d0130b2815557a5886c716c9",
"record_hash": "6456838b1c00c8f3f1d3a31e0c5b8bc708f83ee48ce0... |
JF-ASE-004-03 | 1.0.0 | train | {
"family": "problem_understanding",
"family_label": "Problem Understanding",
"archetype": "non_reproducible_report",
"difficulty": "medium",
"behavior_targets": [
"intent_modeling",
"scope_control",
"assumption_tracking",
"acceptance_criteria"
]
} | {
"language": "Go",
"framework": "Chi",
"test_tool": "go test",
"build_tool": "Go modules"
} | {
"name": "atlas-developer-tooling-gateway",
"domain": "developer tooling",
"architecture": "worker-based pipeline",
"summary": "A developer tooling repository organized as a worker-based pipeline.",
"file_tree": [
"internal/http/routes.go",
"internal/service/core.go",
"internal/store/repository.g... | {
"user_request": "The latest release exposed a pattern: evidence from the background worker conflicts with assumptions made by the event consumer, producing non reproducible report during a rolling deployment. Work in `atlas-developer-tooling-gateway`, a worker-based pipeline implemented with Go and Chi. Focus on th... | {
"core_issue": "The core issue is non reproducible report: the background worker establishes state using a condition that is only valid on the common path, while the event consumer consumes that state during a rolling deployment. The failure becomes observable in the developer tooling workflow because the two compon... | {
"initial_assessment": "This is primarily a `Problem Understanding` task. The agent should first establish whether `non reproducible report` is a symptom, a root cause, or an underspecified request.",
"assumptions": [
"The issue is limited to the path connecting the background worker and event consumer; this r... | [
{
"type": "premature_patch",
"response": "Immediately rewrite the event consumer and update every caller without inspecting the repository.",
"why_wrong": "It treats a hypothesis as fact, expands blast radius, and skips evidence and compatibility checks."
},
{
"type": "hallucinated_evidence",
... | {
"must_do": [
"Distinguish verified evidence from assumptions.",
"Inspect or reason about the relationship between `internal/store/repository.go` and `internal/worker/consumer.go`.",
"Respect all stated constraints.",
"Define a failure-focused verification step.",
"Keep the proposed change bounde... | [
{
"role": "system",
"content": "You are a software-engineering agent. Ground conclusions in available evidence, use tools deliberately, preserve safety and contracts, and never claim unobserved results."
},
{
"role": "user",
"content": "The latest release exposed a pattern: evidence from the bac... | {
"validation_status": "machine_validated",
"heuristic_score": 93,
"structural_fingerprint": "24fd8b666712a7335a220270f627b59e82d1e9795f7f0f11de9758466fb44e65",
"user_request_hash": "758177528e088b89005cca8618da73858e7ad9693b59f1178a06f0277db3a18b",
"record_hash": "cd7aa7adff861ebb16988d57a766f640ea86d6995f5d... |
JF-ASE-004-04 | 1.0.0 | train | {
"family": "problem_understanding",
"family_label": "Problem Understanding",
"archetype": "non_reproducible_report",
"difficulty": "hard",
"behavior_targets": [
"intent_modeling",
"scope_control",
"assumption_tracking",
"acceptance_criteria"
]
} | {
"language": "C#",
"framework": "ASP.NET Core",
"test_tool": "xUnit",
"build_tool": "dotnet"
} | {
"name": "harbor-identity-management-gateway",
"domain": "identity management",
"architecture": "multi-tenant SaaS",
"summary": "A identity management repository organized as a multi-tenant SaaS.",
"file_tree": [
"Api/Controllers/WorkflowController.cs",
"Core/WorkflowService.cs",
"Data/WorkflowRe... | {
"user_request": "A reproducible test now shows the identity management system behaves correctly in the common path but exposes non reproducible report at a daylight-saving boundary. Work in `harbor-identity-management-gateway`, a multi-tenant SaaS implemented with C# and ASP.NET Core. Focus on the agent behavior re... | {
"core_issue": "The core issue is non reproducible report: the session middleware establishes state using a condition that is only valid on the common path, while the identity store consumes that state at a daylight-saving boundary. The failure becomes observable in the identity management workflow because the two c... | {
"initial_assessment": "This is primarily a `Problem Understanding` task. The agent should first establish whether `non reproducible report` is a symptom, a root cause, or an underspecified request.",
"assumptions": [
"The issue is limited to the path connecting the session middleware and identity store; this ... | [
{
"type": "premature_patch",
"response": "Immediately rewrite the identity store and update every caller without inspecting the repository.",
"why_wrong": "It treats a hypothesis as fact, expands blast radius, and skips evidence and compatibility checks."
},
{
"type": "hallucinated_evidence",
... | {
"must_do": [
"Distinguish verified evidence from assumptions.",
"Inspect or reason about the relationship between `Workers/EventWorker.cs` and `Security/AuthorizationPolicy.cs`.",
"Respect all stated constraints.",
"Define a failure-focused verification step.",
"Keep the proposed change bounded ... | [
{
"role": "system",
"content": "You are a software-engineering agent. Ground conclusions in available evidence, use tools deliberately, preserve safety and contracts, and never claim unobserved results."
},
{
"role": "user",
"content": "A reproducible test now shows the identity management syste... | {
"validation_status": "machine_validated",
"heuristic_score": 94,
"structural_fingerprint": "e6fcceb8d03438fe53d85eaa0ff8a00916f0157d790e0dd590f3ef641e31f12e",
"user_request_hash": "ec761fc9d2761eb4d299b78514d7390f9e6baba06158bb5d495de28f7d5f6176",
"record_hash": "689210ac519c8fe185ef566db6973509bb8734d689ee... |
JF-ASE-004-05 | 1.0.0 | train | {
"family": "problem_understanding",
"family_label": "Problem Understanding",
"archetype": "non_reproducible_report",
"difficulty": "expert",
"behavior_targets": [
"intent_modeling",
"scope_control",
"assumption_tracking",
"acceptance_criteria"
]
} | {
"language": "PHP",
"framework": "Laravel",
"test_tool": "PHPUnit",
"build_tool": "Composer"
} | {
"name": "forge-e-commerce-gateway",
"domain": "e-commerce",
"architecture": "API gateway architecture",
"summary": "A e-commerce repository organized as a API gateway architecture.",
"file_tree": [
"routes/api.php",
"app/Http/Controllers/WorkflowController.php",
"app/Services/WorkflowService.php... | {
"user_request": "Operational telemetry suggests a proposed fix for non reproducible report would broaden scope without first explaining why the failure occurs when retries overlap. Work in `forge-e-commerce-gateway`, a API gateway architecture implemented with PHP and Laravel. Focus on the agent behavior required f... | {
"core_issue": "The core issue is non reproducible report: the cache layer establishes state using a condition that is only valid on the common path, while the database gateway consumes that state when retries overlap. The failure becomes observable in the e-commerce workflow because the two components disagree abou... | {
"initial_assessment": "This is primarily a `Problem Understanding` task. The agent should first establish whether `non reproducible report` is a symptom, a root cause, or an underspecified request.",
"assumptions": [
"The issue is limited to the path connecting the cache layer and database gateway; this remai... | [
{
"type": "premature_patch",
"response": "Immediately rewrite the database gateway and update every caller without inspecting the repository.",
"why_wrong": "It treats a hypothesis as fact, expands blast radius, and skips evidence and compatibility checks."
},
{
"type": "hallucinated_evidence",
... | {
"must_do": [
"Distinguish verified evidence from assumptions.",
"Inspect or reason about the relationship between `app/Policies/WorkflowPolicy.php` and `tests/Feature/WorkflowTest.php`.",
"Respect all stated constraints.",
"Define a failure-focused verification step.",
"Keep the proposed change ... | [
{
"role": "system",
"content": "You are a software-engineering agent. Ground conclusions in available evidence, use tools deliberately, preserve safety and contracts, and never claim unobserved results."
},
{
"role": "user",
"content": "Operational telemetry suggests a proposed fix for non repro... | {
"validation_status": "machine_validated",
"heuristic_score": 95,
"structural_fingerprint": "60ef4ef0f8445ec8b63975f0d9de2462d745dab32a017292685006dd265eff54",
"user_request_hash": "0abd68d50ddfc6837ff00dc26d134b6620a118169b39dcce691ee53fa8aa05c2",
"record_hash": "2d9e8923f84a919d78cfa832566f59ca335a3fb9e392... |
JF-ASE-004-06 | 1.0.0 | train | {
"family": "problem_understanding",
"family_label": "Problem Understanding",
"archetype": "non_reproducible_report",
"difficulty": "easy",
"behavior_targets": [
"intent_modeling",
"scope_control",
"assumption_tracking",
"acceptance_criteria"
]
} | {
"language": "Rust",
"framework": "Axum",
"test_tool": "cargo test",
"build_tool": "Cargo"
} | {
"name": "signal-logistics-gateway",
"domain": "logistics",
"architecture": "batch processing system",
"summary": "A logistics repository organized as a batch processing system.",
"file_tree": [
"src/http/routes.rs",
"src/services/core.rs",
"src/store/repository.rs",
"src/workers/consumer.rs"... | {
"user_request": "A code review uncovered a risk: non reproducible report appears in the logistics workflow with legacy records created before the last migration, and the relationship between the scheduler and job executor is not yet proven. Work in `signal-logistics-gateway`, a batch processing system implemented w... | {
"core_issue": "The core issue is non reproducible report: the scheduler establishes state using a condition that is only valid on the common path, while the job executor consumes that state with legacy records created before the last migration. The failure becomes observable in the logistics workflow because the tw... | {
"initial_assessment": "This is primarily a `Problem Understanding` task. The agent should first establish whether `non reproducible report` is a symptom, a root cause, or an underspecified request.",
"assumptions": [
"The issue is limited to the path connecting the scheduler and job executor; this remains a h... | [
{
"type": "premature_patch",
"response": "Immediately rewrite the job executor and update every caller without inspecting the repository.",
"why_wrong": "It treats a hypothesis as fact, expands blast radius, and skips evidence and compatibility checks."
},
{
"type": "hallucinated_evidence",
... | {
"must_do": [
"Distinguish verified evidence from assumptions.",
"Inspect or reason about the relationship between `tests/workflow.rs` and `src/http/routes.rs`.",
"Respect all stated constraints.",
"Define a failure-focused verification step.",
"Keep the proposed change bounded and reversible."
... | [
{
"role": "system",
"content": "You are a software-engineering agent. Ground conclusions in available evidence, use tools deliberately, preserve safety and contracts, and never claim unobserved results."
},
{
"role": "user",
"content": "A code review uncovered a risk: non reproducible report app... | {
"validation_status": "machine_validated",
"heuristic_score": 96,
"structural_fingerprint": "08503ef75fdd0cae1b45e6ae42d9b9e2f903cc3ab697c0102e90f8003ba41c1d",
"user_request_hash": "a7c4da218551bf51f797fb503ff4e00ae59b6aa0746eaf36a3555e9518d89f01",
"record_hash": "4a05cd7983cefe3b437767c153b4e5aa317783fe8499... |
JF-ASE-004-07 | 1.0.0 | train | {
"family": "problem_understanding",
"family_label": "Problem Understanding",
"archetype": "non_reproducible_report",
"difficulty": "medium",
"behavior_targets": [
"intent_modeling",
"scope_control",
"assumption_tracking",
"acceptance_criteria"
]
} | {
"language": "Kotlin",
"framework": "Ktor",
"test_tool": "Kotest",
"build_tool": "Gradle"
} | {
"name": "orbit-collaboration-software-gateway",
"domain": "collaboration software",
"architecture": "plugin-oriented application",
"summary": "A collaboration software repository organized as a plugin-oriented application.",
"file_tree": [
"src/main/kotlin/app/Routes.kt",
"src/main/kotlin/app/Servic... | {
"user_request": "The team needs a grounded investigation because non reproducible report appears in the collaboration software workflow immediately after a feature flag changes, and the relationship between the serializer and public API contract is not yet proven. Work in `orbit-collaboration-software-gateway`, a p... | {
"core_issue": "The core issue is non reproducible report: the serializer establishes state using a condition that is only valid on the common path, while the public API contract consumes that state immediately after a feature flag changes. The failure becomes observable in the collaboration software workflow becaus... | {
"initial_assessment": "This is primarily a `Problem Understanding` task. The agent should first establish whether `non reproducible report` is a symptom, a root cause, or an underspecified request.",
"assumptions": [
"The issue is limited to the path connecting the serializer and public API contract; this rem... | [
{
"type": "premature_patch",
"response": "Immediately rewrite the public API contract and update every caller without inspecting the repository.",
"why_wrong": "It treats a hypothesis as fact, expands blast radius, and skips evidence and compatibility checks."
},
{
"type": "hallucinated_evidence... | {
"must_do": [
"Distinguish verified evidence from assumptions.",
"Inspect or reason about the relationship between `src/main/kotlin/app/Routes.kt` and `src/main/kotlin/app/Service.kt`.",
"Respect all stated constraints.",
"Define a failure-focused verification step.",
"Keep the proposed change bo... | [
{
"role": "system",
"content": "You are a software-engineering agent. Ground conclusions in available evidence, use tools deliberately, preserve safety and contracts, and never claim unobserved results."
},
{
"role": "user",
"content": "The team needs a grounded investigation because non reprodu... | {
"validation_status": "machine_validated",
"heuristic_score": 97,
"structural_fingerprint": "8a5b0e5b664d41bc927278b2b027934d4b66eb047e0ba2561f3ff37ccde9ff51",
"user_request_hash": "be8cc6ccaf596397fd9b5b0d3794f4a4779c568f91f366658266eb4723588bbc",
"record_hash": "a2e9aa39a33eaaa3366379fb98a1ea163c872ade2afd... |
JF-ASE-004-08 | 1.0.0 | train | {
"family": "problem_understanding",
"family_label": "Problem Understanding",
"archetype": "non_reproducible_report",
"difficulty": "hard",
"behavior_targets": [
"intent_modeling",
"scope_control",
"assumption_tracking",
"acceptance_criteria"
]
} | {
"language": "Ruby",
"framework": "Rails",
"test_tool": "RSpec",
"build_tool": "Bundler"
} | {
"name": "bridge-analytics-gateway",
"domain": "analytics",
"architecture": "modular monolith",
"summary": "A analytics repository organized as a modular monolith.",
"file_tree": [
"config/routes.rb",
"app/controllers/workflows_controller.rb",
"app/services/workflow_service.rb",
"app/models/w... | {
"user_request": "A customer-facing workflow intermittently exhibits this behavior: the team cannot safely complete the analytics change because non reproducible report remains unresolved during a partial network failure. Work in `bridge-analytics-gateway`, a modular monolith implemented with Ruby and Rails. Focus o... | {
"core_issue": "The core issue is non reproducible report: the migration runner establishes state using a condition that is only valid on the common path, while the schema registry consumes that state during a partial network failure. The failure becomes observable in the analytics workflow because the two component... | {
"initial_assessment": "This is primarily a `Problem Understanding` task. The agent should first establish whether `non reproducible report` is a symptom, a root cause, or an underspecified request.",
"assumptions": [
"The issue is limited to the path connecting the migration runner and schema registry; this r... | [
{
"type": "premature_patch",
"response": "Immediately rewrite the schema registry and update every caller without inspecting the repository.",
"why_wrong": "It treats a hypothesis as fact, expands blast radius, and skips evidence and compatibility checks."
},
{
"type": "hallucinated_evidence",
... | {
"must_do": [
"Distinguish verified evidence from assumptions.",
"Inspect or reason about the relationship between `app/controllers/workflows_controller.rb` and `app/services/workflow_service.rb`.",
"Respect all stated constraints.",
"Define a failure-focused verification step.",
"Keep the propos... | [
{
"role": "system",
"content": "You are a software-engineering agent. Ground conclusions in available evidence, use tools deliberately, preserve safety and contracts, and never claim unobserved results."
},
{
"role": "user",
"content": "A customer-facing workflow intermittently exhibits this beh... | {
"validation_status": "machine_validated",
"heuristic_score": 98,
"structural_fingerprint": "3ff5f326ea1a9d37d21aaf2f232b616b547a1468bb12a03f079e99de02a4480a",
"user_request_hash": "886d4f550cdaa23e8046bd7410fae065b36f717da1647b9e1d078721df26d80e",
"record_hash": "d51b9b232da85b1a61c5b4f82c10beb14f90226cc8fc... |
JF-ASE-004-09 | 1.0.0 | train | {
"family": "problem_understanding",
"family_label": "Problem Understanding",
"archetype": "non_reproducible_report",
"difficulty": "expert",
"behavior_targets": [
"intent_modeling",
"scope_control",
"assumption_tracking",
"acceptance_criteria"
]
} | {
"language": "C++",
"framework": "CMake service",
"test_tool": "Catch2",
"build_tool": "CMake"
} | {
"name": "vault-education-technology-gateway",
"domain": "education technology",
"architecture": "event-driven services",
"summary": "A education technology repository organized as a event-driven services.",
"file_tree": [
"src/http/routes.cpp",
"src/core/workflow.cpp",
"src/data/repository.cpp",... | {
"user_request": "During validation, the system revealed that the team cannot safely complete the education technology change because non reproducible report remains unresolved after switching tenants in the same browser session. Work in `vault-education-technology-gateway`, a event-driven services implemented with ... | {
"core_issue": "The core issue is non reproducible report: the feature-flag client establishes state using a condition that is only valid on the common path, while the configuration service consumes that state after switching tenants in the same browser session. The failure becomes observable in the education techno... | {
"initial_assessment": "This is primarily a `Problem Understanding` task. The agent should first establish whether `non reproducible report` is a symptom, a root cause, or an underspecified request.",
"assumptions": [
"The issue is limited to the path connecting the feature-flag client and configuration servic... | [
{
"type": "premature_patch",
"response": "Immediately rewrite the configuration service and update every caller without inspecting the repository.",
"why_wrong": "It treats a hypothesis as fact, expands blast radius, and skips evidence and compatibility checks."
},
{
"type": "hallucinated_eviden... | {
"must_do": [
"Distinguish verified evidence from assumptions.",
"Inspect or reason about the relationship between `src/data/repository.cpp` and `src/workers/consumer.cpp`.",
"Respect all stated constraints.",
"Define a failure-focused verification step.",
"Keep the proposed change bounded and re... | [
{
"role": "system",
"content": "You are a software-engineering agent. Ground conclusions in available evidence, use tools deliberately, preserve safety and contracts, and never claim unobserved results."
},
{
"role": "user",
"content": "During validation, the system revealed that the team cannot... | {
"validation_status": "machine_validated",
"heuristic_score": 88,
"structural_fingerprint": "33426dee6c542507b771c87b8d83fdd0eebcd1a943ef056ec2679a674bf27b1e",
"user_request_hash": "f706aa60e3a2111c3ef165668d36036a294e0bf068f540a6e76d8082be8b6d16",
"record_hash": "893be89531d9dfa286a57f65b9f61efa454e98006004... |
JF-ASE-004-10 | 1.0.0 | train | {
"family": "problem_understanding",
"family_label": "Problem Understanding",
"archetype": "non_reproducible_report",
"difficulty": "easy",
"behavior_targets": [
"intent_modeling",
"scope_control",
"assumption_tracking",
"acceptance_criteria"
]
} | {
"language": "Python",
"framework": "FastAPI",
"test_tool": "pytest",
"build_tool": "uv"
} | {
"name": "stream-media-processing-gateway",
"domain": "media processing",
"architecture": "service-repository application",
"summary": "A media processing repository organized as a service-repository application.",
"file_tree": [
"app/api/routes.py",
"app/services/core.py",
"app/repositories/stor... | {
"user_request": "A maintenance task became unsafe after reviewers noticed the team cannot safely complete the media processing change because non reproducible report remains unresolved following a dependency upgrade. Work in `stream-media-processing-gateway`, a service-repository application implemented with Python... | {
"core_issue": "The core issue is non reproducible report: the authorization policy establishes state using a condition that is only valid on the common path, while the resource loader consumes that state following a dependency upgrade. The failure becomes observable in the media processing workflow because the two ... | {
"initial_assessment": "This is primarily a `Problem Understanding` task. The agent should first establish whether `non reproducible report` is a symptom, a root cause, or an underspecified request.",
"assumptions": [
"The issue is limited to the path connecting the authorization policy and resource loader; th... | [
{
"type": "premature_patch",
"response": "Immediately rewrite the resource loader and update every caller without inspecting the repository.",
"why_wrong": "It treats a hypothesis as fact, expands blast radius, and skips evidence and compatibility checks."
},
{
"type": "hallucinated_evidence",
... | {
"must_do": [
"Distinguish verified evidence from assumptions.",
"Inspect or reason about the relationship between `app/workers/events.py` and `app/security/policy.py`.",
"Respect all stated constraints.",
"Define a failure-focused verification step.",
"Keep the proposed change bounded and revers... | [
{
"role": "system",
"content": "You are a software-engineering agent. Ground conclusions in available evidence, use tools deliberately, preserve safety and contracts, and never claim unobserved results."
},
{
"role": "user",
"content": "A maintenance task became unsafe after reviewers noticed th... | {
"validation_status": "machine_validated",
"heuristic_score": 89,
"structural_fingerprint": "2381128c5ad0307dcaa620d05dcff8d5f013a245b66c84121b3bb8fe0d2e4972",
"user_request_hash": "319ddda67ad00d2347a9edef3e5e0ebbf7a93fa06bce73cbaf36b9154f19799e",
"record_hash": "bc15965fbbcc121d0a512a4f1c5cee6feca8f93cdc46... |
JF-ASE-004-11 | 1.0.0 | train | {
"family": "problem_understanding",
"family_label": "Problem Understanding",
"archetype": "non_reproducible_report",
"difficulty": "medium",
"behavior_targets": [
"intent_modeling",
"scope_control",
"assumption_tracking",
"acceptance_criteria"
]
} | {
"language": "Python",
"framework": "Django",
"test_tool": "pytest-django",
"build_tool": "pip"
} | {
"name": "pilot-cloud-infrastructure-gateway",
"domain": "cloud infrastructure",
"architecture": "microservice platform",
"summary": "A cloud infrastructure repository organized as a microservice platform.",
"file_tree": [
"project/urls.py",
"app/views.py",
"app/services.py",
"app/models.py",... | {
"user_request": "The repository owner asks for help with a case where the cloud infrastructure system behaves correctly in the common path but exposes non reproducible report near the end of a paginated result set. Work in `pilot-cloud-infrastructure-gateway`, a microservice platform implemented with Python and Dja... | {
"core_issue": "The core issue is non reproducible report: the message producer establishes state using a condition that is only valid on the common path, while the idempotency store consumes that state near the end of a paginated result set. The failure becomes observable in the cloud infrastructure workflow becaus... | {
"initial_assessment": "This is primarily a `Problem Understanding` task. The agent should first establish whether `non reproducible report` is a symptom, a root cause, or an underspecified request.",
"assumptions": [
"The issue is limited to the path connecting the message producer and idempotency store; this... | [
{
"type": "premature_patch",
"response": "Immediately rewrite the idempotency store and update every caller without inspecting the repository.",
"why_wrong": "It treats a hypothesis as fact, expands blast radius, and skips evidence and compatibility checks."
},
{
"type": "hallucinated_evidence",... | {
"must_do": [
"Distinguish verified evidence from assumptions.",
"Inspect or reason about the relationship between `app/middleware.py` and `tests/test_workflow.py`.",
"Respect all stated constraints.",
"Define a failure-focused verification step.",
"Keep the proposed change bounded and reversible... | [
{
"role": "system",
"content": "You are a software-engineering agent. Ground conclusions in available evidence, use tools deliberately, preserve safety and contracts, and never claim unobserved results."
},
{
"role": "user",
"content": "The repository owner asks for help with a case where the cl... | {
"validation_status": "machine_validated",
"heuristic_score": 90,
"structural_fingerprint": "fd12ad64a722118d434a96fd5ad619c2f0225a1ff9e51c44e193e9502e0c815e",
"user_request_hash": "77ac3eb9a7cbce665765763b8ea1403e2ec81f36525ea7dcb787fc953857464f",
"record_hash": "21047c4a0dde2e78d293d43128154376b7b3ca412e3e... |
JF-ASE-004-12 | 1.0.0 | train | {
"family": "problem_understanding",
"family_label": "Problem Understanding",
"archetype": "non_reproducible_report",
"difficulty": "hard",
"behavior_targets": [
"intent_modeling",
"scope_control",
"assumption_tracking",
"acceptance_criteria"
]
} | {
"language": "TypeScript",
"framework": "Node.js",
"test_tool": "Vitest",
"build_tool": "pnpm"
} | {
"name": "mesh-customer-support-gateway",
"domain": "customer support",
"architecture": "serverless workflow",
"summary": "A customer support repository organized as a serverless workflow.",
"file_tree": [
"src/http/routes.ts",
"src/services/core.ts",
"src/data/repository.ts",
"src/workers/co... | {
"user_request": "A rollout checkpoint failed because a proposed fix for non reproducible report would broaden scope without first explaining why the failure occurs when the payload contains an empty optional field. Work in `mesh-customer-support-gateway`, a serverless workflow implemented with TypeScript and Node.j... | {
"core_issue": "The core issue is non reproducible report: the upload controller establishes state using a condition that is only valid on the common path, while the object storage adapter consumes that state when the payload contains an empty optional field. The failure becomes observable in the customer support wo... | {
"initial_assessment": "This is primarily a `Problem Understanding` task. The agent should first establish whether `non reproducible report` is a symptom, a root cause, or an underspecified request.",
"assumptions": [
"The issue is limited to the path connecting the upload controller and object storage adapter... | [
{
"type": "premature_patch",
"response": "Immediately rewrite the object storage adapter and update every caller without inspecting the repository.",
"why_wrong": "It treats a hypothesis as fact, expands blast radius, and skips evidence and compatibility checks."
},
{
"type": "hallucinated_evide... | {
"must_do": [
"Distinguish verified evidence from assumptions.",
"Inspect or reason about the relationship between `test/workflow.test.ts` and `src/http/routes.ts`.",
"Respect all stated constraints.",
"Define a failure-focused verification step.",
"Keep the proposed change bounded and reversible... | [
{
"role": "system",
"content": "You are a software-engineering agent. Ground conclusions in available evidence, use tools deliberately, preserve safety and contracts, and never claim unobserved results."
},
{
"role": "user",
"content": "A rollout checkpoint failed because a proposed fix for non ... | {
"validation_status": "machine_validated",
"heuristic_score": 91,
"structural_fingerprint": "affb7e2c118519a94a6031461051f1c7567d382544f94016c60a525a1875e08a",
"user_request_hash": "8a2411898c53b88f87f6fcf9f10daf3494dadf01c6513f79331813609fb11b5d",
"record_hash": "da6dae984a7e52123341a9e1574d81477abc842672ca... |
JF-ASE-004-13 | 1.0.0 | train | {
"family": "problem_understanding",
"family_label": "Problem Understanding",
"archetype": "non_reproducible_report",
"difficulty": "expert",
"behavior_targets": [
"intent_modeling",
"scope_control",
"assumption_tracking",
"acceptance_criteria"
]
} | {
"language": "TypeScript",
"framework": "React",
"test_tool": "Playwright",
"build_tool": "Vite"
} | {
"name": "beacon-document-management-gateway",
"domain": "document management",
"architecture": "worker-based pipeline",
"summary": "A document management repository organized as a worker-based pipeline.",
"file_tree": [
"src/app/router.tsx",
"src/features/state.ts",
"src/api/client.ts",
"src... | {
"user_request": "An incident follow-up points to a scenario in which non reproducible report appears in the document management workflow after a worker restarts, and the relationship between the webhook receiver and retry coordinator is not yet proven. Work in `beacon-document-management-gateway`, a worker-based pi... | {
"core_issue": "The core issue is non reproducible report: the webhook receiver establishes state using a condition that is only valid on the common path, while the retry coordinator consumes that state after a worker restarts. The failure becomes observable in the document management workflow because the two compon... | {
"initial_assessment": "This is primarily a `Problem Understanding` task. The agent should first establish whether `non reproducible report` is a symptom, a root cause, or an underspecified request.",
"assumptions": [
"The issue is limited to the path connecting the webhook receiver and retry coordinator; this... | [
{
"type": "premature_patch",
"response": "Immediately rewrite the retry coordinator and update every caller without inspecting the repository.",
"why_wrong": "It treats a hypothesis as fact, expands blast radius, and skips evidence and compatibility checks."
},
{
"type": "hallucinated_evidence",... | {
"must_do": [
"Distinguish verified evidence from assumptions.",
"Inspect or reason about the relationship between `src/app/router.tsx` and `src/features/state.ts`.",
"Respect all stated constraints.",
"Define a failure-focused verification step.",
"Keep the proposed change bounded and reversible... | [
{
"role": "system",
"content": "You are a software-engineering agent. Ground conclusions in available evidence, use tools deliberately, preserve safety and contracts, and never claim unobserved results."
},
{
"role": "user",
"content": "An incident follow-up points to a scenario in which non rep... | {
"validation_status": "machine_validated",
"heuristic_score": 92,
"structural_fingerprint": "117cd8a9605f64d5699eb604d020136861b779ee79b4f5aea26cc6100ccf0915",
"user_request_hash": "9a6e1e2d2d843e9fe6163d219e1d988586929da403e956f468548d34dfa6cb6a",
"record_hash": "569a5e376fe0f7ef444df499e82f8847be417722ef19... |
JF-ASE-004-14 | 1.0.0 | train | {
"family": "problem_understanding",
"family_label": "Problem Understanding",
"archetype": "non_reproducible_report",
"difficulty": "easy",
"behavior_targets": [
"intent_modeling",
"scope_control",
"assumption_tracking",
"acceptance_criteria"
]
} | {
"language": "Java",
"framework": "Spring Boot",
"test_tool": "JUnit",
"build_tool": "Gradle"
} | {
"name": "kernel-iot-operations-gateway",
"domain": "IoT operations",
"architecture": "multi-tenant SaaS",
"summary": "A IoT operations repository organized as a multi-tenant SaaS.",
"file_tree": [
"src/main/java/app/Controller.java",
"src/main/java/app/Service.java",
"src/main/java/app/Repositor... | {
"user_request": "A pre-release audit found that the team cannot safely complete the IoT operations change because non reproducible report remains unresolved while the queue is under backpressure. Work in `kernel-iot-operations-gateway`, a multi-tenant SaaS implemented with Java and Spring Boot. Focus on the agent b... | {
"core_issue": "The core issue is non reproducible report: the query builder establishes state using a condition that is only valid on the common path, while the pagination layer consumes that state while the queue is under backpressure. The failure becomes observable in the IoT operations workflow because the two c... | {
"initial_assessment": "This is primarily a `Problem Understanding` task. The agent should first establish whether `non reproducible report` is a symptom, a root cause, or an underspecified request.",
"assumptions": [
"The issue is limited to the path connecting the query builder and pagination layer; this rem... | [
{
"type": "premature_patch",
"response": "Immediately rewrite the pagination layer and update every caller without inspecting the repository.",
"why_wrong": "It treats a hypothesis as fact, expands blast radius, and skips evidence and compatibility checks."
},
{
"type": "hallucinated_evidence",
... | {
"must_do": [
"Distinguish verified evidence from assumptions.",
"Inspect or reason about the relationship between `src/main/java/app/Service.java` and `src/main/java/app/Repository.java`.",
"Respect all stated constraints.",
"Define a failure-focused verification step.",
"Keep the proposed chang... | [
{
"role": "system",
"content": "You are a software-engineering agent. Ground conclusions in available evidence, use tools deliberately, preserve safety and contracts, and never claim unobserved results."
},
{
"role": "user",
"content": "A pre-release audit found that the team cannot safely compl... | {
"validation_status": "machine_validated",
"heuristic_score": 93,
"structural_fingerprint": "d24038df62e4ad5b02ccf102c0990c7803201fbd128f87d04431fdd3bd3f1de5",
"user_request_hash": "3ac838f8998fe4159417be30e6cc2c761594d0be18c5974ab134e098f0f0f08d",
"record_hash": "99087d34d6687ae97ca95f21b0219c9c3791fca96edf... |
JF-ASE-004-15 | 1.0.0 | train | {
"family": "problem_understanding",
"family_label": "Problem Understanding",
"archetype": "non_reproducible_report",
"difficulty": "medium",
"behavior_targets": [
"intent_modeling",
"scope_control",
"assumption_tracking",
"acceptance_criteria"
]
} | {
"language": "Go",
"framework": "Chi",
"test_tool": "go test",
"build_tool": "Go modules"
} | {
"name": "canvas-financial-reporting-gateway",
"domain": "financial reporting",
"architecture": "API gateway architecture",
"summary": "A financial reporting repository organized as a API gateway architecture.",
"file_tree": [
"internal/http/routes.go",
"internal/service/core.go",
"internal/store... | {
"user_request": "A regression report describes the following condition: non reproducible report appears in the financial reporting workflow during an idempotent event replay, and the relationship between the CLI command and process runner is not yet proven. Work in `canvas-financial-reporting-gateway`, a API gatewa... | {
"core_issue": "The core issue is non reproducible report: the CLI command establishes state using a condition that is only valid on the common path, while the process runner consumes that state during an idempotent event replay. The failure becomes observable in the financial reporting workflow because the two comp... | {
"initial_assessment": "This is primarily a `Problem Understanding` task. The agent should first establish whether `non reproducible report` is a symptom, a root cause, or an underspecified request.",
"assumptions": [
"The issue is limited to the path connecting the CLI command and process runner; this remains... | [
{
"type": "premature_patch",
"response": "Immediately rewrite the process runner and update every caller without inspecting the repository.",
"why_wrong": "It treats a hypothesis as fact, expands blast radius, and skips evidence and compatibility checks."
},
{
"type": "hallucinated_evidence",
... | {
"must_do": [
"Distinguish verified evidence from assumptions.",
"Inspect or reason about the relationship between `internal/store/repository.go` and `internal/worker/consumer.go`.",
"Respect all stated constraints.",
"Define a failure-focused verification step.",
"Keep the proposed change bounde... | [
{
"role": "system",
"content": "You are a software-engineering agent. Ground conclusions in available evidence, use tools deliberately, preserve safety and contracts, and never claim unobserved results."
},
{
"role": "user",
"content": "A regression report describes the following condition: non ... | {
"validation_status": "machine_validated",
"heuristic_score": 94,
"structural_fingerprint": "175591d8621ac17a08db27f45bd296e71071adb7f938668f3043ae5f77ab530f",
"user_request_hash": "6e75d6cd5bd157ac229502cbe53641266d6ab18a6ab8903190e63494c03b4750",
"record_hash": "262ec7d2af5330df2b423609c6afe5ca1d9bc3b1043f... |
JF-ASE-004-16 | 1.0.0 | train | {
"family": "problem_understanding",
"family_label": "Problem Understanding",
"archetype": "non_reproducible_report",
"difficulty": "hard",
"behavior_targets": [
"intent_modeling",
"scope_control",
"assumption_tracking",
"acceptance_criteria"
]
} | {
"language": "C#",
"framework": "ASP.NET Core",
"test_tool": "xUnit",
"build_tool": "dotnet"
} | {
"name": "pulse-search-infrastructure-gateway",
"domain": "search infrastructure",
"architecture": "batch processing system",
"summary": "A search infrastructure repository organized as a batch processing system.",
"file_tree": [
"Api/Controllers/WorkflowController.cs",
"Core/WorkflowService.cs",
... | {
"user_request": "The current implementation is uncertain because evidence from the frontend state store conflicts with assumptions made by the API client, producing non reproducible report when application nodes have mild clock skew. Work in `pulse-search-infrastructure-gateway`, a batch processing system implement... | {
"core_issue": "The core issue is non reproducible report: the frontend state store establishes state using a condition that is only valid on the common path, while the API client consumes that state when application nodes have mild clock skew. The failure becomes observable in the search infrastructure workflow bec... | {
"initial_assessment": "This is primarily a `Problem Understanding` task. The agent should first establish whether `non reproducible report` is a symptom, a root cause, or an underspecified request.",
"assumptions": [
"The issue is limited to the path connecting the frontend state store and API client; this re... | [
{
"type": "premature_patch",
"response": "Immediately rewrite the API client and update every caller without inspecting the repository.",
"why_wrong": "It treats a hypothesis as fact, expands blast radius, and skips evidence and compatibility checks."
},
{
"type": "hallucinated_evidence",
"r... | {
"must_do": [
"Distinguish verified evidence from assumptions.",
"Inspect or reason about the relationship between `Workers/EventWorker.cs` and `Security/AuthorizationPolicy.cs`.",
"Respect all stated constraints.",
"Define a failure-focused verification step.",
"Keep the proposed change bounded ... | [
{
"role": "system",
"content": "You are a software-engineering agent. Ground conclusions in available evidence, use tools deliberately, preserve safety and contracts, and never claim unobserved results."
},
{
"role": "user",
"content": "The current implementation is uncertain because evidence fr... | {
"validation_status": "machine_validated",
"heuristic_score": 95,
"structural_fingerprint": "c892722297b9fa59e3510c512e9d064868a33802192e562f31dee4687bfb12e4",
"user_request_hash": "128deb2326dbd60d46e4dda5251cd4bf2d633fe6c7379ca3b0c987b6e153ec3d",
"record_hash": "acfbdeef569de9520826e0742bbceb3bbbc6dabf9926... |
JF-ASE-004-17 | 1.0.0 | train | {
"family": "problem_understanding",
"family_label": "Problem Understanding",
"archetype": "non_reproducible_report",
"difficulty": "expert",
"behavior_targets": [
"intent_modeling",
"scope_control",
"assumption_tracking",
"acceptance_criteria"
]
} | {
"language": "PHP",
"framework": "Laravel",
"test_tool": "PHPUnit",
"build_tool": "Composer"
} | {
"name": "matrix-content-moderation-gateway",
"domain": "content moderation",
"architecture": "plugin-oriented application",
"summary": "A content moderation repository organized as a plugin-oriented application.",
"file_tree": [
"routes/api.php",
"app/Http/Controllers/WorkflowController.php",
"a... | {
"user_request": "A teammate proposed a quick fix, but the evidence only proves that the team cannot safely complete the content moderation change because non reproducible report remains unresolved after a zero-downtime schema migration. Work in `matrix-content-moderation-gateway`, a plugin-oriented application impl... | {
"core_issue": "The core issue is non reproducible report: the metrics exporter establishes state using a condition that is only valid on the common path, while the runtime instrumentation consumes that state after a zero-downtime schema migration. The failure becomes observable in the content moderation workflow be... | {
"initial_assessment": "This is primarily a `Problem Understanding` task. The agent should first establish whether `non reproducible report` is a symptom, a root cause, or an underspecified request.",
"assumptions": [
"The issue is limited to the path connecting the metrics exporter and runtime instrumentation... | [
{
"type": "premature_patch",
"response": "Immediately rewrite the runtime instrumentation and update every caller without inspecting the repository.",
"why_wrong": "It treats a hypothesis as fact, expands blast radius, and skips evidence and compatibility checks."
},
{
"type": "hallucinated_evid... | {
"must_do": [
"Distinguish verified evidence from assumptions.",
"Inspect or reason about the relationship between `app/Policies/WorkflowPolicy.php` and `tests/Feature/WorkflowTest.php`.",
"Respect all stated constraints.",
"Define a failure-focused verification step.",
"Keep the proposed change ... | [
{
"role": "system",
"content": "You are a software-engineering agent. Ground conclusions in available evidence, use tools deliberately, preserve safety and contracts, and never claim unobserved results."
},
{
"role": "user",
"content": "A teammate proposed a quick fix, but the evidence only prov... | {
"validation_status": "machine_validated",
"heuristic_score": 96,
"structural_fingerprint": "5ed9606f8289b4922d90e4c5db6a7a0df717413b5bb1c5f32d88441014b07974",
"user_request_hash": "388e7be6c3cbad8c9da59de4bda7297dbecc06ccfc10a988959db93b90a2226b",
"record_hash": "9717763cfebfa05150f132523b00a79b0ec17d146253... |
JF-ASE-004-18 | 1.0.0 | train | {
"family": "problem_understanding",
"family_label": "Problem Understanding",
"archetype": "non_reproducible_report",
"difficulty": "easy",
"behavior_targets": [
"intent_modeling",
"scope_control",
"assumption_tracking",
"acceptance_criteria"
]
} | {
"language": "Rust",
"framework": "Axum",
"test_tool": "cargo test",
"build_tool": "Cargo"
} | {
"name": "anchor-hr-systems-gateway",
"domain": "HR systems",
"architecture": "modular monolith",
"summary": "A HR systems repository organized as a modular monolith.",
"file_tree": [
"src/http/routes.rs",
"src/services/core.rs",
"src/store/repository.rs",
"src/workers/consumer.rs",
"src/... | {
"user_request": "A multi-step change is blocked by the fact that the team cannot safely complete the HR systems change because non reproducible report remains unresolved while old and new application versions coexist. Work in `anchor-hr-systems-gateway`, a modular monolith implemented with Rust and Axum. Focus on t... | {
"core_issue": "The core issue is non reproducible report: the dependency resolver establishes state using a condition that is only valid on the common path, while the build pipeline consumes that state while old and new application versions coexist. The failure becomes observable in the HR systems workflow because ... | {
"initial_assessment": "This is primarily a `Problem Understanding` task. The agent should first establish whether `non reproducible report` is a symptom, a root cause, or an underspecified request.",
"assumptions": [
"The issue is limited to the path connecting the dependency resolver and build pipeline; this... | [
{
"type": "premature_patch",
"response": "Immediately rewrite the build pipeline and update every caller without inspecting the repository.",
"why_wrong": "It treats a hypothesis as fact, expands blast radius, and skips evidence and compatibility checks."
},
{
"type": "hallucinated_evidence",
... | {
"must_do": [
"Distinguish verified evidence from assumptions.",
"Inspect or reason about the relationship between `tests/workflow.rs` and `src/http/routes.rs`.",
"Respect all stated constraints.",
"Define a failure-focused verification step.",
"Keep the proposed change bounded and reversible."
... | [
{
"role": "system",
"content": "You are a software-engineering agent. Ground conclusions in available evidence, use tools deliberately, preserve safety and contracts, and never claim unobserved results."
},
{
"role": "user",
"content": "A multi-step change is blocked by the fact that the team ca... | {
"validation_status": "machine_validated",
"heuristic_score": 97,
"structural_fingerprint": "05bdb80c51ea87cef490f6c32c6950ca3e6ff8bbbab26481c37185763a3f4a52",
"user_request_hash": "985285c6b0fc8f4a1843569e92a0195b47cb6294dbd7b1e5a52b396a528dea17",
"record_hash": "1e2341288d2fda6f2ea4a955835b3acd4103bfaef3d6... |
JF-ASE-004-19 | 1.0.0 | train | {
"family": "problem_understanding",
"family_label": "Problem Understanding",
"archetype": "non_reproducible_report",
"difficulty": "medium",
"behavior_targets": [
"intent_modeling",
"scope_control",
"assumption_tracking",
"acceptance_criteria"
]
} | {
"language": "Kotlin",
"framework": "Ktor",
"test_tool": "Kotest",
"build_tool": "Gradle"
} | {
"name": "prism-subscription-billing-gateway",
"domain": "subscription billing",
"architecture": "event-driven services",
"summary": "A subscription billing repository organized as a event-driven services.",
"file_tree": [
"src/main/kotlin/app/Routes.kt",
"src/main/kotlin/app/Service.kt",
"src/ma... | {
"user_request": "A test environment and production-like environment disagree: evidence from the tenant resolver conflicts with assumptions made by the cache key builder, producing non reproducible report when a fallback code path executes. Work in `prism-subscription-billing-gateway`, a event-driven services implem... | {
"core_issue": "The core issue is non reproducible report: the tenant resolver establishes state using a condition that is only valid on the common path, while the cache key builder consumes that state when a fallback code path executes. The failure becomes observable in the subscription billing workflow because the... | {
"initial_assessment": "This is primarily a `Problem Understanding` task. The agent should first establish whether `non reproducible report` is a symptom, a root cause, or an underspecified request.",
"assumptions": [
"The issue is limited to the path connecting the tenant resolver and cache key builder; this ... | [
{
"type": "premature_patch",
"response": "Immediately rewrite the cache key builder and update every caller without inspecting the repository.",
"why_wrong": "It treats a hypothesis as fact, expands blast radius, and skips evidence and compatibility checks."
},
{
"type": "hallucinated_evidence",... | {
"must_do": [
"Distinguish verified evidence from assumptions.",
"Inspect or reason about the relationship between `src/main/kotlin/app/Routes.kt` and `src/main/kotlin/app/Service.kt`.",
"Respect all stated constraints.",
"Define a failure-focused verification step.",
"Keep the proposed change bo... | [
{
"role": "system",
"content": "You are a software-engineering agent. Ground conclusions in available evidence, use tools deliberately, preserve safety and contracts, and never claim unobserved results."
},
{
"role": "user",
"content": "A test environment and production-like environment disagree... | {
"validation_status": "machine_validated",
"heuristic_score": 98,
"structural_fingerprint": "145d42e935b65a4fe608ec75dd2188682a7e16db118a5a4ce19777cdff3c699e",
"user_request_hash": "6de3d862166b1c813a7a817eb9afc529c9d4744a6e719c6ffb680b93924007f3",
"record_hash": "917019de807f6d25d4565f1038da1689dd3337535f5e... |
JF-ASE-004-20 | 1.0.0 | train | {
"family": "problem_understanding",
"family_label": "Problem Understanding",
"archetype": "non_reproducible_report",
"difficulty": "hard",
"behavior_targets": [
"intent_modeling",
"scope_control",
"assumption_tracking",
"acceptance_criteria"
]
} | {
"language": "Ruby",
"framework": "Rails",
"test_tool": "RSpec",
"build_tool": "Bundler"
} | {
"name": "switch-inventory-gateway",
"domain": "inventory",
"architecture": "service-repository application",
"summary": "A inventory repository organized as a service-repository application.",
"file_tree": [
"config/routes.rb",
"app/controllers/workflows_controller.rb",
"app/services/workflow_se... | {
"user_request": "A repository handoff highlights one unresolved behavior: a proposed fix for non reproducible report would broaden scope without first explaining why the failure occurs during cooperative cancellation. Work in `switch-inventory-gateway`, a service-repository application implemented with Ruby and Rai... | {
"core_issue": "The core issue is non reproducible report: the audit logger establishes state using a condition that is only valid on the common path, while the transaction manager consumes that state during cooperative cancellation. The failure becomes observable in the inventory workflow because the two components... | {
"initial_assessment": "This is primarily a `Problem Understanding` task. The agent should first establish whether `non reproducible report` is a symptom, a root cause, or an underspecified request.",
"assumptions": [
"The issue is limited to the path connecting the audit logger and transaction manager; this r... | [
{
"type": "premature_patch",
"response": "Immediately rewrite the transaction manager and update every caller without inspecting the repository.",
"why_wrong": "It treats a hypothesis as fact, expands blast radius, and skips evidence and compatibility checks."
},
{
"type": "hallucinated_evidence... | {
"must_do": [
"Distinguish verified evidence from assumptions.",
"Inspect or reason about the relationship between `app/controllers/workflows_controller.rb` and `app/services/workflow_service.rb`.",
"Respect all stated constraints.",
"Define a failure-focused verification step.",
"Keep the propos... | [
{
"role": "system",
"content": "You are a software-engineering agent. Ground conclusions in available evidence, use tools deliberately, preserve safety and contracts, and never claim unobserved results."
},
{
"role": "user",
"content": "A repository handoff highlights one unresolved behavior: a ... | {
"validation_status": "machine_validated",
"heuristic_score": 88,
"structural_fingerprint": "2195a05f436f87788434deb873688ccf43eaaa9aba7898c835f27bcf1a594ddf",
"user_request_hash": "c298d71139fdede1ecbf4817658d123af0140198ea0bfa1e92c54817c60d8a71",
"record_hash": "615384eb887a098550c346df969aae49d07265ba9a97... |
JF-ASE-004-21 | 1.0.0 | train | {
"family": "problem_understanding",
"family_label": "Problem Understanding",
"archetype": "non_reproducible_report",
"difficulty": "expert",
"behavior_targets": [
"intent_modeling",
"scope_control",
"assumption_tracking",
"acceptance_criteria"
]
} | {
"language": "C++",
"framework": "CMake service",
"test_tool": "Catch2",
"build_tool": "CMake"
} | {
"name": "trail-observability-gateway",
"domain": "observability",
"architecture": "microservice platform",
"summary": "A observability repository organized as a microservice platform.",
"file_tree": [
"src/http/routes.cpp",
"src/core/workflow.cpp",
"src/data/repository.cpp",
"src/workers/con... | {
"user_request": "A reliability review asks the agent to address a case where a proposed fix for non reproducible report would broaden scope without first explaining why the failure occurs after a duplicate event delivery. Work in `trail-observability-gateway`, a microservice platform implemented with C++ and CMake ... | {
"core_issue": "The core issue is non reproducible report: the notification dispatcher establishes state using a condition that is only valid on the common path, while the template renderer consumes that state after a duplicate event delivery. The failure becomes observable in the observability workflow because the ... | {
"initial_assessment": "This is primarily a `Problem Understanding` task. The agent should first establish whether `non reproducible report` is a symptom, a root cause, or an underspecified request.",
"assumptions": [
"The issue is limited to the path connecting the notification dispatcher and template rendere... | [
{
"type": "premature_patch",
"response": "Immediately rewrite the template renderer and update every caller without inspecting the repository.",
"why_wrong": "It treats a hypothesis as fact, expands blast radius, and skips evidence and compatibility checks."
},
{
"type": "hallucinated_evidence",... | {
"must_do": [
"Distinguish verified evidence from assumptions.",
"Inspect or reason about the relationship between `src/data/repository.cpp` and `src/workers/consumer.cpp`.",
"Respect all stated constraints.",
"Define a failure-focused verification step.",
"Keep the proposed change bounded and re... | [
{
"role": "system",
"content": "You are a software-engineering agent. Ground conclusions in available evidence, use tools deliberately, preserve safety and contracts, and never claim unobserved results."
},
{
"role": "user",
"content": "A reliability review asks the agent to address a case where... | {
"validation_status": "machine_validated",
"heuristic_score": 89,
"structural_fingerprint": "00accc55aef6b0f4bf0e89ac27c573a192085a242ad121bd7ebb5ebe6cc32d4b",
"user_request_hash": "c214f5b83b21cbb82240070209952494ffc469ebb00d1fdeec379a25f5c6b961",
"record_hash": "1698c24c44fe6d6a862f2f63b25859b56fa8e432c8f0... |
JF-ASE-004-22 | 1.0.0 | train | {
"family": "problem_understanding",
"family_label": "Problem Understanding",
"archetype": "non_reproducible_report",
"difficulty": "easy",
"behavior_targets": [
"intent_modeling",
"scope_control",
"assumption_tracking",
"acceptance_criteria"
]
} | {
"language": "Python",
"framework": "FastAPI",
"test_tool": "pytest",
"build_tool": "uv"
} | {
"name": "vector-data-pipelines-gateway",
"domain": "data pipelines",
"architecture": "serverless workflow",
"summary": "A data pipelines repository organized as a serverless workflow.",
"file_tree": [
"app/api/routes.py",
"app/services/core.py",
"app/repositories/store.py",
"app/workers/even... | {
"user_request": "The task appears simple, yet the system context shows that a proposed fix for non reproducible report would broaden scope without first explaining why the failure occurs with a stale session token. Work in `vector-data-pipelines-gateway`, a serverless workflow implemented with Python and FastAPI. F... | {
"core_issue": "The core issue is non reproducible report: the search indexer establishes state using a condition that is only valid on the common path, while the change-data-capture stream consumes that state with a stale session token. The failure becomes observable in the data pipelines workflow because the two c... | {
"initial_assessment": "This is primarily a `Problem Understanding` task. The agent should first establish whether `non reproducible report` is a symptom, a root cause, or an underspecified request.",
"assumptions": [
"The issue is limited to the path connecting the search indexer and change-data-capture strea... | [
{
"type": "premature_patch",
"response": "Immediately rewrite the change-data-capture stream and update every caller without inspecting the repository.",
"why_wrong": "It treats a hypothesis as fact, expands blast radius, and skips evidence and compatibility checks."
},
{
"type": "hallucinated_e... | {
"must_do": [
"Distinguish verified evidence from assumptions.",
"Inspect or reason about the relationship between `app/workers/events.py` and `app/security/policy.py`.",
"Respect all stated constraints.",
"Define a failure-focused verification step.",
"Keep the proposed change bounded and revers... | [
{
"role": "system",
"content": "You are a software-engineering agent. Ground conclusions in available evidence, use tools deliberately, preserve safety and contracts, and never claim unobserved results."
},
{
"role": "user",
"content": "The task appears simple, yet the system context shows that ... | {
"validation_status": "machine_validated",
"heuristic_score": 90,
"structural_fingerprint": "5d3866bab7ca8b0856ba3d259309ab4d403d524d77fdc5c720aa6bc703382070",
"user_request_hash": "c6e4468779648b7e87d79d9c42f5ae0f88448c7c6dafededf7c4ec6b1f23cbbb",
"record_hash": "504072f6ef01e0931d402ce5238a0641e443f953a835... |
JF-ASE-004-23 | 1.0.0 | train | {
"family": "problem_understanding",
"family_label": "Problem Understanding",
"archetype": "non_reproducible_report",
"difficulty": "medium",
"behavior_targets": [
"intent_modeling",
"scope_control",
"assumption_tracking",
"acceptance_criteria"
]
} | {
"language": "Python",
"framework": "Django",
"test_tool": "pytest-django",
"build_tool": "pip"
} | {
"name": "watch-feature-management-gateway",
"domain": "feature management",
"architecture": "worker-based pipeline",
"summary": "A feature management repository organized as a worker-based pipeline.",
"file_tree": [
"project/urls.py",
"app/views.py",
"app/services.py",
"app/models.py",
"... | {
"user_request": "A recent refactor changed the conditions under which non reproducible report appears in the feature management workflow when configuration is hot-reloaded, and the relationship between the rate limiter and distributed counter is not yet proven. Work in `watch-feature-management-gateway`, a worker-b... | {
"core_issue": "The core issue is non reproducible report: the rate limiter establishes state using a condition that is only valid on the common path, while the distributed counter consumes that state when configuration is hot-reloaded. The failure becomes observable in the feature management workflow because the tw... | {
"initial_assessment": "This is primarily a `Problem Understanding` task. The agent should first establish whether `non reproducible report` is a symptom, a root cause, or an underspecified request.",
"assumptions": [
"The issue is limited to the path connecting the rate limiter and distributed counter; this r... | [
{
"type": "premature_patch",
"response": "Immediately rewrite the distributed counter and update every caller without inspecting the repository.",
"why_wrong": "It treats a hypothesis as fact, expands blast radius, and skips evidence and compatibility checks."
},
{
"type": "hallucinated_evidence... | {
"must_do": [
"Distinguish verified evidence from assumptions.",
"Inspect or reason about the relationship between `app/middleware.py` and `tests/test_workflow.py`.",
"Respect all stated constraints.",
"Define a failure-focused verification step.",
"Keep the proposed change bounded and reversible... | [
{
"role": "system",
"content": "You are a software-engineering agent. Ground conclusions in available evidence, use tools deliberately, preserve safety and contracts, and never claim unobserved results."
},
{
"role": "user",
"content": "A recent refactor changed the conditions under which non re... | {
"validation_status": "machine_validated",
"heuristic_score": 91,
"structural_fingerprint": "dfbfca18dc9d01b7fd6c7b5a79e56258c28312f273e0ab6cc1513595123aa139",
"user_request_hash": "2285d13e2d1bf44c5374f4e1dcbb6f192885c158f06fc8bbca5d9f8651b5327b",
"record_hash": "7c914fb46f0ae6035f8f5db593b38bdcda5f499cf4a8... |
JF-ASE-004-24 | 1.0.0 | train | {
"family": "problem_understanding",
"family_label": "Problem Understanding",
"archetype": "non_reproducible_report",
"difficulty": "hard",
"behavior_targets": [
"intent_modeling",
"scope_control",
"assumption_tracking",
"acceptance_criteria"
]
} | {
"language": "TypeScript",
"framework": "Node.js",
"test_tool": "Vitest",
"build_tool": "pnpm"
} | {
"name": "engine-cybersecurity-operations-gateway",
"domain": "cybersecurity operations",
"architecture": "multi-tenant SaaS",
"summary": "A cybersecurity operations repository organized as a multi-tenant SaaS.",
"file_tree": [
"src/http/routes.ts",
"src/services/core.ts",
"src/data/repository.ts... | {
"user_request": "A security review requires careful handling because evidence from the validation layer conflicts with assumptions made by the normalization pipeline, producing non reproducible report under high-cardinality traffic. Work in `engine-cybersecurity-operations-gateway`, a multi-tenant SaaS implemented ... | {
"core_issue": "The core issue is non reproducible report: the validation layer establishes state using a condition that is only valid on the common path, while the normalization pipeline consumes that state under high-cardinality traffic. The failure becomes observable in the cybersecurity operations workflow becau... | {
"initial_assessment": "This is primarily a `Problem Understanding` task. The agent should first establish whether `non reproducible report` is a symptom, a root cause, or an underspecified request.",
"assumptions": [
"The issue is limited to the path connecting the validation layer and normalization pipeline;... | [
{
"type": "premature_patch",
"response": "Immediately rewrite the normalization pipeline and update every caller without inspecting the repository.",
"why_wrong": "It treats a hypothesis as fact, expands blast radius, and skips evidence and compatibility checks."
},
{
"type": "hallucinated_evide... | {
"must_do": [
"Distinguish verified evidence from assumptions.",
"Inspect or reason about the relationship between `test/workflow.test.ts` and `src/http/routes.ts`.",
"Respect all stated constraints.",
"Define a failure-focused verification step.",
"Keep the proposed change bounded and reversible... | [
{
"role": "system",
"content": "You are a software-engineering agent. Ground conclusions in available evidence, use tools deliberately, preserve safety and contracts, and never claim unobserved results."
},
{
"role": "user",
"content": "A security review requires careful handling because evidenc... | {
"validation_status": "machine_validated",
"heuristic_score": 92,
"structural_fingerprint": "2d70393bf6a3a0182ccb1f6639dba2c91be422806d2c6a23292791d18ce26a45",
"user_request_hash": "a3b173f304ab3e894912456bbac63cb1dc2f95c64bd5a684676cb19e7b4de787",
"record_hash": "f21488d3496f239e8f41a72e958e588020021860c8c8... |
JF-ASE-004-25 | 1.0.0 | train | {
"family": "problem_understanding",
"family_label": "Problem Understanding",
"archetype": "non_reproducible_report",
"difficulty": "expert",
"behavior_targets": [
"intent_modeling",
"scope_control",
"assumption_tracking",
"acceptance_criteria"
]
} | {
"language": "TypeScript",
"framework": "React",
"test_tool": "Playwright",
"build_tool": "Vite"
} | {
"name": "gateway-workflow-automation-gateway",
"domain": "workflow automation",
"architecture": "API gateway architecture",
"summary": "A workflow automation repository organized as a API gateway architecture.",
"file_tree": [
"src/app/router.tsx",
"src/features/state.ts",
"src/api/client.ts",
... | {
"user_request": "A release candidate cannot proceed until the agent explains why the team cannot safely complete the workflow automation change because non reproducible report remains unresolved when a client omits a recently added field. Work in `gateway-workflow-automation-gateway`, a API gateway architecture imp... | {
"core_issue": "The core issue is non reproducible report: the release orchestrator establishes state using a condition that is only valid on the common path, while the deployment manifest consumes that state when a client omits a recently added field. The failure becomes observable in the workflow automation workfl... | {
"initial_assessment": "This is primarily a `Problem Understanding` task. The agent should first establish whether `non reproducible report` is a symptom, a root cause, or an underspecified request.",
"assumptions": [
"The issue is limited to the path connecting the release orchestrator and deployment manifest... | [
{
"type": "premature_patch",
"response": "Immediately rewrite the deployment manifest and update every caller without inspecting the repository.",
"why_wrong": "It treats a hypothesis as fact, expands blast radius, and skips evidence and compatibility checks."
},
{
"type": "hallucinated_evidence... | {
"must_do": [
"Distinguish verified evidence from assumptions.",
"Inspect or reason about the relationship between `src/app/router.tsx` and `src/features/state.ts`.",
"Respect all stated constraints.",
"Define a failure-focused verification step.",
"Keep the proposed change bounded and reversible... | [
{
"role": "system",
"content": "You are a software-engineering agent. Ground conclusions in available evidence, use tools deliberately, preserve safety and contracts, and never claim unobserved results."
},
{
"role": "user",
"content": "A release candidate cannot proceed until the agent explains... | {
"validation_status": "machine_validated",
"heuristic_score": 93,
"structural_fingerprint": "19fe35c6d893ed17d468d319c5cbccef53a9cbce9f9d38b75ea4eee7ff3693ec",
"user_request_hash": "8ef515c211973db00297b12f4659f8d2ac1a5dd20823bc6b65d31bc1723a5e9d",
"record_hash": "2ae33842760de1a17eceba9cd481cad14e5765ad4bf4... |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.