Summary
Real Reach Journal screenshots can contain intimate/dyad context, actor names, request timing, response notes, and synthetic smoke-test artifacts. They should not be casually published.
Observed behavior
A real Reach Journal screenshot was excluded from the public repo because it showed private journal context, older UI wording, and a smoke-test event.
Expected behavior
The project needs a public-safe way to demonstrate Reach Journal without exposing private dyad history.
Privacy/truth impact
High. The Reach Journal is local-first and can contain intimate subjective response notes. Screenshots are public truth surfaces and should not leak private response context.
Possible approaches
- demo/sample journal mode with synthetic entries
- screenshot scrubber/redaction helper
- docs-only mockup generated from fixture data
- UI control to hide request IDs/notes/addresses before capture
Acceptance criteria
- Public Reach Journal screenshots use synthetic or scrubbed data.
- Current UI wording is represented accurately.
- No private response notes, request IDs, MACs, or raw events appear in public artifacts.
Summary
Real Reach Journal screenshots can contain intimate/dyad context, actor names, request timing, response notes, and synthetic smoke-test artifacts. They should not be casually published.
Observed behavior
A real Reach Journal screenshot was excluded from the public repo because it showed private journal context, older UI wording, and a smoke-test event.
Expected behavior
The project needs a public-safe way to demonstrate Reach Journal without exposing private dyad history.
Privacy/truth impact
High. The Reach Journal is local-first and can contain intimate subjective response notes. Screenshots are public truth surfaces and should not leak private response context.
Possible approaches
Acceptance criteria