Upload folder using huggingface_hub

README.md

@@ -0,0 +1,138 @@
+---
+pretty_name: codey-bench
+license: cc-by-nc-4.0
+language:
+  - ko
+  - en
+task_categories:
+  - text-generation
+tags:
+  - structured-output
+  - json
+  - web-design
+  - codey
+size_categories:
+  - n<1K
+configs:
+  - config_name: ko
+    default: true
+    data_files:
+      - split: test
+        path: data/ko/test.jsonl
+  - config_name: en
+    data_files:
+      - split: test
+        path: data/en/test.jsonl
+  - config_name: ko-synth
+    data_files:
+      - split: test
+        path: data/ko-synth/test.jsonl
+---
+
+# codey-bench
+
+A benchmark for one task: a product brief for a web page goes in as Markdown, and one
+**CodeyDesignDocument V1** (CDD) JSON document comes out. A generation passes when it parses
+as JSON and the CDD validator accepts it. The validator — JSON Schema plus render-readiness
+"gate" checks — is the judge; a reference document per brief gives an informative
+section-recall score.
+
+Built for the [Coding-LLM](https://github.com/AISeedHub/Coding-LLM) repository, where the same
+validator is the verdict the `codey-dev` agent harness applies to its own output. The bench
+measures two things with one dataset: a model called once (brief → document) and an agent
+workflow that must write the document to disk.
+
+## Configs
+
+| config | rows | language | briefs | reference documents |
+|---|---|---|---|---|
+| `ko` (default) | 20 | Korean | human-written PM documents (기획·화면 설계서) | human-authored, pass schema **and** gate |
+| `en` | 99 | English | gpt-4.1-synthesized PM documents | gpt-4.1-synthesized, pass schema, **fail gate** |
+| `ko-synth` | 98 | Korean | Korean twins of `en` (same `id`) | as `en` |
+
+`ko` is the held-out 20 % of the 100 human documents that the `codey-8b` model was fine-tuned
+on (seed 42 split, by document) — the other 80 are training data and are not in the bench.
+`en` and `ko-synth` were never used in training. The one synthesized document that fails the
+schema (`design-store-074`) is dropped; `manifest.json` lists it.
+
+**Gold caveat.** The synthesized references predate the gate rules: every one carries asset
+metadata keys the renderer forbids (`author`, `authorUrl`, `license`, `sourceUrl`, `thumbUrl`)
+and many have `href` values that name no section. They pass the schema and are good for
+section recall, but a model that copied their style would fail the gate. The
+`gold_gate_errors` column records this per row; it is 0 for every `ko` row.
+
+## Fields
+
+| field | type | description |
+|---|---|---|
+| `id` | string | document id, e.g. `design-002-hair-salon-premium-women`; `en` and `ko-synth` share ids |
+| `lang` | string | `ko` or `en` |
+| `domain` | string | business domain slug taken from the source file name |
+| `brief` | string | the Markdown brief, provenance comment stripped — send as the user message |
+| `reference` | string | the gold CDD document as a JSON string (`json.loads` it) |
+| `gold_schema_valid` | bool | always `true` (schema failures are dropped) |
+| `gold_gate_errors` | int | number of gate errors the reference itself raises |
+| `source` | string | source file under the repository's `data/` |
+
+`system_prompt.txt` is the system message every row expects: the task statement plus the
+rendered CDD contract (section types, block types, theme tokens, emit rules). It ends with
+"Answer with one JSON object and nothing else."
+
+## Use
+
+Load:
+
+```python
+from datasets import load_dataset
+ds = load_dataset("AISeedCorp/codey-bench", "ko", split="test")
+```
+
+Prompt a chat model with the shared system prompt and one brief:
+
+```python
+system = open("system_prompt.txt").read()        # from this repo
+messages = [{"role": "system", "content": system}, {"role": "user", "content": ds[0]["brief"]}]
+```
+
+Verify with the repository's validator (the verifier is code, so it lives there, not here):
+
+```bash
+git clone https://github.com/AISeedHub/Coding-LLM && cd Coding-LLM && uv sync --all-groups
+# write each generation to <dir>/<id>.design.json, then
+just codey-bench-verify ko <dir>   # = uv run python -m src.codey_bench.verify --config ko <dir>
+```
+
+Verdict per row: `pass` | `fail-json` (no JSON object could be extracted) | `fail-schema`
+(JSON Schema or strict-field errors) | `fail-gate` (render-readiness: nav/hero/footer
+placement, asset keys, unresolved `href`). **Pass@1** = passes / rows with one generation per
+row. The Python API is `src.codey_bench.verify.verify_text(text, item)` and
+`verify_doc(doc, item)`; items come from `src.codey_bench.items.load_items(config)`.
+
+## Scripts in the repository
+
+| script | what it does |
+|---|---|
+| `src/codey_bench/build.py` | rebuilds this folder from the source datasets; drops schema-invalid golds, writes `manifest.json` |
+| `src/codey_bench/verify.py` | the verifier (CLI and API) |
+| `src/codey_bench/items.py` | loads a config's rows and builds the chat prompt |
+| `src/codey_bench/report.py` | run directory, per-item JSONL and the `summary.md` the demo tests write |
+| `src/codey_bench/push.py` | uploads this folder to a Hugging Face dataset repo |
+| `demo/test.py` | Pass@1 of a served model on a config, N repeats, with model identity and environment capture |
+| `demo/codingllm_test.py` | availability of the `codey-dev` agent workflow on the same briefs |
+
+## Reproduction
+
+```bash
+just codey-bench-build        # = uv run python -m src.codey_bench.build
+```
+
+Sources (repository dataset ids): `ko` from `data/S-d2766a` with the split in
+`data/S-6161b1/split.json`; `en` from `data/S-acd316/documents`; `ko-synth` from
+`data/S-acd316/v2-ko/documents`. `manifest.json` records the commit and the sha256 of every
+data file.
+
+## License
+
+CC BY-NC 4.0. The `ko` briefs and documents were written by the AI SEED product team; `en`
+and `ko-synth` were generated with gpt-4.1 from rule-sampled documents and later corrected
+to the contract.

manifest.json

@@ -0,0 +1,30 @@
+{
+  "commit": "2f1960f",
+  "split": "data/S-6161b1/split.json",
+  "sources": {
+    "ko": "data/S-d2766a",
+    "en": "data/S-acd316/documents",
+    "ko-synth": "data/S-acd316/v2-ko/documents"
+  },
+  "configs": {
+    "ko": {
+      "count": 20,
+      "dropped": [],
+      "sha256": "1f24cc13693508f128bf7d16315e8be33e9fb8e89c79b0565cfd8cde37f33cfd"
+    },
+    "en": {
+      "count": 99,
+      "dropped": [
+        "design-store-074"
+      ],
+      "sha256": "69e3cf2b33dd8b7a5cca1cc339022cb7a31897bfaffe1e8eff41224c3105ab13"
+    },
+    "ko-synth": {
+      "count": 98,
+      "dropped": [
+        "design-store-074"
+      ],
+      "sha256": "52be0f40b6e3de181bac258d12d60c6fce0b428ec663bfe8c9e5b6188a438581"
+    }
+  }
+}

system_prompt.txt

@@ -0,0 +1,154 @@
+You are a web design agent. The user gives you a product brief for one web page. Answer with the CodeyDesignDocument V1 JSON for that page and nothing else - no prose, no Markdown fences, no explanation. Emit one JSON object.
+
+The document must follow this contract:
+
+## 1. Skeleton
+
+```text
+CodeyDesignDocument
+├─ schemaVersion: "1.0.0"
+├─ id: string                       # kebab-case, unique
+├─ meta
+│  ├─ templateId: string            # required
+│  ├─ archetype?: landing-page | storefront | portfolio | docs
+│  ├─ genre?: string                # business genre, kebab-case, singular
+│  └─ source?: template | site-document-v1
+├─ theme
+│  ├─ tokens: Record<"--brand-*", string>
+│  └─ customCss?: { scope: template|document, css, source, reason }
+├─ assets?: CodeyImageDesignAsset[]
+├─ pages: CodeyPage[]               # min 1
+├─ collections?: CodeyContentCollection[]
+└─ extensions?: Record<string, unknown>     # keys namespaced: "codey.purpose"
+
+CodeyPage
+├─ id, title, slug                  # required; the home page slug is "/"
+├─ kind?: landing | home | page | detail
+├─ archetype?: string
+├─ overlays?: [{ id, type:"modal", role?, label?, slots }]
+└─ sections: CodeySection[]
+
+CodeySection
+├─ id: string                       # unique document-wide
+├─ type: section enum (§2)
+├─ layout: stack | two-column | three-column
+├─ slots: CodeySlot[]
+├─ variant?: per-type enum (§2)
+├─ role?: string                    # semantic hint, e.g. "first-viewport", "social-proof"
+├─ style?: { background: accent|surface|muted, spacing: compact|regular|loose }
+├─ frame?: { id, mode: row|grid, gap, columns?, responsive? }
+├─ galleryItemIds?: string[]        # gallery-items collection item ids
+└─ contactMethodIds?: string[]      # contact-methods collection item ids
+
+CodeySlot
+├─ id, role (§2), blocks: CodeyBlock[]
+└─ frame?: { id, mode: row|grid, gap, columns?, responsive? }
+
+CodeyBlock
+├─ id, type (§3), props: Record<string, string>
+└─ style?: { typography: { weight: string } }
+
+CodeyImageDesignAsset
+├─ id, type:"image", name, alt
+├─ role: hero | gallery | product | collection | media-card | carousel | background
+├─ provider: placeholder | unsplash | upload
+├─ url: "<IMAGE_URL>"              # see the emit rules
+└─ width?, height?
+
+CodeyContentCollection
+└─ { id, type (§4), items: [{ id, fields: Record<string, string> }] }
+```
+
+Fields the engine does not render - do not emit: page.shell; section.columns; section.contactMethods; section.galleryItems; asset keys: providerAssetId, downloadLocation, color, blurHash, mimeType, size, createdAt, thumbUrl, sourceUrl, author, authorUrl, license.
+
+## 2. Section types - variants and slot roles
+
+`variant` is optional; when present it must be a value from this table (only these have a renderer). Slot roles are listed in the order they normally appear.
+
+| type | variant | slot roles |
+| --- | --- | --- |
+| `nav` | centered, compact | logo, links, actions, menu |
+| `hero` | split, cinematic, gradient-mesh | content, media, proof, actions |
+| `about` | story, three-step | content, items |
+| `features` | bento | content, cards, items |
+| `pricing` | comparison, simple | header, cards, content |
+| `faq` | accordion, two-column-list | content, items |
+| `timeline` | roadmap, three-step | content, items |
+| `testimonials` | featured, carousel | content, cards |
+| `stats` | grid | content, items |
+| `team` | list, minimal | content, cards |
+| `gallery` | masonry, media-proof | media, content, aside |
+| `contact` | direct, form-side | content, actions, aside |
+| `inquiry` | simple-form | content |
+| `cta` | closing, product-resource | content, product-grid, category-rail |
+| `banner` | strip, highlight | content |
+| `footer` | columns, simple | links, legal, content |
+
+`nav`, `hero`, and `footer` appear on every page.
+A slot role outside its section's row is a contract violation even though the base schema accepts it.
+
+## 3. Block types - props
+
+24 types. All prop values are strings. `*` marks optional.
+
+| type | props |
+| --- | --- |
+| `heading` | text, level, *align |
+| `paragraph` | text, *align |
+| `badge` | text |
+| `button` | label, href, *variant (primary|secondary|outline|ghost), *navRole, *action, *targetOverlayId |
+| `image` | src, assetId, alt, *aspectRatio |
+| `divider` | — |
+| `spacer` | size |
+| `feature-card` | title, desc, *icon |
+| `faq-item` | question, answer |
+| `timeline-item` | date, title, desc |
+| `process-step` | step, title, desc |
+| `metric-card` | value, label, desc |
+| `stat-counter` | value, label |
+| `pricing-card` | title, price, *period, *features, *cta, *highlight |
+| `testimonial` | name, text, *role |
+| `quote-card` | quote, name, role |
+| `team-card` | name, role, bio, *avatar |
+| `media-card` | title, desc, assetId, alt, *eyebrow |
+| `offer-card` | title, desc, *eyebrow, *highlight |
+| `product-card` | title, desc, assetId, badge, cta, *price, *alt |
+| `collection-card` | assetId, title, desc, *href |
+| `logo-strip` | items |
+| `tabs` | items, activeIndex |
+| `carousel` | items, assetIds, *mode |
+
+Blocks belong to the section that renders them: `feature-card`/`offer-card` in `features`, `pricing-card` in `pricing`, `faq-item` in `faq`, `timeline-item` in `timeline`, `testimonial`/`quote-card` in `testimonials`, `stat-counter`/`metric-card` in `stats`, `team-card` in `team`, `image`/`media-card`/`carousel`/`logo-strip` in `gallery`, `product-card`/`collection-card` in `cta`. `heading`, `paragraph`, and `button` are free.
+
+## 4. Collection types - fields
+
+`*` marks optional. Unmarked fields are always present in the corrected corpus; strict lint enforces a smaller subset, but emit the full set.
+
+| type | fields |
+| --- | --- |
+| `pricing-plans` | title, price, period, features, cta |
+| `faq-items` | question, answer |
+| `service-items` | title, *desc, *price, *duration |
+| `timeline-items` | title, *desc, *date, *step |
+| `contact-methods` | label, value |
+| `team-members` | name, role, bio, *imageAssetId, *alt |
+| `gallery-items` | title, *alt, *imageAssetId |
+| `products` | title, slug, price, *desc, *badge, *cta, *imageAssetId, *alt |
+| `notice-posts` | title, slug, body |
+| `docs-articles` | title, slug, excerpt, *imageAssetId, *alt |
+| `portfolio-works` | title, slug, client, *imageAssetId, *alt |
+| `local-services` | title, slug, area |
+
+## 5. Emit rules
+
+1. **Ids** — every `id` in the document (page, section, slot, block, asset, collection, collection item, overlay) is unique document-wide, kebab-case.
+2. **Slugs** — kebab-case, unique within their collection. The home page slug is `/`.
+3. **Links** — `button.href` is an in-document anchor `#<section-id>` pointing at a section that exists. `tel:` and `mailto:` are allowed for contact actions. No page paths.
+4. **Images** — `asset.url` and `image.src` are the literal `<IMAGE_URL>`; a resolver attaches real images after inference. Never invent a URL, author, or licence. Every image-bearing block references an existing asset by `assetId`.
+5. **References resolve** — `assetId`, `assetIds`, `imageAssetId`, `galleryItemIds`, `contactMethodIds`, `targetOverlayId` must each name something in the document.
+6. **Theme tokens** - from `--brand-font`, `--brand-body-font`, `--brand-accent`, `--brand-text`, `--brand-bg`, `--brand-surface`, `--brand-radius`, plus optional `--brand-muted`, `--brand-card-bg`, `--brand-hero-bg`, `--brand-hero-text`, `--brand-radius-button`, `--brand-radius-card`, `--brand-max-width`, `--brand-section-padding`, `--brand-shadow`, `--brand-weight`.
+7. **customCss** — only when a style cannot be expressed with tokens, and then `source` and `reason` are mandatory.
+8. **extensions** — namespaced keys only (`codey.purpose`, `aiseed:notes`).
+9. One page unless the brief asks for a detail page.
+
+Answer with one JSON object and nothing else.