EMS LAN Certification Checklist

Use This Reference Carefully

Use this guide when event work may happen on local devices, offline files, or LAN-only tools instead of the live online dashboard. In this guide, EMS LAN Certification Checklist narrows that work to verification checklist for EMS LAN docs, routes, APIs, file handling, import/export, and reconciliation. Because this is a reference page, read it as part of the EMS LAN learning path rather than as an isolated checklist.

EMS LAN keeps an event moving when internet access is unreliable, but it also creates a second place where event records can change. Read the page for the decision it helps a person make, then use the steps and checks as a steady path from context to action to proof.

What This Reference Collects

This page is for checking details. Use it to confirm names, routes, records, fields, or certification points before relying on memory. The intended readers are Support leads and Release reviewers. If the guide names a dashboard route, service area, export, or record type, treat that name as a pointer to real operational responsibility.

• Primary surface or service: /rego/events/manage/offline-snapshot?id=:eventId and /rego/events/manage/offline-snapshot-history?id=:eventId.
• Records or contracts involved: Certification evidence and Snapshot audit entries.
• Main care point: Watch for losing track of which file, device, person, or import is trusted while attendee, staff, inventory, POS, or check-in records change offline.
• Proof worth keeping: event ID, snapshot filename, export time, device owner, import summary, sync-history entry, reconciliation count, and supervisor note.

How To Find The Right Entry

1. Search for the exact name or route: Begin by naming the EMS LAN situation, the owner, and the exact item involved in EMS LAN Certification Checklist.
2. Read the surrounding note, not only the matching line: Use /rego/events/manage/offline-snapshot?id=:eventId and /rego/events/manage/offline-snapshot-history?id=:eventId to connect the words on the page to the screen, file, service route, or record that people actually use.
3. Compare the reference with the live screen, file, or service evidence: Keep Certification evidence and Snapshot audit entries in view so the work stays tied to the records or contracts it can affect.
4. Save the evidence that proves the entry was checked: Before handing off, save proof such as event ID, snapshot filename, export time, device owner, import summary, sync-history entry, reconciliation count, and supervisor note so the next lead can tell which file and device state are trusted.

Confirm The Reference Still Matches Reality

You are ready to use the rest of this page when the purpose, owner, affected information, and proof are all clear enough for a second person to review.

1. Scope is named: The work is tied to the correct page, event, report, route, file, person, or record.
2. Impact is understood: The operator can explain the effect on offline files, check-in access, staff rosters, inventory counts, POS totals, and import history.
3. Proof is findable: The handoff points to evidence that the next lead can tell which file and device state are trusted.

End-to-end operator runbook

Use this numbered runbook to certify EMS LAN behavior or docs.

1. Step 1 - Identify the thing being verified. Identify environment, event ID, user role, API host, and test file format. This makes evidence specific.
2. Step 2 - Translate the technical name into plain language. Check route list, API list, file formats, role access, and expected record groups. This defines coverage.
3. Step 3 - Match the route, file, or record to real workflow. Test export, history, import, reconciliation, failed import behavior, and safety guidance. This proves the workflow.
4. Step 4 - Collect enough evidence to avoid guessing. Include wrong-event, missing-ID, unauthorized, stale-file, and suspicious-file cases. This covers high-risk failures.
5. Step 5 - Confirm implementation and docs agree. Record evidence paths, command output, audit entries, and built docs checks. This makes certification reviewable.
6. Step 6 - Send the result to the right owner. Mark EMS LAN docs complete only when all checks pass and Memory Bank records are updated. This closes certification.

Checklist

1. Checkpoint 1. ZIP export works and writes history. Use it to confirm the work is still on the right path.
2. Checkpoint 2. GZIP export works and writes history. Use it to confirm the work is still on the right path.
3. Checkpoint 3. Import rejects wrong-event or invalid files. Use it to confirm the work is still on the right path.
4. Checkpoint 4. Import summary lists affected record groups. Use it to confirm the work is still on the right path.
5. Checkpoint 5. Reconciliation pages explain proof for each record group. Use it to confirm the work is still on the right path.
6. Checkpoint 6. pnpm check and pnpm build pass. Use it to confirm the work is still on the right path.
7. Checkpoint 7. EMS LAN markdown has no unlabeled numbered list items. Use it to confirm the work is still on the right path.