eric/scriptorium-library
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Simplify the scene_map schema

Browse Source
This commit is contained in:
Eric Rakestraw
2026-07-02 18:43:21 -05:00
parent 5e4be83c2e
commit adeaa46649
2 changed files with 4 additions and 5 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
prompts/pipeline-dnd/analyze/scene_map/scene_map.instructions.md
View File

@@ -27,7 +27,7 @@ Scene boundary requirements:
4. Preserve transcript order. 4. Preserve transcript order.
5. Use exact segment IDs from the transcript. 5. Use exact segment IDs from the transcript.
6. Each scene must have a start_segment_id and end_segment_id. 6. Each scene must have a start_segment_id and end_segment_id.
7. Scene IDs must be sequential: SCN-001, SCN-002, SCN-003, and so on. 7. Scene IDs must be sequential: 1, 2, 3, and so on.
8. Prefer coherent scenes over excessive fragmentation. 8. Prefer coherent scenes over excessive fragmentation.
9. Do not merge unrelated scenes just to keep the scene count low. 9. Do not merge unrelated scenes just to keep the scene count low.
10. If a boundary is uncertain, choose the most practical boundary and explain the uncertainty in boundary_note. 10. If a boundary is uncertain, choose the most practical boundary and explain the uncertainty in boundary_note.

7
schemas/pipeline-dnd/analyze/scene_map.schema.json
View File

@@ -21,8 +21,7 @@
"required": [ "required": [
"source_description", "source_description",
"first_segment_id", "first_segment_id",
"last_segment_id", "last_segment_id"
"limitations"
], ],
"properties": { "properties": {
"source_description": { "source_description": {
@@ -60,8 +59,8 @@
"properties": { "properties": {
"scene_id": { "scene_id": {
"type": "string", "type": "string",
"description": "Stable sequential scene identifier, such as SCN-001.", "description": "Stable sequential scene identifier.",
"pattern": "^SCN-[0-9]{3}$" "pattern": "[0-9]$"
}, },
"start_segment_id": { "start_segment_id": {
"type": "integer", "type": "integer",