Public-content intake path (never direct task input)

backlog priority 3 estimate M

workspace-dashboard/005 · created 2026-08-05 · updated 2026-08-05 · blocked by workspace-dashboard/001

What to do

Build the intake path for public suggestions per overview.md’s constraint 2 — a form that writes a markdown file, or similar, landing as triage material Kris reviews by hand. There must be no automatic path from public input to an agent acting on it. (GitHub Discussions and outside PRs are off the table: all lor repos are permanently private per the 2026-08-04 decision, ../questions/001-repo-visibility.md — giscus/Discussions require a public repo.)

Definition of done

A working intake mechanism (form-to-file or similar) that lands content somewhere Kris reviews and manually promotes into an epic/task/question if warranted — never anywhere an agent reads it as a task prompt automatically.

Where the work lands

site/ in this workspace repo, plus whatever the intake mechanism needs (which cannot be GitHub Discussions — private repo).

Docs to read first

overview.md constraint 2 in full — the reasoning (prompt-injection risk, hostile-commit failure mode) matters as much as the mechanism.

View source in repository · also available as raw markdown.