Question 1

What does Zamski do?

Accepted Answer

Engineering got 10x faster. Coordination didn't. Zamski watches GitHub, Jira, Slack, and your calendar. When the stories those tools tell stop adding up, it names the engineers, the files, and the gap. Not a dashboard. An incident report before the incident.

Question 2

What is an ARC?

Accepted Answer

An ARC is an At-Risk Coordination. Not an alert. A living narrative. It tells you three engineers are editing the same service, the AI agent opened eight PRs, and the reviewer has no focus time. ARCs evolve with timestamps, evidence, and cross-system context. They name the pattern while you can still do something about it.

Question 3

What is The Offline?

Accepted Answer

Your project tracker says on track. Your repo says no reviews in 3 days. Your calendar shows the reviewer in back-to-back meetings. Each tool is right. Together they reveal a capacity constraint nobody saw. We call that gap The Offline. The coordination reality that lives between your tools.

Question 4

How is Zamski different from dashboards?

Accepted Answer

Dashboards show you that cycle time went down. They do not show you that three people are unknowingly rewriting the same module. They report activity after the fact. Zamski detects coordination patterns in real time across multiple systems and names the gap before it becomes a failure.

Question 5

What is the Zamski MCP server?

Accepted Answer

Install with npx @zamskiinc/mcp-server. It gives your AI coding agent organizational memory. 15 tools across 5 groups: file context before you edit, cross-platform search, expert discovery, situation awareness, and work management. Works inside Claude Code, Cursor, and Windsurf.

Question 6

What integrations does Zamski connect to?

Accepted Answer

GitHub (PRs, commits, issues via webhooks and GitHub App). Jira (OAuth). Slack (real-time webhooks). Google or Microsoft calendars (OAuth, 15-minute sync). All read-only. Zamski never modifies your data and never reads source code. Only metadata like PR titles, commit messages, and issue descriptions.

Question 7

Is Zamski secure?

Accepted Answer

SOC 2 Type II. AES-256-GCM encryption. TLS 1.3. Multi-tenant isolation. Complete audit logging. Read-only integrations. Zamski never accesses your source code.

Coordination Assessment

When a coordination failure happens (missed deadline, duplicated work, blocked PRs), how long does it typically take for someone to notice?

If a Slack conversation about a risk never became a Jira ticket, would your team catch it?

How many tools does your team use for engineering work (code, tickets, chat, docs, calendar)?

Team size(optional)