[title]

Use this contract to make a package that Radar can review and ingest. It describes the candidate package only; it does not authorize changes to the canonical library.

Required candidate structure

delivery/<lab-slug>/
  README.md
  lab.md
  facilitator-guide.md
  example/worked-example.md
  gallery/gallery-entry.md

Add materials/ only for reusable inputs named in the brief. Never add app/ without a separate approved static-learning-asset decision.

README metadata

Use this exact field set. Values in brackets come from the completed brief.

---
title: "[title]"
type: "lab"
lifecycle_stage: "Draft"
learner_availability: "Drafting"
primary_module: "[exact primary module slug]"
related_modules: ["[exact module slug]"]
related_tracks: ["[exact track slug]"]
level: "[level]"
owner: "[owner / credit name]"
review_status: "[specific human reviews and unresolved gaps]"
---

Use related_modules: [] when none are supplied. Do not leave required fields blank. Do not use any lifecycle stage other than Placeholder, Draft, Testing, or Final; this workbench produces only Draft.

README hub

Include a short description, links to every package file, a primary-module link in this form, and an honest visible review statement:

**Primary module:** [Module title](/websites/rs-ai-learning-lab/ops/contributor-packs/modules/[primary-module-slug]/module/)

The module link is expected to resolve after Radar ingests the folder into labs/<lab-slug>/; it will not resolve in this isolated workbench.

Content standard

• Teach one coherent concept, skill, or applied use case with an observable learner output.
• Preserve the brief’s distinction from nearby labs. Do not rename or merge other work.
• Write for the stated level in direct, non-hype language. Keep human ownership and verification visible.
• Make tool use optional unless the brief makes it essential. Do not describe a prompt as magic or self-validating.
• State what the activity cannot establish and what must remain with a human reviewer.
• Use labels such as illustrative for invented examples. Never present synthesized examples, policies, results, or sources as real.
• Support a written-only path and non-color cues. Do not require disclosure of personal, organizational, or sensitive information.

What Radar adds during ingestion

Radar checks source relationships, collisions, package and rendered links, catalog placement, reciprocal module links, metadata validation, and the local rendered page. Radar may request corrections rather than copying a candidate unchanged.

---

Source: contributor-packs/claude-code-lab-drafter/references/ingestion-contract.md