Data estate assessment
Classify each table to a cloud-neutral role, map it to this cloud's product, score it against the AI-Ready Data Framework, and flag names an agent cannot reason over.
Semantic catalogue — state unknown
The catalogue's state could not be read from this API. That is unknown, not “not configured” — do not conclude either way from this card.
The profile selects which of the framework's requirements apply — 0 for agents.
Federate or migrate — egress inputs
“Query it where it sits” does not move data at rest; it moves it at query time, and someone is billed for the bytes. Tell us where the data lives today and we will price a full scan against the published rate, and say how many scans a month make moving it cheaper.
Leave a box empty and it stays unknown — nothing here is defaulted to zero. Without the migration cost the crossover is withheld rather than guessed: on transfer alone it comes out the same for every estate, so it would be arithmetic, not analysis.