mirror of
https://github.com/garrytan/gstack.git
synced 2026-11-20 23:23:26 +01:00
docs(ethos, plan-tune, eval-plan): absorb four pstack principles, the observable-questions rule and candidate-side blinding (GSTA-124)
Co-authored-by: capy-ai[bot] <230910855+capy-ai[bot]@users.noreply.github.com>
This commit is contained in:
1 parent
576839cb8c
commit
92002dc228
10 files changed
+251
No files matched your search
@@ -56,3 +56,17 @@ if you stored `off` before that, it takes the answer as given and does not ask.
|
||||
|
||||
If collisions with other skill packs keep coming up under `core`, the fallback
|
||||
Garry approved on 2026-10-25 is `off` by default.
|
||||
|
||||
## Questions a skill asks on its own
|
||||
|
||||
The setting above governs which skills gstack offers unasked. A second rule
|
||||
governs what a running skill may ask you unasked: a question whose answer the
|
||||
skill could observe is not yours to answer. Whether a change is faster, whether
|
||||
two renders differ, whether an endpoint accepts a payload, whether a test still
|
||||
fails: each of those is settled by running the thing (time it, render both,
|
||||
call it, run the test) and reporting the result, not by a prompt. The only
|
||||
questions that come to you are product and preference calls (what the product
|
||||
should do, what you want, what you are willing to spend or risk), and they
|
||||
arrive with the observation already in hand so the choice is between measured
|
||||
options. `/plan-tune` applies the same rule when it audits the question log: an
|
||||
observable question is a defect in the asking skill, not a preference to tune.
|
||||
Reference in new issue
Block a user