The Break-Glass Protocol is TISSA’s framework for handling legitimate exceptions to brand standards. Real-world pressure — tight deadlines, market events, partner requirements — sometimes demands deviation from the approved system. Break-Glass makes those deviations safe by making them visible.
Every Break-Glass exception must be documented in the Decision Log with a mandatory kill date: the date by which the exception expires and the standard resumes. There is no such thing as a permanent exception. If the exception reveals a genuine need, the standard itself is updated through the proper governance process.
The protocol follows three principles: ship text-first (approve message and structure before design), use only existing components from the library (new ones are added to tokens the same day), and document every deviation with a kill date. No exception lives longer than 30 days without formal review.
