Expand request review tooling and KB
This commit is contained in:
parent
ab1dfbf029
commit
cae21b61b7
16 changed files with 1258 additions and 241 deletions
|
|
@ -18,9 +18,10 @@ Turn raw launcher submissions into structured request items that are:
|
|||
2. Split it into candidate atomic requests.
|
||||
3. Retrieve likely systems from `docs/kb/systems.json`.
|
||||
4. Load the matching `docs/kb/systems/*.md` files.
|
||||
5. Ask the local model for JSON that matches `docs/kb/request-analysis-schema.json`.
|
||||
6. Validate the JSON.
|
||||
7. Promote high-confidence items and hold low-confidence items for review.
|
||||
5. Load the standardized request tags from `docs/kb/tags.json`.
|
||||
6. Ask the local model for JSON that matches `docs/kb/request-analysis-schema.json`.
|
||||
7. Validate the JSON.
|
||||
8. Promote high-confidence items and hold low-confidence items for review.
|
||||
|
||||
## Suggested Confidence Rules
|
||||
|
||||
|
|
@ -52,10 +53,11 @@ You are processing Worldshaper editor requests.
|
|||
You must:
|
||||
- split the submission into one or more atomic requests
|
||||
- assign one primary category per item
|
||||
- assign tags grounded in the provided KB
|
||||
- assign tags grounded in the provided KB and limited to `docs/kb/tags.json`
|
||||
- write a short descriptive title
|
||||
- explain the user intent in plain language
|
||||
- propose a likely implementation path
|
||||
- provide a short review rationale and possible options when confidence is low
|
||||
- avoid inventing systems that are not in the KB
|
||||
- return only valid JSON matching the provided schema
|
||||
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue