Independent record: This site is not operated by CoDA, Inc., the Issues Mediation Committee, the CoDA Board, or any official CoDA service body. Conclusions expressed here are based on the documented record reproduced on this site. Terminology: “Governor(s)” is a rhetorical description, not an official CoDA title; CoDA uses “trusted servant(s).”

Questions for fellowship conscience

The issues in plain language

Do you believe an online meeting should continue to receive CoDA recognition while operating in ways that disregard the Traditions and Fellowship Service Manual?

When trusted servants act as governors, should anonymity be allowed to shield their official actions from accountability?

Do you believe personal relationships between trusted servants should shield them from accountability for their actions?

Why I am bringing this to the fellowship

Email to the Board and meeting

This began with meeting #WW11731, but it no longer ends there.
This is now a Board-level and fellowship-wide concern about whether CoDA service bodies are protecting the Traditions, or allowing them to be bypassed under the language of meeting autonomy and without adequate safeguards against bias.

The meeting structure I reported involved an unelected few meeting owners, which used the omission of the 7th tradition in a way that bypassed the 2nd tradition and concentrated control over the fellowship. That concentrated control was then used in ways I believe were abusive toward newcomers and members alike. When I raised this concern with what should have been trusted servants, I was ostracized, browbeaten, and ultimately banned without explanation.

When I brought the matter through CoDA service channels, I expected objectivity, accountability, transparency, and guidance rooted in the Steps, Traditions, and Fellowship Service Manual. Instead, I received apparent bias, avoidance, contradiction, unsupported accusations, frame-shifting, and the repeated mantra that the meeting was healthy and I was the problem.

Autonomy is not a right to abuse.

Autonomy is not a right to silence members, avoid group conscience, remove business-meeting accountability, disregard self-support, practice favoritism, neglect fellowship-wide responsibilities, or treat foundational safeguards as optional “format.”

If a meeting fails to uphold the principles that give it autonomy and thereby becomes abusive, it should not be listed or endorsed by CoDA. It should find another way to advertise itself and its unhealthy, adulterated facsimile of CoDA.

The practical position taken by IMC and HMC is that, when it comes to finding a healthy online meeting, the newcomer and member are simply rolling the dice. The Steps and Traditions become suggestions to be discarded when inconvenient. A meeting may become toxic, unhealthy, and structurally abusive, with members potentially leaving unheard and harmed, while IMC and HMS still endorse the unhealthy meeting as healthy.

The true harm to our primary purpose is as follows:

The newcomer is not being led out of codependence. They are being abused by a CoDA-endorsed version of it, wrapped in false recovery language.

The members working the program are a part of the in-meeting safeguard that makes meeting autonomy trustworthy. Here, that safeguard against institutional abuse was removed, unsupported, and recast as the problem by the very service structure meant to protect CoDA unity.

The trusted servant acting out is not receiving guidance that could strengthen their recovery. Their unhealthy behavior is being labeled healthy, protected by false autonomy, and reinforced by the service structure.

I do not believe the worldwide fellowship would knowingly agree to fund this.

So I am asking the Board to answer plainly:

Does CoDA endorse and promote meetings that fail to practice the Traditions and FSM safeguards resulting in the abuse and disenfranchisement of new comers and members?

Does CoDA endorse the behavior and service-process handling documented in this record?

If a group conscience is taken to issue that response, please provide the date, decision language, and meeting minutes or written record with your response.

As recognized by the FSM I am officially demanding the service records and meeting minutes for the multiple group conscience decisions Gail S. referenced in answering or avoiding my requests and questions.

Sincerely,
Aaron U.

Supporting context

Contemporaneous Communications

Redacted communications from before and during the dispute are available so readers can evaluate later characterizations of conduct against the contemporaneous record.

View supporting communications

Documented process record

Process Break Matrix

The record is presented chronologically. Each entry shows the issue or request, the response given, the identified process break, and the CoDA material cited in support.

Meeting and Healthy Meetings process

Back to top
Record 1
Issue / request
Access to group conscience was requested, including whether the meeting remained open to modification through current group conscience, whether “us” meant the whole group, and whether the meeting was effectively “like it or leave it.” (Feb. 12)
Response given
A leader stated that the format had been decided by those who had shown up for decision-making up to that point, suggested review of CoDA service material, and said there had been recent discussion of regularly scheduled GC meetings with an announcement expected soon; specific items could be emailed for possible agenda placement. (Feb. 16)
Break from CoDA guidelines / process
The request did not result in a group-conscience discussion or vote. Members were directed to submit specific items to the organizers by email for possible agenda placement.
Rule / principle
Tradition 2; FSM Group Conscience Process
FSM page
8, 22
Sample language
“For our group purpose…” / “Anyone may ask for…”
Record 2
Issue / request
A scheduled forum for group conscience items was requested after concerns were raised about unilateral meeting-wide decisions. (Mar. 3, 2026)
Response given
It was stated that the meeting does not hold business meetings because Zoom is privately funded, and that concerns should be sent to the organizers’ email. (Mar. 3)
Break from CoDA guidelines / process
7th Tradition break: Private platform funding was used as the reason no regular business forum exists, while meeting-wide issues were redirected into a private channel rather than a group process.
Rule / principle
FSM Business Meetings; FSM Group Conscience Process; Tradition 2
FSM page
8,9
Sample language
“Business meetings provide a forum…” / “The home group typically…” / “Our leaders are but…”
Record 3
Issue / request
Request made on Mar 4th for a brief GC at the beginning of the Mar. 10 meeting on one narrow item: whether the meeting would establish a recurring, scheduled GC check-in, and when it would occur. Confirmation was also requested that the item would be placed at the beginning of the meeting and facilitated by discussion and vote. (Mar. 4)
Response given
Null: No response.
Break from CoDA guidelines / process
2nd Tradition break begins; "trusted servant(s) become governor(s). The member submitted the request by email as instructed. The governors did not place the issue before the group. The Mar. 4 request was bypassed. No vote was held, no minutes, motion, or outcome were produced. The simple Mar. 4 request remains unanswered.
Rule / principle
Tradition 2; FSM Process of Determining a Group Conscience; Service Concept 5
FSM page
8,9, 22, 23
Sample language
“Our leaders are but…” / “To begin the group…” / “Trusted servants are directly…”
Record 4
Issue / request
March 10th very end of the meeting. Asked if my email was read and asked if someone would please respond to it.
Response given
a meeting organizer stated that the second half of the meeting was now designated for personal shares only. (Mar. 10)
Break from CoDA guidelines / process
Governor(s) unilaterally changed the meeting format. What had been a parking-lot discussion was restricted to personal shares, leaving governor(s) to decide what share is or isn't compliant. The result was a meeting that made no provision for an orderly 2nd Tradition discussion and vote, effectively banning 2nd Tradition action within the meeting.
Rule / principle
FSM Group Conscience Process; Tradition 2
FSM page
22, 8
Sample language
“A group conscience may…” / “Our leaders are but…”
Record 5
Issue / request
Guidance was requested of the IMC on what CoDA recommends when an online meeting does not provide a clear forum to bring GC items for discussion and vote by the members present, and whether IMC mediation was available. (Mar. 10)
Response given
Request being routed and processed
Break from CoDA guidelines / process
N/A
Rule / principle
N/A
FSM page
N/A
Sample language
N/A
Record 6
Issue / request
March 12th attempted to join the meeting and was immediately banned.
Response given
Null: No communication
Break from CoDA guidelines / process
The member was immediately banned without warning, written explanation, or any identified process basis.
Rule / principle
FSM Disagreement, Mediation, and Resolution; Traditions 3, 5, 12
FSM page
24
Sample language
“If mediation fails…” / “Each person’s right…”
Record 7
Issue / request
IMC was notified that the requester had been removed by the host without warning or explanation and appeared blocked from rejoining, which was described as retaliation for requesting access to the GC process. (Mar. 12)
Response given
IMC forwards emails from Mar 10th, 12th to Healthy Meetings. (Mar. 12)
Break from CoDA guidelines / process
N/A
Rule / principle
N/A
FSM page
N/A
Sample language
N/A
Record 8
Issue / request
Forwarded emails from March 10th and 12th
Response given
HMC responds asks what I hope to get from "a recurring, scheduled group conscience check-in". (Mar. 13)
Break from CoDA guidelines / process
HMC bypassed the issue presented. The request had already been clearly stated. Instead of addressing the absence of any clear, orderly forum for a members-present 2nd Tradition discussion and vote, HMC treated the right to request group conscience as something that had to be justified in advance.
Rule / principle
FSM Group Conscience Process; FSM Process of Determining a Group Conscience
FSM page
22, 23
Sample language
“Anyone may ask for…” / “To begin the group…”
Record 9
Issue / request
Clarification given: The meeting does not provide an accessible forum where members present can raise meeting-wide framework/format items and determine group conscience by discussion and vote. (Mar. 13)
Response given
Healthy Meetings stated that a committee member attended the meeting, found it in complete compliance with CoDA meeting standards, said it was well run. (Mar. 19)
Break from CoDA guidelines / process
Healthy Meetings’ response did not show that it tested the actual issue. It did not identify whether the meeting had a regular business meeting or any orderly forum for group conscience, and instead called the meeting compliant without identifying any review of that process.
Rule / principle
Tradition 2; FSM Group Conscience Process; FSM Process of Determining a Group Conscience
FSM page
8, 22,23
Sample language
“For our group purpose…” / “Anyone may ask for…” / “To begin the group…”
Record 10
Issue / request
Requested Guidance: Restore Access so I can participate (Mar. 13)
Response given
HMC states: If another format better meets your needs, finding another meeting on coda.org may provide that for you.
Break from CoDA guidelines / process
The issue is not whether the member fits a format. The issue is whether CoDA a supports governance and process issue that blocks the 2nd and 7th Traditions, puts governors over members, and permits crosstalk against newcomers who do not share perfectly. HMC’s response did not address the governance and process issues even though that was the subject of the complaint. Instead, it treated the member who made the plain 2nd Tradition request as the problem while calling the meeting that blocks those Traditions “healthy and quite well run.”
Rule / principle
Tradition 2; FSM Disagreement, Mediation, and Resolution
FSM page
8, 24
Sample language
“Our leaders are but…” / “it isn’t Higher Power’s will…”
Record 11
Issue / request
Requested Guidance: to support the meeting in using an accessible group conscience process for meeting-wide matters. (Mar. 13)
Response given
Healthy Meetings bypasses (Mar 13) stated reason and insists that my feelings/needs for wanting a vote on a scheduled orderly 2nd tradition forum were not explained. (Mar. 19)
Break from CoDA guidelines / process
The purpose of the requested GC was explicitly stated in writing four times prior. The meeting's governor(s) and now the HMC repeatedly refused to acknowledge that the member had the right to ask for a vote and that the meeting’s "trusted servants" were supposed to place that request before the group. Instead, the governor(s) and HMC treated the blocked vote itself as a non-issue, while the direct fix, a members-present 2nd Tradition vote, remained unacknowledged and blocked.
Rule / principle
FSM Group Conscience Process; FSM Process of Determining a Group Conscience
FSM page
22, 23
Sample language
“Anyone may ask for…” / “To begin the group…”
Record 12
Issue / request
Clarification was given that the issue was not meeting format or whether the meeting was healthy, but only access to group conscience as described by the FSM and 2nd Tradition. The requested vote was restated as procedural: whether the meeting should set aside a regular time for GC items affecting the whole meeting. (Mar. 19)
Response given
HMC: "Their response is clear that the group endeavored to work with you to no avail" (Mar. 20)
Break from CoDA guidelines / process
HMC treated replies from three meeting organizers, the meeting governor(s), as though they were the group itself. They are not the group. Nothing needed to be “worked through”; only a 2nd Tradition vote was needed to decide whether the meeting would set aside time for 2nd Tradition issues. No group conscience, motion, vote, minutes, or outcome were produced showing that the members present were even aware of the request, let alone acted on it. HMC then shifted posture and began using accusatory “you” statements.
Rule / principle
Tradition 2; FSM Structure and Organization
FSM page
8, 11
Sample language
“Our leaders are but…” / “Members of groups may…”
Record 13
Issue / request
Restating that the requested vote was procedural: whether the meeting should set aside a regular time for group conscience items affecting the whole meeting. (Mar. 19)
Response given
Healthy Meetings said a GC had already been held, that the outcome was not the one desired, and that it seemed another GC was being demanded to force the issue. (Mar. 20)
Break from CoDA guidelines / process
HMC and the meeting governor(s) once again bypassed the restated 2nd Tradition request. Instead, they inserted the separate, already-resolved chat issue and recast the matter as dissatisfaction with an outcome. The actual issue was not that chat was closed, but that the governor(s) closed it without group conscience, without minutes, and without any recorded act of the members present. Nowhere in this email thread did the member raise Zoom chat features at all.
Rule / principle
FSM Group Conscience Process; FSM Process of Determining a Group Conscience
FSM page
22, 23
Sample language
“Anyone may ask for…” / “To begin the group…”
Record 14
Issue / request
Does a member need a specific, pre-approved reason to request a group conscience? If yes, where is that written? (Mar. 19)
Response given
Healthy Meetings answered that GC is used to make decisions affecting the group, quoted FSM language stating that anyone may ask for a GC, and again said a GC had already been held.(Mar. 20)
Break from CoDA guidelines / process
HMC admitted that a member does not need a pre-approved reason to request group conscience, yet still refused to explain why this simple member’s meeting-wide 2nd Tradition request was denied.
Rule / principle
FSM Group Conscience Process
FSM page
22
Sample language
“Anyone may ask for…”
Record 15
Issue / request
Are online meetings exempt from any Traditions or from the group conscience decision-making process? If yes, where is that written? (Mar. 19)
Response given
Healthy Meetings answered no, and said every group may decide how often to hold business meetings. (Mar. 20)
Break from CoDA guidelines / process
HMC said online meetings are not exempt from the Traditions, yet treated this one as though it were. The meeting governor(s) used private Zoom control as the reason no business meeting exists, which left no current vote on whether one should be held and no orderly, members-present path to 2nd Tradition action. HMC answered “no exemption” while calling that governance and process failure “healthy and quite well run.”
Rule / principle
Tradition 2; Tradition 7; FSM Business Meetings
FSM page
8,9
Sample language
“Our leaders are but…” / “Every CoDA group ought…” / “Business meetings provide a forum…”
Record 16
Issue / request
During the committee member’s visit, did anyone raise a group conscience item and was a vote taken? (Mar. 19)
Response given
Healthy Meetings answered no, and stated that GC is not a function of a regular meeting.(Mar. 20)
Break from CoDA guidelines / process
HMC bypassed the actual issue, and its response did not show that the issue had been tested. It admitted that no group conscience item was raised and no vote was taken during the committee visit, then claimed group conscience is not a function of a regular meeting. That directly contradicts its own FSM quote that a group conscience may be requested during a regular meeting when needed.
Rule / principle
FSM Group Conscience Process
FSM page
22
Sample language
“A group conscience may…”
Record 17
Issue / request
Was this even the right committee for this issue? (Mar. 19)
Response given
Healthy Meetings answered yes. (Mar. 20)
Break from CoDA guidelines / process
N/A
Rule / principle
N/A
FSM page
N/A
Sample language
N/A
Record 18
Issue / request
NULL — no such issue or question was raised in the (Mar. 19)
Response given
Healthy Meetings said the chat feature had been disabled after reports of inappropriate private messages, and that members present voted not to reopen chat. (Mar. 20)
Break from CoDA guidelines / process
Meeting governor(s) and HMC proxy moved from dodging the 2nd Tradition request to asserting undefined “inappropriate messages” as fact through accusatory “you” statements. The allegation was not defined, no process for testing it was identified, and it was not put to the member for response before HMC repeated it as true. HMC then set up a false frame that the member’s issue was reopening chat, even though that issue had already been settled and was not the request before HMC.
Rule / principle
FSM Disagreement, Mediation, and Resolution; FSM Group Conscience Process
FSM page
24; 10
Sample language
“During the group conscience process…” / “Thirty Second Timeout…”
Record 19
Issue / request
NULL — no such issue or question was raised in the (Mar. 19)
Response given
Healthy Meetings cited policies on harassment, bullying, 13th stepping, intolerance, safeguarding the Traditions, common welfare, and no crosstalk. (Mar. 20)
Break from CoDA guidelines / process
This language was better directed at the meeting governor(s). The member’s written record shows sincere questions, an amends for an imperfect objection, a plain 2nd Tradition request, and willingness to accept group conscience, not threats or attacks. HMC answered with bullying and harassment language while never correcting the blocked 2nd Tradition process that gave rise to the complaint or the member’s improper, unexplained removal from a fellowship he had attended for appr. 56 meeting.
Rule / principle
N/A
FSM page
N/A
Sample language
N/A
Record 20
Issue / request
NULL — no such issue or question was raised in the (Mar. 19)
Response given
Healthy Meetings said emails were answered until they became badgering. (Mar. 20)
Break from CoDA guidelines / process
Only two respectful emails had been sent to the meeting governor(s): the Feb. 12 email stated a “genuine spirit of inquiry, not as an attack,” and the Mar. 4 email included amends, a narrow 2nd Tradition request, and stated willingness to accept group conscience. If HMC read that attached thread, the “badgering” and misconduct framing is unsupported by the written record; if it did not, conclusions were drawn without reading the record.
Rule / principle
N/A
FSM page
N/A
Sample language
N/A
Record 21
Issue / request
NULL — no such issue or question was raised in the (Mar. 19)
Response given
Healthy Meetings said the group reported interruptions during shares, direct crosstalk, anger when corrected, repeated behavior, and attacks on trusted servants and other members. (Mar. 20)
Break from CoDA guidelines / process
Again, governor(s) are not the group. HMC answered none of the March 19 questions here. Instead, it replaced answers with a stack of unverified accusations. No dates, no examples, no prior notice, no screenshots, no message copies, no minutes, and no other supporting record were produced. The allegations were just declared true.
Rule / principle
FSM Proper email etiquette
FSM page
21
Sample language
“Proper email etiquette should…” / “taking others’ inventories”
Record 22
Issue / request
NULL — no such issue or question was raised in the (Mar. 19)
Response given
Healthy Meetings quoted FSM language stating that in extreme cases a group may ask an individual to leave the meeting. (Mar. 20)
Break from CoDA guidelines / process
HMC invoked the FSM’s “extreme cases” language while the member’s documented request remained a 2nd Tradition request for an orderly scheduled vote. No group conscience, motion, vote, minutes, or outcome were produced showing that the members present had asked the member to leave. HMC treated governor(s) accusations as settled fact.
Rule / principle
FSM Process of Determining a Group Conscience; Tradition 2
FSM page
23, 8
Sample language
“To begin the group…” / “Our leaders are but…”
Record 23
Issue / request
NULL — no such issue or question was raised in the (Mar. 19)
Response given
Healthy Meetings encouraged reflection, referenced sustainable recovery, and noted that there were four other English-speaking meetings in the same time slot. (Mar. 20)
Break from CoDA guidelines / process
HMC treated accusations as fact and again shifted the remedy to departure. Instead of directing the meeting governor(s) to hold the requested 2nd Tradition vote or follow FSM guidance, HMC pointed the member to other meetings and left the blocked process untouched.
Rule / principle
FSM Disagreement, Mediation, and Resolution
FSM page
24
Sample language
“it isn’t Higher Power’s…”
Record 24
Issue / request
Confirmation was requested of one of three things:
1.That the requested procedural vote was taken with minutes, date, time, exact motion, and outcome;
2. that it was not taken; or
3. why it was not held at the beginning of the Mar. 10 meeting as requested.(Mar. 26)
Response given
NULL — no direct answer was given in the Mar. 29, 2026 response.
Break from CoDA guidelines / process
The Mar. 26 record request was ignored. HMC did not say whether the requested procedural vote was taken, did not produce minutes, date, time, exact motion, or outcome, and did not explain why the vote was not held at the beginning of the Mar. 10 meeting as requested.
Rule / principle
Service Concept 12
FSM page
10
Sample language
“Every member has the…”
Record 25
Issue / request
Clarification was requested as to whether two respectful emails on different topics, one on Feb. 12 and one on Mar. 4, constitute “badgering,” and whether Healthy Meetings had actually read both before using that label.(Mar. 26)
Response given
NULL — no direct answer was given in the Mar. 29, 2026 response.
Break from CoDA guidelines / process
A serious characterization remained operative without being defined or justified against the actual email record.
Rule / principle
FSM Proper email etiquette
FSM page
21
Sample language
“Avoid offensive language…”
Record 26
Issue / request
It was clarified that the prior GC regarding chat had been accepted, that the chat issue had not been raised again (Mar. 26, 2026)
Response given
NULL — no direct answer was given in the Mar. 29, 2026 response.
Break from CoDA guidelines / process
The clarification that the chat GC had been accepted as evidenced by all emails, did not receive a response, leaving the substitution of the chat issue for the requested procedural vote unresolved.
Rule / principle
FSM Business meetings; FSM Group Conscience Process
FSM page
9
Sample language
“Business meetings provide a…” / “A group conscience may…”
Record 27
Issue / request
Definition of “inappropriate” private messages was requested, with dated exhibits supported by screenshots or dated message copies. (Mar. 26)
Response given
NULL — no direct answer was given in the Mar. 29, 2026 response.
Break from CoDA guidelines / process
Meeting governor(s) and the HMC proxy never defined “inappropriate.” No screenshots. No dated message copies. No examples. No specifics. The accusation was left hanging without proof and without any chance to answer it. The member still does not know what conduct is supposedly being called inappropriate, and nothing produced so far shows conduct that dishonors himself, other members, or CoDA.
Rule / principle
N/A
FSM page
N/A
Sample language
N/A
Record 28
Issue / request
Identification was requested of what specific behavior was allegedly repeated after amends, and on what dates.(Mar. 26)
Response given
NULL — no direct answer was given in the Mar. 29, 2026 response.
Break from CoDA guidelines / process
meeting governor(s) and HMC proxy alleged “repeated behavior” but never identified what behavior it meant. No conduct was named. No dates were given. No examples were produced. The allegation was left floating without particulars, so the member had no way to know what was supposedly repeated or to answer it.
Rule / principle
Service Concept 12
FSM page
10
Sample language
“Every member has the right…”
Record 29
Issue / request
Dated exhibits were requested showing multiple corrections, along with clarification whether any corrections were addressed by name.(Mar. 26)
Response given
NULL — no direct answer was given in the Mar. 29, 2026 response.
Break from CoDA guidelines / process
Meeting governor(s) and the HMC proxy claimed there were “multiple corrections,” but produced nothing. No dated exhibits. No examples. No record of what was said, when it was said, or whether the member was ever addressed by name. The claim was left unsupported. The member cannot recall a single correction on fellowship rules in four years of CoDA and AA participation and service, including roughly 1.2 years in this meeting.
Rule / principle
Service Concept 12
FSM page
10
Sample language
“Every member has the right…”
Record 30
Issue / request
Confirmation was requested as to whether any emails regarding CoDA conduct had ever been sent, as the personal email to the member was known since early Feb 2026. No such emails appeared in the requester’s records.(Mar. 26)
Response given
NULL — no direct answer was given in the Mar. 29, 2026 response.
Break from CoDA guidelines / process
Leadership had the member’s email since early February, yet no conduct-related email notice was shown. They appear to have used the email only once, and even then did not answer the member’s questions. When asked directly whether any such emails had ever been sent, no direct answer was given.
Rule / principle
Service Concept 12
FSM page
10
Sample language
“Every member has the right…”
Record 31
Issue / request
The inconsistency was raised between later accusations and the Feb. 16 leadership statement thanking the requester for presence, shares, and reading service over prior months.(Mar. 26)
Response given
NULL — no direct answer was given in the Mar. 29, 2026 response.
Break from CoDA guidelines / process
On Feb. 16, a meeting governor thanked the member for his presence, shares, and reading service over prior months. Later, that same member was framed as a conduct problem. The inconsistency was never explained. No direct answer was given, and nothing in the record shows the request was put to the meeting governor(s) for response.
Rule / principle
N/A
FSM page
N/A
Sample language
N/A
Record 32
Issue / request
NULL — no such issue or question was raised in the Mar. 26, 2026 email.
Response given
Healthy Meetings explained CoDA as an inverted pyramid, stating that authority, power, and direction reside with the members of groups and flow downward through trusted servants and service structures. (Mar. 29)
Break from CoDA guidelines / process
HMC partially quoted CoDA’s “inverted pyramid” language, but left out the part with teeth: trusted servants are not to “govern, coerce, or attempt to control others,” and hierarchy itself cannot adhere to CoDA’s principles. Yet the meeting governor(s) and HMC proxy bypassed the only issue raised by the member: a framework that blocks access to group conscience, with private platform control being used as the reason no business meeting exists.
Rule / principle
Tradition 2; Service Concept 7; FSM Structure and Organization
FSM page
8, 9, 11
Sample language
“Our leaders are but…” / “Trusted servants do not…” / “a hierarchical system cannot…”
Record 33
Issue / request
NULL — no such issue or question was raised in the Mar. 26, 2026 email.
Response given
Healthy Meetings quoted FSM language describing a CoDA meeting as a place of healthy and loving relationships, sponsorship, fellowship, and community belonging. (Mar. 29)
Break from CoDA guidelines / process
No such issue was raised in the Mar. 26 email. HMC replaced answers with meeting ideals. It quoted “healthy and loving relationships” but omitted the FSM warning that “it isn’t Higher Power’s will that we go along to get along.” A request for a 2nd Tradition vote is not a violation of that standard. It is the process CoDA says members use.
Rule / principle
FSM Process of Determining a Group Conscience
FSM page
23
Sample language
“Finally, be warned that…” / “It isn’t Higher Power’s…”
Record 34
Issue / request
NULL — no such issue or question was raised in the Mar. 26, 2026 email.
Response given
The Healthy Meetings committee can only advise members and groups regarding the steps to take to solve disagreements.  (Mar. 29)
Break from CoDA guidelines / process
HMC spoke as though it had authority when accusing and framing the member, but claimed only advisory capacity when pressed on the unresolved procedural break. The inconsistency is in the record.
Rule / principle
N/A
FSM page
N/A
Sample language
N/A
Record 35
Issue / request
NULL — no such issue or question was raised in the Mar. 26, 2026 email.
Response given
Each group governs their meetings and are accepted as CoDA meetings under the requirements stated in the FSM. There are requirements to be a CoDA meeting - which this group meets - the rest is guidance. (Mar. 29)
Break from CoDA guidelines / process
HMC said no meeting is exempt from the Traditions, then treated this meeting as exempt in practice. It accepted governance and process issues where private platform control was used to block an orderly path to group conscience, while still calling the meeting compliant because it met basic listing requirements. That reduces the Traditions to optional guidance in the very place where they should govern.
Rule / principle
Traditions 1, 2, 4, 7; FSM Group Conscience Process
FSM page
8, 22
Sample language
“Our common welfare…” / “For our group purpose…” / “Each group should remain…” / “Every CoDA group ought…” / “Anyone may ask for…”
Record 36
Issue / request
NULL — no such issue or question was raised in the Mar. 26, 2026 email.
Response given
Again, as there has admittedly been damage done to the sense of safety and community in this meeting. (Mar. 29)
Break from CoDA guidelines / process
HMC pointed to “damage” to safety and community, although the member had made no such admission. The damage identified in the record was the blocked 2nd Tradition process, blocked self-support, absence of a business meeting because of private platform control, crosstalk policing of shares, and repeated pressure to accept the governance and process failures or leave. At the same time, HMC relied on undefined allegations without notice, particulars, or any meaningful opportunity to answer. The result was exclusion without an identified process.
Rule / principle
Traditions 1, 2; FSM Group Conscience Process
FSM page
8, 22
Sample language
“Our common welfare…” / “For our group purpose…” / “Anyone may ask for…”
Record 37
Issue / request
NULL — no such issue or question was raised in the Mar. 26, 2026 email.
Response given
it may not be the place for your continued recovery. (Mar. 29)
Break from CoDA guidelines / process
HMC again said no meeting format is exempt from the Traditions, yet left the same break in place: the meeting governor(s) refused to allow the requested 2nd Tradition vote. Rather than address that refusal, HMC shifted the burden to the member and suggested he leave. The unresolved issue was not fit. It was the blocked right of the group to decide.
Rule / principle
Tradition 2; FSM Process of Determining a Group Conscience
FSM page
8, 23
Sample language
“Our leaders are but…” / “It isn’t Higher Power’s…”

IMC Process Breaks / Service-Record Avoidance

Back to top
Record 38
Issue / request
Board and IMC were asked to restore fellowship access, substantiate or withdraw allegations, review whether HMC acted impartially, and state plainly whether CoDA guidance on business meetings, group conscience, and self-support are binding safeguards. (Apr. 13)
Response given
IMC stated that it was reaching out to Healthy Meetings for clarification regarding HMC’s findings and response. (Apr. 13)
Break from CoDA guidelines / process
n/a
Rule / principle
n/a
FSM page
n/a
Sample language
n/a
Record 39
Issue / request
IMC was asked to restore the member to fellowship in good standing and uphold a Second Tradition vote. (Apr. 13)
Response given
IMC answered that it could not do this because each meeting is autonomous, and suggested finding another meeting or starting a new meeting. (Apr. 24)
Break from CoDA guidelines / process
The member was not removed through the processes that defines healthy meeting autonomy; the record shows unilateral removal by the meeting host(s) IMC misuses healthy “meeting autonomy” by treating it as immunity from accountability for bypassing or abusing the Traditions, Steps, and FSM. The unresolved issue is whether a CoDA endorsed and promoted meeting can use autonomy/format to justify abusing or bypassing the Traditions, Steps, and FSM.
Rule / principle
Tradition 2; FSM Group Conscience Process; FSM Disagreement, Mediation, and Resolution
FSM page
8; 22; 24
Sample language
“Our leaders are but…” / “Anyone may ask for…” / “It isn’t Higher Power’s will…”
Record 40
Issue / request
IMC was asked to substantiate the allegations or withdraw them. (Apr. 13)
Response given
IMC answered: “IMC cannot do this.” (Apr. 24)
Break from CoDA guidelines / process
IMC referred the matter to HMC and then relied on HMC’s response, but when asked to substantiate or withdraw the allegations in that response, IMC answered only that it “cannot do this.” No process was identified for substantiating, withdrawing, correcting, or testing the allegations. The member still does not know what specific conduct is being treated as improper.
Rule / principle
Service Concept 12; FSM Proper Email Etiquette; FSM Disagreement, Mediation, and Resolution
FSM page
10; 21; 24
Sample language
“Every member has the right…” / “Avoid offensive language…” / “During the group conscience process…”
Record 41
Issue / request
IMC was asked to review whether the HMC process was impartial. (Apr. 13)
Response given
IMC answered: “HMC follows a process. The process was followed.” (Apr. 24)
Break from CoDA guidelines / process
IMC substituted a conclusion rather than declaring the results of an impartiality review. No process criteria, records, participants, conflict check, bias analysis, or review of HMC’s handling of undefined accusations was provided.
Rule / principle
Service Concept 12; Service Concept 5; FSM Disagreement, Mediation, and Resolution
FSM page
10; 9; 24
Sample language
“Every member has the right…” / “Trusted servants are directly…” / “During the group conscience process…”
Record 42
Issue / request
IMC was asked to state plainly whether CoDA guidance on business meetings, group conscience, and self-support are binding safeguards, and whether the documented governance pattern was consistent with that guidance. (Apr. 13)
Response given
IMC answered that each meeting is autonomous, that CoDA World makes healthy suggestions, that suggestions are not enforced as rules, and that the only requirement for website listing is reading the four foundational documents. (Apr. 24)
Break from CoDA guidelines / process
Again. IMC used autonomy as immunity. It did not answer whether CoDA has binding safeguards for business meetings, group conscience, and self-support. Instead, IMC recast CoDA-issued Traditions/Steps/FSM concerns as the member’s “acceptable terms,” as if the member had invented his own standard. IMC states that CoDA offers “healthy suggestions,” but then treats a meeting that abused the Traditions and ignored CoDA-issued guidance as healthy, compliant, and deserving of continued CoDA endorsement.
Rule / principle
Traditions 1, 2, 4, 7; FSM Business Meetings; FSM Group Conscience Process
FSM page
8; 9; 22
Sample language
“Our common welfare…” / “Our leaders are but…” / “Every CoDA group ought…” / “Business meetings provide a forum…” / “Anyone may ask for…”
Record 43
Issue / request
Asked IMC to reconcile its autonomy position with FSM sanction language, reconcile “healthy meetings hold regular business meetings” with the claim that only four documents are required, state whether HMC’s process was proper, answer whether IMC/HMC members personally knew the meeting owners, and provide any corrective guidance sent to #WW11731. (Apr. 26)
Response given
no response issued
Break from CoDA guidelines / process
no response issued
Rule / principle
Service Concept 12; FSM Group Conscience Process; FSM Disagreement, Mediation, and Resolution
FSM page
10; 22; 24
Sample language
“Every member has the right…” / “Anyone may ask for…” / “During the group conscience process…”
Record 44
Issue / request
Follow up email sent informing that the issue was still open (Jun 1)
Response given
IMC later acknowledged the Apr. 26 email and stated: “IMC’s GC was not to respond to that specific email.” (Jun. 2)
Break from CoDA guidelines / process
After approximately six weeks without a written response, IMC stated that its group conscience decision was not to respond to the Apr. 26 follow-up with no notification.
Rule / principle
Rule: Service Concept 12; FSM Group Conscience Process
FSM page
Page: 10; 22
Sample language
“Every member has the right…” / “Anyone may ask for…”
Record 45
Issue / request
Asked whether the IMC Chair or IMC/HMC members who handled the matter personally knew the meeting owners involved in #WW11731. (Apr. 26)
Response given
IMC did not answer the bias/conflict question. Instead, IMC stated that its GC was not to respond to the email and again offered a Zoom meeting with two IMC members plus one HMC participant. (Jun. 2)
Break from CoDA guidelines / process
The bias/conflict question was material because HMC’s neutrality was challenged. IMC avoided the question and proposed a private Zoom including a participant from the challenged HMC process, rather than providing a written conflict answer.
Rule / principle
Service Concept 12; Service Concept 5; FSM Disagreement, Mediation, and Resolution
FSM page
10; 9; 24
Sample language
“Every member has the right…” / “Trusted servants are directly…” / “During the group conscience process…”
Record 46
Issue / request
Written follow-up asked IMC to provide the written guidance, recommendations, or corrective direction sent to #WW11731 regarding the Tradition, governance, or crosstalk violations raised in the report. (Apr. 26)
Response given
IMC did not provide any corrective guidance or state that none existed. (Jun. 2)
Break from CoDA guidelines / process
IMC gave the member guidance to find another meeting or start one, but produced no corresponding corrective guidance to the meeting whose governance and process were challenged. The burden of correction was shifted to the reporting member.
Rule / principle
Traditions 1, 2, 4, 7; FSM Business Meetings; FSM Group Conscience Process
FSM page
8; 9; 22
Sample language
“Our common welfare…” / “Our leaders are but…” / “Each group should remain…” / “Every CoDA group ought…” / “Business meetings provide a forum…”
Record 47
Issue / request
Because IMC identified its non-response to the Apr. 26 email as a group conscience decision, the member requested the basic service record of that decision: date, minutes/notes/decision language, participants, recusals, prior relationships, and the reason for not responding. (Jun. 3)
Response given
IMC acknowledged receipt from a personal/non-CoDA email account, characterized the request as “demands,” and stated the matter would be discussed at the next IMC monthly meeting. (Jun. 4)
Break from CoDA guidelines / process
A basic request for the service record of an invoked GC decision was recast as “demands” and delayed into another meeting. A new GC should not be necessary to fulfill a service-record request for records that should already exist and be available to the membership. IMC did not provide the requested date, minutes/notes, decision language, participants, recusals, relationship disclosures, or reason for non-response.
Rule / principle
Service Concept 12; FSM Group Conscience Process; Service Concept 5
FSM page
10; 22; 9
Sample language
“Every member has the right…” / “Anyone may ask for…” / “Trusted servants are directly…”
Record 48
Issue / request
An official IMC response was sent from a personal/non-CoDA email account, then corrected two minutes later from the CoDA account. (Jun. 4)
Response given
IMC apologized and stated that the response should have come from the CoDA licensed account. (Jun. 4)
Break from CoDA guidelines / process
n/a
Rule / principle
n/a
FSM page
n/a
Sample language
n/a
Record 49
Issue / request
The member clarified that no demands had been made, that the request was for basic service accountability, and that the 10-business-day timeframe remained unchanged. (Jun. 4)
Response given
no response issued
Break from CoDA guidelines / process
n/a
Rule / principle
n/a
FSM page
n/a
Sample language
n/a
Record 50
Issue / request
The current issue before IMC was the Jun. 3 service-record request for the GC decision not to answer the Apr. 26 questions. (Jun. 3)
Response given
IMC responded by listing the member’s original Apr. 13 requests and repeating IMC’s prior answers in blue. (Jun. 20)
Break from CoDA guidelines / process
IMC answered a prior email rather than the current service-record request. The current request for GC records, participants, recusals, prior relationships, and reasons for non-response was not answered. This substituted an earlier issue for the actual request before IMC.
Rule / principle
Service Concept 12; FSM Group Conscience Process
FSM page
10; 22
Sample language
“Every member has the right…” / “Anyone may ask for…”
Record 51
Issue / request
IMC invoked another group conscience on Jun. 20 while the prior GC record remained unproduced. (Jun. 20)
Response given
IMC stated: “Based on today’s GC, we make this offer one last time,” and again offered Zoom. (Jun. 20)
Break from CoDA guidelines / process
IMC compounded the transparency break by invoking a second GC while refusing to provide the basic service record of the first GC. The result was that GC authority was invoked while the requested written accountability and decision record remained unprovided.
Rule / principle
Service Concept 12; Service Concept 5; FSM Group Conscience Process
FSM page
10; 9; 22
Sample language
“Every member has the right…” / “Trusted servants are directly…” / “Anyone may ask for…”
Record 52
Issue / request
The member requested written answers and declined Zoom because accusations, bias concerns, and lack of transparency made private Zoom unsafe and unsuitable for preserving an accurate record. (Jun. 3)
Response given
IMC again offered a private Zoom with two IMC members and one HMC participant. (Jun. 20)
Break from CoDA guidelines / process
IMC treated private Zoom as a substitute for written service records and direct written answers. A Zoom meeting would not cure the missing GC record, unresolved bias question, unanswered FSM questions, or lack of corrective guidance to #WW11731.
Rule / principle
Service Concept 12; FSM Disagreement, Mediation, and Resolution
FSM page
10; 24
Sample language
“Every member has the right…” / “During the group conscience process…”
Record 53
Issue / request
The member requested whether any IMC member had a prior personal, sponsorship, friendship, service, or other meaningful relationship with meeting owners, organizers, or trusted servants involved in #WW11731. (Jun. 3)
Response given
IMC did not answer. (Jun. 20)
Break from CoDA guidelines / process
The conflict/bias question remained unanswered after being asked directly in both Apr. 26 and Jun. 3 correspondence. The record therefore leaves unresolved whether the matter was handled through a neutral service process.
Rule / principle
Service Concept 12; Service Concept 5; FSM Disagreement, Mediation, and Resolution
FSM page
10; 9; 24
Sample language
“Every member has the right…” / “Trusted servants are directly…” / “During the group conscience process…”
Record 54
Issue / request
The member requested the reason IMC chose not to respond in writing to questions regarding FSM compliance, group conscience access, healthy-meeting standards, possible bias, HMC process, and corrective guidance to #WW11731. (Jun. 3)
Response given
IMC did not provide the reason. Instead, it repeated prior responses to original requests and again offered Zoom. (Jun. 20)
Break from CoDA guidelines / process
IMC declined to explain the basis for its non-response while using GC language as authority. The decision affected an unresolved Traditions/FSM concern but the reason, record, and decision language were not provided.
Rule / principle
Service Concept 12; FSM Group Conscience Process
FSM page
10; 22
Sample language
“Every member has the right…” / “Anyone may ask for…”
Record 55
Issue / request
The member noted that IMC had again avoided the current service-record request, declined to provide the requested records, and failed to answer material Traditions/FSM questions in writing. (Jul. 10)
Response given
IMC responded only: “Email received,” with BCC to the full IMC committee and CoDA Board liaisons. (Jul. 11)
Break from CoDA guidelines / process
IMC acknowledged receipt but did not cure the record. No service records were provided, no bias/conflict answer was given, no corrective guidance was produced, and no written answers were supplied to the material Traditions/FSM questions.
Rule / principle
Service Concept 12; Service Concept 5; FSM Disagreement, Mediation, and Resolution
FSM page
10; 9; 24
Sample language
“Every member has the right…” / “Trusted servants are directly…” / “During the group conscience process…”

Source correspondence

Actual Emails

The correspondence below is a text transcription of the source emails. Repeated quoted copies of earlier messages are omitted when that message already appears separately. Redactions are shown in brackets.

Redactions: the publisher’s email address, last name, and phone number are redacted. A private non-CoDA email address and the surname inadvertently exposed through that account are also redacted. Official CoDA and meeting service addresses remain visible.

For a printable archival copy, use your browser’s Print command and choose “Save as PDF.” The print layout expands all correspondence automatically.

Anonymity and redaction

Privacy without changing the record

Private email addresses, phone numbers, personal addresses, unrelated recovery disclosures, and unnecessary personal identifiers are redacted where possible. Names are limited where possible to service-role identifiers. Some identifying information may remain where necessary to preserve the integrity of the service record.

No harassment request

This site is not a request that anyone contact, confront, pressure, or harass any individual trusted servant, meeting member, or service body. Its purpose is fellowship review of a service-process issue.

Corrections and clarifications

Accuracy matters

If a factual statement in this record is believed to be inaccurate or materially incomplete, the exact statement and supporting documentation may be submitted for review. Substantiated factual errors will be corrected, with the correction noted in the record.

Contact address: add the dedicated domain email here after it has been configured and tested.