Protocol Submission Interface

(FML-PSI-01)

"All protocols must eventually answer for themselves."

Before proceeding, submitters are strongly encouraged to review the Protocol Taxonomy Below and ensure their work can be reasonably classified within the established operational and relevation model.

Submissions failing to align with known reality, physics, or common sense may still be accepted.

FatMinLabs Protocol Submission Taxonomy (FPTS-1.0)

I. Classification Overview

All protocol submissions are categorized according to the FatMinLabs Unified Relevation Model™ (FURM), which exists primarily to impose order on chaos and to give diagrams something to point at.

Each submission is evaluated along four primary axes:

II. Operational Domain

Defines where the protocol exists in the grand machinery of things.

III. Relevation Tier

Describes the protocol's spiritual and operational maturity.

IV. Implementation State

Used to determine how much pain the reviewer is about to experience.

V. Entropy Index (EI)

A semi-scientific measure of how chaotic the protocol is in practice.

VI. Axial Mapping (Optional but Encouraged)

Each submission may be plotted on the Protocol Axial Matrix, using:

This positioning is advisory, not prescriptive, and may be recalculated during review using unspecified but authoritative methods.

VII. Submission Classification Example

Protocol Name: FL-SYNC-2026-A
Domain: OBS / AUT
Relevation Tier: R3
Implementation State: Deployed
Entropy Index: EI-2
Axial Position: (0.62, 0.84)

"Stable, widely used, and only mildly haunted."

VIII. Closing Notes

Classification within this taxonomy does not imply endorsement, fitness for purpose, or continued sanity of the implementer.

All designations are subject to revision, reinterpretation, or ceremonial deprecation at the discretion of FatMinLabs.

1. Submitter Identification

2. Protocol Identification

3. Abstract / Summary

4. Implementation Status & Entropy

5. Axial Coordinates (Optional)

6. Reference Links & Attachments

Separate multiple links with commas
You may attach supporting documentation, diagrams, or evidence of functionality