A structured football playbook system for modeling, validating, teaching, and organizing American football concepts. Plays are stored as football semantics first, then rendered into fields, assignments, install plans, and matchup views.
The central model treats a play as 11 players plus formation, jobs, intent, timing, and matchup context. The UI does not store drawing paths as the source of truth. It derives routes, assignment cards, install context, youth explanations, and matchup overlays from normalized football contracts.
The project stabilized football language before investing heavily in interface polish. Formations, concepts, routes, assignments, fronts, and coverages became inspectable data.
A play is not stored as circles and arrows. The drawing is derived from football objects, which lets the system validate, teach, export, and compare the same canonical play.
The hard problem is domain correctness and workflow truth. Local file persistence avoids auth, sync, and collaboration work until the product loop is more stable.
Actions that implied unsupported backend behavior were removed or renamed. The interface only exposes real collection behavior where contracts and persistence exist.
Football has technique, timing, intent, and coaching language embedded in every play. The solution is a layered model: canonical data first, then render and teaching adapters.
Coaching is contextual, but validation needs repeatability. Stable contract fields, deterministic IDs, and render manifests keep the engine testable.
Youth coaches, coordinators, players, and curious fans need different explanations. The same underlying play objects can be presented through different teaching layers.