Help prove Citadel's activation: 25 installs, verified handoff, and 7-day return #182
SethGammon
started this conversation in
General
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Help prove whether Citadel delivers repeat use
Citadel now has broad attention. The harder question is whether independent users reach a verified handoff, resume the work, and return after seven days.
This is not a request for testimonials. Failures count. Missing evidence stays unknown.
The milestone
The first cohort targets:
Seven-day return is calculated only from successful installs observed for at least seven days. Citadel will not claim retained human use until every gate passes.
Share your journey
Use the current
mainbranch and complete a real, non-sensitive task through Citadel. From the target repository, run:If your Citadel source clone is separate from the target project, run:
The command writes
.planning/product-proof/activation-share.jsonand prints the same JSON. It performs no network request.Review the file. If you consent, post only that JSON object as a comment below. Run the command again after day seven and reply with the updated object. The opaque ID stays stable, so an update replaces the earlier observation instead of counting one install twice.
Privacy boundary
The bundle contains only:
The schema rejects prompts, repository names, paths, commands, source code, user identity, tokens, secrets, and extra fields.
Posting is public and GitHub shows your account. The JSON itself contains no GitHub username or other personal identity. Use a non-sensitive project and do not add logs or task content.
Full protocol and denominators:
https://github.com/SethGammon/Citadel/blob/main/docs/PRODUCT_PROOF_TRIAL.md
Thank you for helping separate a popular repository from a product people actually return to.
All reactions