PUBLIC RELEASE

2026 FRC Security Classification Guide

  1. GENERAL
    1. Purpose
      1. This document provides instructions and guidance on the classification of technical information and strategic data related to the 2026 competition robot built by The RoboBees.
    2. Applicability and Scope
      1. This classification guide applies to information or material relating to the development, construction, and implementation of the 2026 FIRST Robotics Competition robot developed by The RoboBees.
      2. This guide will be used as the basis for derivative classification, downgrading, or declassification of information and material associated with the growingSTEMS FIRST Robotics Competition team The RoboBees.
    3. Office of Primary Responsibility (OPR)
      1. This guide is issued by, and all inquiries concerning content and interpretation, as well as any recommendations for changes, should be addressed to:
      2. Andrew Koch, PhD, Lead Coach (ankoch@growingstems.org)
    4. Classification Challenges
      1. If at any time, any of the security classification guidance contained herein is challenged, the items of information involved shall continue to be protected at the level prescribed by this guide until such time as a final decision is made on the challenge by appropriate authority.
      2. Classification challenges should be addressed to the OPR.
    5. Reproduction, Extraction, and Dissemination.
      1. Authorized recipients of this guide may reproduce, extract, and disseminate the contents of this guide, as necessary, for application by specified groups involved in robot development.
      2. Copies of separate guides issued to operating activities in application of this guide shall be sent to the OPR.
    6. Public Release.
      1. The fact that this guide shows certain details of information to be unclassified does not allow automatic public release of this information.
      2. Proposed public disclosures of information regarding the 2026 competition robot shall be processed through the appropriate channels, detailed in section 5.
  2. CLASSIFICATION DEFINITIONS
    1. Information within this project is categorized into three levels of sensitivity based on the impact of disclosure on the team’s competitive standing:
      1. ROYAL JELLY (TS): Information that, if disclosed, would cause serious damage to the team’s competitive advantage by allowing opponents to replicate or counter key mechanisms or software logic.
      2. HONEYCOMB (HC): Information that reveals strategic intent or subsystem integration that should remain internal until revealed during a competition.
      3. HONEY (H): Unclassified, yet sensitive data needing control.
      4. UNCLASSIFIED (U): Information intended for public release, sponsorship recognition, or general scouting.
    2. Information within this project is classified based on the damage that is expected to result as a result of the release of the information
      1. Competitive Advantage (CA) - Information that could allow other teams to gain a strategic or tactical advantage during the competition season.
      2. Design Insight (DI) - Information that provides insight into how the team designs our robot. This could allow other teams to reproduce our designs or find flaws in our robot. This could include the current season or could extend to future seasons.
      3. Controlled Disclosure (CD) - Information that is intended to be disclosed at a specific time in the season. Early release of this information could harm public image.
  3. CLASSIFICATION TABLE
Topic Classification Reason Declassify on
3.1 DESIGN DATA
3.1.1 Source CAD (original SOLIDWORKS files) ROYAL JELLY DI Never to be released to external parties.
3.1.2 Pit visualizations (non-measurable 3D models/animations) HONEYCOMB DI Start of the first competition (03/14/2026).
3.1.3 Basic robot dimensions & weight HONEYCOMB CD Start of the first competition (03/14/2026)
3.1.4 Full source code (GitLab repos) ROYAL JELLY DI Start of the next build season (01/09/2027).
3.1.5 Interface & planning docs (high-level architecture) HONEYCOMB CA, DI Start of the first competition (03/14/2026).
3.1.6 Autonomous routines (details) ROYAL JELLY CA, DI Start of the next build season (01/09/2027).
3.1.7 Game unique mechanism geometry and materials ROYAL JELLY DI Start of the next build season (01/09/2027).
3.2 STRATEGY & OPERATIONS
3.2.1 Gaps in system requirements ROYAL JELLY CA, DI Start of the first competition (03/14/2026).
3.2.2 Match playbooks / strategic exploits ROYAL JELLY CA Start of the next build season (01/09/2027).
3.2.3 Technical documentation (for judges) HONEYCOMB CD, DI Start of the first competition (03/14/2026).
3.2.4 Robot name and branding HONEY CD Release of the robot reveal (03/13/2026).
3.2.5 Scouting data ROYAL JELLY CA Start of the next build season (01/09/2027).
3.3 PERFORMANCE DATA
3.3.1 Prototype performance testing videos HONEYCOMB DI After the final event of the season (05/02/2026).
3.3.2 On-field performance CD Start of the first match (03/14/2026).
3.3.3 Promotional performance HONEY CD Release of robot reveal (03/13/2026).
  1. HANDLING AND DISSEMINATION
    1. Digital Storage.
      1. HONEYCOMB and ROYAL JELLY files must be stored in restricted folders
      2. HONEYCOMB and ROYAL JELLY code must remain in a private GitLab Repository. No public forks are permitted until the declassification date.
    2. Physical Security
      1. Non-team members (e.g, other teams, VIPs) should be approved by the Lead Coach or the Senior Robot Advisor prior to exposure.
      2. During build season, any ROYAL JELLY subsystem must be obscured from view when non-team members are present in the shop.
      3. When non-team members are in the shop, a verbal warning should be provided and a visual indicator (e.g., blue light) should be visible.
    3. Competition Security
      1. Non-measurable 3D models may be displayed on team tablets/monitors.
      2. Source CAD is prohibited from being opened on any laptop visible to the public in the pit area.
      3. Copies of technical documentation intended for judges must be stored securely until the morning of the first event.
  2. DECLASSIFICATION AUTHORITY
    1. Declassification occurs automatically based on the milestones listed in section 3.
    2. The OPR has the ultimate authority for declassification of team material.
    3. Requests for early declassification must be submitted to the relevant Manager and the Senior Robot Advisor for approval.
      1. Senior Robot Advisor (Carson Bistline)
      2. Senior Robot Technical Manager (Collin Haycraft)
      3. Strategy Manager (Colin Butrym)
      4. Public Relations Manager (Dominic Musolino)
      5. Business Manager (Andrew Koch)
      6. Event Manager (Everett Thompson)