torque/scrims

Public: anyone can read this; nobody can change it.

A scrim board for the cs crew. Three things, each a resource in contract.json with its api so the forge can knock on every door: - announcement: only an admin posts, edits or removes one; anyone, signed in or not, reads and lists them. - match: any signed-in person posts a match (map, time, slots); the person who posted it, or an admin, edits or cancels it; anyone reads and lists. - signup: a signed-in person joins a match once and can leave it; the match's poster and an admin can see who signed up; anyone can see how many slots are left, never who. Keep the notes example only if it still earns its place; otherwise replace it. Every door asks permit; the contract test acts as every identity at every door. Plain server-rendered pages, the JSON API, the MCP tools and the terminal all serve the same actions. Small, fast, no dependencies.

forked from trevato/scrims

workbenchthis machine

0 forks

The family, by who follows whom

trevato/scrims A scrim board for the cs crew. Three things, each a resource in contract.json with its api so the forge can knock on every door: - announcement: only an admin posts, edits or removes one; anyone, signed in or not, reads and lists them. - match: any signed-in person posts a match (map, time, slots); the person who posted it, or an admin, edits or cancels it; anyone reads and lists. - signup: a signed-in person joins a match once and can leave it; the match's poster and an admin can see who signed up; anyone can see how many slots are left, never who. Keep the notes example only if it still earns its place; otherwise replace it. Every door asks permit; the contract test acts as every identity at every door. Plain server-rendered pages, the JSON API, the MCP tools and the terminal all serve the same actions. Small, fast, no dependencies.
- torque/scrims A scrim board for the cs crew. Three things, each a resource in contract.json with its api so the forge can knock on every door: - announcement: only an admin posts, edits or removes one; anyone, signed in or not, reads and lists them. - match: any signed-in person posts a match (map, time, slots); the person who posted it, or an admin, edits or cancels it; anyone reads and lists. - signup: a signed-in person joins a match once and can leave it; the match's poster and an admin can see who signed up; anyone can see how many slots are left, never who. Keep the notes example only if it still earns its place; otherwise replace it. Every door asks permit; the contract test acts as every identity at every door. Plain server-rendered pages, the JSON API, the MCP tools and the terminal all serve the same actions. Small, fast, no dependencies. you are hereproposesin step