update-ecosystem-hub

To check your knowledge hub for stale content, scan published pages for verification dates and prioritize the oldest entries. The staleness check compares these dates against live source data from GitHub, Jira, and Google Docs to identify outdated information.

Yes, you can selectively update HTML pages without rebuilding the entire ecosystem hub. After generating a structured change report and receiving user approval, the tool applies edits only to specific pages and refreshes their verification dates.

A staleness check reconciles live source data by performing a parallel source fetch across Slack channels and Google Docs. It compares these live updates against the published hub and organizes findings into new, changed, stale, and failed sources.

The best way to prepare a source-backed change report is to sweep live source systems for new or changed information and compare it against the published hub. This process categorizes findings into new, changed, stale, and failed sources for user approval.

Yes, the ecosystem hub refresh works with local transcripts and documents. The live source sweep checks local files alongside Google Docs, GitHub repositories, Jira tickets, and Slack channels to find new or changed information for the update process.

You need user approval before applying selective HTML updates to maintain a controlled, source-backed refresh. This requirement ensures that only verified changes from the structured change report are applied to the knowledge hub, preventing unintended edits.