Software That Is Sold, Not Rented
Full charge up front, a long stable release cycle, and no switch the seller can throw on a copy already running
A licensing architecture where enforcement sits only on the paid layer — the free software holding a customer's own records carries no licence check at all, so an expired licence ends new releases and paid features, never access to what is already installed.
Keywords: perpetual licensing, software distribution, subscription economics
Read Paper →A Licence Boundary Drawn by Architecture, Not by Features
One archive runs free; the layer that asks a single question of many archives at once is the part that costs money
Argues the free/paid line should be drawn by architecture, not a feature list — one archive runs free under permissive terms; the aggregation layer that queries many archives at once is where the commercial boundary, and a stronger copyleft term, actually belongs.
Keywords: open-core licensing, software architecture, licence boundary design
Read Paper →Ownership You Can Prove Without the Seller
A sealed licence, a payment recorded in public, and no activation server that has to outlive the company
Describes this site's own deployed verification architecture — a public payment record, an offline-verifiable Ed25519 licence token, and a hash-chained per-binary artifact ledger — and why a buyer should be able to prove ownership without asking the seller.
Keywords: license verification, cryptographic provenance, offline verification
Read Paper →Software for a Reporting Issuer, Not for a Multinational
Comparable operational complexity, incomparable organisational scale — and why that distinction, not company size, is the design brief
Argues the right design brief is a reporting issuer's real operational complexity, not enterprise-multinational scale — a distinction the software's actual target customer makes load-bearing, not company size.
Keywords: reporting issuer software, transaction cost economics, product scope
Read Paper →