Skip to content

docs: require API grain proof before ship dispatch #16

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
kaku-san merged 2 commits into from
Sep 14, 2026
Merged

docs: require API grain proof before ship dispatch #16

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
c777ce5
Prove third-party source grain before dispatching a ship.
kaku-san Sep 14, 2026
d981c38
no-mistakes(review): Narrow API grain dispatch rule
kaku-san Sep 14, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
3 changes: 3 additions & 0 deletions AGENTS.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -293,6 +293,9 @@ For one-off or infrequent operational work, start with the simplest direct end-t
Do not build wrappers, control planes, policy layers, custom verifiers, or automation unless the direct path exposes a concrete blocker or repeated need that justifies the added machinery.

Before commissioning an investigation, consult existing reports and established evidence.
Before dispatching a ship that depends on a third-party API, prove that API can answer at the grain the product needs.
If it cannot, stop and tell the captain.
Do not spawn.
Classify the deliverable:

- **Ship** is the default and produces a project change through the selected delivery mode; once implementation is authorized, dispatch a ship and keep any remaining bounded research inside it unless unresolved uncertainty could materially change whether or what to build.
Expand Down
Loading