76e3e6c0f2
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.
10 lines
No EOL
268 B
JSON
10 lines
No EOL
268 B
JSON
{
|
|
"digest": "37a9774dc7569335d8135828aa5b97d294e26252185b0b31dc4a8f4dadde59db",
|
|
"algorithm": "sha256",
|
|
"file": "catalog.json",
|
|
"byte_length": 80389,
|
|
"rebuilt_at": "2026-10-29T20:23:11.578Z",
|
|
"method_version": "btr-0.1",
|
|
"products": 123,
|
|
"assessed": 1
|
|
} |