Define TapAuth security-gated public readiness - #6
Closed
devkyato wants to merge 1 commit into
Closed
Conversation
Owner
Author
|
Closing stale draft readiness PR leftover from earlier agent work. Current releases and main already supersede this draft. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What changed
Adds a security-gated public-readiness plan covering one-time tap sessions, proper administrator authentication, transactional attendance, durable offline reconciliation, process separation, deployment hardening, upload safety, usability, documentation, and release testing.
Why
TapAuth must not be promoted as production-ready while its identity and privacy boundaries remain unsafe. The plan separates legitimate usability and discoverability work from premature public deployment.
User and developer impact
This establishes explicit release blockers and a path from experimental prototype to independently reviewable pilot software.
Validation
Documentation-only change grounded in the current 1.1.0 routes, runtime initialization, storage, deployment scripts, dependency policy, and CI coverage.