Ty
d6b74c42f6
Add dry-run-default connect dispatcher and per-integration scripts with gitignored local capability state, docs, and unit tests. Mutations require --apply and use nemohermes/openshell only.
1.7 KiB
1.7 KiB
Owner Setup UX (post-install)
Status: Skill implemented (fixtures only). See skills/setup-education/. Scenarios: design/scenarios.md.
Prerequisite
Install stages S0–S6 complete (INSTALL.md). S7 connect scripts available (INSTALL.md § S7).
Flow
- Name the assistant → profile/sandbox name.
- Profile intake — business, timezone, hours, priorities, hard rules.
- Channels — WhatsApp, Email, Telegram (connect / skip / later).
- Scheduling — owner's Vagaro and/or Square.
- Books — owner's QuickBooks Online.
- Expectations — draft-only client send; no auto-publish; no inventing live data.
- Capability report — plain language.
Rules
- Owner never receives terminal/Docker/editor instructions.
- Secrets via operator
scripts/connect-*.sh+ OpenShell providers / NemoClaw channel flows. - Agent explains vendor browser steps only.
Operator connect scripts (S7)
After install, the operator runs connect scripts to wire the owner's SaaS:
# Preview all connections
./scripts/connect.sh all --dry-run
# Connect specific integrations
./scripts/connect.sh square --apply
./scripts/connect.sh channels --target whatsapp --apply
./scripts/connect.sh quickbooks --apply
./scripts/connect.sh vagaro --apply
# Check status
./scripts/connect.sh status
See docs/INSTALL.md § S7 for full details.
Related
design/use-cases.md family E · design/mcp-integrations.md