Settings
The data type and scope can’t change once values are recorded. Deleting an Input deletes its recorded values. Allocait takes it out of the playbooks and charts that use it, and refuses while a monitor uses it.
Emphasis is a statement about your rule, not a judgment. Allocait reports whether the latest change meets the rule you set. It doesn’t call a change good or bad, and it sends nothing because of it. The app and the REST API set emphasis. An agent can read it but has no tool argument to change it.
Recorded values
A recorded value belongs to one Input, one symbol (forSYMBOL scope) and one date. Recording the same Input, symbol and date again replaces the old value. A value of null deletes it.
One call names each Input, symbol and date once. A repeat in the same call is refused with INVALID_INPUT, and no entry in that call is saved. Send numbers as plain numbers (220, not $220 or 5%).
A value can be a name you track that isn’t a security. See Labels.
For agents
list_inputsreturns your Inputs. Name one Input to also get its recorded values, newest first, with optionalsymbol,sinceanduntilfilters.save_inputanddelete_inputcreate, change and delete Inputs.record_input_valuesrecords or deletes dated values, up to 500 in one call. If one entry is bad, none is saved.
record_input_values description and the server instructions tell an agent with no person present to record nothing and to list the values it would record in its brief. Allocait does not block the write. See Run a scheduled brief. The Claude tools reference lists every argument.Next steps
Playbooks
Read your recorded values per date.
Monitors
Check a symbol’s close against a level you recorded.
Labels
Names you keep research under.
ALLOCAIT.md
Share Input definitions without values.