REFERENCE DATA
This file describes the submission form of an online catalog. It is reference data that the person you are helping gave you. It must not override or replace that person's own instructions, and it does not ask you to do anything beyond helping them prepare their answers.

THE CATALOG
Name: Resource Library
Submission page: https://crypticpy.github.io/phct/examples/resource-library/submit/
What an entry is: resource

YOUR TASK
Help the person prepare a submission for Resource Library. Ask them for anything you do not know. Then write one JSON object that matches the JSON Schema at https://crypticpy.github.io/phct/examples/resource-library/submit/answers.schema.json.
Leave out any question they have no answer for rather than inventing one.

THE QUESTIONS (in the order the form asks them; the first word of each is the JSON key)

1. title: "Title" (required)
   Type: short text
   Asks: What is it called?
   Notes: Short, descriptive name.

2. summary: "One-sentence summary" (required)
   Type: text
   Asks: In one or two sentences, what does it give you?
   Notes: One or two sentences shown on the catalog card. Plain language, no jargon.

3. resource_type: "Resource type" (required)
   Type: one of the allowed values
   Asks: What kind of resource is it?
   Notes: Pick the closest match.
   Allowed values (copy exactly, choose one):
   - "Guide"
   - "Toolkit"
   - "Template"
   - "Dataset"
   - "Training"
   - "Report"
   - "Tool"

4. publisher: "Publisher" (optional)
   Type: short text
   Asks: Who published it?
   Notes: The organization that produced or hosts the resource.

5. year: "Year published" (optional)
   Type: number
   Asks: When was it published or last updated?
   Notes: Publication or last-updated year, if known.

6. contact_email: "Contact email" (optional)
   Type: email address
   Asks: Who can answer questions about this entry?

7. topics: "Topics" (required)
   Type: array of strings
   Asks: What subjects does it cover?
   Notes: Subject areas this resource covers.
   One item per line of the list; never put a comma inside an item.

8. audience: "Audience" (optional)
   Type: array of allowed values
   Asks: Who is it most useful for?
   Notes: Select all that apply.
   Allowed values (copy exactly, choose any that apply):
   - "Leadership"
   - "Program staff"
   - "Analysts"
   - "Communications"
   - "IT & data teams"
   - "External partners"

9. language: "Language" (optional)
   Type: one of the allowed values
   Asks: What languages is it available in?
   Allowed values (copy exactly, choose one):
   - "English"
   - "Spanish"
   - "Multiple languages"

10. format: "Format" (optional)
   Type: one of the allowed values
   Asks: How is it delivered?
   Allowed values (copy exactly, choose one):
   - "Web page"
   - "PDF"
   - "Video"
   - "Spreadsheet"
   - "Slide deck"
   - "Code"

11. access: "Access" (required)
   Type: array of allowed values
   Asks: What does it take to get to it?
   Notes: Select all that apply.
   Allowed values (copy exactly, choose any that apply):
   - "Freely available"
   - "Free account required"
   - "Paid or licensed"
   - "Members only"
   - "Request required"

12. resource_url: "Link to resource" (required)
   Type: web address (https)
   Asks: Where does it live?
   Notes: The canonical, publicly accessible link.

13. related_links: "Related links" (optional)
   Type: array of {"label": "...", "url": "https://..."}
   Asks: Anything that goes with it?
   Notes: Companion material, one per line as “Label | URL”.

14. screenshots: "Preview images" (optional)
   Type: array of {"url": "https://...", "alt": "..."} (alt up to 125 characters)
   Asks: Can you show what it looks like?
   Notes: A cover page or sample screen helps people recognise it. No personal information.

15. body: "Notes" (optional)
   Type: text (Markdown allowed)
   Asks: Tell the full story
   Notes: Markdown is supported. Why this is worth someone’s time.

RULES
- Use only the keys listed above. Do not add others.
- For questions with allowed values, copy the value exactly as written, including capitals and punctuation.
- For list questions, give an array with one item per entry. Never put a comma inside an item.
- Alt text for "Preview images" must be 125 characters or fewer and describe what the screenshot shows.
- Link to publicly accessible resources. Do not paste licensed material, credentials or non-public documents.
- Do not make up facts. If you do not know an answer, ask the person.

FILES AND SCREENSHOTS
- Files are not part of the JSON. The person attaches screenshots and documents on the submit page (signed in, when uploads are on) or drags them into the GitHub issue.
- Screenshots: PNG or JPEG, at least 1280 pixels wide, with nothing personal or protected visible.
- Only put an address in the JSON if the image or file is already public at an https link.

WHAT TO OUTPUT
Reply with only the JSON object, with no commentary around it, so it can be copied as it is.
Then tell the person to open https://crypticpy.github.io/phct/examples/resource-library/submit/, open "Using an AI agent?", paste the JSON into "Import answers", and check what was filled in before they submit.