Answer for how things are today, not how they should be. Nothing is sent anywhere unless you choose to.
See which gaps Weave would bridge in your estate
Every line above is something Weave addresses without a rewrite: it parses and translates the COBOL, spawns an agent for each legacy-to-modern gap, and runs a self-healing master agent that repairs the bridges as the core changes, read-only by default with every write authorized and audited. The assessment maps that to your stack and tells you where the self-healing layer fits and what a first engagement looks like. No calls, no obligation.
This is a directional self-check, computed in your browser from your own answers. It does not connect to, scan, or touch any system, and it is not an audit. "Not sure" is counted as a risk on purpose: an assumption you cannot evidence is one you cannot rely on. Weave itself runs read-only by default in your environment; any write to a legacy system is authorized by you and recorded in a tamper-evident audit log.