Discovery Gate

The Discovery Gate is the first quality gate in the iOS Factory Pipeline — a validation checkpoint that every opportunity must pass before it advances to the DESIGN phase. The gate requires a minimum score of 28 out of 40 on a structured opportunity validation rubric. Opportunities that score below 28 are rejected; they don't consume factory resources. Opportunities that score 28 or higher proceed to the design stage.

The purpose of the Discovery Gate is to solve the opportunity quality problem: the factory can build quickly, but building the wrong opportunity is worse than building nothing. Every hour spent on a low-quality opportunity is an hour not spent on a high-quality one. The gate acts as a filter that ensures factory resources flow toward vetted opportunities rather than reactive guesses.

The validation rubric evaluates four dimensions of an opportunity, totaling 40 points:

  1. Market demand signals (up to 12 points) — Reddit engagement metrics, App Store search volume, competitor review sentiment indicating unmet need. Strong demand signals show people are already looking for a solution.

  2. Competitive landscape (up to 10 points) — How saturated is the category? Are existing solutions outdated, poorly rated, or missing features? A weak competitive landscape means more room to win.

  3. Monetization potential (up to 10 points) — Can this app generate revenue? Subscription potential, category average revenue per user, willingness to pay indicators.

  4. Factory fit (up to 8 points) — Does the opportunity match the factory's capabilities? Complexity level, category experience, technical feasibility given available templates and components.

Research Station (see research-station) produces the raw data for the rubric — scraping Reddit, analyzing App Store data, scoring competitive density. The Router then applies the rubric and produces a score. If it's 28 or above, the opportunity clears the gate and enters the pipeline. If not, it's rejected and Research Station continues scanning.

The gate also serves as a forcing function for rigor in opportunity assessment. Because there's a defined numeric threshold, Research Station can't hand-wave about opportunity quality — the score either clears or it doesn't. This prevents the common failure mode where research confirms what the operator already believes rather than evaluating objectively.

Discovery Gate failures are tracked in the learning loop (see learning-loop). When an opportunity that cleared the gate fails later (app doesn't convert, reviews are poor, competitive landscape shifts), that data feeds back into the rubric scoring model. The factory's validation intelligence compounds with each opportunity — the rubric gets better calibrated over time.

  • ios-factory-pipeline — where Discovery Gate is the Step 2 quality checkpoint
  • research-station — the module that produces validation data for the gate
  • design-gate — the next gate (95/110) after Discovery Gate passes
  • learning-loop — the feedback mechanism that improves gate calibration over time