levilime / contextproject-danshal Goto Github PK

The goal agent needs to know what a request is for. For a land buy request it needs to know the Multipolygon. And for a request to build the BuildingId. Also the implications of the building or the value of the land should be known, a requestId should be connected with the correct actionlog entries that tell these implications. Additional functionality might be needed in the connector to make these links.

The bot has a rudimentary way of determining if the permit (at least a building or sell land) is good or bad for it's indicators and makes a decision on the permit accordingely. This behaviour can be enhanced with #35 to make it more complex.

This is not yet in the connector.

Goal update, means that there is a new goal jar available. This has to replace the old goal jar on the repo and the naming the travis needs to be adjusted to the new Goal jar.

Other stakeholders might need to be able to get permits for things that negatively influence the municipality directly. But it might still be a benificial transaction for both parties if the other stakeholder does more actions that contribute to the municipality indicators. This can be tracked through how the municipality feels about other stakeholders. If a stakeholder has asked for permissions that benefit the municipality then his score goes up, the municipality will like him. If then he asks for a permit that the municipality in the default case would not allow, the municipality will allow it, but might like the stakeholder less. This can also be used with money and land. Where if a stakeholder gives it to the municipality, the municipality will like him more.

In the connector for a request percept sent the stakeholderIDs that the request is visible for need to be sent with the percept. This way the agent can de deduce who it's from. Even nicer would be that this can be deduced straight away in the connector with additional logic. This ticket will be about implementing in the Goal bot which stakeholder sent a request, but needs additional information from the connector to deduce this.