A practical guide to current plan source and refresh entitlements in TEMIRIN using configured records, explicit market identity, current controls, and human review.
August 3, 2026 · 3 min read
Source capacity is the number of configured research inputs a workspace can maintain under its current plan, not a promise of complete market coverage. Count RSS feeds, HTTPS web sources, and any provider-configured Telegram or X inputs that the team actively owns. Then compare that count with the number of watchlist markets, review frequency, and people responsible for failures. A smaller curated set often produces better evidence than a large list nobody checks.
Estimate capacity from a representative week. Note how many sources publish useful records, how many duplicates are suppressed, which readers fail, and how many items receive an explicit market link. Include burst periods such as election nights or scheduled economic releases. The workspace needs enough room for deliberate coverage and testing, while the operator needs enough time to verify primary material and maintain credentials. Those are different constraints and both belong in plan selection.
Starter fits a focused solo workflow using public-wallet context, RSS, and HTTPS web sources. Pro Operator expands an active single-seat setup with provider-dependent Telegram and X inputs, alert paths, and faster refresh entitlement. Elite Desk supports a broader multi-source and multi-seat review operation. Fund adds professional-team capacity and controls, while Custom is handled through a sales-led scope. The live pricing page remains authoritative for exact limits and commercial terms.
Do not compare tiers by source count alone. Review watchlist-market capacity, refresh policy, connected accounts, alert destinations, team seats, permissions, paper-order access, and support needs. A source-refresh entitlement controls the scheduled policy available to the workspace; publisher behavior and provider availability can still delay observations. Likewise, adding an external alert channel improves routing options but does not change the underlying evidence quality or create an approval action outside TEMIRIN.
Upgrade pressure should come from a documented workflow constraint. Examples include a source list that repeatedly reaches its enforced limit, a legitimate need for a provider-configured connector, multiple authorized reviewers who need role-aware seats, or a refresh policy that no longer matches a time-sensitive publishing calendar. Capture the blocked action and expected owner before changing plans. Buying unused capacity without an operating design usually adds maintenance rather than clarity.
Also consider consolidation. Disable obsolete feeds, remove duplicate coverage, narrow an unfocused watchlist, and review destinations that nobody reads. Preserve historical evidence and audit records while removing the configuration from active use. If the remaining need still exceeds the entitlement, compare the next plan against that cleaned baseline. This produces a defensible commercial decision and keeps the team from paying for noise created by abandoned experiments.
After a plan change, verify the workspace entitlement shown by the product and test only the capabilities included in that tier. Add a non-sensitive source, observe its ingestion state, confirm the configured refresh policy, and check that authorized seats and alert destinations behave as expected. For a provider-dependent reader, validate credentials and access separately from billing. A paid entitlement cannot repair a revoked token, unavailable publisher, or incorrect channel identifier.
Review usage before the next renewal using retained configuration, source health, delivery attempts, and team ownership. Record which limits were approached, which features were actually used, and which sources produced attributable review value. Keep financial approval separate from research decisions. The purpose of plan governance is to fund a maintainable current workflow, with clear limits and responsibilities, rather than advertise capabilities the workspace has not configured or the product does not provide. Include inactive seats and unused destinations in that review.
Plan displays can state configured-source count, watchlist capacity, refresh interval, seats, available snapshot history, and available alert channels, with each value tied to a product surface the workspace user can inspect.
Compare active configured-source usage with the plan entitlement, then inspect the source record and recent ingestion status. Capacity, provider health, and source configuration are separate facts with separate records.
The same field names should remain consistent wherever they are available: stake cap, source and category states, max-stake overrides, confidence settings, free-capital percentage, price-move guard, and kill switch.
