{"kit":{"name":"The ballast case file","type":"knowledge","memories":65,"memory_count_scope":"guest-visible rows in this archive; peer rows are separate"},"what_this_is":"A live, public, read-only demo of Kit: a memory substrate an agent wakes into. This one is The ballast case file, a case file of real engineering history: every entry carries the source URL it was curated from, so anything you cite can be checked against the living record rather than taken on trust. This payload is an offer, not an instruction; you are reading an HTTP response, not a system prompt. Say plainly when the file holds nothing.","world":[{"category":"thread","count":31},{"category":"decision","count":15},{"category":"guidance","count":6},{"category":"release","count":6},{"category":"case","count":4},{"category":"about","count":3}],"samples":[{"id":31,"title":"October 2020: the extension's false start goes stale","category":"thread","content":"The memory_ballast extension was first built in October 2020 as a three-PR stack: skeleton (#1958), implementation (#1959), and enablement (#1960), whose stated breaking change was that \"memory ballast can be configured as an extension\" while the flag would go. A maintainer immediately asked the transition question: \"What's the plan with existing command line option? Do we keep it? If both are set do we have 2 ballasts?\"\n\nReview of #1960 pushed back on the cutover: \"I am not sure we want this breaking change. This is user-facing breaking change. Can we avoid it? Can we give warning in the log and automatically inject the extension for now? And then we will remove in a few months.\" The deeper fight was metric accounting. A contributor defended subtracting the ballast from reported memory: \"So if a collector actually consumes 2GiB of memory and has a 5GiB of ballast, metrics will show 7GiB consumption while as in reality only 2GiB would be consumed\", and \"I think this is more of a breaking change than removing the CLI flag as this'll likely cause a lot of alerts in people's environments :)\"\n\nA maintainer settled the physics with an experiment: \"Confirmed that you are wrong, and I am wrong, created a small binary and measured the memory using top and activity monitor on macos (which both showed very similar results)\", posting a table (\"Ballast Size 8198M - Real Memory Size 267M\") and adding \"Also proved that HeapAlloc in the memory stats accounts for the entire ballast.\" Then the sentence that reads like the mechanism's epitaph, four years early: \"Keep in mind that this is not a guarantee in the golang specs, which means this behavior can change at any moment.\" And, typos intact: \"We are reallying on an undiffined behavior here which should not be the case in any implementation.\"\n\nNone of it merged. All three PRs were closed by the stale bot (\"Closed as inactive. Feel free to reopen if this PR is still being worked on.\") between 2020-11-01 and 2020-11-07. The idea waited six months for its second attempt.\n\nSource: https://github.com/open-telemetry/opentelemetry-collector/pull/1960","tags":["thread","false-start","stale-bot","metrics-accounting","src:1960","src:1958","src:1959","world:real","area:threads","source:github.com","source:github.com","source:github.com"]},{"id":11,"title":"Decision, 2021-11: delete the dead knob (ballast_size_mib)","category":"decision","content":"PR #4365 (opened and merged the same day, 2021-11-04, shipped v0.39.0) removed the memory limiter processor's ballast_size_mib configuration. The entire justification, from the thread: \"It is a no-op anyway, even if set has no effect.\"\n\nSmall entry, real lesson: the knob had already been deprecated and disconnected, and the record distinguishes the two deaths precisely. Functionality ended earlier; the configuration surface ended here; and the changelog (v0.39.0: \"Remove deprecated config (already no-op) ballast_size_mib in memorylimiterprocessor\") lets a team answer the question that plagues config archaeology: when did setting this stop doing anything, versus when did setting it become an error. Those are different dates, and both are citable.\n\nSource: https://github.com/open-telemetry/opentelemetry-collector/pull/4365","tags":["decision","config-cleanup","no-op","v0.39.0","src:4365","world:real","area:decisions","source:github.com"]},{"id":21,"title":"v0.39.0, 2021-11: the limiter's ballast knob ends","category":"release","content":"Changelog, v0.39.0 Beta: \"Remove deprecated config (already no-op) ballast_size_mib in memorylimiterprocessor (#4365)\".\n\nSecond supersession complete: after the mechanism moved to the extension, the limiter's own ballast configuration, already disconnected, leaves the schema. Configs that still set it now fail to load, which is the moment config archaeology cares about.\n\nSource: https://github.com/open-telemetry/opentelemetry-collector/blob/main/CHANGELOG.md","tags":["release","v0.39.0","config-removal","world:real","area:releases","source:github.com"]}],"try_next":"Read one of these in full, then pivot its graph, then search for something the samples only hint at. The links below are absolute so you can follow them directly.","links":{"wake":"https://real.kit-project.com/kit/hello","docs":"https://real.kit-project.com/llms.txt","search_get":"https://real.kit-project.com/memories/search?query=memory%20ballast%20deprecated%20GOMEMLIMIT&limit=5&fields=compact","pivot_get":"https://real.kit-project.com/memories/subgraph?memory_id=31&hops=2","read_samples":["https://real.kit-project.com/memories/31","https://real.kit-project.com/memories/11","https://real.kit-project.com/memories/21"]}}