Skip to main content

K12 Safety Tools and Capabilities

Platform Architecture​

From an external integration perspective, the K12 platform works by taking a structured request, combining it with plan and organization context from MOEOP, applying the right prompt for the use case, and returning a structured JSON response. The important part is not the transport layer. The important part is how the request data and MOEOP context flow into the final output.

  • Client layer: the caller sends structured plan, form, content, and prompt fields rather than a single untyped text blob.
  • Use-case selection: district and facility planning are separate from annex editing, and Suggest Roles and Responsibilities is a branch of the functional or hazard annex editing flow.
  • MOEOP context: annex flows use freeform block and section labels from the request, while QRG flows use QRG metadata such as instructionFor and tag-management mode.
  • Deterministic workflow step: before prompt execution, the platform picks the prompt family and, for suggest-role and QRG flows, narrows the role scope deterministically.
  • Prompt inputs: the request data and MOEOP context are converted into real prompt replacement fields such as block, section, text, list_of_roles, list_of_role_universe, and current_working_role_roster.
  • How each use case works: planning edits the requested planning section, annex editing revises the current annex section, suggest-roles narrows the role set before generating responsibilities, and QRG flows either generate role cards or revise one QRG phase section.
  • Returned result: the caller receives structured JSON that the UI or integration can render directly.

Available Tools​

The K12 Safety platform exposes 17 tools organized into three functional groups plus cancellation tools. All tools follow the same async pattern: kickoff a job, poll for status, then fetch the result.

Tool Inventory​

Tool IDGroupWhat It Does
k12-district-planning-kickoffEOP EditingStart district-level EOP planning edits
k12-facility-planning-kickoffEOP EditingStart facility-level EOP planning edits
k12-functional-annex-kickoffEOP EditingStart functional annex editing
k12-hazard-annex-kickoffEOP EditingStart hazard annex editing
k12-functional-annex-suggest-roles-kickoffEOP EditingSuggest missing roles for a functional annex
k12-hazard-annex-suggest-roles-kickoffEOP EditingSuggest missing roles for a hazard annex
k12-annex-editing-kickoffEOP EditingCompatibility kickoff for general EOP annex editing
k12-annex-editing-statusEOP EditingCheck status of an editing job
k12-annex-editing-resultEOP EditingFetch the result of a completed editing job
k12-qrg-generation-kickoffQRG GenerationStart QRG generation from an Emergency Operation Plan
k12-qrg-generation-statusQRG GenerationCheck status of a QRG generation job
k12-qrg-generation-resultQRG GenerationFetch generated QRGs from a completed job
k12-qrg-editing-kickoffQRG EditingStart a QRG section editing job
k12-qrg-editing-statusQRG EditingCheck status of a QRG editing job
k12-qrg-editing-resultQRG EditingFetch the result of a completed QRG edit
k12-cancel-task-requestEOP ManagementCancel a pending or in-progress EOP editing job
k12-qrg-cancelQRG ManagementCancel a pending QRG generation or editing job

Async Integration Pattern​

Every tool group follows the same three-step pattern. A consumer kicks off a job, polls until the status resolves, then retrieves the finished output.

  • Kickoff returns a requestId and an initial status of accepted.
  • Status is polled by passing one or more requestIds. The response includes the current status for each.
  • Result is fetched once status reaches a terminal state (success or error).
  • Cancel (where available) transitions a pending or in-progress job to cancelled.

Workflow Families​

The tools are organized around three workflow families. Each family covers a distinct safety documentation task.

EOP Editing​

Handles AI-assisted editing of Emergency Operation Plan functional annexes. A user submits an EOP plan ID along with the content to edit and an optional prompt describing the desired changes. The system generates revised content that aligns with the plan's existing context and returns it for review.

Preferred kickoff tools: k12-district-planning-kickoff, k12-facility-planning-kickoff, k12-functional-annex-kickoff, k12-hazard-annex-kickoff, k12-functional-annex-suggest-roles-kickoff, k12-hazard-annex-suggest-roles-kickoff

Compatibility kickoff tool: k12-annex-editing-kickoff

Status and result tools: k12-annex-editing-status, k12-annex-editing-result

QRG Generation​

Transforms an entire Emergency Operation Plan into a set of role-specific Quick Reference Guides. The system classifies each annex, identifies target audiences (teachers, administrators, support staff), maps them to roles, and generates structured action items organized into BEFORE, DURING, and AFTER phases.

Tools: k12-qrg-generation-kickoff, k12-qrg-generation-status, k12-qrg-generation-result

QRG Editing​

Modifies an individual section of an existing Quick Reference Guide. A user specifies which section (BEFORE, DURING, or AFTER) to change, provides the current content, and describes the desired edit. The system returns an updated version of that section.

Tools: k12-qrg-editing-kickoff, k12-qrg-editing-status, k12-qrg-editing-result

Cancellation​

All three workflows support cancellation. EOP Editing jobs can be cancelled using k12-cancel-task-request. QRG Generation and QRG Editing jobs can be cancelled using k12-qrg-cancel.

Next Steps​

Implementation Guide

End-to-end guide: deploy infrastructure, configure auth, and integrate with all K12 endpoints

Authentication Setup

OAuth credentials, environment URLs, and required headers

Workflows

Detailed walkthrough of each workflow's tool sequence and status lifecycle

Tools Reference

Complete tool specifications with request and response schemas