Skip to content

Add Ripple content history and bounded rollout - #26

Merged
LeiterConsulting merged 1 commit into
mainfrom
feature/ripple-bounded-rollout
Oct 7, 2026
Merged

LeiterConsulting merged 1 commit into
mainfrom
feature/ripple-bounded-rollout

Conversation

@LeiterConsulting

Copy link
Copy Markdown
Owner

Ripple’s footer opens /ripple/updates with actual content additions, separate operating checks, and conditional rollout target dates. The public mount exposes measured operations while all collection, assessment and research writers remain on the existing owner-private backend. Main VersionCompass navigation stays unlinked.

The backend adds durable queue/session/event/usage records, a persistent 150-request daily collection cap, bounded retries and five admitted 12-minute research sessions per day. No discovery source or vulnerability conclusion is added, and no paid integration is introduced.

Validation: 25 Ripple production-workflow tests using SQLite with the actual migration, TypeScript, private build; 162 VersionCompass tests, four ordered generation gates and Worker build. Browser rendering/native export are not claimed. The comparison report and export implementation are unchanged; affected Ripple live reads/writers and guard checks are recorded separately in the rollout audit.

@LeiterConsulting
LeiterConsulting merged commit 53ee045 into main Oct 7, 2026
2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant