-
Notifications
You must be signed in to change notification settings - Fork 1
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.
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
Spec should be higher level #1
Comments
i'm not sure I understand. wouldn't that be an assumption because
there to invoke the arbiter behavior, but lmk if you have other ideas on how to do this! |
It is an input from the environment but with the assumption it is not "fully controlled" by the environment. The environment needs to obey the assumption (or the assumption is false and we trivially win the game). We want the system to not just update the passage with toMarket but keep doing that until we actually get to the market. So the spec really should say, force us to get the market, not just update the passage. Does that make sense? |
I say does it make sense because I'm not 100% sure it makes sense to me either |
yeah I think it does! like ideally the automaton should stay in the same state outputting toMarket() until atMarket() returns true. that seems to work okay with the spec I have. |
CYOA-TSL/spec engineering/CYOAxTSL.md
Line 13 in 2f84fd1
Why not
F inCave()
The text was updated successfully, but these errors were encountered: