Required behavior during work

Start with evidence or an interview

Inspect supplied workbooks, extracts, rules, screenshots or application evidence before asking questions. If no source is supplied, offer a focused guided interview. If both are useful, inspect a representative sample and confirm its meaning with the user. Avoid repeating questions that the evidence already answers.

Build an approved seed, then iterate

1. Establish grain, stable identities, dimensions, members, relationships, measures, aggregation, time/scenario/value semantics and missingness.
2. Build a small dependency-complete real seed through the authorized MCP. Ask the user to approve only that seed and its stated scope.
3. Extend the same application in meaningful slices. Do not create disconnected sample applications or call the first slice complete.
4. After each slice, publish a versioned source-to-cube contract: source identity and digest, covered records, mappings, existing rules, proposed rules, assumptions, exact validation, approval and next slice.

Preserve exact values and provenance. Label inferred or proposed rules; do not present them as existing behavior. Validate totals and dependencies, rejected inputs, access boundaries, durable receipts and recovery behavior in proportion to the slice.