Remove four internal assessments from the public repository - #67
Merged
Merged
Conversation
gtm-assessment.md scored go-to-market readiness at 7.5/10. ASSESSMENT.md listed the project's weaknesses as an internal maturity review. MVP.md was a 30-day build plan, completed months ago. repo-completeness- assessment.md audited the repo against an internal checklist. All four are internal planning documents written for the team, all dated April 2026, and all sitting in a public repository. Two of them I moved into docs/ earlier today while tidying the root, without reading them closely enough to notice what they were. The honest-limits material worth keeping in public already exists, written deliberately for readers: packages/pctr/README.md documents what blast radius does not measure, that trust must be wired to a real attestation source, that keys are on disk rather than in a KMS, and that pctr serve is plain HTTP. That is a different thing from publishing an internal scorecard. Also drops the now-dangling MVP.md reference from protocol/spec.md. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
|
You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard. |
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.
gtm-assessment.mdscored go-to-market readiness at 7.5/10.ASSESSMENT.mdlisted the project's weaknesses as an internal maturity review.MVP.mdwas a 30-day build plan, finished months ago.repo-completeness-assessment.mdaudited the repo against an internal checklist.All four are internal planning documents written for the team, dated April 2026, sitting in a public repository. Two of them I moved into
docs/earlier today while tidying the root — without reading them closely enough to notice what they were.This isn't a retreat from honesty. The limits worth publishing already exist, written deliberately for readers:
packages/pctr/README.mddocuments what blast radius doesn't measure, that trust needs wiring to a real attestation source, that keys sit on disk rather than a KMS, and thatpctr serveis plain HTTP. Publishing an internal scorecard is a different thing.Also drops the now-dangling
MVP.mdreference fromprotocol/spec.md.🤖 Generated with Claude Code