Core configuration vs secondary configuration

Why layering?

PitchCopilot's report does not just give a single conclusion, but divides the research direction into core configurations, secondary configurations and observation items. This stratification allows readers to understand the differences in model confidence, data completeness, and risk exposure. If all signals are placed on the same layer, the report will appear rich but will actually be difficult to evaluate.

Core configurations usually represent market-implied pricing, model distribution, data premium baselines, and manual review that are all more consistent. The second-choice configuration represents an interpretable signal, but sample, price, schedule or lineup uncertainty makes it unsuitable as a primary research direction. If you want to understand the language behind weights, start by reading /guides/asset-weight-allocation.

Standards for core configuration

Core configuration is not synonymous with "will happen". It means that at the time of publication, the model believes that this direction is most consistent with the data and pricing differences. The administrator will check whether the report clearly describes the reasons, whether it uses compliance vocabulary, whether the restrictions are written out, and confirms that the settlement definition can be applied afterwards.

Core configurations are tracked separately by public performance. This is important because if the model also crams low-confidence items into the core layer, the long-term dashboard will reflect a decrease in quality. Readers can check the hit rate, Brier score and virtual point performance of the core configuration at /performance.

The value of the secondary configuration

Second-choice configurations are not inferior content, but rather ways to preserve research flexibility. There is clear Divergence in some events, but the data is not complete; some directions are greatly affected by lineup news and need to wait for confirmation before the game; there are also some conclusion models that support it, but the historical calibration is not strong enough to be listed as the core. These situations are suitable for secondary configuration.

For FPL players, secondary configurations can serve as alternative captains, rotation players, or defensive risk reminders. For creators, it can complement the level of the article so that the narrative does not have only one answer. When citing, you can refer to /guides/creators-citation-guide to avoid writing the second choice in an overly positive tone.

How to avoid misreading

The most common misunderstanding is to regard the core configuration as an absolute guarantee and the secondary configuration as unimportant. PitchCopilot's methodology emphasizes chance and calibration: misses can still happen with high confidence, and misses can still happen with low confidence. What really should be tracked is whether the long-term stratification is reasonable, that is, whether the core layer is stable and better than the secondary layer, and whether the model version is gradually improved.

This is where public performance, human review, and virtual points research intersect. Layering gives each conclusion its place, human review keeps the tone appropriate, and dashboards enable post-mortem inspection. To understand hit definitions, read /guides/settlement-hit-definitions.

How to determine the release threshold

The difference between the core and secondary selections comes from the joint decision of model distribution, data completeness, calibration records and manual review. If the market-implied pricing is consistent with the direction of the model and the actuarial premium rate reaches the threshold, it is still necessary to confirm that there are no major gaps in the event data. Conversely, even if the model score is outstanding, it may be relegated to second choice or watch as long as the lineup or schedule information is still highly uncertain.

This threshold design makes the report more like a research publication than a scoreboard. PitchCopilot will put the core configuration into public performance for stricter inspection, so the core layer cannot be over-inflated. The secondary layer retains useful signals to let readers know what other directions are worth pursuing, but the tone must be more cautious than the core layer.

When reading in practice, you can think of the core configuration as a "priority check" and the secondary configuration as a "supplementary situation". If you are an FPL player, the core configuration may influence captain and transfer research; the secondary configuration is suitable for identifying substitute options or defensive risks. If you are a creator, layering can help you arrange the main and secondary lines of the article to avoid expressing all opinions with the same intensity.

Additional reading reminder

If you just want a quick scan report, you can look at the configuration level first and then read back to the reasons. You should be wary if the core configuration is not supported by clear documentation, or if the secondary configuration is written to be as certain as the core. Good layering will give readers a sense of discipline in the model, rather than pushing every signal to the front.

FAQ

Can there be multiple core configurations?

Yes, but the greater the number, the greater the need to clearly state the weight and confidence to avoid diluting the main signal.

Will the second-choice configuration be included in performance statistics?

Yes, it is usually tracked separately from the core configuration to avoid mixing different confidence levels.

What are the uses of observations?

Observations alert readers to information that has not yet reached the configuration threshold, such as lineup, weather, or schedule changes.

This translation is for convenience only; the Traditional Chinese version prevails.