Changes for page Open Source Model and Licensing

Summary

• Page properties (1 modified, 0 added, 0 removed)

Details

Page properties

Content

...	...	@@ -1,7 +1,10 @@
1	1	= Open Source Model and Licensing =
	2	+
2	2	== 1. Purpose and Relation to Other Documents ==
	4	+
3	3	This page explains **how FactHarbor is run from a licensing and enforcement perspective** – as an open, trustworthy, non-profit oriented, but professionally maintained project.
4	4	It covers in particular:
	7	+
5	5	* the **licensing choices** for code, documentation, data, and core specifications,
6	6	* how contributors grant the project the right to use and enforce those licenses,
7	7	* how AI-related components (such as AKEL) fit into the licensing picture,
...	...	@@ -9,7 +9,7 @@
9	9	* **organisational transparency commitments**,
10	10	* **privacy and data protection standards**.
11	11	Together with the other Organisation pages, it defines **how FactHarbor is run**:
12		-* [[Governance>>FactHarbor.Organisation.Governance.WebHome]] – who decides what, and under which principles
	15	+* [[Governance>>Archive.FactHarbor 2026\.02\.08.Organisation.Governance.WebHome]] – who decides what, and under which principles
13	13	* [[Finance & Compliance>>FactHarbor.Organisation.Finance-Compliance]] – how funding, transparency, and internal controls work
14	14	* [[Legal Framework>>FactHarbor.Organisation.Legal-Framework]] – legal forms, contracts, and regulatory aspects
15	15	The **Specification** (Mission, Requirements, Architecture, Data Model, Workflows, etc.) describes **what FactHarbor does**.
...	...	@@ -16,8 +16,11 @@
16	16	This Open Source Model and Licensing page (together with Governance and Finance & Compliance) describes **how FactHarbor is run and protected**.
17	17	For historical context, earlier drafts used a purely AGPLv3-centric model for the core software.
18	18	The current licence mix is defined in the sections below and takes precedence over any older drafts.
	22	+
19	19	== 2. Overview ==
	24	+
20	20	FactHarbor is, and will remain, an **open source project** that:
	26	+
21	21	* publishes its work openly whenever legally and ethically possible
22	22	* makes its reasoning and evidence inspectable
23	23	* invites contributions under clear, transparent rules
...	...	@@ -31,24 +31,31 @@
31	31	* the standards that repositories must follow,
32	32	* **organisational transparency and privacy commitments**.
33	33	Normative licensing decisions on this page **override** any older variants or drafts.
	40	+
34	34	== 3. Licensing (Current Decisions) ==
	42	+
35	35	=== 3.1 Documentation ===
	44	+
36	36	All general **documentation** (organisational and technical) is licensed under:
	46	+
37	37	* **Creative Commons Attribution-ShareAlike 4.0 (CC BY-SA 4.0)**
38	38	This allows:
39	39	* reuse, adaptation, and translation of documentation,
40	40	* including commercial reuse,
41	41	* as long as:
42		- * clear attribution to FactHarbor is preserved, and
43		- * derivative works are shared under the **same license (CC BY-SA 4.0)**.
	52	+* clear attribution to FactHarbor is preserved, and
	53	+* derivative works are shared under the **same license (CC BY-SA 4.0)**.
44	44	Exception handling:
45	45	* In rare cases, **security-sensitive or abuse-enabling documentation** may be:
46		- * published only in partial form, or
47		- * made available under more restrictive terms, or
48		- * kept internal.
	56	+* published only in partial form, or
	57	+* made available under more restrictive terms, or
	58	+* kept internal.
49	49	* Any such exceptions must be **explicitly documented** where they apply.
	60	+
50	50	=== 3.2 Core Protocol & Data Model ===
	62	+
51	51	The **core protocol**, core **data model** (including key ERDs), and other "defining specifications" are licensed under:
	64	+
52	52	* **Creative Commons Attribution-ShareAlike 4.0 (CC BY-SA 4.0)**
53	53	Intent:
54	54	* enable **collaborative evolution** of the protocol and data model,
...	...	@@ -59,23 +59,26 @@
59	59	* You may **use, implement, and modify** the protocol/data model in your own systems.
60	60	* You may **publish derivative or modified specifications** under CC BY-SA 4.0.
61	61	* Derivative specifications must:
62		- * be clearly attributed to FactHarbor,
63		- * use different branding/names (trademark protection),
64		- * state they are "derived from FactHarbor protocol",
65		- * remain under CC BY-SA 4.0 (share-alike).
	75	+* be clearly attributed to FactHarbor,
	76	+* use different branding/names (trademark protection),
	77	+* state they are "derived from FactHarbor protocol",
	78	+* remain under CC BY-SA 4.0 (share-alike).
66	66	* Changes to the **canonical FactHarbor specification** are governed through FactHarbor's internal review and release processes.
67	67	**Trademark Protection:**
68	68	The "FactHarbor" name and associated marks are protected separately from the license. Derivative protocols may not use "FactHarbor" branding without explicit permission, ensuring users can distinguish official from derivative implementations.
69	69	This approach (license for sharing + trademark for brand protection) follows successful models like Mozilla Firefox and the W3C.
	83	+
70	70	=== 3.3 Code ===
	85	+
71	71	**Default License:** Unless explicitly stated otherwise, **code** produced under the FactHarbor project is licensed under:
	87	+
72	72	* **MIT License**
73	73	This allows:
74	74	* broad reuse, including in commercial software,
75	75	* proprietary integrations and extensions,
76	76	* as long as:
77		- * the MIT license text is included, and
78		- * attribution to the FactHarbor project is preserved.
	93	+* the MIT license text is included, and
	94	+* attribution to the FactHarbor project is preserved.
79	79	**Hybrid Licensing for Core Components:**
80	80	For the **core reasoning engine** and **AKEL components**, we recommend using **AGPL-3.0** to prevent black-box deployments and ensure transparency of modifications.
81	81	The recommended hybrid approach:
...	...	@@ -87,27 +87,33 @@
87	87	* Prevents "FactHarbor-as-a-service" black boxes that contradict transparency mission
88	88	* MIT for peripheral components maximizes ecosystem growth
89	89	* Strong protection of **openness of reasoning** is handled via:
90		- * open protocol and data model (CC BY-SA),
91		- * open documentation (CC BY-SA),
92		- * AGPL for core reasoning components,
93		- * and explicit transparency rules.
	106	+* open protocol and data model (CC BY-SA),
	107	+* open documentation (CC BY-SA),
	108	+* AGPL for core reasoning components,
	109	+* and explicit transparency rules.
94	94	The decision to implement this hybrid model should be made explicitly before the first public release.
	111	+
95	95	=== 3.4 Structured Data & Curation Artefacts ===
	113	+
96	96	Structured data, curated knowledge artefacts and derived datasets are licensed under:
	115	+
97	97	* **Open Database License (ODbL)**
98	98	**Note on ODbL:** The Open Database License includes a share-alike requirement, ensuring derivative databases remain open. This aligns with FactHarbor's commitment to openness and prevents proprietary capture of community-curated data.
99	99	Principles:
100	100	* data used for public reasoning should be:
101		- * reusable and remixable,
102		- * properly attributed,
103		- * versioned and traceable,
104		- * kept open through share-alike.
	120	+* reusable and remixable,
	121	+* properly attributed,
	122	+* versioned and traceable,
	123	+* kept open through share-alike.
105	105	* privacy, safety, and legal constraints may require:
106		- * partial publication or anonymity,
107		- * stronger access control around certain datasets.
	125	+* partial publication or anonymity,
	126	+* stronger access control around certain datasets.
108	108	Concrete exceptions and more restrictive handling must be **documented at dataset level**.
	128	+
109	109	=== 3.5 Attribution Guidelines (Non-Mandatory but Recommended) ===
	130	+
110	110	FactHarbor encourages, but generally does not require beyond the base licenses, that:
	132	+
111	111	* user interfaces show a short line such as:
112	112	`Powered by FactHarbor (open documentation, open protocol, open data)`
113	113	Intent:
...	...	@@ -114,35 +114,47 @@
114	114	* strengthen **brand recognition** and trust,
115	115	* keep attribution light-weight and compatible with open licenses,
116	116	* avoid creating extra legal conditions beyond the existing licenses.
	139	+
117	117	== 4. Licensing Goals and Principles ==
	141	+
118	118	Earlier "Open Source Model & Licensing" drafts contained valuable reasoning about **why** strong open-source protections might be needed. The core goals remain relevant, even though the exact license mix has evolved.
119	119	FactHarbor's licensing aims to:
	144	+
120	120	* **Protect openness of reasoning**
121		- * Users must be able to understand how conclusions were reached.
122		- * Code and documentation that materially affect user-visible behaviour should be inspectable or clearly described.
	146	+* Users must be able to understand how conclusions were reached.
	147	+* Code and documentation that materially affect user-visible behaviour should be inspectable or clearly described.
123	123	* **Discourage hostile or misleading forks**
124		- * Avoid "closed clones" that keep the FactHarbor name or appearance while hiding important changes.
125		- * Forks that significantly diverge should use their own branding and not pretend to be official FactHarbor instances.
	149	+* Avoid "closed clones" that keep the FactHarbor name or appearance while hiding important changes.
	150	+* Forks that significantly diverge should use their own branding and not pretend to be official FactHarbor instances.
126	126	* **Make modifications traceable**
127		- * Substantial changes to code, specs, or governance documents should be documented and versioned.
128		- * Users interacting with a service based on FactHarbor should be able to see **which version or fork** they are using.
	152	+* Substantial changes to code, specs, or governance documents should be documented and versioned.
	153	+* Users interacting with a service based on FactHarbor should be able to see **which version or fork** they are using.
129	129	* **Support long-term sustainability and legal clarity**
130		- * Licenses and governance must be enforceable in practice.
131		- * The organisation should have clear standing to protect the project if needed.
	155	+* Licenses and governance must be enforceable in practice.
	156	+* The organisation should have clear standing to protect the project if needed.
	157	+
132	132	== 5. Contributors, Governance & CLA ==
	159	+
133	133	=== 5.1 Contributor Journey (from licensing perspective) ===
	161	+
134	134	The contributor journey (Visitor → New Contributor → Contributor → Trusted Contributor → Contributor → Moderator → Trusted Contributor) is defined in more detail in the **Contributor Processes** and **Organisation** pages.
135	135	From a *licensing* perspective, the key points are:
	164	+
136	136	* All contributions must be compatible with the chosen licenses (CC, MIT, AGPL, ODbL, etc.).
137	137	* Contributors confirm that they have the right to contribute the material under these licenses.
138	138	* Higher-trust roles (Trusted Contributors, Contributors, Moderators) help enforce licensing and attribution rules when reviewing changes.
139	139	For full role definitions, see the **Organisation / Contributor Processes** documentation.
	169	+
140	140	=== 5.2 Contributor License Agreement (CLA) ===
	171	+
141	141	To keep the legal situation clear and enforceable, FactHarbor uses a **Contributor License Agreement (CLA)**.
142	142	See [[Contributor License Agreement>>FactHarbor.Organisation.CLA]].
	174	+
143	143	==== 5.2.1 Dual Contributor Model ====
	176	+
144	144	FactHarbor distinguishes between two contributor types with different copyright arrangements:
145	145	**Unpaid Contributors (Volunteers)**:
	179	+
146	146	* **Retain copyright** of their contributions
147	147	* Grant FactHarbor a perpetual, royalty-free license to use and distribute
148	148	* Enable the project to enforce licenses on their behalf
...	...	@@ -157,65 +157,87 @@
157	157	* Provides clarity for commercially sponsored work
158	158	* Ensures FactHarbor can effectively maintain and defend the project
159	159	* Maintains transparency about contribution sources
	194	+
160	160	==== 5.2.2 Core Intent (All Contributors) ====
	196	+
161	161	Regardless of contributor type, the CLA ensures:
	198	+
162	162	* Contributors grant the **FactHarbor organisation**:
163		- * a **perpetual, worldwide, irrevocable license** to use, modify, and redistribute their contributions under the project's chosen licenses (CC BY-SA, MIT, AGPL, ODbL, etc.), and
164		- * the **express right to enforce** those licenses and **pursue legal action** against infringers on their behalf.
	200	+* a **perpetual, worldwide, irrevocable license** to use, modify, and redistribute their contributions under the project's chosen licenses (CC BY-SA, MIT, AGPL, ODbL, etc.), and
	201	+* the **express right to enforce** those licenses and **pursue legal action** against infringers on their behalf.
165	165	This ensures that:
166	166	* the organisation has **clear standing** to defend the project legally,
167	167	* individual contributors do not have to act alone against infringements,
168	168	* licensing remains enforceable even if contributors become inactive.
	206	+
169	169	==== 5.2.3 Determining Contributor Type ====
	208	+
170	170	* **Default**: Contributors are considered unpaid volunteers unless they have a written agreement specifying paid status.
171	171	* **Paid Status Indicators**: Employment contract, written contracting agreement, or grant/sponsorship agreement.
172	172	* **Transparency**: Contributor type should be disclosed where applicable.
173	173	See [[Contributor License Agreement>>FactHarbor.Organisation.CLA]] for complete terms.
	213	+
174	174	== 6. AI Models and Licensing (AKEL) ==
	215	+
175	175	AKEL (AI Knowledge Extraction Layer) may rely on different types of models. Licensing and transparency rules are crucial here.
	217	+
176	176	=== 6.1 Open vs Proprietary Models ===
	219	+
177	177	AKEL may use:
	221	+
178	178	* **Open-source models (preferred)**:
179		- * weights and code are openly available under compatible licenses,
180		- * prompts, evaluation logic and integration code are made public where licenses permit.
	223	+* weights and code are openly available under compatible licenses,
	224	+* prompts, evaluation logic and integration code are made public where licenses permit.
181	181	* **Proprietary / hosted models (allowed but constrained)**:
182		- * used only when necessary for quality or feasibility,
183		- * must be clearly **disclosed to the user** at point of use,
184		- * AKEL must label which parts of its output derive from proprietary tools,
185		- * surrounding **integration logic remains open** (MIT/AGPL or compatible) and is documented.
	226	+* used only when necessary for quality or feasibility,
	227	+* must be clearly **disclosed to the user** at point of use,
	228	+* AKEL must label which parts of its output derive from proprietary tools,
	229	+* surrounding **integration logic remains open** (MIT/AGPL or compatible) and is documented.
186	186	Rules:
187	187	* No deployment may suggest "fully open" AI if proprietary models are used without disclosure.
188	188	* For high-impact reasoning (e.g. health, politics, safety-critical topics), **open, auditable models** are preferred wherever feasible.
189	189	* Where proprietary models are unavoidable, additional care is taken to:
190		- * document limitations,
191		- * avoid overstating certainty,
192		- * and keep reasoning layers as transparent as possible.
	234	+* document limitations,
	235	+* avoid overstating certainty,
	236	+* and keep reasoning layers as transparent as possible.
	237	+
193	193	=== 6.2 Prompts, Pipelines and Integration Code ===
	239	+
194	194	* Orchestration code, pipelines and evaluation logic around AKEL are treated as part of the **open FactHarbor codebase** (MIT or AGPL).
195	195	* Where prompts or model configurations are licensed in a way that restricts publication, this must be documented clearly, and safe abstractions should be used in public documentation.
	242	+
196	196	=== 6.3 AI Prompts and Orchestration ===
	244	+
197	197	* Prompts, system instructions, and orchestration code are considered **Code** and licensed under **MIT** or **AGPL** (depending on component).
198	198	* They must be visible in the repository to ensure the system is not a 'black box'.
199	199	* If a proprietary model requires a prompt that cannot be shared (e.g. contractual restriction), that component cannot be part of the open core.
	248	+
200	200	== 7. Third-Party Libraries and Components ==
	250	+
201	201	FactHarbor depends on third-party libraries under:
	252	+
202	202	* permissive licenses (MIT, Apache-2.0, BSD), and/or
203	203	* other compatible open-source licenses.
204	204	Requirements:
205	205	* All dependencies must be **license-compatible** with:
206		- * the MIT/AGPL-licensed code,
207		- * and the overall FactHarbor licensing strategy.
	257	+* the MIT/AGPL-licensed code,
	258	+* and the overall FactHarbor licensing strategy.
208	208	* License information is documented in:
209		- * `/LICENSE` and, where applicable, `/NOTICE`,
210		- * and a dedicated "Third-Party Licenses" section in project documentation.
	260	+* `/LICENSE` and, where applicable, `/NOTICE`,
	261	+* and a dedicated "Third-Party Licenses" section in project documentation.
211	211	FactHarbor actively avoids dependencies that:
212	212	* restrict redistribution in ways incompatible with open-source norms,
213	213	* prevent network users from accessing the relevant source,
214	214	* or conflict with the project's transparency and licensing goals.
	266	+
215	215	== 8. Repository Standards ==
	268	+
216	216	Each official FactHarbor repository must follow a minimum standard.
	270	+
217	217	=== 8.1 Required Files ===
	272	+
218	218	Each repository should contain at least:
	274	+
219	219	* `README` – purpose, scope, status, and how to use it.
220	220	* `LICENSE` – the applicable license(s) for the repository.
221	221	* `CONTRIBUTING` – how to propose changes; coding/writing guidelines.
...	...	@@ -222,29 +222,40 @@
222	222	* `CODEOWNERS` – who is responsible for which parts.
223	223	* `CHANGELOG` – human-readable log of important changes.
224	224	* `SECURITY` (or `SECURITY.md`) – how to report vulnerabilities and how they are handled.
	281	+
225	225	=== 8.2 Prohibited Content ===
	283	+
226	226	FactHarbor repositories must **not** contain:
	285	+
227	227	* purely ideological advocacy texts unrelated to the project's purpose,
228	228	* opaque binaries or artefacts that cannot reasonably be inspected or reproduced,
229	229	* embedded secrets (API keys, passwords, private tokens),
230	230	* content that materially contradicts the stated licenses or governance rules.
	290	+
231	231	== 9. Historical Licensing Option: AGPLv3 for Core Engine (Non-Normative Background) ==
	292	+
232	232	Earlier versions of this page explored a **strong copyleft** option for the core software based on **GNU Affero General Public License v3 (AGPLv3)**.
233	233	Those drafts argued that:
	295	+
234	234	* AGPLv3, as a **network-copyleft license**, would:
235		- * require modified network services to publish their source to users,
236		- * prevent closed forks of the core reasoning engine,
237		- * ensure that any public "FactHarbor-like" service stays inspectable.
	297	+* require modified network services to publish their source to users,
	298	+* prevent closed forks of the core reasoning engine,
	299	+* ensure that any public "FactHarbor-like" service stays inspectable.
238	238	They also defined:
239	239	* the scope of AGPLv3 coverage (backend services, AKEL logic, frontend),
240	240	* expectations for forks (must remain AGPLv3, must declare they are forks),
241		- * and the same CLA principles now adapted to the current license mix.
	303	+* and the same CLA principles now adapted to the current license mix.
242	242	These AGPLv3 considerations have been **partially adopted** in the hybrid licensing model (section 3.3), where AGPL-3.0 is recommended for core reasoning components.
243	243	They are preserved here as **design background** and may be revisited for specific components or future arrangements.
	306	+
244	244	== 10. Organisational Transparency ==
	308	+
245	245	FactHarbor is committed to exceptional transparency in all aspects of its operations, governance, and finances. This commitment is essential to build trust in a system claiming to support well-grounded judgments.
	310	+
246	246	=== 10.1 Financial Transparency ===
	312	+
247	247	We commit to publishing annually:
	314	+
248	248	* Complete financial statements (audited where possible)
249	249	* Swiss tax filings (annual statements per Swiss law)
250	250	* Income sources in aggregate (grants, donations, sponsorships)
...	...	@@ -251,8 +251,11 @@
251	251	* Expense breakdown by category
252	252	* Compensation ranges for staff roles (not individual salaries)
253	253	* Major funding relationships and partnerships
	321	+
254	254	=== 10.2 Governance Transparency ===
	323	+
255	255	We commit to publishing:
	325	+
256	256	* All governance documents (bylaws, policies, procedures)
257	257	* Governing Team composition and meeting schedules
258	258	* Governing Team meeting minutes (with narrow exceptions for privacy, security, or legal matters)
...	...	@@ -259,8 +259,11 @@
259	259	* Policy changes with rationale and effective dates
260	260	* Decision-making process documentation
261	261	* Conflict of interest policies and disclosures
	332	+
262	262	=== 10.3 Operational Transparency ===
	334	+
263	263	We commit to publishing:
	336	+
264	264	* Transparency reports (published twice yearly)
265	265	* Content moderation statistics and practices
266	266	* AKEL performance metrics and audit results
...	...	@@ -268,8 +268,11 @@
268	268	* Partnership agreements and funding relationships
269	269	* Incident reports (security, moderation, governance)
270	270	* System uptime and performance data
	344	+
271	271	=== 10.4 Privacy Protection ===
	346	+
272	272	While maintaining organisational transparency, we protect:
	348	+
273	273	* Individual user privacy and personal data
274	274	* Security vulnerabilities (until patched, typically 30-90 days)
275	275	* Personnel matters and personal information
...	...	@@ -276,7 +276,9 @@
276	276	* Ongoing legal matters (until resolved)
277	277	* Whistleblower and abuse reports
278	278	* Authentication credentials and sensitive operational details
	355	+
279	279	=== 10.5 Review and Oversight ===
	357	+
280	280	* Annual review of all information marked "private"
281	281	* Public reporting on transparency compliance
282	282	* Community input opportunities on transparency policies
...	...	@@ -283,15 +283,22 @@
283	283	* Appeals process for information requests
284	284	* Independent transparency audits (when feasible)
285	285	See [[Transparency Policy>>FactHarbor.Organisation.How-We-Work-Together.Transparency-Policy]] for complete details.
	364	+
286	286	== 11. Privacy and Data Protection ==
	366	+
287	287	FactHarbor is committed to protecting user privacy while maintaining transparency in operations and governance.
	368	+
288	288	=== 11.1 Data Collection Principles ===
	370	+
289	289	* **Data minimization**: Collect only what is necessary for functionality
290	290	* **Purpose limitation**: Use data only for stated purposes
291	291	* **Short retention**: Delete data when no longer needed
292	292	* **User control**: Provide access, correction, and deletion rights
	375	+
293	293	=== 11.2 User Rights ===
	377	+
294	294	Users have the right to:
	379	+
295	295	* Access their personal data
296	296	* Correct inaccurate information
297	297	* Delete their accounts and associated data
...	...	@@ -298,20 +298,27 @@
298	298	* Export their data (portability)
299	299	* Object to certain processing
300	300	* Lodge complaints with supervisory authorities
	386	+
301	301	=== 11.3 What We Collect ===
	388	+
302	302	For specific details on data collection practices, retention periods, and processing purposes, see [[Privacy Policy>>FactHarbor.Organisation.How-We-Work-Together.Privacy-Policy]].
303	303	In general:
	391	+
304	304	* **Public contributions**: Permanently public and attributed (essential for transparency)
305	305	* **Account information**: Email, username (minimal required data)
306	306	* **Technical data**: IP addresses, user agents (short retention, logged out users)
307	307	* **Usage data**: Aggregated, anonymized analytics
	396	+
308	308	=== 11.4 What We Never Do ===
	398	+
309	309	* Sell or rent user data
310	310	* Share personal data with third parties for marketing
311	311	* Track users across unrelated sites
312	312	* Use personal data for purposes beyond stated scope
313	313	* Keep personal data longer than necessary
	404	+
314	314	=== 11.5 Security Measures ===
	406	+
315	315	* Encryption in transit (TLS/HTTPS)
316	316	* Encryption at rest for sensitive data
317	317	* Access controls and authentication
...	...	@@ -320,9 +320,12 @@
320	320	* Vulnerability disclosure program
321	321	* **Data Protection Impact Assessments (DPIA)** for high-risk processing (required by FADP Article 22)
322	322	See [[Privacy Policy>>FactHarbor.Organisation.How-We-Work-Together.Privacy-Policy]] for complete details.
	415	+
323	323	=== 11.6 Data Protection Officer (DPO) ===
	417	+
324	324	**If we serve users in the European Union**, we will appoint a Data Protection Officer (DPO) as required by EU GDPR Article 37.
325	325	The DPO will:
	420	+
326	326	* Advise on data protection compliance
327	327	* Monitor FADP and GDPR compliance
328	328	* Serve as contact point for Swiss FDPIC and EU data protection authorities
...	...	@@ -333,20 +333,30 @@
333	333	* Large-scale systematic monitoring of data subjects
334	334	* Large-scale processing of sensitive personal data (including political opinions, health information)
335	335	Given that FactHarbor processes claims containing political opinions and uses AI for systematic evaluation, we commit to appointing a DPO if we process personal data of EU residents.
	431	+
336	336	== 12. Exceptions and Appeals ==
	433	+
337	337	=== 12.1 Requesting Information ===
	435	+
338	338	If you believe FactHarbor should disclose specific organisational information:
	437	+
339	339	1. Submit a written request to [Transparency contact to be established]
340	340	2. Specify the information requested and rationale
341	341	3. Expect initial response promptly
	441	+
342	342	=== 12.2 Appeals Process ===
	443	+
343	343	If a transparency request is denied:
	445	+
344	344	1. Appeal to the Transparency Committee (if established)
345	345	2. Provide additional context or rationale
346	346	3. Expect appeal decision promptly
347	347	4. Final appeals may be escalated to the Governing Team
	450	+
348	348	=== 12.3 Exception Criteria ===
	452	+
349	349	Information may be withheld only if disclosure would:
	454	+
350	350	* Violate individual privacy rights
351	351	* Compromise security (vulnerability, credential)
352	352	* Violate legal obligations (court order, attorney-client privilege)