Ongoing watch

Dependency Watch

CA$1,500 / quarter

A dependency-surface probe that examines visible dependency and config signals and compounds across repeated runs into a watch pattern. Delivered as a bounded evidence report each cycle.

The "watch" value grows through repeated Stability Ledger entries: each cycle records what changed since the last entry, so continuity compounds rather than restarting from zero.

After delivery, clients may provide private feedback and optionally approve a public testimonial.

What this probe helps you decide

Whether the agreed dependencies, frameworks, SDKs, or technical choices still deserve trust this quarter, need migration planning, or need a deeper scoped review.

Best lifecycle moment

After adoption, when trust must be re-checked over time without pretending there is live monitoring.

What you submit

An agreed watch list and the decision each item supports. The watch list is scoped before the quarter begins.

What product or surface this targets

Tell us the product, service, feature, SDK, app, workflow, dependency choice, AI-generated slice, or legacy module inside the repo/project that the probe should focus on. The repo is evidence; it is not automatically the whole target.

What we inspect

Changed-since-last-review public evidence, stale trust signals, support reality, documentation drift, migration pressure, and visible risk indicators.

What the report returns

CA$1,500 per quarter buys one operator-reviewed cycle for the agreed watch list: what was rechecked, what changed, risk table, migration pressure, and recommended action.

Stability Ledger

Each Dependency Watch cycle appends a new private Stability Ledger entry for the agreed watch list. The entry records what was rechecked, what changed since the last entry, what improved, what regressed, what remained unresolved, what new dependency or trust risks appeared, and the next closure move. Delivery is manual and witness-backed unless a dedicated runner or test fixture is explicitly scoped. It is not continuous monitoring, incident response, a public registry, or a guarantee.

Sample report / example

See the Gemini SDK Dependency Watch sample: a quarterly-style review of a dependency whose official support path moved while the old package remained installable.

What this does not include

  • Continuous monitoring
  • Incident response
  • Security audit
  • Unlimited advisory support

Boundary of claim

Dependency Watch is a quarterly scoped review of an agreed watch list only. It is not live monitoring, emergency response, or a guarantee that dependencies are safe.

Best-fit examples

  • Small agreed dependency/framework watch list.
  • Quarterly engineering leadership review.
  • Migration pressure and stale support signal tracking.