administrator/Worldshaper
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Upgrade request analysis routing

Browse source
This commit is contained in:
Andraxion 2026-06-27 01:44:11 -04:00
parent 1cd446bae8
commit db3e080640
19 changed files with 1520 additions and 66 deletions
Download patch file Download diff file Expand all files Collapse all files

12
docs/kb/README.md
View file

@ -18,12 +18,18 @@ The goal is to give request-processing tools stable system summaries instead of
- JSON schema for structured request parsing output.
- `tags.json`
- Standardized request tags for queue analysis and admin review.
- `terminology.json`
- Canonical editor terminology and user-language aliases.
- `modules.json`
- Machine-readable index of granular KB slices for targeted retrieval.
- `queue-workflow.md`
- First-pass automation and review flow.
- `editor-capabilities.md`
- Shorthand capability matrix for common request-analysis questions.
- `systems/*.md`
- Human-readable system notes, organized by editor subsystem.
- `modules/*.md`
- Smaller topical docs that can be mixed into model context without sending the whole KB.
## Current System Coverage
@ -40,14 +46,15 @@ The scaffold currently covers:
- Persistence and save pipeline
- Floating windows and popout shell
- Content catalog and record APIs
- Routing terminology and modular retrieval slices
## How To Use This For Request Analysis
Suggested queue flow:
1. Pull a raw request submission from the launcher request store.
2. Retrieve likely systems from `systems.json` using tags, aliases, and file names.
3. Provide the matching `systems/*.md` files to the local model as context.
2. Run a routing pass using `systems.json`, `modules.json`, and `terminology.json`.
3. Retrieve only the most relevant `systems/*.md` and `modules/*.md` files.
4. Require the model to use only tags from `tags.json`.
5. Ask the model to split the submission into atomic requests.
6. Require output that matches `request-analysis-schema.json`.
@ -56,6 +63,7 @@ Suggested queue flow:
## Recommended Next Additions
- Keep expanding modules until every major tool and runtime handoff has at least one focused doc.
- Add concrete file-level notes for major controllers as they evolve.
- Add a small extractor script that refreshes endpoint lists from `server.js`.
- Add examples of well-tagged historical requests for few-shot prompting.