GGridiron LegendDesign Bible · v1.4
▶ Play QB ChallengeFranchise ModeSeason Recaps

Document 07 · Gridiron Legend

Future Enhancements Backlog

CompanionReference

GRIDIRON LEGEND

Future Enhancements Backlog

Companion to the Design Bible (v1.3 — ARCHITECTURE LOCKED)

Purpose

The Design Bible is locked. This document exists so that locking the Bible doesn't mean locking thinking — new ideas, feature requests, "what if we also..." moments, and expansion concepts still have a home. They just don't go straight into the Bible anymore.

The rule: anything that would have been a Bible edit before the lock goes here instead, until a deliberate decision is made to reopen the Bible for it — which is a different, heavier action than adding a paragraph to a module.

How an item moves from here into the Bible

An entry in this backlog is not a commitment. It becomes one only when:

  1. A phase of the roadmap (Stress Test, Engineering Spec, Prototype, Alpha, Beta) surfaces a concrete reason it's needed, or
  2. The Chief Architect explicitly decides to reopen the Bible for a new expansion cycle (a deliberate, named event — e.g., "v2.0 Expansion Pass" — not a quiet edit).

Items that turn out, on reflection, to be a bug, contradiction, or architectural flaw in the locked Bible do not belong here — they go straight back to the Bible under the existing three-category reopen policy stated in its lock banner.

Entry format

Each entry should carry enough context to be picked back up cold, months later, without re-litigating the whole conversation:

### [Short Title]
- Origin: (who/what surfaced this, and when)
- Category: New Mechanic | Expansion Module | Cross-Universe (Legend Engine) |
            UI/UX Idea | Monetization Idea | Other
- One-paragraph description
- Which existing module(s) it would touch, if built
- Why it was deferred rather than built now

Backlog

(Empty at time of lock — v1.3. No items have been deferred yet; this document is seeded and ready to receive them as Phase 2 and beyond proceed.)

Notes on scope discipline

A few things flagged during the Bible's own construction were deliberately deferred to "later" without being formally logged as backlog items — worth carrying forward here explicitly so they aren't lost:

  • The "Legend Engine" cross-game architecture discussion — multiple modules (3, 4, 5, 8) flagged strong reuse potential for Diamond Legend and Bitcoin Speedway (scheduling/standings, ownership/RiskState pattern, market-tier/revenue-sharing, staff Hot Seat/buyout framework) but explicitly deferred designing a shared engine to avoid derailing the football-specific work. This is the single largest deferred idea in the project and probably deserves to be the first real entry logged here.
  • Play-calling as an optional sub-system — Module 1.2 states the default loop stays at ownership/GM altitude, but explicitly leaves the door open for "a later module" to add optional tactical play-calling for players who want it. Never designed, never scoped — a candidate entry.
  • Non-risk StateMachineFramework instantiations — Module 2.7's generalization (v2.1) explicitly noted that a coordinator's HC-readiness track, a player's career-arc phase, or similar progressions could be modeled with the new generic framework, without committing to actually building any of them. Candidate entries, not commitments.