The irreducible epistemic atoms underlying the curriculum. 4,828 atoms across 8 types and 2 molecules
Define professional scope boundaries by writing what your role explicitly includes and excludes, then default to 'no' for requests falling outside that scope unless you consciously choose to make an exception.
Frame professional boundaries as commitments to work quality rather than confessions of personal weakness ('To protect the architecture review, I'm limiting meetings to 15 hours per week' vs 'I have too many meetings'), because quality-based framing generates respect while capacity-based framing generates sympathy.
When receiving requests that don't map to your top three priorities, use the forced-choice formula 'I can do X or Y this week—which matters more to you?' to surface tradeoffs rather than silently absorbing both demands.