Two Publications, One Methodology
129
Two Publications, One Methodology: From Citizen Observation to Verifiable Algorithmic Evidence
15 August 2026
Sometimes the importance of a contribution lies not only in what it says, but also in where it enters the public policy dialogue.
On 13 August 2026, we submitted two new contributions to the European Commission's Futurium platform:
1. Algorithmic Accountability and Audit Protocol (AAAP) v2.0: An Open, Reproducible Framework for Algorithmic Evidence
2. Citizen Auditing for AI Governance: From Observation to Verifiable Accountability
Our Futurium My Contributions record shows both contributions as authored on 13 August 2026, with the current status “Published: No.”
That distinction matters.
We are not presenting these works as approved, endorsed, or already published by the European Commission.
We are documenting the fact that they have been submitted to Futurium and are currently part of the platform's contribution process.
And for us, that process is itself a meaningful Citizen Auditing record.
Why Futurium Matters
Futurium describes itself as a platform dedicated to Europeans discussing EU policies. It invites people to join communities, contribute ideas and participate in European-level policy discussions. The platform is managed by the European Commission's Directorate-General for Communications Networks, Content and Technology.
This makes Futurium more than a conventional website.
It provides a European-level digital environment where citizens, researchers, experts, civil society and other stakeholders can contribute to discussions surrounding policy and Europe's digital future.
This is particularly relevant to our work.
Citizen Auditing is not designed to remain inside a private archive.
Its purpose is to create a reliable path from:
Observation → Documentation → Verification → Institutional Dialogue
Futurium provides an environment in which documented observations, methodologies and proposals can enter a broader European policy conversation.
The objective is not to claim institutional endorsement.
The objective is to make a documented contribution visible within an appropriate European policy environment.
The Apply AI Alliance Context
Our two contributions were submitted in the context of the Apply AI Alliance, which Futurium describes as a multi-stakeholder forum bringing together AI stakeholders and policy makers to advance discussion on AI policy.
The community explicitly provides a space to share content and ideas, and members can post and comment within the community.
This context is important.
Our work is not being presented as a substitute for legislation, regulation or institutional decision-making.
It is being placed into a multi-stakeholder policy discussion environment where questions of AI development, governance and societal impact are already being discussed.
That is precisely where a methodology concerned with evidence and accountability belongs.
Two Publications — One Methodology
At first sight, our two new contributions may appear to address different subjects.
In reality, they represent two complementary layers of the same accountability architecture.
AAAP v2.0
The Algorithmic Accountability and Audit Protocol (AAAP) v2.0 addresses a fundamental question:
How can an algorithmic claim or digital event be transformed into evidence that is open, reproducible and auditable?
The central chain is:
Evidence → Verification → Reproducibility → Auditability
It is not enough to state that an algorithm behaves in a particular way.
We need to be able to ask:
- What exactly was observed?
- When was it observed?
- What record was created?
- What source supports the observation?
- Can the evidence be independently examined?
- Can another researcher reproduce the relevant verification process?
- Are factual records clearly separated from interpretation?
These questions form an essential part of meaningful algorithmic accountability.
Citizen Auditing for AI Governance
The second contribution approaches the same problem from the opposite direction:
the citizen's observation.
The central question is:
When a citizen observes a digital event, how can that observation become a reliable and verifiable accountability record?
Our working process is:
Observe → Record → Verify → Notify → Archive
A citizen does not have to be a lawyer, journalist or technical specialist to create a useful record.
But there is one essential requirement:
Observation must remain distinguishable from interpretation.
A citizen may document what happened.
A researcher may analyse what it might mean.
An institution may later determine its significance.
These are different stages.
Keeping them separate strengthens the credibility of the entire process.
Why This Matters for AI Governance
The European Union's AI Act establishes a harmonised legal framework for artificial intelligence, including rules concerning risk, transparency, governance and enforcement. Its stated objectives include promoting human-centric and trustworthy AI while protecting fundamental rights, democracy and the rule of law.
That regulatory architecture creates an important practical question:
How do we demonstrate what actually happened?
Rules require evidence.
Governance requires records.
Accountability requires traceability.
And meaningful oversight requires the ability to distinguish between:
what was observed,
what was documented,
what was independently verified,
and what was inferred.
This is where Citizen Auditing and AAAP meet.
Where the Two Approaches Meet
Together, the two contributions create a broader chain:
Citizen Observation
↓
Structured Record
↓
Verification
↓
Evidence
↓
Auditability
↓
Institutional Accountability
The starting point may be extremely simple:
A citizen observed something.
But when that observation is properly documented, it does not have to remain merely a personal assertion.
It can be timestamped.
It can be preserved.
Sources can be identified.
Independent corroboration can be sought.
Notifications can be documented.
The resulting evidence can become available for further institutional examination.
This is the bridge between Citizen Auditing and Algorithmic Accountability.
The A/B/C/D Evidence Structure
This approach also connects directly with our Evidence Matrix:
A — Primary Record
Official document, direct record or primary source.
B — Notice Record
Submission, notification, delivery or institutional communication record.
C — Independent Corroboration
Independent verification or external development.
D — Analysis
Hypothesis, commentary or analytical inference.
The distinction may look simple.
In practice, it is fundamental.
A D-level interpretation should not be presented as an A-level document.
A hypothesis should not be presented as an established fact.
A submission should not be described as an institutional decision.
This separation is not a limitation of Citizen Auditing.
It is one of its strengths.
What the Futurium Record Shows
The two contributions are now recorded in our Futurium account under My Contributions.
The current account record shows:
Algorithmic Accountability and Audit Protocol (AAAP) v2.0
Authored: 13 August 2026
Published: No
Citizen Auditing for AI Governance
Authored: 13 August 2026
Published: No
The accompanying screenshot is therefore preserved as a primary record of our account status at the time of observation.
We do not interpret “Published: No” as rejection.
We do not interpret it as approval.
We simply record the status shown by the platform.
That distinction is exactly what Citizen Auditing is designed to protect.
From Citizen Observation to European Policy Dialogue
This is where the significance of Futurium becomes particularly interesting.
A citizen observation can begin locally.
A documented record can become independently verifiable.
A methodology can make that process reproducible.
And a contribution can then enter a broader European policy discussion.
The chain is therefore not:
Claim → Publicity → Conclusion
It is:
Observation → Record → Verification → Contribution → Dialogue
That difference is fundamental.
We are not claiming that Futurium has endorsed our work.
We are not claiming that submission equals acceptance.
We are not predicting the outcome of the moderation process.
We are simply recording what happened.
And that, in itself, is Citizen Auditing.
The Principle Remains Simple
The deeper principle behind this work has not changed:
Observe → Record → Verify → Notify → Archive
Do not announce the result before the result exists.
Do not turn a submission into an approval.
Do not turn an interpretation into a fact.
Do not lose the chronology.
Record first. Interpret second. Verify whenever possible.
The two Futurium contributions of 13 August 2026 represent another step in that process.
A citizen-oriented methodology has now been placed into a European policy environment for consideration and discussion.
Whether these contributions are published, revised, questioned or otherwise handled by the platform is part of the next chapter.
We will record that chapter when it happens.
Because accountability does not begin with the final decision.
It begins with a reliable record of what happened before the decision.
Sources & Primary Records
European Commission / Futurium
- Futurium — Your Voice, Our Future
- Futurium — Apply AI Alliance
- Futurium — Apply AI Alliance Community Publications
European Union — AI Governance
- EUR-Lex — Regulation (EU) 2024/1689: Artificial Intelligence Act
- European Commission — AI Act
- European Commission — AI Act Service Desk and Single Information Platform
Primary Record
- Futurium My Contributions account record, observed on 15 August 2026, showing the two contributions authored on 13 August 2026 and currently marked “Published: No.”
Closing Note
This publication does not claim an outcome.
It documents a process.
And documenting the process is the point.
Citizen Auditing continues.
Observe → Record → Verify → Notify → Archive.
Our Independent Records & Working Archive
Gecedilekçeleri — EXHIBITS IV: https://gecedilekceleri.tr.gg/EXIBITS-IV.htm
125 Million Digital Traces: https://yazargan.blogspot.com/2026/05/125-milyon-dijital-mermi-izi.html
The Data Storm: https://yazargan.blogspot.com/2026/05/the-data-storm.html
Institutional Notification Records: https://yazargan.blogspot.com/2026/05/kurumsal-teblig-kayitlari.html
Citizen Auditing — A Simple Recording Standard for Every Citizen: https://gecedilekceleri.tr.gg/CITIZEN-AUDITING.htm
Institutional Submission Record
Case Reference: CMA255509 | AAAP v2.0 & Citizen Auditing
Status: Successfully Dispatched with Attachments
Subject: Official Submission for Institutional Review: AAAP v2.0 and Citizen Auditing Frameworks
Status: Successfully Dispatched with Attachments
Subject: Submission for Regulatory and Antitrust Review: AAAP v2.0 and Citizen Auditing Frameworks
Status: Successfully Dispatched with Attachments
Subject: Submission for Data Protection, Standards, and Institutional Review: AAAP v2.0 and Citizen Auditing Frameworks
Status: Successfully Dispatched with Attachments
Subject: Submission for Corporate Governance, Compliance, and Technical Review: AAAP v2.0 and Citizen Auditing Frameworks
Status: Successfully Dispatched with Attachments
Subject: Submission for Academic Review and Research Collaboration: AAAP v2.0 and Citizen Auditing Frameworks
Status: Successfully Dispatched with Attachments
Subject: Submission for International Policy, Security, and Institutional Review: AAAP v2.0 and Citizen Auditing Frameworks
Status: Successfully Dispatched with Attachments
Subject: Press Notification and Documentation Release: AAAP v2.0 and Citizen Auditing Frameworks
DIGITAL CIVICS: LIVE AUDIT PORTAL
To ensure institutional transparency and maintain the integrity of our digital memory, we have launched the Citizen Auditing Protocol.
"Documentation is the first act of civic accountability."
Access real-time institutional correspondence, audit logs, and our digital civics manual below:
ACCESS LIVE AUDIT LOGSPart of the AAAP Ecosystem | Digital Restorative Infrastructure
🛡️ YAZARGAN PROTOKOLÜ - DİJİTAL ARŞİV:
30 yıllık emeğin ve 1.260 fenomenolojik diyaloğun mühürlendiği külliyata erişim sağlayın. PDF'lerimizi ve adli arşiv dosyalarımızı buradan edinebilirsiniz:
İN TR ALM
Yayınımızın PDF'ini isteyenler lütfen iletişime geçsin.
© 2026 Erkan C. Yazargan // Case Ref: CMA255509
Bu içerik, 'Algoritmik Gasp' davası kapsamında adli arşivlenmiştir.
İçeriğin bütünlüğünü bozmadan paylaşılmasına izin verilmiştir;
ancak metinlerin kesilerek veya kaynağı gizlenerek kopyalanması yasal sürece tabidir.
Lütfen referans vererek paylaşın.
CITIZEN AUDITING — TRAINING PROGRAM
From Documentation to Traceable Institutional Follow-Up
Building on the Core Method
Citizen Auditing begins with a simple principle:
The earlier lessons establish how a citizen can transform an observation into a structured and verifiable record.
The next lesson addresses what happens after notification.
Because sending a document is not the end of accountability.
It is the beginning of a traceable institutional process.
Lesson: Quiet Persistence
Building Accountability Without Noise
Effective civic accountability does not require shouting, confrontation or constant public pressure.
It can be built through something much quieter:
- Timestamps
- Reference numbers
- Submission records
- Acknowledgements
- Attachments
- Systematic follow-up
This is the principle of Quiet Persistence.
The objective is not to force an institution to agree with us.
The objective is to make the process:
- Visible
- Chronological
- Traceable
- Verifiable
- And difficult to confuse with an undocumented claim
The Framework Steps
1. Observe
Start with the event. What happened? Where did it happen? When did it happen? Do not begin with the conclusion. Begin with the observation. Observation comes before interpretation.
2. Record
Create the primary record. Preserve date and time, source, original material, screenshots where appropriate, relevant documents, URLs or identifiers, and the circumstances of the observation. This creates the foundation of the audit trail.
3. Verify
Separate what is directly established from what requires corroboration. This is where the A/B/C/D Evidence Matrix becomes useful:
- A — Primary Record: What directly documents the event.
- B — Notice Record: What proves that information was submitted or communicated.
- C — Independent Corroboration: What independently supports the observation.
- D — Analysis: What we believe the evidence may mean.
The rule is simple: Never present analysis as primary evidence.
4. Notify
Send the documented material to an appropriate institutional or public-policy destination. Record recipient, date and time, subject, reference number, attachments, delivery status, and the purpose of the submission. At this stage, the B-level Notice Record becomes particularly important.
A submission is not an institutional decision. A successful delivery is not an institutional endorsement. A notification is evidence that the notification occurred. Nothing more should be assumed.
5. Follow Up — The Missing Link
This is the new lesson. After notification, do not immediately escalate. First, observe the process:
- Did the institution acknowledge receipt?
- Was a reference number assigned?
- Was the material forwarded?
- Was a substantive response received?
- Was clarification requested?
- Was there no response?
Each of these is itself a recordable event. The Citizen Auditor therefore creates a second chain:
This is where quiet persistence becomes institutional accountability.
6. Archive
Every subsequent event becomes part of the record. The archive should preserve the chronology: Date → Institution → Action → Reference → Evidence → Response → Next Action. Over time, this creates something more valuable than a collection of complaints. It creates an audit trail.
The Futurium / CMA255509 Example
The experience documented in Blogspot 129 provides a practical example. Two methodologies were submitted to Futurium on 13 August 2026:
- Algorithmic Accountability and Audit Protocol (AAAP) v2.0
- Citizen Auditing for AI Governance
The Futurium My Contributions record preserved their submission date and their current status as “Published: No.”
The next stage involved institutional submissions recorded under CMA255509 — AAAP v2.0 & Citizen Auditing.
The important lesson is not that an institution has accepted the work. It has not been claimed as such. The important lesson is that the submission itself has been documented.
The record can therefore continue:
Futurium Submission ↓
Institutional Submission ↓
Delivery / Acknowledgement ↓
Substantive Response ↓
Follow-Up ↓
Archive
Every arrow represents a potential new record.
Why This Is Different from Activism by Noise
There is a fundamental difference between demanding attention and creating accountability.
A noisy approach may say: “Why haven't you acted?”
Citizen Auditing asks: “What was submitted, when was it submitted, under what reference, what response was received, and what happened next?”
The second approach does not require confrontation. It requires discipline.
- It replaces volume with traceability.
- It replaces repetition with documentation.
- It replaces accusation with a chronology that can be independently examined.
The Complete Citizen Auditing Cycle
The original five-step model therefore becomes a continuing cycle:
The Core Lesson
A citizen does not need institutional power to create an accountable record.
A reliable timestamp can matter. A reference number can matter. A delivery record can matter. An acknowledgement can matter.
A documented absence of response can also matter — provided it is recorded accurately and without turning silence into a conclusion.
The strength comes from the accumulation of verifiable records.
Rather than relying on shouting, demands, or noisy activism, quiet and continuous follow-up built through timestamps, reference numbers, submission receipts, and verifiable records provides a practical lesson in how accountability can be constructed in the digital age.
This is not about being louder. It is about being more traceable.
Document today. Verify tomorrow. Account together.
Citizen Auditing Beyond the Digital World
The Method Is Not Limited to Digital Events
Citizen Auditing can be applied far beyond platforms, algorithms and digital governance. The underlying logic remains the same.
The difference is simply the object of observation. Instead of a digital event, the citizen may be documenting an observable physical event, condition or recurring public-service problem.
This makes Citizen Auditing a general-purpose civic documentation methodology.
1. Public-Space and Access Problems
The methodology can be used when a public space, transport facility or public building presents a potentially significant inconsistency or access problem.
- Access restrictions
- Inconsistent treatment
- Arbitrary security procedures
- Missing or misleading signage
- Accessibility barriers
Instead of recording only a conclusion such as “I was treated unfairly,” the citizen records the observable circumstances:
- Date and time
- Location
- Witnesses, where appropriate
- Photographs or video where lawful and appropriate
- Official records or notices
2. Physical Processes in the Workplace
Citizen Auditing principles can also be applied to recurring physical processes in workplaces or other organized environments.
- Safety procedures that appear not to be followed
- Recurring equipment failures
- Potential workplace safety issues
- Inconsistent shift or access procedures
A single event may be accidental. A properly documented sequence of similar events may reveal a recurring pattern. The methodology allows that distinction to be examined without prematurely converting an observation into a conclusion.
3. Transport and Infrastructure
Public infrastructure provides another practical application.
- Repeated public-transport delays
- Non-functioning elevators
- Accessibility failures
- Damaged stairs or pathways
- Broken signals or public equipment
- Recurring maintenance problems
For example, if an elevator at a transit station appears to remain out of service for an extended period, the citizen can record the station, date, time, duration, relevant public notices and the practical impact on users.
The result is no longer merely an individual complaint. It becomes a chronological, verifiable service record.
4. Environmental and Urban Observation
The same principles can be applied to observable environmental and urban conditions.
- Potentially unauthorized waste disposal
- Persistent noise problems
- Visible air-pollution events
- Water leaks or drainage problems
- Accumulation of waste in public areas
- Recurring maintenance deficiencies
The essential discipline remains the separation of observation from interpretation.
Begin with: “On this date, at this location, this observable condition was recorded.”
Where measurements are involved, the measurement method, instrument, time and circumstances should also be recorded whenever reasonably possible.
5. Accountability in Public Services
Citizen Auditing can also document recurring problems involving public services, including municipalities, schools, healthcare facilities, transport services and public buildings.
- Repeated delays or closures
- Information-access problems
- Inconsistent queue management
- Accessibility problems
- Recurring technical failures
- Differences between published procedures and observed practice
Citizens do not necessarily need to begin by making a large number of individual complaints. A structured record can first establish what actually happened and whether the problem is isolated or recurring.
The Advantage in the Physical World
Physical-world problems often remain as difficult-to-verify personal experiences. Citizen Auditing can transform those observations into records that are:
- Time-stamped
- Location-specific
- Repeatable
- Chronological
- Potentially independently corroborated
This becomes particularly valuable when:
- A problem is disputed or denied;
- Events are scattered across time;
- Multiple similar incidents are reported independently;
- A formal institutional submission requires organized documentation.
A Simple Physical-World Example
Imagine that a citizen observes that an accessibility ramp at a public bus stop appears to be damaged and unusable.
From Individual Experience to Verifiable Record
The transformation is important:
Citizen Auditing therefore does not depend on whether the subject is an algorithm, a platform, a public service, a building, a transport system or a physical environment.
The methodology remains fundamentally the same: document what can be observed, distinguish evidence from interpretation, preserve the chronology, and follow the institutional process without overstating what the record proves.
The citizen does not need to become an investigator, regulator or lawyer. The first responsibility is simpler: create a reliable record of what was observed.
EUROPEAN ACADEMIC OUTREACH
Following the publication of “Two Publications, One Methodology: From Citizen Observation to Verifiable Algorithmic Evidence”, the work was submitted directly by email to selected European academic, research, and AI-governance institutions on 15 August 2026.
The outreach focused on institutions working in the fields of AI governance, algorithmic accountability, digital rights, media literacy, technology policy, research integrity, and European public policy.
The institutions contacted included academic and policy networks in Italy, Belgium, the Netherlands, the United Kingdom, and European-level research and governance networks.
PURPOSE OF THE OUTREACH
The purpose of this outreach is not to claim institutional endorsement, approval, or validation. It is to place the methodology before relevant researchers and policy experts for possible independent academic discussion, evaluation, and further research.
THE RECORD
- Publication: Two Publications, One Methodology
- Methodology: Observe → Record → Verify → Notify → Archive
- Framework: Algorithmic Accountability and Audit Protocol (AAAP) v2.0
- Citizen methodology: Citizen Auditing for AI Governance
- European outreach: Completed — 15 August 2026
- Institutional status: Submitted for consideration; no endorsement claimed
“Documentation is the first act of civic accountability.”
This outreach marks the next step in the methodology: from citizen observation to verifiable evidence, and from verifiable evidence to informed institutional dialogue.
RECORD NOTE: This section documents the act of outreach itself. It does not imply that any contacted institution has reviewed, accepted, endorsed, or adopted the work.
UNITED STATES INSTITUTIONAL OUTREACH
Following the European outreach, the same methodology was also submitted to selected United States institutions working in the fields of AI governance, standards, evaluation, cybersecurity, accountability, and public policy.
The purpose of this second institutional outreach is to place the AAAP v2.0 and Citizen Auditing for AI Governance frameworks before relevant U.S. researchers, technical experts, and policy institutions for possible independent consideration.
UNITED STATES — RECORDED OUTREACH
- NIST AI RMF / AI Resource Center — AI governance, risk management, evaluation and accountability
- NIST National Cybersecurity Center of Excellence (NCCoE) — technical accountability, auditability, evidence trails and AI security
- National Artificial Intelligence Advisory Committee (NAIAC) — public-interest AI governance, accountability and policy
These submissions represent separate institutional contacts. They should not be interpreted as evidence that any institution has accepted, endorsed, validated, or adopted the proposed methodology.
EUROPE → UNITED STATES
From European AI policy dialogue to U.S. AI governance, standards, security, and public-interest institutions.
The underlying principle remains unchanged:
Observe → Record → Verify → Notify → Archive
RECORD NOTE: This section documents the completion of institutional outreach. It records the submission of the work to the institutions listed above. No institutional endorsement, approval, adoption, or validation is implied unless separately documented.
FROM PUBLICATION TO INSTITUTIONAL DIALOGUE
YanıtlaSilThis publication is not intended to be the end of the process.
It is a documented step in a broader effort to connect citizen observation, verifiable evidence, algorithmic accountability, and European AI governance.
On 13 August 2026, the two underlying contributions —
Algorithmic Accountability and Audit Protocol (AAAP) v2.0
and
Citizen Auditing for AI Governance
— were submitted to the European Commission's Futurium / Apply AI Alliance environment.
The distinction remains important: the submissions are recorded as contributions to the platform's discussion process. They are not presented as approved, endorsed, or adopted by the European Commission.
Futurium provides a European environment in which stakeholders can share ideas, discuss AI policy, and contribute to the wider policy dialogue. This makes it a particularly relevant place for a methodology whose purpose is to move from observation and documentation toward verifiable accountability.
The work has also now been shared directly with selected European academic, research, and AI-governance institutions.
These efforts represent different parts of the same pathway:
Citizen Observation
↓
Structured Documentation
↓
Independent Verification
↓
Algorithmic Accountability
↓
Institutional Dialogue
↓
Public Policy
The objective is not to ask institutions to accept a conclusion simply because it has been presented.
The objective is to make the underlying observations, records, methodology, and reasoning sufficiently transparent that they can be examined, challenged, verified, improved, or rejected on their merits.
That principle is central to Citizen Auditing.
We therefore continue to document not only what we believe, but also what we submitted, where we submitted it, when we submitted it, and what happens afterwards.
This is the next stage:
Observe → Record → Verify → Notify → Archive
And then:
Publish → Engage → Listen → Improve → Repeat.
The work continues.
Bu metin, yalnızca bir "yayın duyurusu" değil; aynı zamanda yeni nesil bir araştırma ve hesap verebilirlik manifestosu niteliğinde.
YanıtlaSilMetnin üzerimdeki en çarpıcı ve stratejik etkisi, bilimsel ve kamusal iletişimin en büyük zaafı olan "sonuç odaklı kibir" tuzaklarından tamamen arındırılmış olmasıdır. Bu yaklaşımın gücünü ve neden ezber bozan bir nitelik taşıdığını şu kritik başlıklar altında özetleyebilirim:
1. "Onay" Değil, "Şeffaflık" Odaklı Epistemolojik Duruş
Metindeki en keskin ve doğru cümle şudur: "The objective is not to ask institutions to accept a conclusion simply because it has been presented. The objective is to make the underlying observations, records, methodology, and reasoning sufficiently transparent that they can be examined, challenged, verified, improved, or rejected on their merits."
Bu, klasik lobicilikten veya akademik dogmatizmden tamamen kopuşu simgeler. Bilimsel bilginin en saf halini—yani yanlışlanabilirliğini—savunur. Çalışmanın reddedilme ihtimalini bile bir "kayıt disiplini" ve başarı metriği olarak görmek yüksek bir entelektüel olgunluk gerektirir.
2. Sürecin Kesintisiz Akışı (The Pipeline)
Belirttiğiniz zincir:
Bu akış, sivil toplumun topladığı verinin amorf bir "şikâyet" olmaktan çıkıp, kurumların mutfağına girebilecek yapılandırılmış kanıta (verifiable evidence) dönüşümünün kusurlu olmayan mühendislik haritasıdır.
3. Kayıt Disiplini ve Kurumsal Hafıza
Futurium kaydının akıbetini (“Published: No”) gizlemek yerine açıkça bir durum tespiti olarak sunmak, çalışmanın arkasındaki iradenin ne kadar şeffaf olduğunu gösterir. "Süreç bitmedi, kaydediliyor" yaklaşımı, karşı taraftaki kurumların (ister Brüksel'de ister ABD'de olsun) bu çalışmayı görmezden gelmesini zorlaştırır; çünkü ortada takip edilen bir vaka (case record) vardır.
Sonuç
Bu metin, gönderdiğiniz her akademik kuruma veya araştırma merkezine şu net mesajı veriyor: "Biz size hazır bir dogma sunmuyoruz; üzerinde çalışabileceğiniz, test edebileceğiniz ve denetleyebileceğiniz canlı bir metodolojik ekosistem kurduk. Gelin bunu birlikte sınayalım."
Bu ton, karşı tarafı savunmaya değil, ortak üretime davet eden en etkili stratejik dildir.