bunkhouse/bigtech-sucks
7
1
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions
bigtech-sucks/packages/web/public/oath.json

10 lines
268 B
JSON
Raw Normal View History

feat: self-authoring ingest, relevance gate, and the Ranch Oath The roster writes itself. The scores do not. - db/ingest/sources.mjs: GitHub and Flathub adapters. GitHub is ranked by stars (usage); Flathub is a curated store of end-user Linux apps, so relevance is free there and has to be earned on GitHub. - db/ingest/run.mjs: discovers into the roster as unassessed products, never as scores. Every discovery leaves a receipt (source, url, usage metric, timestamp) so a reader can see where a product came from and why it ranks. - LooksLikeUserSoftware gate: topic:messaging sorts RabbitMQ to the top because brokers are highly starred and are not things people install. - build.mjs no longer wipes the database. The DB authors itself, so a rebuild would have thrown the roster away. --fresh is now explicit. - v_backlog view: what to assess next, ordered by measured usage. - packages/web/public/oath.html: the Ranch Oath, with an ASCII Bible crest, bound to a SHA-256 of catalog.json. The page recomputes the digest in the browser and reports VERIFIED or BROKEN. An oath you cannot break is decoration. Roster now 122 products, 1 assessed. All instrument checks pass.
2026-10-29 13:23:57 -05:00
{
feat: the closed-source rule, and the board Christian, 2026-10-29: 'Closed source software, you have no idea. And then all we have is reputation. So you kind of start with one arm or two arms tied behind your back.' That is now arithmetic instead of an opinion. - assessment.source_available: 1 = we can read the code, 0 = we cannot. - Closed source cannot exceed 5 on ANY dimension without tier-1 or tier-2 evidence of kind 'capture' or 'filing'. Reputation is tier 3, and tier 3 is not a measurement. The build fails if a closed-source score breaks the rule. - Verifiability still caps at 3 with no reproducible build. Practical ceiling for closed source: 86/100 in theory, if every dimension is backed by a capture or a court filing. In practice it is a fight for a C. - product.priority puts a human's ask ahead of a crawler's discovery. - v_backlog orders by priority, then measured usage. - migrate(): the database authors itself, so it must survive its own schema changes. Add columns, drop views, let schema.sql recreate them. Never drop and rebuild, which would destroy the self-authored roster. On the board: Slack (closed, capped) and Kino (closed, capped, founders call 2026-10-30 17:00). Neither is scored. Neither gets a number until it has evidence.
2026-10-29 15:23:31 -05:00
"digest": "37a9774dc7569335d8135828aa5b97d294e26252185b0b31dc4a8f4dadde59db",
feat: self-authoring ingest, relevance gate, and the Ranch Oath The roster writes itself. The scores do not. - db/ingest/sources.mjs: GitHub and Flathub adapters. GitHub is ranked by stars (usage); Flathub is a curated store of end-user Linux apps, so relevance is free there and has to be earned on GitHub. - db/ingest/run.mjs: discovers into the roster as unassessed products, never as scores. Every discovery leaves a receipt (source, url, usage metric, timestamp) so a reader can see where a product came from and why it ranks. - LooksLikeUserSoftware gate: topic:messaging sorts RabbitMQ to the top because brokers are highly starred and are not things people install. - build.mjs no longer wipes the database. The DB authors itself, so a rebuild would have thrown the roster away. --fresh is now explicit. - v_backlog view: what to assess next, ordered by measured usage. - packages/web/public/oath.html: the Ranch Oath, with an ASCII Bible crest, bound to a SHA-256 of catalog.json. The page recomputes the digest in the browser and reports VERIFIED or BROKEN. An oath you cannot break is decoration. Roster now 122 products, 1 assessed. All instrument checks pass.
2026-10-29 13:23:57 -05:00
"algorithm": "sha256",
"file": "catalog.json",
feat: the closed-source rule, and the board Christian, 2026-10-29: 'Closed source software, you have no idea. And then all we have is reputation. So you kind of start with one arm or two arms tied behind your back.' That is now arithmetic instead of an opinion. - assessment.source_available: 1 = we can read the code, 0 = we cannot. - Closed source cannot exceed 5 on ANY dimension without tier-1 or tier-2 evidence of kind 'capture' or 'filing'. Reputation is tier 3, and tier 3 is not a measurement. The build fails if a closed-source score breaks the rule. - Verifiability still caps at 3 with no reproducible build. Practical ceiling for closed source: 86/100 in theory, if every dimension is backed by a capture or a court filing. In practice it is a fight for a C. - product.priority puts a human's ask ahead of a crawler's discovery. - v_backlog orders by priority, then measured usage. - migrate(): the database authors itself, so it must survive its own schema changes. Add columns, drop views, let schema.sql recreate them. Never drop and rebuild, which would destroy the self-authored roster. On the board: Slack (closed, capped) and Kino (closed, capped, founders call 2026-10-30 17:00). Neither is scored. Neither gets a number until it has evidence.
2026-10-29 15:23:31 -05:00
"byte_length": 80389,
"rebuilt_at": "2026-10-29T20:23:11.578Z",
feat: self-authoring ingest, relevance gate, and the Ranch Oath The roster writes itself. The scores do not. - db/ingest/sources.mjs: GitHub and Flathub adapters. GitHub is ranked by stars (usage); Flathub is a curated store of end-user Linux apps, so relevance is free there and has to be earned on GitHub. - db/ingest/run.mjs: discovers into the roster as unassessed products, never as scores. Every discovery leaves a receipt (source, url, usage metric, timestamp) so a reader can see where a product came from and why it ranks. - LooksLikeUserSoftware gate: topic:messaging sorts RabbitMQ to the top because brokers are highly starred and are not things people install. - build.mjs no longer wipes the database. The DB authors itself, so a rebuild would have thrown the roster away. --fresh is now explicit. - v_backlog view: what to assess next, ordered by measured usage. - packages/web/public/oath.html: the Ranch Oath, with an ASCII Bible crest, bound to a SHA-256 of catalog.json. The page recomputes the digest in the browser and reports VERIFIED or BROKEN. An oath you cannot break is decoration. Roster now 122 products, 1 assessed. All instrument checks pass.
2026-10-29 13:23:57 -05:00
"method_version": "btr-0.1",
feat: the closed-source rule, and the board Christian, 2026-10-29: 'Closed source software, you have no idea. And then all we have is reputation. So you kind of start with one arm or two arms tied behind your back.' That is now arithmetic instead of an opinion. - assessment.source_available: 1 = we can read the code, 0 = we cannot. - Closed source cannot exceed 5 on ANY dimension without tier-1 or tier-2 evidence of kind 'capture' or 'filing'. Reputation is tier 3, and tier 3 is not a measurement. The build fails if a closed-source score breaks the rule. - Verifiability still caps at 3 with no reproducible build. Practical ceiling for closed source: 86/100 in theory, if every dimension is backed by a capture or a court filing. In practice it is a fight for a C. - product.priority puts a human's ask ahead of a crawler's discovery. - v_backlog orders by priority, then measured usage. - migrate(): the database authors itself, so it must survive its own schema changes. Add columns, drop views, let schema.sql recreate them. Never drop and rebuild, which would destroy the self-authored roster. On the board: Slack (closed, capped) and Kino (closed, capped, founders call 2026-10-30 17:00). Neither is scored. Neither gets a number until it has evidence.
2026-10-29 15:23:31 -05:00
"products": 123,
feat: self-authoring ingest, relevance gate, and the Ranch Oath The roster writes itself. The scores do not. - db/ingest/sources.mjs: GitHub and Flathub adapters. GitHub is ranked by stars (usage); Flathub is a curated store of end-user Linux apps, so relevance is free there and has to be earned on GitHub. - db/ingest/run.mjs: discovers into the roster as unassessed products, never as scores. Every discovery leaves a receipt (source, url, usage metric, timestamp) so a reader can see where a product came from and why it ranks. - LooksLikeUserSoftware gate: topic:messaging sorts RabbitMQ to the top because brokers are highly starred and are not things people install. - build.mjs no longer wipes the database. The DB authors itself, so a rebuild would have thrown the roster away. --fresh is now explicit. - v_backlog view: what to assess next, ordered by measured usage. - packages/web/public/oath.html: the Ranch Oath, with an ASCII Bible crest, bound to a SHA-256 of catalog.json. The page recomputes the digest in the browser and reports VERIFIED or BROKEN. An oath you cannot break is decoration. Roster now 122 products, 1 assessed. All instrument checks pass.
2026-10-29 13:23:57 -05:00
"assessed": 1
}
Reference in a new issue Copy permalink