- The group reviewed the rollout strategy for the core Displacement & Dismissal Policy updates.
- Lorenzo noted that the Intersect Steering Committee (ISC) requested this update alongside the transition to 2-year committee terms.
- Gintama urged the group to complete drafts within two weeks to shift focus toward optimizing the business process models before the next cohorts take office.
| Lorenzo: Consolidate the working draft to present to the ISC for a preliminary review on Monday week. | | Working Group Socialization & Echo Chamber Risks |- Terence (Tax) flagged a systemic risk that the working group functions as an echo chamber of the same 4–5 participants, lacking broader community input before passing policies.
- Gintama counter-argued that a lack of intrinsic reward or incentive limits general ecosystem interest in lengthy, asynchronous policy-drafting work.
- The group discussed that over 70+ members currently sit across all committees and representing their collective feedback is a critical first step.
| All Committee Chairs: Tasked with explicitly bringing the upcoming policy drafts back to their respective committees to secure a 10x multiplier on direct feedback data.Lorenzo: Promote the working group visibility publicly as soon as the revised working group directory tools go live. | | Phased Escalation vs. Immediate Dismissal |- The group refined the graduation of penalties to avoid jumping straight to a harsh dismissal process.
- Lorenzo reiterated that stopping monthly compensation serves as a clean, low-level tracking point for non-participation.
- Gintama proposed that missing a meeting without a valid excuse should temporarily stall a member's voting rights for the subsequent call, since they would lack contextual awareness.
| Working Group: Structure the exact sequence of the phased process (Reward Pause → Vote Suspension → Formal Accountability Review) in the main document draft. | | Defining Participation Benchmarks |- Gintama suggested a flat 50% monthly meeting attendance benchmark to stop compensation, noting that committees with low workloads meet as rarely as twice a month.
- Thiago pushed for a stricter 75% minimum voting participation rate on asynchronous committee business via the internal portals.
- The group noted that calculating hard hourly mandates is impractical since active groups like Budget meet multiple times a week while others operate on a bi-weekly maintenance schedule.
| Lorenzo: Frame the criteria around a combination of percentage-based meeting attendance and mandatory asynchronous vote counts. | | Value-Driven Incentives vs. Punishment |- Jose and Mark argued that the group is overly focused on penalizing low attendance rather than building production-focused frameworks (such as milestone-based sprints or backlogs) that make members feel seen.
- Jose shared that the Cardano Foundation Ambassador Program utilizes fixed dollar-pegged compensation tied to verifiable proof of public value contribution.
- Jose proposed aligning with CF stakeholders (Alexander Maza and Sebastian Ravena) to potentially tie Project Catalyst funding application permissions to active Intersect membership registration.
| Jose: Coordinate an initial alignment call with CF representatives to explore shared community onboarding and incentive milestones. | | Strict Enforcement Rules & Outreach Mandates |- Terence strongly asserted that no dismissal should ever be automatic or purely script-driven unless an explicit, multi-channel outreach protocol fails.
- A strict removal can only trigger if a member ignores a sequential wave of notifications spanning a 4-week window across four distinct channels: public Discord tags, direct messages, internal committee chat pings, and direct emails.
| Lorenzo: Codify the 4-channel outreach sequence directly into the operational guidelines of the dismissal policy text to safeguard against unfair removals. | --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://committees.docs.intersectmbo.org/intersect-steering-committee/working-group/working-groups/working-group-meeting-notes/2026/march-12-2026.md?ask=