MESHLINK — GATEWAY
SPEC
Between the radio and the model
Sits at the retrans, validates what comes in, enforces who may ask what, and cuts the answer to fit the channel.
01 / RESPONSIBILITIES
Four jobs, done strictly
REASSEMBLE
Collect fragments, drop duplicates, and reject anything malformed without answering.
AUTHENTICATE
Verify the callsign, then check what it may ask and which tasks it may run.
ACKNOWLEDGE
#ACK before any work starts. Nobody waits blind.
FRAGMENT
Cut the answer to the session byte budget and pace it inside the duty cycle.
02 / TASKING POLICY
Nothing runs that was not authorised first
EXAMPLE POLICY — ILLUSTRATIVE
callsign N4
allow ?Q corpus=routes,logs
allow ?RUN sync.cache
budget tokens=512 seconds=40 bytes=200
log all # for AAR
CALLSIGNS
Provisioned, not claimed. An unknown origin gets no answer at all.
SPEC
TASK LIST
Named tasks with fixed arguments. No free-form execution over the air.
SPEC
BUDGETS
Per-callsign token, time and byte ceilings passed down with every job.
DRAFT
AUDIT
Every frame in and out logged locally, for the after-action review.
PLANNED
CONTACT
What does your net look like?
Radio, channel plan, node count, and what you already push over it.
TALK TO THE TEAM
ROGER
Received. We will come back to you direct.