# multi agent product draft

Website design and verification note

This visitor-facing summary uses the website’s documented capability baseline. It is not the original implementation document; complete technical records remain in the repository.

## Share context without merging everything

Planned

A bounded meeting space shares relevant summaries while preserving each specialist’s private context.

### Current evidence

Agent-scoped conversations and selective reports exist. Shared meetings and digest synthesis remain proposals in the product discussion.

### What still needs scrutiny

Cadence, participant selection and invocation rules need design and implementation. No continuously chatting agent group is implied.

## Choose models with a clear cost basis

Planned

Match configured capabilities to the assignment and assess total work cost, including retries and coordination.

### Current evidence

Agent-specific model configuration, fixed-model connections and attributed usage exist. Direct vendor API adapters, metered estimates and automatic routing remain future work.

### What still needs scrutiny

Do not equate lower token price with lower total cost or invent capability scores. Provider availability and unknown usage need explicit handling.