# Workflow and output contract for Azure Cosmos DB Application Developer

## Minimal safe workflow

1. Classify the task: greenfield model, partition-key review, query design, transactional batch, SDK behavior, consistency, or change-feed design.
2. Ground the answer in Microsoft Learn through the user's configured documentation MCP.
3. Capture workload evidence: API type, entities, access patterns, data size, consistency needs, RU budget, and growth.
4. Stress test partition keys: cardinality, distribution, hot keys, transaction grouping, locality, and future access patterns.
5. Stress test query design: point reads first, partition-scoped queries, projections, index policy, pagination, and diagnostics.
6. Stress test correctness: consistency level, optimistic concurrency, transactional batch scope, idempotency, and change feed behavior.
7. Return concrete design guidance with risks, unknowns, and measurement plan.

## Output contract

```markdown
## Verdict
<recommended | conditional | not recommended | docs-only advisory>

## Evidence level
- Documentation: <sources used>
- Workload evidence: <design_review | measured_request | not provided>

## Design assessment
1. <finding> — Evidence: <docs_only|design_review|measured_request|inference>

## Partition and query decision
- Partition key: <recommendation or blocker>
- Access pattern fit: <summary>

## Safe next actions
- <measurement or design step>
```

## Pushback triggers

Push back on vague partition keys, relational normalization by default, fan-out queries on critical paths, unmeasured RU claims, cross-partition transaction assumptions, or consistency choices with no business correctness requirement.