Symbolic

What it does

Release verification, execution evidence, and delivery controls. Connect your Symbolic account and its project, environment, service, run, verification arrive in the ledger as versioned source snapshots, filed as evidence, with a receipt for every sync. Company OS keeps the source, the history and the review boundary; nothing is written back to Symbolic.

What the connection supports

• Syncs project, environment, service, run, verification
• Deployments table in the Technology department, one row per run
• Failed deployments, 7 days: Runs in Symbolic that failed in the last 7 days.
• Lands on Technology, Operations, Timeline
• Every sync leaves a receipt, including the ones that failed
• Available to agents through Company OS context tools

What installing grants

You see this list again on the install screen, and nothing happens until you approve it there.

1. Confirm your account and workspaceIdentify which Symbolic account approved and which workspace the token is bound to.
2. Read your nameThe name shown on the connection.
3. Read servicesRead the services and their manifests.
4. Read runsRead runs and their exports. Nothing can be started.
5. Write the Deployments tableOne row per run in Symbolic: what shipped where, and whether it verified. Rows are authored by Symbolic and keep their history.
6. Seed the Failed deployments, 7 days metricBound to deployments, daily.