When Official Sources Disagree: What to Verify Before You Decide
An official page is not automatically the final answer just because it is official. A pricing page, a help article, a developer document, and a terms page can describe the same condition at different scopes or with different status language.
That is a different evidence state from silence. The guide to questions official documentation leaves open deals with an operation for which the reviewed material does not provide a same-scope answer. This article deals with a subject for which multiple official records exist but do not line up. Keeping those states separate prevents an unanswered question from becoming a capability verdict, and prevents a conflict from being flattened into a single preferred sentence.
Recorded source conflicts
A conflict row means the reviewed sources address the same subject but do not line up. It is not a decision about which source is correct, why the difference exists, or what the provider intended. The source statements and their conditions stay visible below.
| Provider / subject | Record | Sources and statements | What remains unresolved |
|---|---|---|---|
| Teachable Community availability | Canonical record Preserved in the structured cohort record. |
| The canonical record preserves a pricing-page feature listing beside a Help Center statement that Community is in maintenance mode: existing communities will continue to work and uptime will be maintained, while no new features or active bug fixes are planned; Community is unavailable for new schools and for schools that have not previously created a community. It does not decide which statement controls. |
| Circle Affiliate tier labels | Research record Recorded in the research notes and kept separate from the canonical pricing claims. |
| The research record says the same referral-volume bands and rates are paired with different labels for the middle and upper bands. Compare the band and rate, not the label alone. |
| Mighty Networks Affiliate reward condition | Research record Recorded in the research notes and kept separate from the canonical pricing claims. |
| The current landing-page material and the older agreement describe different reward conditions. The record leaves the condition to verify at the point of application. |
| Skool Pro transaction-fee scope | Research record Recorded in the research notes and kept separate from the canonical pricing claims. |
| The general pricing and analytics pages omit a transaction-size condition while the payments FAQ adds a higher-rate bracket. The difference is a scope question that should remain visible. |
| Skool and Stripe Subscription-billing comparison rate | Research record Recorded in the research notes and kept separate from the canonical pricing claims. |
| A Skool help page and the current Stripe Billing pricing page show different comparison rates. The record does not treat either rate as the platform's own extra charge. |
| Patreon Payment-processing scope | Research record Recorded in the research notes and kept separate from the canonical pricing claims. |
| The sources cannot be combined for lower-value payments without clarification because one describes a uniform rate while another introduces a threshold. |
Uncertain or changing states
A status such as maintenance, beta, early access, or paused is not a stable capability label. Preserve the status wording, the object it applies to, and the source date status before using it in a decision.
| Provider / subject | State | Recorded statement and source |
|---|---|---|
| Teachable Community | Maintenance mode | The Teachable Help Center says Community is in maintenance mode: existing communities will continue to work and Teachable will maintain uptime; it is no longer available for new schools or schools that have not previously created a community, and Teachable is not adding new features or actively fixing reported Community bugs. Teachable Help Center — checked 2026-09-02; source-date status: Updated over 3 weeks ago (exact date not displayed). |
| Patreon Email-list import | Beta / early access | The research record describes this as an email-only subscriber feature in early access; it is not evidence of paid-subscription migration. Patreon email-list import — checked 2026-09-01; source-date status: Not recorded in the research note. |
| Mighty Networks Default plan for invites | Beta-labelled source | The research source list includes a beta-labelled invite document; the record does not establish a broader availability claim. Mighty Networks invite documentation — checked 2026-08-21; source-date status: Not recorded in the research note. |
| Patreon Creator Referral Program | Paused | The research record says the Creator Referral Program is currently paused. Patreon Creator Referral Rules — checked 2026-08-28; source-date status: Not recorded in the research note. |
Source-date audit across the canonical records
The checked-on date tells you when the record was retrieved. It is not the same as the source page's publication or update date. The audit below counts evidence records, including repeated mirrors of a source; it does not turn those repetitions into separate conflicts.
| Record group | Evidence records | No source-date field | Unclear source date |
|---|---|---|---|
| Existing pricing records | 75 | 75 | 0 |
| Existing limits records | 30 | 30 | 0 |
| Additional pricing records | 44 | 44 | 0 |
| Additional limits records | 63 | 63 | 0 |
| Newer pricing records | 82 | 78 | 4 |
| Newer limits records | 17 | 17 | 0 |
Across the canonical records: 311 evidence records were inspected; 307 have no source-date field, and 4 carry an unclear source-date status across 7 distinct source URLs. A missing source-date field is recorded as missing metadata, not as proof that a page has never been updated.
A conflict is not a verdict
The Teachable Community row is useful precisely because it keeps the pricing-page record and the Help Center record side by side. The Help Center record says that Community is in maintenance mode: existing communities will continue to work and Teachable will maintain uptime, while no new features will be added and reported Community bugs will not be actively fixed. It also says Community is no longer available for new schools or for schools that have not previously created a community. An existing school can therefore still be outside the stated availability scope if it has never created a community. The table does not decide which source controls, whether either page is current enough for a particular account, or why the wording differs.
The same discipline applies to the research-record examples. A changed tier label, a different reward condition, a threshold that appears in a single document, or a status such as beta may matter to a decision. None of those observations establishes intent. They establish a question that needs a narrower check.
How to check an official conflict yourself
- Define the object before comparing sentences. Write down the feature, plan, audience, payment route, country, app or web context, and the action you need to take.
- Open every relevant page from the provider’s own site. Save the page title, URL, visible update wording, and the date you checked it.
- Preserve the source’s own status words. “Maintenance,” “beta,” “early access,” and “paused” describe a state; they do not become a permanent yes or no by omission.
- Compare scope before wording. A general pricing label, a plan-specific help article, a developer endpoint, and an application-only term may not answer the same question.
- Record what each source says and what it does not say. Do not use the more convenient statement as a substitute for the missing condition.
- Ask the provider with both URLs attached. State the exact plan and operation, ask which condition applies now, and save the reply with the date and the account context.
- Recheck before a commitment when a source has no visible update date or uses a relative update label. A checked-on date tells you when you saw the page; it does not establish when the page changed.
How to handle a missing source date
Keep the checked-on date and the source-date status apart. The checked-on date records the retrieval event. The source-date status records whether the page showed a publication or update date, showed only relative wording, or provided no source date in the record.
When the source date is absent, avoid a chronology claim such as “the newer page says…” unless the page itself provides that basis. Describe the observation as time-bounded: this is what the page said when it was checked. When a page says it was updated “over” a period but hides the exact date, keep that relative wording instead of converting it into a guessed calendar date.
The source-date audit above also distinguishes an absent field from an explicitly unclear source date. Repeated records can point to the same URL, so evidence-record counts are not conflict counts. A large count of missing metadata does not prove that every underlying page lacks an update date; it shows that the date was not captured in the canonical record.
What the record lets you say
Use attribution and conditions: “The pricing page states this,” “the Help Center describes that status,” and “the reviewed records do not resolve which condition applies to this operation.” This makes the evidence useful without turning an unresolved difference into a product judgment.
Do not write that a provider is deceptive, careless, or acting in bad faith. The records show differences in statements, scope, and freshness; they do not show intent. Do not choose a vendor, reject a vendor, or rank a vendor from the existence of a conflict alone.
A useful decision note records the operation, the sources checked, the source-date status, and the follow-up question. If the answer arrives later, append it as a new dated record rather than silently overwriting the earlier observation.
Scope and Methodology
- The conflict table includes the required canonical Teachable conflict and additional conflicts recorded in the site’s research notes. Research-note records are labeled separately from canonical pricing claims.
- The source-date audit scans the site’s existing and added pricing and limits records. It reports metadata presence and does not infer a page’s publication history from a missing field.
- Each displayed source keeps its URL, checked-on date, verification method, and source-date status. The links are provided so a reader can repeat the check.
- The single Teachable Help Center page in this article was confirmed by a user screen check and extraction from the PDF text layer, recorded as “user screen confirmation + PDF text-layer extraction”; this does not claim Codex static retrieval or rendered-browser inspection for that page.
- This is a comparison of official documents and recorded research notes, not a product test. The operator has not paid for these platforms and has no first-hand product results to report.
- The article does not measure product quality, ease of use, support, migration success, or provider intent.
When the answer matters to a launch, migration, or recurring charge, keep the source pair and the follow-up answer together. That record is more durable than a single unqualified feature label.