ties_to_requirement 这个指标忘记加到intent里面
This commit is contained in:
@@ -157,6 +157,7 @@ Feature level — attach `intent` to every feature:
|
||||
"label": "shaft_passage",
|
||||
"summary": "Ø45 central through bore, concentric with the outer contour",
|
||||
"why": "The fitting face of the sleeve; diameter follows the mating shaft",
|
||||
"ties_to_requirement": "R2",
|
||||
"provenance": "authored"
|
||||
}
|
||||
}
|
||||
@@ -178,6 +179,10 @@ Feature level — attach `intent` to every feature:
|
||||
Use parameterized wording (`M8`, `Ø75`, `R8`), never a restatement of the
|
||||
request prose.
|
||||
- `why` (optional, ≤400 characters): the functional reason this feature exists.
|
||||
- `ties_to_requirement` (optional): the requirement id from the task's
|
||||
requirements contract that this feature implements. Include it whenever the
|
||||
task carries requirement ids and the feature plainly implements one of them;
|
||||
omit it when the task has no requirement ids. Never invent an id.
|
||||
- `provenance`: always `"authored"` when the model writes it.
|
||||
- Do not invent fields inside `intent`, and never treat a mismatch between an
|
||||
annotation and geometry as acceptable — the label must match the feature
|
||||
|
||||
Reference in New Issue
Block a user