--- name: frc-season description: "Use when selecting or interpreting an FRC season, manual, update, Kit of Parts or software baseline." --- # Season and authority review Read [grounding policy](../../docs/grounding.md). Start with the [learning brief](../../docs/briefs.md): npm run brief -- --workflow season --season YEAR --as-of YYYY-MM-DD. The brief is optional scaffolding, not a source-reading substitute. No vault is required; local catalog use must be explicitly configured. ## Establish context - Requested season and event. - Manual edition and update trail. - Decision date and deadline timezone. ## Work through the evidence 1. Open official manual and updates; identify the rule or explicitly unresolved question. 2. Separate final rules, previews, announcements and planning pages. 3. Record conflicting deadline wording and transaction-specific evidence. Inspect unmatchedQueries, omitted counts, source versions and review dates. Open relevant official/pinned sources before factual decisions. Keep source findings, recommendations and unknowns separate. Never infer compatibility from an empty season list or a matching keyword. ## Reviewable output Deliver a dated decision table with claim, authority, applicability and unresolved items. For each material claim identify source URL/version, applicability and verification level. Record actual commands/results separately from proposed tests. - Every legality claim has an official edition/rule citation. - Unknown future timings or dimensions stay unknown. - Team registration/payment status is not assumed. No hardware operation or deployment is authorized by this skill. Do not infer physical safety, CAD validity or model effectiveness from static review or passing software fixtures. Source/file/dependency licenses must be checked before copying. Use the [hardware rule reading map](../../docs/rulebook-hardware-review.md) before selecting components. Require event stage and manual/update revision as well as year; the 2024 archive includes Championship radio and weight changes. A named event remains unresolved until its edition is matched.