Closed levilime closed 8 years ago
Code on itself looks nice :+1: Please note though that there is some form of duplication in your code. Maybe it's better to replace it with knowledge or macro's. (Knowledge for code in one base (e.g. belief base) and macro's for code using multiple bases.)
I approve :+1: , however travis is not working :-1:
i do aprove, if @levilime could re run the travis build now the servers are working again it can be merged
The build is green, enough approval for merge, merge is real
In this feature Requests percept of the current contextbranch env is gotten. It becomes an open_request in the beliefs which need to be answered. The logic is written to do this. The request is connected with the correct actionlog entries and from the indicator changes in the action log it can be deduced if the request is good or bad for us.
Also part of the decision is favors the stakeholders can have. If a stakeholder does things to improve our indicators we favor him. If he then does something that is bad for us, we will still accept it when he's favored. This is to simulate cooperation between stakeholders without communication different from the TygronEngine.
Developing feelings is still pretty rudimentary and the behaviour can be deepened later.