Set Up Traceway

Analyze the application first, agree on its Traceway project structure with the user, help them create that structure in the dashboard, and only then integrate and verify it.

Operating Contract

• Inspect before asking for credentials or changing code.
• Explain what was detected, what is already tracked, and how each production component should report to Traceway.
• Present a proposed project map and wait for the user to confirm it before implementation.
• There are two classes of credentials, treated differently:
  • Setup tokens (prefix tws_) are org-scoped, expire in 6 hours, and can only propose a setup plan; nothing is created until the user approves the plan on the Traceway website. They are designed to transit chat, and asking the user to paste one is expected.
  • Project ingest tokens and upload tokens are long-lived. Never print their values, never ask the user to paste them into chat, and never commit them. When Step 3's apply script (or the traceway CLI) writes an approved plan's ingest tokens into env files, read only the variable names and statuses from its output, never the values.
• Never print token values found in files or the environment. Report only that a value exists and the variable name that carries it.
• Never commit tokens or filled connection strings.

Invocation Forms