Pre-Check Library¶
Use the Pre-Check Library when the core question is not how to recover after a platform has already acted, but whether you should proceed before the failure path hardens.
This section exists for action-before-commitment decisions:
- should proceed
- should not proceed
- risk gating
- checklist-driven review
- early warning before escalation
What a Pre-Check Is¶
A pre-check is a structured risk judgment made before you commit to a path that may later fail, get rejected, get restricted, or become expensive to reverse.
Use a pre-check when you need to answer questions like:
- Should we submit this now, or are obvious failure conditions already present?
- Should we accept this project, or are we entering a bad path before kickoff?
- Are the inputs clear enough to proceed, or are we about to create preventable review or delivery risk?
- Do we need a checklist first, or do we already have enough warning signals to pause?
How Pre-Check Differs From Platform Pages¶
The platform library explains how external systems enforce rules, reject submissions, or terminate accounts.
Use platform pages when the controlling system is already known:
- Stripe risk, reviews, disputes, and termination
- YouTube traffic, monetization, copyright, and channel enforcement
- Apple App Store review, privacy, and spam rejection
- IEEE submission validation failures
Use the Pre-Check Library when the main problem is still upstream:
- you have not committed yet
- you want to stop a predictable failure path
- the right next move is still a decision, not a recovery workflow
What Belongs Here¶
Pages in this section should stay narrow and diagnostic.
Good fit:
- pre-commitment risk checks
- pre-submit checks
- failure-path screening
- should proceed / should not proceed decisions
- checklist and risk-scan style pages
Not a fit:
- marketing advice
- generic productivity content
- growth playbooks
- proposal writing tips
- personal brand content
- broad commercial strategy
Current Themes¶
The first non-platform pre-check theme is:
This cluster focuses on one question:
- before accepting a project or client commitment, are there already enough warning signals to stop, pause, or restructure the engagement?
How to Use This Section¶
Choose a path based on how clear the risk already is:
- Start with a cluster page if you need to classify the problem.
- Start with a checklist if you need a fast structured review.
- Start with a risk scan if multiple warning signals are already active and you need a proceed / caution / stop decision.
Related Site Areas¶
Next Step¶
- Start with Client Risk Precheck if the main question is whether you should commit to the project at all.