Documentation route
Start with the four-state runbook and record the exact stage, operating system, runtime version, package output, and a sanitized error.
Read How It WorksInstallation support should distinguish copying, running, configuring, and validating the first result. Never include API keys, tokens, or identifiable prospect data in a support message.
Start with the four-state runbook and record the exact stage, operating system, runtime version, package output, and a sanitized error.
Read How It WorksKeep credentials in scoped environment secrets. Remove personal data and authorization headers from logs before sharing them.
Review privacy guidanceSelf-serve guidance is available at any time. Operational review windows are described as documentation support, not a sales or managed-outreach service.
Browse field notes
Copy it, run it in your own terminal, inspect every prompt, configure only minimum-scope access, and test a known account before connecting production data.