How-to guides

Recipes for a task you already have in mind: choosing a mode, reporting chosen decisions, revising.

• Choose Default or Direct mode: When to list the consequences yourself, and when to let Eevo weigh the options itself.
• Write good stakeholders and consequences: What to put in the context, which stakeholders to include, and how to list consequences.
• Report what was done: Tell Eevo which option was carried out, so the console shows whether its advice is followed.
• Revise a decision and record whether you agree: Call again when a result shows something was missed, and record your own verdict.
• Link decisions to chats, issues and pull requests: Send metadata so your team can find each decision in the log by thread, issue, PR or person.
• Handle long runs, rate limits and timeouts: What a 202 means, which errors to retry, how long to wait, and what is never charged.
• Configure data controls: Choose how long each key’s requests are kept, and whether Eevo may learn from them.
• Publish a decision page: Give a decision a public page anyone with the link can read, and take it down again.