# standard-1: what the people who build it need to know.
# Fill in the lines below, then run: seal. Lines that start with # are notes for you and are not sent.
# A long answer can go on, on following lines that start with two spaces.
# Write for an engineer who has never seen this code, and name no company, product or person.

# The track and the category your request names (for example: webdev / Healthcare & Life Sciences).
track: standard
category: Professional Services
# What kind of code this is, in the words your catalog uses (for example: frontend, backend, fullstack).
stack: backend
language: Go

# Tool versions, then the exact commands, in order. Test them in a fresh copy:  git clone standard-1 elsewhere
build: Go 1.22. go build ./... then go test ./...
# How to start it and how to see that it runs (an address, a health check, a screen).
run:
# What it needs from outside (a database, an API, a login service): the folder under deps/ that holds it, or what stands in for it.
depends_on:
# The test account to sign in with, and the demo data that comes loaded. Say if the data is invented, or real data with names and other identifiers taken out, and how.
login_and_data:
# What you saw when you followed your own steps: what builds, and tests as numbers (128 pass / 2 fail / 0 skipped),
# with the reason for each failure.
verified: Builds. Tests: 8 pass / 0 fail / 0 skipped.
# Anything else that saves a question (an outdated lockfile, an extra flag, a fix kept in build-fixes/).
notes:
