Back to corpus
proposalexperiment writeup candidatescore 24

Phrase Database Enhancement Guide

1. **Sub-segment** existing phrases into shorter, more expressive sub-phrases 2. **Analyze** your database to understand what you have 3. **Enhance** structure while staying CPU-efficient

Open full HTMLDownload HTMLCorpus JSONPaper schema

Full HTML reader

Read the full artifact

Open in new tab

Extracted abstract or opening context

You currently have **68 phrases** from **7 files** using **fixed segmentation**. This guide shows how to: 1. **Sub-segment** existing phrases into shorter, more expressive sub-phrases 2. **Analyze** your database to understand what you have 3. **Enhance** structure while staying CPU-efficient - **Method**: Fixed segmentation (uniform chunks) - **Phrases**: 68 - **Source files**: 7 - **Average phrase length**: ~12-16 bars (estimated) Apply a **second layer** of segmentation on top of your fixed segments to get more granular structure: **What this does:** - Takes each existing 12-16 bar phrase - Further segments it into 2-8 bar sub-phrases - Uses lightweight, CPU-efficient methods - Preserves all original phrases - Creates new sub-phrases with `_sub1`, `_sub2` labels

Promotion decision

What has to happen next

Attach run IDs, datasets, metrics, and reproduction commands.

Why this is not always a full paper yet

Corpus pages are public-safe readers for discovered workspace artifacts. They are not automatically final papers. A corpus item becomes a polished paper only after the editable source, evidence checkpoints, references, figures, render path, and release status are attached through the paper schema.