Cost/manufacturing complexity. If you are country struggling to defend your self you don't think problems in 30 years if today problem is does the country exists or not. Might be difficult to put your self to a small defending countries shoes which is absolute running our of resources.
If you don't have workflows which repeat in inet you don't need openClaw.
- Messages from school where to react
- Getting payments from someone and tracking that you get them
- Summary of news the way you like it from sources you like it every day
- Integrated task lists reminders
- Drafting taxation reports based on spending
etc etc.
I just don't trust "the claw" so I build following system
- Docker 1:
* Locked up Claw docker - user level priv. Access outside to "one port" only.
- Docker 2:
* Tool gateway with pre-baked commands - openclaw can only index what command to execute
* Keys are here
* Telegram hook to approve all "post" commands i.e. sending email or posting something somewhere.
- Docker 3:
* LLM gateway keeping track of cost and routing
No as you could have multiple examples of expected output in single prompt.
You should just "ask" - that's zero shot.
If you "ask + provide" examples then you are in the n+1 shot realm.
But I suppose terminology is shifting from this...
What confused me is the fact that in the paper all logical steps are give. It basically check that when all relevant facts are provided explicitly as links , how far and how complex a chain can the model correctly follow before it breaks down?
So it's simpler than "reasoning". This is not necessarily a bad thing as it boils down the reasoning to a simpler, more controlled sub problem.
Depends on the country. In Finland, it's ok to record your own discussions. Whether the recorder is BK (a third party) or the cashier is an interesting question, though.
Creating a database of recordings without user being able to know/influence is clearly violation of GDPR IF there is PII. That's going to be costly for BK.