> It is 110% not good to have any major corporation go into a technical default.
Q: rather than going into debt, would it be possible for the government to just... suspend the activation of financial covenants generally for a while? Enact a law putting a temporary patch on how contract law works vis-a-vis financial instruments?
Something like... any covenant with triggers written after date X would now be required to be written to include additional language Y; and any covenant triggers written before date X would be implicitly interpreted as if they did contain language Y. Language Y specifies that the activation of the covenant is suspended when the government says a certain named financial-market state "Z" pertains; and, when state "Z" is declared as having ended, only then would the covenant be evaluated for activation, based on the present state of the debtor, rather than its state during the historical period during condition "Z". Effectively, the covenant wouldn't be able to "see into" whatever happened during "Z" to apply its triggering logic to it.
(I'm picturing here how you can, in an RDBMS, create constraints that don't validate until a transaction is complete, such that you can temporarily put a table into a constraint-violating state during the TX, and—as long as you fix things before the end of the TX—everything will be fine, and the trigger won't run.)
Q: rather than going into debt, would it be possible for the government to just... suspend the activation of financial covenants generally for a while? Enact a law putting a temporary patch on how contract law works vis-a-vis financial instruments?
Something like... any covenant with triggers written after date X would now be required to be written to include additional language Y; and any covenant triggers written before date X would be implicitly interpreted as if they did contain language Y. Language Y specifies that the activation of the covenant is suspended when the government says a certain named financial-market state "Z" pertains; and, when state "Z" is declared as having ended, only then would the covenant be evaluated for activation, based on the present state of the debtor, rather than its state during the historical period during condition "Z". Effectively, the covenant wouldn't be able to "see into" whatever happened during "Z" to apply its triggering logic to it.
(I'm picturing here how you can, in an RDBMS, create constraints that don't validate until a transaction is complete, such that you can temporarily put a table into a constraint-violating state during the TX, and—as long as you fix things before the end of the TX—everything will be fine, and the trigger won't run.)