PURPOSE
Trust starts with claims a buyer can inspect and challenge.
PowerHouse public content should explain what the enterprise product does, how a licensed record behaves, where uncertainty remains, and which terms depend on a customer agreement. It should not disguise forecasts as facts, imply guaranteed results, or blur the boundary between the B2B service and the separate consumer PowerHouse Picks business.
These standards apply to marketing pages, buyer guides, technical documentation, public examples, and methodology explanations on powerhouseaffiliates.com. Private customer agreements and integration documentation can contain additional obligations.
PUBLISHING STANDARDS
Six rules govern public product communication.
Separate facts from forecasts
Fixtures, participants, scheduled times, market data, model outputs, and editorial interpretation play different roles. Our public materials identify predictions and probabilities as forecasts rather than established outcomes.
Do not promise outcomes
PowerHouse does not describe a pick, confidence value, probability, model, product, or licence as a guaranteed winner. Sporting outcomes remain uncertain.
Explain product boundaries
Coverage, target output, field availability, delivery, and rights can depend on schedule, source state, quality gates, market availability, and the active licence.
Preserve provenance
Public documentation explains when attribution forms part of the record or licence. Customer transformations should not silently change the meaning of a selection, probability, or lifecycle state.
Correct material errors
When a public page contains a material factual, product, or technical error, PowerHouse updates the page and its review date. Operational API corrections follow the documented record lifecycle.
Respect marks and rights
Competition and team marks identify covered events only. Their use does not imply endorsement, sponsorship, or partnership unless expressly stated.
WHO OWNS WHAT
Responsibility changes across documentation and publication.
- 01
Product documentation
Maintained against the implemented API, delivery contract, lifecycle behavior, and entitlement model.
- 02
Methodology explanations
Describe qualification, uncertainty, withholding, and governance without exposing proprietary model internals or making unsupported performance claims.
- 03
Commercial guidance
Explains typical evaluation questions. The signed customer agreement remains the controlling source for pricing, rights, support, and service commitments.
- 04
Customer publication
Customers remain responsible for their own editorial judgment, local legal review, age gating, responsible-gambling measures, and audience-facing presentation.
The sports picks qualification methodology explains how candidates become enterprise records. The public API field dictionary documents the implemented record fields and lifecycle states.
CORRECTIONS
Material public errors are corrected at the source page.
A material error is one that could change a reasonable buyer's understanding of coverage, delivery, product behavior, rights, methodology, or a technical contract. We correct the affected page and update its last-reviewed date. Minor spelling and presentation changes do not require a formal correction notice.
API records follow a separate operational lifecycle. Customers should use stable IDs, status, result, and settlement fields rather than treating an initial response as a permanent snapshot. The complete behavior is documented in the sports picks API documentation.
AUTOMATION AND AI
Automation supports the product; accountability remains explicit.
PowerHouse uses automated systems in the sports intelligence and publishing workflow. Public content should explain the relevant role of models, normalization, qualification, and quality gates when that context helps a buyer evaluate the product.
Automated output is not treated as self-validating. A candidate can be withheld when identity, timing, market, field-completeness, quality, or licence conditions are not satisfied. Customers decide how licensed records are reviewed and presented in their own products.
CONTACT
Questions and correction requests go to PowerHouse Enterprise.
Send the page URL, the statement or field concerned, and any supporting evidence to pepe@powerhouseaffiliates.com. Product and commercial questions can also use the enterprise contact form.