TIP-1: The TIP Process

[pfarnsworth]

Summary

First tltv Improvement Proposal. Defines the formal process for proposing, discussing, and adopting changes to the tltv protocol.

What's in TIP-1

• Format: Markdown with YAML front matter
• File naming: tip-NNNN-descriptive-slug.md in tips/ directory
• Types: Standards Track (protocol changes) and Process (meta)
• Lifecycle: Draft → Accepted → Final (+ Withdrawn, Rejected, Superseded)
• Required sections: Abstract, Motivation, Specification, Backwards Compatibility, Security Considerations, Rejected Alternatives, Reference Implementation
• Spec relationship: TIPs feed the spec — when a TIP goes Final, its text gets folded into PROTOCOL.md. The spec is always the single source of truth.
• Spec versioning: major.minor (V1.0 → V1.1 → ...). Minor bumps when TIPs are incorporated.
• Traceability: Changelog entries and inline *[Added in V1.1 (TIP-2)]* annotations
• Governance: Lightweight for now, with hooks for formal review periods later
• Template: tips/tip-template.md included — copy and fill in

Design influences

BitTorrent BEPs, Python PEPs, Matrix MSCs, Rust RFCs — taking what works and leaving what doesn't.

Files

• tips/tip-0001-tip-process.md — TIP-1
• tips/tip-template.md — template for future TIPs
• tips/README.md — TIP index

[pfarnsworth]

First TIP defines how all future TIPs work. Process is lightweight now, grows with the project.

Approved.