# 0007: MeshPRS 1.0 requires position, message/ack, telemetry, object and status

- **Status:** accepted
- **Date:** 2026-10-29
- **Answers:** OPEN-QUESTIONS Q2
- **Spec sections affected:** §15

## Context

Decision 0002 gave every service a code point. The trial should prove a small core first; airtime and the room-server limits (findings §3.4) make bulletins and neighbour reports the riskiest.

## Options

1. **Position only:** ships soonest; against: messaging is the main ask from hams.
2. **Core five required, the rest optional:** position (0x00), message (0x01), ack (0x02), telemetry (0x03), object/item (0x05) and status (0x09) required; weather (0x04), bulletin (0x06) and neighbour report (0x08) optional.
3. **Everything required.**

## Decision

Option 2. Query (0x07) is required to be *parsed* (it is never gated) but not to be answered. Decided by Alec, 2026-10-29, on the lead agent's recommendation after the Phase 3 review.

## Consequences

§15's profiles name the required subtypes. A 1.0-compliant iGate gates every required subtype; an optional one it does not implement is dropped as `unknown subtype`.