Plans and provenance

Plans make Answerplane's interpretation explicit before or alongside execution. Provenance records what actually ran.

Plan contents

A plan can identify source operations, selected objects, relationships, filters, grouping, ordering, result bounds, requested presentation, and assumptions. It is source-neutral until compiled for a connector.

Compilation

The same intent can compile to SQL, a document aggregation pipeline, a file query through DuckDB, or an approved API tool. Connector-aware quoting and capabilities are applied at this stage.

Provenance

The answer retains enough evidence to audit its route: source, scoped identity, operation, relevant metadata, and result characteristics. Sensitive credentials are never part of provenance.

Why both matter

A correct plan with a failed operation is an execution problem. A successful operation from the wrong plan is a correctness problem. Review both when investigating an answer.