@signaliz/cli 1.0.2 → 1.0.3

package/README.md

@@ -11,6 +11,29 @@ Fresh enrichment throughput now allows Free 60/min, Builder 300/min, Team
 600/min, Agency 1,000/min, and Pay-As-You-Go 1,000/min, with a 5,000/hour
 workspace safety cap.
 
+## Where To Start
+
+If you are not sure whether to use the UI, CLI, Codex, MCP, or SDK, start here:
+
+```bash
+signaliz start
+```
+
+Signaliz is the GTM brain over any stack. Use CLI, MCP, Codex, or SDK when an
+agent needs to build, audit, route, or debug work. Use the UI as the human
+cockpit to inspect state, connect tools, approve gated actions, and monitor
+results.
+
+`signaliz start` is read-only. It checks workspace health, credits, Ops proof,
+Kernel readiness, and provider-route blockers, then recommends one next safest
+move plus exact commands for five plain workflows:
+
+- Build a campaign plan: `signaliz build "campaign brief"`.
+- Connect tools and provider routes: `signaliz connect`.
+- Audit previous campaigns: `signaliz audit`.
+- Improve results from learning: `signaliz improve <campaign_id>`.
+- Prove Ops delivery: `signaliz prove`.
+
 ## Install
 
 ```bash
@@ -23,21 +46,35 @@ npm install -g @signaliz/cli
 # 1. Authenticate
 signaliz auth login
 
-# 2. Check workspace/API health and discover GTM tools
+# 2. Get the recommended next safest move
+signaliz start
+signaliz build "Build a campaign for industrial maintenance buyers" --target-count 50
+signaliz connect
+signaliz audit
+signaliz prove
+
+# 3. Check workspace/API health and discover GTM tools
 signaliz health
+signaliz gtm context
+signaliz gtm bootstrap --include-samples
+signaliz gtm plan "Build 100 verified VP Sales leads at B2B SaaS companies" --target-count 100 --json > plan.json
+signaliz gtm commit-plan --plan-file plan.json
+signaliz gtm commit-plan --plan-file plan.json --write --confirm
+signaliz gtm prepare-build <campaign_id> --build-input --json > build-args.json
+signaliz campaign build --input-file build-args.json
 signaliz discover --query "build a campaign with webhook delivery" --category ops
 
-# 3. Plan and create a prompt-first Op
+# 4. Plan and create a prompt-first Op
 signaliz /plan "Build 100 verified VP Sales leads at B2B SaaS companies"
 signaliz quickstart company_research
 signaliz /goal "Build 100 verified VP Sales leads at B2B SaaS companies" --confirm-spend
 
-# 4. Run, poll, and retrieve results
+# 5. Run, poll, and retrieve results
 signaliz run <op_id>
 signaliz status <op_id>
 signaliz results <op_id> --limit 100 --json
 
-# 5. Debug async execution and queue health
+# 6. Debug async execution and queue health
 signaliz ops run-status <trigger_run_id>
 signaliz queue --summary
 signaliz debug <op_id>
@@ -149,6 +186,76 @@ signaliz email status <job_id>
 signaliz email find --company-domain stripe.com --full-name "Jane Smith"
 ```
 
+## GTM Kernel
+
+```bash
+# Inspect the workspace Kernel context available to agents
+signaliz gtm context
+signaliz gtm context --no-memory --limit 5 --json
+
+# Check Kernel, Brain, feedback, memory, and connection readiness gates
+signaliz gtm bootstrap
+signaliz gtm bootstrap --campaign-id <campaign_id> --include-samples --json
+
+# Compose a read-only campaign build plan before creating, routing, or spending
+signaliz gtm plan "Find CTOs at fintech startups in NYC" \
+  --target-count 100 \
+  --layers icp,lead_generation,email_verification,sender,feedback \
+  --preferred-providers instantly \
+  --include-planned
+
+# Save the JSON plan, then dry-run a reviewed campaign-object commit
+signaliz gtm plan "Find CTOs at fintech startups in NYC" --target-count 100 --json > plan.json
+signaliz gtm commit-plan --plan-file plan.json
+signaliz gtm commit-plan --plan-file plan.json --write --confirm
+
+# List and inspect first-class GTM campaigns
+signaliz gtm campaigns --status active
+signaliz gtm campaign <campaign_id> --log-limit 20 --memory-limit 20
+
+# Search ranked GTM memory instead of dumping raw history
+signaliz gtm memory "positive replies from technical founders" \
+  --outcome-type positive_reply \
+  --limit 10
+
+# Plan Brain learning in dry-run mode
+signaliz gtm learning <campaign_id> --include-network --write-mode dry_run
+signaliz gtm learning-run <campaign_id> \
+  --phases workspace_pattern_extraction,failure_pattern_detection,defaults_seed,delivery_risk \
+  --write-mode dry_run
+signaliz gtm calibrate <campaign_id> --min-sample-size 10
+
+# Inspect and repair provider readiness without leaving the CLI
+signaliz gtm execution <campaign_id>
+signaliz gtm integrations --campaign-id <campaign_id> --include-planned
+signaliz gtm route-preview --campaign-id <campaign_id> --layer sender
+signaliz gtm activate-route --campaign-id <campaign_id> \
+  --provider-id instantly \
+  --layer sender
+
+# Derive exact dry-run build input from the committed GTM campaign object
+signaliz gtm prepare-build <campaign_id> --build-input --json > build-args.json
+signaliz campaign build --input-file build-args.json
+
+# Reproduce the full first-run proof path as one local receipt
+node scripts/gtm-kernel-first-run-proof.mjs \
+  --brief "Find CTOs at fintech startups in NYC" \
+  --confirm-draft-write \
+  --out-dir /tmp/gtm-kernel-first-run-proof
+
+# Write route changes only after reviewing the dry-run
+signaliz gtm activate-route --campaign-id <campaign_id> \
+  --provider-id instantly \
+  --layer sender \
+  --write \
+  --confirm
+
+# Prepare feedback ingress with feedback-triggered Brain learning
+signaliz gtm feedback-webhook --provider instantly \
+  --campaign-id <campaign_id> \
+  --write-mode dry_run
+```
+
 ## Campaign Builder
 
 ### Build a campaign