Record the Where block as one question in the decisions
Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
This commit is contained in:
1 parent
9e92be848a
commit
6f273cfdd6
1 file changed
+1
-1
+1
-1
@@ -170,7 +170,7 @@ What was decided for roledesk and the one reason for each. The longer reasoning
|
||||
|
||||
**Job boards are a list with New, edited in place like the agent cards.** The form used to sit open above the list and Edit filled it, which read as a stray form. It is a `<template>` now: Edit turns the row into the form, New puts a blank one on top, Save and Cancel close it, and one is open at a time.
|
||||
|
||||
**Gates are a Where block and rule rows; the JSON is a read-only view.** The location rules are the ones every agent has, so they are written in words: only roles in these countries (require), and one of country, remote or place (any), prefer hybrid. Every other gate is a row of field, mode, values and weight. A gate the Where block cannot express whole, such as a require with a weight other than 1, lands in the rows, so a load and save without edits returns the same gates.
|
||||
**Where is one question, and a role passes when it matches any of its lines; the other rules sit under Advanced.** The first Where block showed the two levels of the gates as they are stored, a required set of countries and then a one-of set, with ISO codes, and the owner could not read it. It asks "Where can the role be?" now: in these countries (by name), in these towns, remote within Europe or anywhere, and a sentence below says what they add up to, the same sentence the card shows. The stored gates did not change: the lines are `any` gates on `country`, `place` and `remote`, and "within Europe" is a require gate on `country` holding the Europe list plus the countries line. A require gate on `country` the block cannot say, such as Denmark and Sweden only, is a row under Other rules, which moved under Advanced above the read-only JSON and opens when the agent has one. Prefer hybrid ranks rather than filters, so it stands apart. Spellings of a town that differ by accents only share one chip, since `place` matches without case but with accents, and both are stored. A gate the block cannot express whole lands in the rows, so a load and save without edits returns the same gates.
|
||||
|
||||
**Affinity and votes are per agent.** A company hidden for one hunt may be a favourite for another, and a vote says what one agent should learn from, so both carry the agent id, and the Roles tab and the company list ask for one agent's. Without an agent id the API uses the default agent, the enabled one with the lowest id, so the CLI and older callers keep working.
|
||||
|
||||
|
||||
Reference in new issue
Block a user