# TEP-0000: TEP Process and Template

**Status:** Active
**Type:** Process
**Created:** 2026-08-28

---

## What is an TEP?

An **TEP** (TTEOP Extension Proposal) is the mechanism for proposing changes to the TTEOP specification. TEPs are the primary governance instrument for evolving the protocol.

## TEP Types

| Type | Description |
|------|-------------|
| `standards` | Changes to normative requirements in SPEC.md |
| `metric` | New metrics or changes to existing metric definitions |
| `adapter` | New provider adapters or changes to existing adapters |
| `privacy` | New privacy modes or changes to existing modes |
| `conformance` | Changes to conformance classes or test requirements |
| `process` | Changes to governance, TEP process, or contribution model |

## TEP Lifecycle

```text
Draft → Submitted → Under Review → (Accepted | Rejected | Withdrawn | Deferred)
                                           ↓
                                      Implemented
                                           ↓
                                      Integrated (in a versioned release)
```

### Status definitions

| Status | Meaning |
|--------|---------|
| `Draft` | Author is writing the proposal; not yet submitted |
| `Submitted` | Proposal is ready for review; posted as a PR |
| `Under Review` | Community review in progress; minimum 14 days for normative, 7 days for non-normative |
| `Accepted` | Proposal accepted; ready for implementation |
| `Rejected` | Proposal rejected; rationale documented |
| `Withdrawn` | Author withdrew the proposal |
| `Deferred` | Proposal deferred to a future version |
| `Implemented` | Implementation complete and tested |
| `Integrated` | Included in a versioned release |

## Review Windows

- **Normative changes** (standards, metric, conformance): minimum 14 days
- **Non-normative changes** (adapter, process): minimum 7 days
- **Security exceptions**: expedited, minimum 72 hours with advisory board notification

## TEP Template

```markdown
# TEP-XXXX: [Title]

**Status:** Draft
**Type:** [standards | metric | adapter | privacy | conformance | process]
**Created:** [YYYY-MM-DD]
**Author:** [name or pseudonym]

## Summary

[One paragraph summary of the proposal]

## Motivation

[Why is this change needed? What problem does it solve?]

## Specification

[The precise normative change. Include exact text, formulas, schemas, or code.]

## Rationale

[Why this approach over alternatives? What trade-offs were considered?]

## Backward Compatibility

[Does this break existing implementations? How is migration handled?]

## Conformance Impact

[Which conformance classes are affected? What tests need to change?]

## Test Vectors

[At least one test vector demonstrating the change.]

## Security Considerations

[Any security implications?]

## Privacy Considerations

[Any privacy implications?]

## Open Questions

[Unresolved questions for discussion during review.]
```

## Submission Process

1. Copy this template to `teps/TEP-XXXX.md` (request a number from the maintainer)
2. Fill in all sections
3. Open a pull request with the TEP file
4. The maintainer assigns the `Under Review` status
5. After the review window, the maintainer makes a decision (accept/reject/defer)
6. If accepted, implementation proceeds in a follow-up PR

## Appeals

A rejected TEP MAY be appealed by:
1. Requesting reconsideration with new evidence or arguments
2. Requesting a maintainer vote (for normative changes)
3. Requesting advisory board review (for governance or process changes)

Appeals must be filed within 30 days of the rejection decision.