When autonomy meets dependency.
A portfolio mandate becomes a SongzCorp condition when separate companies or initiatives encounter a consequential decision they cannot resolve in isolation. The mandate names the shared condition, the authority required, and the record that keeps coordination from becoming ambient oversight.
Intended engagement design — internal and portfolio-only
Mandate register / entry conditions
Not every difficult decision belongs at portfolio level. These conditions indicate that local autonomy now intersects with a shared obligation.
Timing, sequence, access, or a shared standard in one workstream changes what another workstream can decide or deliver.
Two or more mandates require the same finite capability, capacity, or attention and no local owner can resolve the tradeoff.
Several leaders hold legitimate authority over parts of the condition, yet the deciding right and escalation path remain unclear.
The consequence of delay, inconsistency, or inaction can no longer be contained by the workstream where the signal first appeared.
Defines purpose, authority, clauses, boundaries, and review posture.
Names who decides, contributes, executes, and receives escalation.
Sets when a shared condition is reviewed and what triggers a change.
Records how constrained shared resources are assigned and reconsidered.
Names the trigger, context, receiving authority, and next decision.
Preserves the decision, rationale, owner, review condition, and superseding event.
The charter turns that standard into an inspectable public method, with sources, revision posture, and limitations kept visible.