GameCult/Eureka
Watch
9
0
Fork
You've already forked Eureka
 0
Code Issues Pull requests 3 Projects Releases Packages Wiki Activity Actions

Prior art before every nontrivial fork: an Eyes pass on papers and implementations precedes the question

Browse source 
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This commit is contained in:
Eureka 2026-10-02 18:42:28 +02:00
commit 4b79dc5447
2 changed files with 22 additions and 0 deletions
Download patch file Download diff file Expand all files Collapse all files

13
SKILL.md
View file

@ -187,6 +187,19 @@ Templates are in `references/briefs.md` and `references/campaign-state.md`.
### 2. Operator rulings
**Prior art comes before every nontrivial fork.** Before a nontrivial question
goes to the operator, Self stops the line that raised it. Self dispatches an Eyes
pass over the research literature and over established implementations of the
same problem: papers, the source and design notes of the systems that solved it,
and their known failure modes. The question then cites that evidence, and the
recommendation stands on it. Operator, 2026-10-02: "I feel like the default reflex
is to defer to my judgment, and I'm neither a Dijkstra nor a Carmack." The
operator rules on what the project is for and what it values. Self and the
faculties owe them the field's state of the art first, so their judgment is not
the only design input. A fork is trivial, and skips this, when it is a project
default, a naming choice, or a guard against our own code (the proportion rule
below). When unsure, run the pass.
Put the open questions to the operator together, from the open-questions recipe,
each with its options, recommendation, and what depends on the answer. Self
admits every answer as a `ruling` that answers its question, keeping the