mirror of
https://github.com/norandom/OpenUltraSAST.git
synced 2026-10-18 12:39:28 +00:00
27 lines
1.2 KiB
JSON
27 lines
1.2 KiB
JSON
|
{
|
||
|
|
"feature_name": "constrained-detector",
|
||
|
|
"created_at": "2026-09-06T14:30:00Z",
|
||
|
|
"updated_at": "2026-09-06T16:00:00Z",
|
||
|
|
"language": "en",
|
||
|
|
"phase": "requirements",
|
||
|
|
"approvals": {
|
||
|
|
"requirements": {
|
||
|
|
"generated": true,
|
||
|
|
"approved": false
|
||
|
|
},
|
||
|
|
"design": {
|
||
|
|
"generated": false,
|
||
|
|
"approved": false
|
||
|
|
},
|
||
|
|
"tasks": {
|
||
|
|
"generated": false,
|
||
|
|
"approved": false
|
||
|
|
}
|
||
|
|
},
|
||
|
|
"ready_for_implementation": false,
|
||
|
|
"depends_on": [
|
||
|
|
"learning-harness"
|
||
|
|
],
|
||
|
|
"approval_note": "2026-09-06 brief drafted at the maintainer's direction ('I'd rather spend time to design the exact DSPy style interface and evolutionary / statistical prompt optimization than fixing piece by piece'). Not approved; requirements not generated.; 2026-09-06 renamed from detector-optimizer to constrained-detector after the trajectory measurement: the brief's own conclusion is that the optimiser is not the next thing to build, and the spec should be named for what it delivers; 2026-09-06 requirements generated at the maintainer's direction, with the maintainer's emphasis recorded as Requirement 3 ('don't forget the emphasis on the real world bugs from the larger projects to avoid overfitting. we otherwise benchmark for cases that are not relevant')"
|
||
|
|
}
|