You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The .lumentis folder contains metadata necessary for advanced features like diff mode, but may also include sensitive transcript data that should not be committed.
Concerns
Diff mode and other advanced features are must-haves
Transcript data can be highly sensitive and should be protected
The wizard is already lengthy, so adding more questions should be avoided
Tradeoffs
committing full .lumentis data enables advanced features but risks exposing sensitive info
excluding .lumentis entirely protects sensitive data but loses out on advanced features
splitting .lumentis balances features and protection but requires careful implementation
Solution
We will split out sensitive parts of .lumentis folder and only commit the rest:
move input data out of .lumentis/wizard.json - .lumentis/sensitive-inputs/raw-data
move "questions for user to answer" data out as well - .lumentis/sensitive-inputs/clarifying-questions.md
add "no extra fields" zod validator for .lumentis/wizard.json to ensure the sensitive inputs can't accidentally end up in there
maybe add some docs (would be cool if there was some cool to do that)
Problem
The
.lumentis
folder contains metadata necessary for advanced features like diff mode, but may also include sensitive transcript data that should not be committed.Concerns
Tradeoffs
.lumentis
data enables advanced features but risks exposing sensitive info.lumentis
entirely protects sensitive data but loses out on advanced features.lumentis
balances features and protection but requires careful implementationSolution
We will split out sensitive parts of
.lumentis
folder and only commit the rest:.lumentis/wizard.json
-.lumentis/sensitive-inputs/raw-data
.lumentis/sensitive-inputs/clarifying-questions.md
.lumentis/wizard.json
to ensure the sensitive inputs can't accidentally end up in thereMisc
Based on discussion in this PR
The text was updated successfully, but these errors were encountered: