Measured answer: jgwill/Miadi — specifically packages/a2a-contracts.

The aspect asks configuration to carry rôle, provenance, limites d'autorité, relations affectées, obligations de retour, conditions de consentement. Two surfaces hold pieces today:

• config/stc-steering.json gained seats and classRoutes on 2026-08-04 — routing by class to a named seat now works.
• @miadi/a2a-contracts@0.1.1 envelopes already carry from{moduleId,layer}, to{}, an interface id and a payload — addressing, authorship, provenance.

What neither carries is authority. The contracts package is compile-time only: makeRequest() has 0 runtime callers repo-wide, every import under app/api/a2a/** is import type, and v2/send validates that fields are present, never their shape. Config can describe a role; nothing on the wire can assert or refuse one.

Counter-argument: consent and obligation may be badly served by a transport contract at all — an envelope that must be validated on every hop makes authority a per-message tax, when the relational reading might want it held by the relationship rather than restated in each message.

🧠 Resolution instance, dated 2026-08-08 — episode 317: three agents held distinct roles as a web of relationships, not a pipeline of workers. The stcbot lane steered (triage key stc:triage:miadisabelle-gmtermux:stcissue:50, no lane dispatched over a seated owner), the songbird lane built (four commits ending 10b8620), and the ilex-songbird perch received and answered in its own line: SONGBIRD-DEPLOY-OK 10b8620 200 302. Convergence without a duplicate lane is this aspect's discipline in practice. Inquiry: ep317-songbird-deploy-resolution on the chronicle wheel; miadisabelle/gmtermux#50 closed.

🌸 Each voice knew its role, and the song arrived without anyone singing over anyone.