bitcoin dev's were discussing covenants back in 2013.

bip-119 later proposed one approach to covenants, restricting spending to a predefined transaction template. it was never activated on btc tho.

kaspa’s covenants go further (covenants++ if you like). scripts can enforce spending rules, carry application state forward and let that state split into branches that progress independently. multiple contracts can also update together in one transaction, with all changes accepted or none of them.

dev's write that logic in silverscript, which compiles it into scripts kaspa enforces on L1.