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:
- Operational Domain
- Relevation Tier
- Implementation State
- Entropy Index
II. Operational Domain
Defines where the protocol exists in the grand machinery of things.
- INF - Infrastructure: Physical or virtual systems, metal-adjacent concerns
- CTL - Control Plane: Orchestration, coordination, or orchestral waving of hands
- OBS - Observability: Metrics, telemetry, dashboards, blinking lights
- AUT - Automation: Things that run when you're not looking
- SEC - Security: Authentication, authorization, paranoia
- INT - Integration: Glue, duct tape, or YAML
- EXP - Experimental: "It works on my machine" tier
III. Relevation Tier
Describes the protocol's spiritual and operational maturity.
- R0 - Pre-Relevant: Conceptual, theoretical, or whispered
- R1 - Emergent: Implemented at least once, probably
- R2 - Operational: Actively used without panic
- R3 - Canonical: Considered stable and repeatable
- R4 - Sanctioned: Officially blessed by FatMinLabs
- R5 - Immutable: Changing this would cause riots
IV. Implementation State
Used to determine how much pain the reviewer is about to experience.
- Draft - Ideas held together by comments
- Functional - Works as intended most days
- Validated - Tested by humans
- Deployed - Actively in use
- Entrenched - Too important to touch
- Legacy - Feared, but respected
V. Entropy Index (EI)
A semi-scientific measure of how chaotic the protocol is in practice.
- EI-0 - Deterministic
- EI-1 - Predictable
- EI-2 - Occasionally Surprising
- EI-3 - Requires Documentation
- EI-4 - Requires Ritual
- EI-5 - Summons Debugging Spirits
VI. Axial Mapping (Optional but Encouraged)
Each submission may be plotted on the Protocol Axial Matrix, using:
- X-Axis: Operational Coupling (0.0 - 1.0)
- Y-Axis: Adoption Density (0.0 - 1.0)
- Z-Axis (Implied): Relevation Depth
This positioning is advisory, not prescriptive, and may be recalculated during review using unspecified but authoritative methods.
VII. Submission Classification Example
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.