Skip to content

Agent / decision making should be a nested table #11

@piscisaureus

Description

@piscisaureus

Each decision making criterion is like properties and others. The ‘aspect’ field of the decision criterion is like properties etc and can be added as new components. So we have one of these complex fields within another complex field. The condition is an open text for now. Threshold is a number and therefore should be checked.

Decision making criterion:

  • Label: Drop down menu, can create new ones in the list, more than one aspect is possible: more than one can be selected.
  • Condition
  • Threshold Check whether it is a number

Decision aspect:

  • Label: List from personal values, properties, (conditions?) and (sanctions?): only one can be selected.
  • Weight: Check whether it is a number

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions