Seamark

**Repository history and code blast radius for your editor, agents, and CI.**

Seamark finds which files change together, explains unusual code, and shows which code paths can reach a database write, a process spawn, or production infrastructure. It provides editor diagnostics, answers `why` on the CLI, and checks agent commands against your rules. The rules are machine checks, not paragraphs in a prompt. **Mistakes get caught instead of explained.**

A _seamark_ is a navigational marker that shows both the safe channel and the hazard.

• Why seamark?
• Get started
• The mental model
• Journey 1: understand an unfamiliar repository
• Journey 2: stop repeating review mistakes
• Journey 3: guard agent commands
• Surfaces: editor, agents, maintainers
• How much can the answers be trusted?
• Durable state
• Configuration
• How it works
• Honest limits
• Status & roadmap

Why seamark?

Most code-graph tools use the same design: parse symbols, store a graph, and save tokens. Three problems remain:

| Problem | W