2026-10-06 ยท CPH Network Reporting, Creator Publishing Hub website
Verified production counters and six-hour aggregate reporting for the Creator Publishing Hub homepage.
What changed
- Reports current published article inventory, CPH-processed graphics with local file evidence, and Facebook published-post totals verified directly from connected Page APIs. Scheduled posts are excluded.
- Adds completed audio counts, known duration and provider breakdowns backed by a deduplicated attachment ledger.
- Provides a public aggregate JSON feed with freshness and reporting coverage, and four homepage counters driven by that feed.
- Updates enrolled installations every six hours. Each site signs its reports; the public feed excludes domains, license keys, credentials, visitor information and content.
- Counts only fully retrieved Facebook published-post inventories; capped summary responses are not used. Definite failed credentials are held until changed, while healthy connections continue reporting.
Verification
- Eight existing owned installations independently inventoried before rollout; license terms recorded for preservation.
- Focused native WordPress source and collector checks passed with no provider calls and verified fixture cleanup. Hero tests cover null values, stale data and incomplete coverage.
- Connected Page published-post edges were retrieved to exhaustion using distinct IDs, with no time filter or post-text collection. Native summary responses were found capped and excluded.
- Independent live readback confirmed installed source hashes, accepted reports, active six-hour timers, unchanged license entitlements and an aggregate-only public response. Desktop and mobile browser checks confirmed the displayed values match the feed after the homepage cache was refreshed.
- Verified October 6 snapshot: 14,789 published articles, 2,827 evidenced graphics, 4,872 completed audio files with 158.6 known hours, and 12,640 retrievable Facebook posts. These are dated observations, not fixed counters.
Rollout
Deployed and verified on eight existing enrolled installations and the Creator Publishing Hub homepage. Initial aggregate reports were accepted from all eight sites, with six-hour reporting timers active. The managed scheduler uses companion 2026.10.06.003; the WordPress reporter and homepage remain 2026.10.06.002. The Facebook verifier reports four connected Pages; unavailable connections remain excluded and labeled.
Updating
- Replace the shared network reporter with this version on enrolled installations and configure the authenticated Hub collector.
- Owned deployments use a server timer for six-hour reporting; other installations require working WordPress cron.
- Existing customer reporting choices are retained. Expanded production reporting requires administrator consent; this update does not activate checkout or create customer licenses.
- Managed reporting services must use scheduler companion 2026.10.06.003. The original 2026.10.06.002 artifacts remain preserved; the companion corrects isolated service startup and delivery verification.
Scope and limitations
- Article and graphics totals are current inventory, not proof that CPH authored every historical article or all-time generation totals.
- Audio is an observed attached lower bound; deleted or previously unrecorded audio cannot be reconstructed. Unknown providers and durations remain unknown.
- Facebook totals describe published records currently retrievable from the connected Page APIs. Deleted or API-inaccessible posts are not inferred; the count does not claim that every post was authored by CPH.
- Offline or unenrolled installations do not contribute fresh production totals. Coverage and last verification are displayed.
- Facebook Page connections are verified separately; unavailable credentials are not treated as verified connections.
- This rollout covers eight enrolled owned installations. It does not automatically enroll every external customer installation or activate commercial checkout.