51. Delegated management teams and operational accountability

A successful vehicle account may eventually involve an owner, steward, mechanic, driver, media lead, sponsor manager, auction operator, accountant, safety reviewer, race engineer, fleet operator, and autonomous agents. The substrate models the team’s charter and assignments without turning a team name into a superuser or treating membership as authority.

#51.1 Team identity and charter

ManagementTeam names beneficiaries, managed asset/profile selectors, charter, required functional roles, separation rules, escalation policy, and state. A team is an organizational object, not an authenticated principal. Every action is still attributable to a human, service, or device principal acting under a current grant.

#51.2 Membership and effective roles

TeamMembership binds principal, role codes, duty scopes, authority bases, conflict declarations, valid interval, and status. INVITED, ACTIVE, SUSPENDED, EXPIRED, and REVOKED are distinct. A member may hold duties without the grant to execute them, or a grant may be invalidated when required membership expires.

#51.3 Responsibility and accountability assignment

ResponsibilityAssignment names work kind and subjects, exactly one accountable principal, responsible principals, consulted and informed principals, approval quorum, backups, service target, escalation path, interval, and status. Models and vehicle agents may be responsible for bounded work, but every high-impact assignment retains one accountable human principal.

#51.4 Approval quorums and separation of duties

ApprovalMatrix declares proposer, reviewer, approver, quorum, prohibited role combinations, and emergency override rules by action class. Marketplace close, seller payout, title clearance, incident closure, rights override, moderation appeal, and financial reconciliation can require distinct principals. A policy-required separation MUST NOT collapse because the team is small; the action waits, escalates, or uses an independently authorized service.

#51.5 Delegation, escalation, and emergency access

Delegation and subdelegation only attenuate asset, action, field, purpose, geography, time, amount, tool, and risk scope. Emergency access is a separately declared path with trigger, duration, exact permissions, approval/notification, audit, and mandatory after-review. It cannot become standing access through repeated renewal.

#51.6 Handoff, absence, offboarding, and succession

ManagementHandoffReceipt binds outgoing and incoming principals, responsibilities, open cases, actions, unknown effects, credentials/epochs, acknowledgement time, and unresolved items. Offboarding advances relevant membership, grant, session, connector, and management epochs before dispatch. A missed handoff invalidates dependent decisions instead of silently assigning work to whoever remains online.