Repository navigation
docs: founder-bound why/how gists + graph-benchmark 0.17.1 re-run - #55
Closed
M0nkeyFl0wer wants to merge 1 commit into
Closed
M0nkeyFl0wer wants to merge 1 commit into
M0nkeyFl0wer wants to merge 1 commit into
Conversation
- docs/gists/why-and-how.md: canonical why/how explainer (dogfooding-led), corruption claim removed (debunked on 0.17.1), answer-key catch kept - docs/gists/why-benchmarks-cant-see-the-bug.md: companion, orthogonal-axes - docs/gists/origin-how-multipass-began.md: long-form origin (MemPalace #101) - docs/related_work/graph-benchmark.md: prrao87 relation + same-machine 0.15.3-vs-0.17.1 re-run (latency flat, ~10% smaller on disk on 0.17.1) - industry_benchmark_gap_analysis 2.5: perf benchmarks as fifth family - ideas.md: topology-as-cost-predictor research thread
Owner
Author
|
Retracting — these gists are not ready to be public-facing yet. Closing and deleting the branch. |
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
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.
Founder-bound explainer docs (all under
docs/), cherry-picked offorigin/mainso they don't carry the stale CKG feature branch.What's here
docs/gists/why-and-how.md— canonical, dogfooding-led why/how explainer (the first gist to ship).docs/gists/why-benchmarks-cant-see-the-bug.md— companion: perf benchmarks measure speed on correct-by-construction data; SME measures whether the graph is correct.docs/gists/origin-how-multipass-began.md— long-form origin (MemPalace #101). Note: partially redundant with the inline origin inwhy-and-how.md— candidate to prune later.docs/related_work/graph-benchmark.md— prrao87 relation + same-machine 0.15.3-vs-0.17.1 re-run (latency flat within noise; on-disk ~10% smaller on 0.17.1, 50→45MB). Numbers verified vs live README.docs/industry_benchmark_gap_analysis_2026.md§2.5 (perf = fifth family) +docs/ideas.md(topology-as-cost-predictor thread).Founder-safety
These are intended to be shared with the LadybugDB founder. The earlier "incremental-write corruption" claim is debunked on 0.17.1 (standalone per-edge repro, 0 corruption; mis-measured dedup-merge effect) and appears here only as explicit do-not-assert guard-rail framing. No AI-attribution lines.