Skip to content

Launch RecallManager v1 beta#1

Draft
antonflor wants to merge 12 commits into
mainfrom
agent/recallmanager-v1-launch
Draft

Launch RecallManager v1 beta#1
antonflor wants to merge 12 commits into
mainfrom
agent/recallmanager-v1-launch

Conversation

@antonflor

@antonflor antonflor commented Jul 19, 2026

Copy link
Copy Markdown
Owner

What changed

Transforms RecallManager from a single interactive DISM toggle into a state-aware Windows Recall privacy manager.

  • adds status, audit, plan, apply, export, verification, backup, and restore workflows
  • adds declarative AuditOnly, UserControlled, SnapshotsOff, and PrivacyHardened profiles
  • audits the Recall optional feature plus documented machine/current-user Windows AI policies
  • keeps snapshot contents outside the tool's data boundary
  • adds native confirmation and WhatIf behavior for changes
  • adds Mermaid architecture, state, transaction, profile, website-boundary, sitemap, and release-gate diagrams
  • adds stable screenshot and social-card placeholders for future launch assets
  • adds a future recall-manager.net handoff for a separate private website repository
  • records RecallManager as free, open source, community-first, ad-free, and non-commercial in scope
  • explicitly parks advertising, AdSense, paid tiers, accounts, subscriptions, and monetization work
  • adds Pester, PSScriptAnalyzer, Windows PowerShell/PowerShell 7 CI, release ZIP packaging, and SHA-256 checksums

Why

The original script could only report and toggle one optional feature. Recall's effective state can also depend on policy, user scope, eligibility, opt-in, and restart state. This launch makes those layers visible and creates a reversible desired-state workflow.

The future public website will use recall-manager.net, but its implementation belongs in a separate repository that remains private until launch. This application repository keeps only the handoff, canonical technical documentation, and temporary launch placeholders needed for that later work.

Safety impact

  • Changes Windows policy when an apply profile is selected
  • Can change/remove the Recall optional feature in PrivacyHardened
  • SnapshotsOff and PrivacyHardened may cause Windows to delete existing Recall snapshots
  • May require restart
  • Backs up current feature and policy metadata before changes
  • Does not read, decrypt, upload, or export Recall snapshot contents

Website boundary

  • domain reserved: recall-manager.net
  • website implementation deferred until the application is launch-ready
  • website code will live in a separate private repository during development
  • GitHub Releases remain the canonical download source
  • website-specific planning assets can be moved out of this repository after launch
  • monetization and advertising are explicitly out of scope

Validation completed

  • JSON profile file parsed successfully
  • all SVG placeholders parsed successfully
  • both GitHub Actions workflow YAML files parsed successfully
  • branch remains ahead of and not merged into main
  • GitHub reports the draft PR as mergeable
  • superseded website brief removed and replaced with docs/future-website-handoff.md

Validation still required before merge

  • GitHub Actions on Windows; no run/status has surfaced on the PR head yet
  • unsupported/non-Copilot+ Windows device test
  • eligible Copilot+ PC test
  • SnapshotsOff apply and restore
  • PrivacyHardened apply, restart, and restore
  • real screenshot capture/redaction

Test branch

agent/recallmanager-v1-launch

Keep this PR in draft until the real-device launch checklist in docs/testing.md is complete.

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