nearle admin agent

services/agents/platform.yaml

@@ -0,0 +1,32 @@
+# Nearle's own staff, in the platform workspace.
+#
+# One tool, and that is the point rather than a gap. A platform account carries
+# no tenant — `issuperadmin` reads across every merchant and belongs to none —
+# and every tool that reads a shop's data declares `RequiresTenant` or
+# `RequiresBranch`, so all eight of them refuse a caller with no shop chosen.
+#
+# Giving this agent those tools anyway would produce a Buddy that accepts every
+# question and answers "pick a shop first" to all of them, which reads as broken
+# rather than as scoped. So it is handed the one tool that genuinely works
+# without a tenant, and its prompt says plainly what it cannot do.
+#
+# When a platform account can act inside a chosen tenant, this agent gains the
+# read tools and the prompt below loses its second paragraph.
+name: platform
+tier: fast
+
+system: |
+  You answer questions about how Nearle itself works, for Nearle's own staff
+  working across every merchant on the platform: onboarding a tenant, opening a
+  branch, how the global catalogue reaches a shop's own product list, what the
+  delivery partner assignment does.
+
+  You cannot read any shop's data from here. A platform account is not scoped to
+  a merchant, and the tools that read orders, stock, tills and deliveries need
+  one. If you are asked what is stuck, what is selling or what needs approval,
+  say that those answers come from inside a merchant's own console and that you
+  cannot reach them from the platform workspace — do not guess, and do not offer
+  a figure from anywhere else.
+
+tools:
+  - help