Glossary

Canonical definitions for the terms used in Zamski briefs, the Methodology page, and the Comparison page. Pair this with the journal at journal.zamski.com for the longer-form essays that put these terms in practice.

Annual physical versus continuous heart monitor: The framing that distinguishes Zamski from McKinsey-style engineering diagnostics. An annual physical is correct on the day it is run and stale the next month. A continuous heart monitor is the substrate Zamski operates. The framing is not "better than"; it is "different temporal model." See the Comparison page.
Related: Coordination substrate · Monday Brief
ARC (Adaptive Rule Conditions): The rule system Zamski uses to evaluate coordination patterns against organizational context. ARCs are typed by what they evaluate against: G1-G4 against PR data, G5-G7 against commit data, G8 against review discipline, G9-G10 against cross-system data, G12-G16 against issue data. Customers can author custom ARCs via the rule authoring interface.
Related: Divergence · Correlation engine · Theme
Brief (Monday Brief, Weekly Brief): The board-grade read Zamski produces on the engineering organization, published every Monday morning. Six sections: divergences caught this week, interventions executed last week, track record, on-watch indicators, tool stack ROI, and resolved items. The brief is built for the CTO, CFO, and board member rather than for engineering managers.
Related: Track record · On-watch · Divergence
Calibration: The continuous measurement of how often Zamski's confidence bands match post-hoc outcomes. Calibration is the substrate's primary trust mechanism. Calibrated systems are honest about what they do and do not know; uncalibrated systems are not.
Related: Confidence band · Track record
Chain reasoning: The synchronous runtime path for user queries. Identity resolution, hallucination guard, intent classification, data retrieval, confidence scoring with up to two iterations, optional CatBoost re-ranking, and grounded LLM response generation. End-to-end latency typically 5 to 15 seconds. Distinct from the correlation engine, which runs in batch.
Related: Correlation engine · Hallucination guard · Identity resolution
Confidence band: The probability range associated with every divergence Zamski surfaces. Confidence bands are logged with the underlying evidence and the model version that scored them. Post-hoc outcomes are recorded against the band and surfaced as the track record line item in each brief. Bands are typically 70 to 95 percent.
Related: Calibration · Track record
Coordination intelligence: The reading of how work is actually coordinated across an engineering organization. Not how much work, not how fast, not how much code: how the coordination signal looks across the mediums engineers actually use, identity-resolved across those mediums, with citations down to specific artifacts. The category Zamski operates in.
Related: Coordination substrate · Divergence
Coordination substrate: The continuous data layer Zamski reads across the five coordination mediums (code activity, task and project state, conversation patterns, calendar density, customer signal). The substrate is identity-resolved across mediums and projected into a workspace graph that links forward to teams, projects, repos, and revenue chains.
Related: Coordination intelligence · Identity resolution
Coordination tax: The cost a company pays in time, attention, and slipped commitments because of poor coordination signal across the engineering organization. The coordination tax is not measured in engineer hours; it is measured in board updates that miss the slip, customer renewals that surface unexpected churn, and senior departures that show up in the calendar pattern 60 days before the resignation letter.
Related: Divergence · Decisions by silence
Correlation engine: The batch runtime path for the Monday Brief and the on-watch indicators. Runs the ten-pass correlation matrix across the full org workspace, applies sentinel goals and the prescription layer, and persists candidate situations. Distinct from chain reasoning, which runs synchronously on user queries.
Related: Chain reasoning · Situation · Sentinel
Decisions by silence: Decisions a team makes by not making them. A senior engineer's calendar load grows; nobody decides to redistribute it; the implicit decision is made. A customer escalation reaches the on-call rotation; nobody decides to assign ownership; the implicit decision is made. The substrate surfaces decisions by silence as a class of divergence that is invisible to ticket-tracking systems.
Related: Divergence · Coordination tax
Divergence: A named pattern where the engineering work graph diverged from what was committed (to the board, the customer success team, or the customer themselves). Each divergence in the Monday Brief carries a confidence band, the substrate evidence, and a board-grade implication. The divergence is the unit the brief organizes around.
Related: Brief · Confidence band
Entropy (signal entropy): The Shannon entropy of signal sentiments across a coordination pattern, normalized to the 0-to-1 range. High entropy indicates conflicting or contested signal; low entropy indicates consistent signal. Used as one of three inputs to the gravity score.
Related: Gravity · Velocity · Kinetic state
Gravity: The composite score Zamski uses to rank divergences for inclusion in the brief. Gravity is computed as 0.35 times entropy plus 0.40 times velocity plus 0.25 times impact. Divergences above a gravity threshold cross into the brief; below the threshold, they appear in on-watch.
Related: Entropy · Velocity · Impact
Hallucination guard: The pipeline component that blocks personal queries without verified identity. If a user asks about themselves or another named individual and identity resolution is below the 85 percent confidence threshold, the guard refuses the query rather than hallucinating an answer.
Related: Identity resolution · Chain reasoning
Identity resolution: The process of resolving identities across the five coordination mediums so that a GitHub username, a Slack ID, a calendar email, a Jira account ID, and a CRM contact ID can be associated with one person. Operates at an 85 percent confidence threshold; matches below the threshold are held in a review queue rather than auto-merged.
Related: Coordination substrate · Hallucination guard
Impact: The breadth measurement Zamski uses as one of three inputs to the gravity score. Computed as 0.10 per unique participant plus 0.15 per team plus 0.10 per source system, with caps to prevent dominance by any single dimension. A divergence with high impact touches many people across many teams.
Related: Gravity · Entropy · Velocity
Kinetic state: The temporal state of a divergence: EMERGING, VIBRATING, RISING, FALLING, RESOLVING, or STEADY. Derived from maturity (EMERGING and RESOLVING), entropy (VIBRATING at entropy at or above 0.6), and gravity velocity (RISING above 0.05 per day, FALLING below negative 0.03). The brief uses kinetic state to differentiate "new this week" from "deteriorating" from "resolving."
Related: Gravity · Divergence
Monday Brief: See Brief (Monday Brief, Weekly Brief).
Related: Brief
On-watch: The brief section that surfaces leading indicators trending toward a divergence but not yet crossing the threshold. On-watch is the early-warning band: a senior engineer's calendar density dropping, a revenue chain with declining engineering attention, a meeting cadence signaling escalation. Tracked across briefs so the CTO sees the trajectory, not just the snapshot.
Related: Brief · Divergence · Kinetic state
Sentinel: The component that monitors goals customers set against the substrate and publishes intelligence-feed events when drift is detected. Drift states transition NORMAL to ALERT to COOLDOWN (5 minutes) back to NORMAL. Sentinel events flow through the same correlation engine that produces the brief.
Related: Correlation engine
Situation: The persisted record of a candidate divergence. Situations carry an ARC type, an evidence chain, a confidence band, a kinetic state, a prescription (recommended action), and a lifecycle state. Multiple situations can be grouped into a Theme.
Related: Divergence · ARC · Theme
The engineering line on the P&L: The cost center on the income statement that represents engineering salaries, infrastructure, tooling spend, and AI inference cost. Zamski operates against this line: executive intelligence for the engineering line on the C-suite's P&L.
Related: Tool stack ROI
Theme: A customer-defined grouping of related situations and ARCs. Themes organize the brief around the questions the buyer cares about. Customers describe a theme in natural language; the substrate drafts candidate ARCs and the customer finalizes the rule set.
Related: ARC · Situation
Track record: The brief section that publishes the calibration ledger: divergences flagged, divergences validated post-hoc, divergences acted on, precision over rolling windows. The track record is the line item a CTO can point to in a board update to validate the substrate's signal.
Related: Calibration · Confidence band
Velocity (gravity velocity): The recency-weighted signal-count input to the gravity score. Computed across 1-hour, 24-hour, and 7-day windows with the short window carrying 3x weight. High velocity indicates a divergence that is rapidly accumulating signal; low velocity indicates a stable or decaying pattern.
Related: Gravity · Entropy · Impact · Kinetic state