docs(wip): capture n8n scope decisions

WIP.md

@@ -14,10 +14,27 @@ Started: `2026-03-12`
 ### Architecture decision
 - Keep `openclaw-action` as the narrow authenticated ingress into n8n.
 - Keep approval/state/logging in n8n.
+- Use workflow static data for tiny internal state and recent operational breadcrumbs.
+- Do not adopt n8n data tables as the default state store yet; revisit only when shared row-based data, UI browsing/editing, or richer querying becomes a real need.
 - Use host-side `gog` execution for Google Workspace actions for now.
 - Attach execution results back into n8n history so approval items become auditable records.
 - Prefer this over broad n8n Google credential sprawl unless a later need clearly justifies it.
 
+### Where n8n is a good fit here
+- approval-gated actions and human-in-the-loop workflows
+- cross-system glue / action-bus routing
+- inbound event filtering, normalization, and dedupe
+- notification fanout and formatting
+- retries / backoff / rate-limit wrappers around brittle integrations
+- fetch-and-normalize pipelines for URLs or provider payloads
+- compact audit trail / operator history
+
+### Where n8n is not the default
+- primary long-term database
+- heavy archival logging
+- large or fast-growing datasets
+- business logic that is clearer and safer in normal code
+
 ## What is already done
 
 ### n8n action bus
@@ -99,6 +116,10 @@ Started: `2026-03-12`
 
 ## Nice-to-have / future
 - [ ] Evaluate whether native n8n Google nodes are worth adding later
+- [ ] Add retry/backoff wrappers for fragile or rate-limited actions
+- [ ] Expand notification fanout / routing rules if more channels become useful
+- [ ] Add more inbound event normalization/filtering when new providers are wired in
+- [ ] Revisit n8n data tables only if shared row-based operator data becomes useful
 - [ ] If useful, sync this work into the LAN Gitea repo for safer backup/review and easier long-lived tracking
 
 ## Current recommendation