Build a Fail-Closed Ship Folder for a Small AI CLI

Описание и применение

Создайте папку ship с обязательными файлами, чтобы гарантировать, что небольшая CLI‑программа с бесплатным AI‑сервером будет безопасно развернута, соблюдая fail‑closed и правила отката.

Задача

Ensuring a small AI CLI can be shipped safely when using free, unreliable AI models, without hidden failures or side effects.

Результат

The ship folder guarantees that the CLI will not ship unless all evidence files are present and meet size thresholds, enforcing fail‑closed logic and clear rollback paths.

Рабочий процесс

• Create ship/ folder next to CLI
• Write GOAL.md with single task, user, and constraints
• Write BOUNDARY.md with time, cost, blast radius limits
• Freeze a single prompt fixture in PROMPT_FIXTURE.json
• Define FAIL_CLOSED.md rules for silent failures
• Specify ROLLBACK.md steps for quick exit
• Document COST.md limits for free model usage
• Provide HEALTH.json schema for health checks
• Write ABANDON.md walk‑away conditions
• Implement checker script that verifies presence and size of all files

Доказательства

If the checker exits nonzero, I stop. No "just this once" merge. That is the fail‑closed rule.

Источник

Write only the cap you will enforce yourself. Anything else is marketing in a runbook.

Источник