# MailSchema type proposal

Status: proposal. Submission does not establish acceptance or implementation compatibility.

This is the writing guide. Use the examples and checker at `/contribute/` to prepare the JSON contribution file. New types, amendments and implementation declarations use the same validated ingestion path.

## Name and summary

- Proposed type name:
- One-sentence description:
- Contributor name and public website:
- Proposed maintainers and their public websites:

## Workflow

Describe the request a person receives, the actions an agent should understand and the services that could use the same definition.

## Existing work

Identify related MailSchema types and existing standards. Explain the additional behaviour this proposal needs.

## Definition

- Target and applicable revision rules:
- Available operations:
- Required inputs and validation:
- Permission checks:
- Human participation:
- Results and failure states:
- Retry and duplicate handling:
- Recovery after an interrupted exchange:

## Examples

Show a successful exchange and the failure cases needed to understand the interaction.

## Representation

Include a proposed representation or state that it is undecided. Identify any existing vocabulary or schema format used.

## Open questions

List decisions that remain unresolved.

## Implementation evidence, if available

- Client and service:
- Maintainer and ownership:
- Exact type and execution profile versions:
- Operations covered:
- Evidence location and reproduction instructions:
- Support declaration or independently reproduced test:

The current Registry accepts support declarations and submitted test reports. An independent reproduction claim needs separate review; it cannot be selected as a certification status in a vendor submission.