Redacted public extract · names and identifying details removed
The issue was raised clearly before the complaint outcome.
This page preserves a limited sequence from email correspondence. It does not publish the full exchange, identify people unnecessarily, or invite personal targeting. The point is to show that questions about use, non-use, credit, withdrawal, protection, and live participant expectation were repeatedly raised before the complaint response later narrowed the issue.
The extracts are redacted to keep the focus on the participation-accountability pattern rather than on individual reputations.
If a project later says there was no intention to use the work, the ethical question is why that was not made clear when use, non-use, credit, protection, agreement, and individual/project boundaries were repeatedly being discussed.
17 April 2026 · boundary raised early
Professional, project, personal, and informal boundaries were raised at the start
Before the later complaint route, the participant-author had already asked for boundary clarity around material shared with an individual involved in the project.
This matters because the later concern was not created after the fact. Boundary, role, and mutuality were raised before the formal complaint.
23 April 2026 · clarification and concern
Use, credit, workability, and ethical framework were already live issues
The participant-author explained that the concern was not a complaint at that stage, but a clarification about use of work within the project.
This directly contradicts any later minimisation of the matter as ordinary personal encouragement. The questions of use, credit, seriousness, and ethical framework had already been put in writing.
23 April 2026 · senior contact reply
The concern was treated as clear and agreement/protection were named
The senior contact did not respond by saying the concern was irrelevant or that the participant-author was mistaken. The response encouraged formalising an agreement around collaboration, contribution, and protection of material.
23 April 2026 · participant reply
Reading/discussion were distinguished from use
The participant-author then clarified the action sought: the concern should be noted, formalised, and no use should proceed beyond reading or discussion without written agreement.
This gave a clear route: discussion was not being refused, but use required boundary, attribution, protection, and agreement.
23 April 2026 · senior contact confirmation
The concerns and agreement route were acknowledged
The senior contact again treated the position as clear and left open involvement if agreement could not be reached.
23 April 2026 · direct request to project management
The project was directly asked for a formal written agreement
On the same day, the participant-author contacted project management directly asking for written agreement about collaboration, contribution, role, use, credit, protection, and ethical terms.
That is a direct written non-use boundary. If the work was never going to be used, adapted, implemented, or credited, that was a clear opportunity to say so.
28 April 2026 · route and formalisation issue
The distinction between individual sharing and project use was explicitly raised
The participant-author then raised the problem that the material had not been shared generally with the project, but with an individual involved in it. That distinction is central to the later ambiguity.
This shows that the participant-author was not collapsing every interaction into formal project use. The concern was exactly the unclear boundary between individual recognition, project context, possible wider engagement, discussion, and use.
28 April 2026 · ethical/political boundary
The work was framed as critique toward repair, not anti-system withdrawal
The same email also clarified the ethical direction of the work and why it was not being offered as anti-system or oppositional performance.
29 April 2026 · seriousness and non-pressure
The work was not dependent on this project or immediate adoption
The participant-author clarified that the work was already serious before publication and that, if the individual did not take it on, the work could wait for another route.
This is important because it separates the ethical concern from pressure for adoption. The participant-author was not insisting the project must use the work; he was asking that possible use and non-use be handled clearly.
30 April 2026 · grounds of ethical transmission
Use, adaptation, implementation, credit, and non-use were explicitly named
The participant-author sent a declaration setting out the terms on which the work could be taken up or used.
This was not vague. The distinction between reading/discussion and use/adaptation/implementation/credit was set out in writing.
30 April 2026 · clarification of withdrawal, non-use, and protection
The non-use route was also named
The participant-author then clarified that if the stated grounds could not be accepted, the appropriate issue was withdrawal, non-use, and protection of material already shared.
This matters because it gave the project a clear opportunity to say, at that point, that there was no intention to use, adapt, circulate, implement, or work with the material.
30 April 2026 · project lead response
The response acknowledged the declaration and protected materials
The project lead did not respond by saying the work was irrelevant or that there was no intention to use it. The reply acknowledged and respected the declaration and referred to withdrawal and protection of shared materials.
The participant-author then replied that the confirmation was helpful, specifically thanking the project lead for confirming that the materials already shared were protected.
Formal declaration · ethical use of the work
The work was for repair, not exit
The attached declaration also set the wider ethical boundary for use of the work.
11 May 2026 · formal complaint
Verbal assurance, management contact, and practice change were explicitly raised
The participant-author raised a formal complaint and made the central sequence explicit: contact routes, verbal assurance, management-level discussion, visible practice change, authorship, and retrospective narrowing.
The formal complaint then asked directly whether the verbal assurances about being worked with and credited were authorised and meaningful, and if not, why those assurances were given.
12 May 2026 · complaint route uncertainty
The route itself was unclear across institutions
A senior academic contact acknowledged that the matter was now a formal complaint and noted that governance and complaint routes may vary because different institutions governed different aspects of the work.
The participant-author replied that the concern was not only about where to route a complaint, but about the underlying process: contact routes, subsequent narrowing, authorship and acknowledgement, possible influence, and whether it was appropriate to direct the complaint back through the same line of concern without clearer safeguards.