工作方案
决定
已记录的决策和提交法律顾问的问题。每条记录保持原文。
01登记册
问题、建议和记录以英文原文显示。负责人的话按原文引用，因此不翻译。
D1 开放
Multisite set-up on kurds.global: subdirectory install, and the subsite paths in content/network/network.json
建议 Subdirectory multisite with the master site at /, area subsites and one subsite per country programme, as in dist/sites.csv
验收关口 KU-WP-13
D2 开放
Names and paths of the area subsites
建议 As in content/network/network.json, confirmed with the charter’s organs
验收关口 KU-WP-13
D3 开放
Course hosting
建议 Courses authored in this repository’s course format and served by the LMS chosen for the Learn subsite
验收关口 KU-WP-11
D4 开放
Launch languages
建议 As in locales/locales.json (launch phase)
验收关口 KU-WP-06
D5 开放
Serving users inside the homeland states
建议 Public educational content for all; member features only after counsel’s review (L3, L5)
D6 开放
How the council and scholarly board are formed
建议 Open call plus nominations, published criteria, two-year terms
验收关口 KU-WP-02
D7 开放
Funding policy
建议 No funding from homeland governments, parties or armed groups; every funder disclosed
验收关口 KU-WP-27
D8 开放
Advocacy
建议 None run by the platform; partners linked
D10 开放
Adopt the proposed public-interest campaigns (content/campaigns/campaigns.json): Count us in, Teach the mother tongue, Safe by default
建议 Add them to the Work Program one at a time, each with its milestones, after the General Assembly confirms they are non-partisan and within the charter’s public-communications scope
D12 开放
Adopt the recognition framework for learning and participation (content/network/credentials.json): learning credits, course badges, capstones, stackable pathway credentials, participation badges and learner levels, served by GamiPress with Tutor LMS
建议 Decide by the General Assembly, through the Work Program. Until then the Site Kit creates every item as a draft and the pages call it proposed. The learner-level thresholds (one and three pathway credentials) are proposals
D13 开放
Third-party scripts on the live pages: Google Analytics and the iubenda widget load from outside servers, against the platform rule (no third-party scripts, fonts, embeds or trackers)
建议 Proposed, privacy first. Remove both. On the native stack the nexus-foundry consent module replaces iubenda with an empty service registry: no third-party service, so no banner, and no analytics by default. Google Analytics is not carried over. Any later measurement is first-party and aggregate, and needs its own decision with counsel (L1, L2). The owner and counsel write the privacy notice and terms pages on kurds.global; the estate footer links them
D14 开放
Activate the learning stack: Tutor LMS on the Learn subsite, GamiPress network-activated so credits and badges span the main site (BuddyPress) and the Learn subsite
建议 Activate Tutor LMS on /learn/ only and GamiPress network-wide. Do not install the separate GamiPress BuddyPress or Tutor add-ons: GamiPress 8 bundles both, and the separate BuddyPress add-on stops the site with a fatal error (tested). Then import the course and credential drafts from Tools > Site Kit
D15 已决定 2026-10-22
Network hues for the page design (version 3, Nexus Foundry public grammar)
建议 Adopt sun to meadow to valley water (#f2c14e, #3fa36b, #1f7a8a) as a three-hue gradient used only as 1 to 2 px rules and chart marks, never as fills, backgrounds or text colour. Coordinate with the nexus-wp estate code for this site (OD-61 leaves the hues open)
记录 Owner, 2026-10-22: approved the D15 hues. Superseded by D28 (2026-10-23): both networks follow the Nexus Standards colour system.
D16 开放
Country flags on pages
建议 Show the state flag only for diaspora host countries. Show no flag for the homeland states (Iran, Iraq, Syria, Turkiye), because the flag of a homeland state is political for this community, nor where the state flag is contested or has changed (currently Afghanistan, Iran, Syria). Those rows carry a neutral mark. Flags come from flag-icons (MIT), self-hosted; the name is always written beside the flag
D17 开放
Academy structure: faculties that group the disciplines (schools) of the Learn site
建议 Adopt four faculties (Kurdish Languages; History, Memory and Humanities; Diaspora, Society and Research; Land, Livelihoods and Wellbeing), each with its disciplines, courses and a faculty model on its page. The faculties are a curriculum grouping, not organs of the charter; disciplines keep their existing names and pages
L1 开放
GDPR and UK GDPR lawful basis for data revealing ethnic origin, political opinion or religion (Art. 9); DPIA
建议 Explicit consent and the not-for-profit body basis; DPIA before launch
L2 开放
Canadian privacy law (PIPEDA, Quebec Law 25) for the lead entity
建议 Counsel to confirm
L3 开放
Sanctions: services to users in sanctioned states (US OFAC Iran GL D-2, Canadian SEMA, Syria measures)
建议 Free educational content within counsel’s limits; screen any paid transaction
L4 开放
Proscription laws and moderation of support for proscribed organisations
建议 Country-specific moderation rules from counsel; lawful cultural and political expression protected
L5 开放
Internet and anti-terror laws in the homeland states for users there
建议 Counsel to advise per state before member features
L6 开放
Copyright for heritage, oral history, music and film; linking instead of republishing reference works
建议 Link out; license or commission everything shown
L7 开放
Child safeguarding for youth programmes and language schools
建议 Safeguarding policy per country before any youth programme
L8 开放
Job-board liability and regulation of immigration advice
建议 Information and referral only; vetted partners give advice
R1 已决定 2026-10-23
Licence for this repository’s code and content
建议 Code under an open-source licence; original content under CC BY-SA 4.0; third-party material under its own terms (owner decides)
记录 Owner, 2026-10-23: content (courses, materials, pages, translations, data the network creates) under CC BY 4.0; code under MIT.
R2 开放
Repository visibility
建议 Private until the safety review (IR/KU-WP-07) is complete
D18 开放
Main-site languages and the language register
建议 Build the main site in Kurmanji, Sorani, Arabic, Persian, Turkish and Azerbaijani and a main language of each G20 member state (German, Spanish, French, Hindi, Indonesian, Italian, Japanese, Korean, Portuguese, Russian, Chinese). Every translation stays an AI draft marked for native review until a native reviewer sets it reviewed. Zazaki, Southern Kurdish, Gorani and Hawrami, Laki, and Kurmanji in the Arabic-based and Cyrillic scripts get a page in the language register now and an interface only from native translators, never from machine translation
D19 已决定 2026-10-23
Publishing translations of the area sites and courses
建议 Area sites and courses go live in each language as AI drafts, labelled on every page as a translation under native review, as the main sites do. Low-resource languages get human translation only
记录 Owner, 2026-10-23: labelled AI drafts are published; native review follows.
D20 已决定 2026-10-23
Where translators and reviewers work
建议 Weblate (open source), connected to the repository, with a glossary of charter terms and review states per string
记录 Owner, 2026-10-23: Weblate. Hosting (self-hosted or Weblate’s hosted plan) to be chosen.
D21 已决定 2026-10-23
Courses in each language in Tutor LMS
建议 One draft course per language, imported by the Site Kit and linked through the language switcher; no multilingual plugin
记录 Owner, 2026-10-23: one course per language.
D22 已决定 2026-10-23
Map tiles for the interactive OpenStreetMap maps
建议 Self-hosted OSM tiles (Protomaps PMTiles) on the network’s own host, so pages make no third-party request
记录 Owner, 2026-10-23: OpenFreeMap tiles, styles, fonts and sprites (tiles.openfreemap.org). A scoped exception to rule 6: map pages request map tiles from OpenFreeMap, which sees the reader’s IP address. MapLibre GL itself is self-hosted. Self-hosted tiles remain the alternative.
D23 已决定 2026-10-23
Credit and records for every contribution (courses, materials, translations, datasets)
建议 The organisation is the author of record. Contributors who opt in are named with ORCID and CRediT role; only public credit data is kept, never contact details
记录 Owner, 2026-10-23: organisation plus consenting contributors with ORCID and CRediT roles.
D24 已决定 2026-10-23
Zenodo records and DOIs
建议 End-to-end editorial flow by the platform team: metadata drafted in the repositories, draft deposits on Zenodo, drafts shown to the owner; nothing is published and no DOI is minted before the owner approves the rendered drafts
记录 Owner, 2026-10-23: the team runs the whole editorial flow on the sites and on Zenodo and shows the owner drafts before publishing.
D25 开放
Zenodo set-up: open owner actions
建议 The owner creates the Zenodo account and the community (sandbox first) from .zenodo-preview/community-<network>.json, sets ZENODO_SANDBOX_TOKEN and ZENODO_TOKEN in the environment, reviews the drafts and publishes each one in the Zenodo web interface. For code releases, one route only: the release:code draft (recommended, as it is reviewed first) or the Zenodo GitHub integration with .zenodo.json, which publishes each GitHub release at once. Translations stay files of the course record, linked to each translated page; separate records per language are not proposed.
D27 已决定 2026-10-23
Service subsites and the Academy structure
建议 Eight service subsites on each network: civic, learn, language, opportunities, research, development, heritage, news. Community becomes Development (economic and social development); resilience folds into Development; colleges or standards become the Academy’s communities of practice. The Academy holds a full structure of faculties, departments, disciplines and fields based on OECD FORD 2015 and ISCED-F 2013, open to contributors from every background, and never presents itself as a university.
记录 Owner, 2026-10-23: renamed the IDCDC subsites to these eight (community to development) and asked for the same on KCO, with a full academic structure on the Academy subsite and courses cross-linked across the platform.
D28 已决定 2026-10-23
Colour system of both networks (supersedes the D15 network hues)
建议 Follow the Nexus Standards colour system exactly: a black and white shell; the red to yellow Standards gradient (#ff0044, #ff5a2a, #ffa100 on light; #ff4d6d, #ff8a4c, #ffc233 on dark) as the network mark; one pastel-gradient inner-page hue for each of the 8 service subsites from the same family; hues only as 1 to 2 px rules, underlines, bars, chart marks and large key figures, never as fills behind text.
记录 Owner, 2026-10-23: both networks follow the Nexus Standards colour system. D15 is superseded.
D29 已决定 2026-10-23
How the platform protects members from surveillance and exposure
建议 Private by default, public by the member’s choice: random public handles instead of login names; per-member profile visibility (everyone, signed-in members, only me; default signed-in members) applied to every list, stream and API; no presence display, no Gravatar, no upload metadata, no stored IP addresses, no account-revealing sign-in messages, XML-RPC off. Existing accounts get handles only when the owner runs the migration.
记录 Owner, 2026-10-23: members must be protected because of diaspora sensitivities, with the best and most robust approach. Public profiles and portfolios stay possible by the member’s choice. The default profile level and the handle migration of existing accounts are owner settings.
D30 已决定 2026-10-23
How communities are organised across the network
建议 BuddyPress activated site by site. Each country site is a community of its own: its own BuddyPress data (activity, groups, profile fields, friends, messages, notifications), its own member lists and its own rules (joining open to every member by default, or by approval or invitation; member directory; default profile visibility; components), set per site with network defaults. A member, once registered and approved, belongs to every site; administrators limit a member’s access to any community, and see and manage every community. The main site and the service subsites stay network-wide. Access control in the Site Kit is interim: the Nexus Community plugin takes it over.
记录 Owner, 2026-10-23: BuddyPress is activated site by site, not network-wide, on every subsite including the countries, because primary communities are built inside each country’s administrative boundaries with separate rules, needs and relations; contextualisation and granular control per country, city and community. The rules of each community are owner settings. Owner, same day: a member, once in, has access to all communities and subsites unless an administrator limits it; administrators have full access and control; access control will come from the Nexus Community plugin being finalised, so the kit’s version is interim and aligned with it.
D31 已决定 2026-10-23
Community sharing (events, jobs, opportunities, listings, news tips through nexus-forms): open owner choices
建议 1. Publish the sharing forms per site only after review: wp pf-kit contributions –import makes drafts on each country site and service subsite; the owner publishes each form, which switches its public listing on. 2. Stewards per country community (D30) get the nexus-forms capabilities nexus_forms_view_entries and nexus_forms_manage on their site only; their entries list is the community’s moderation queue, and publishing an entry to the listing is the verified step. 3. Retention: the forms keep entries for 3650 days (the most nexus-forms allows) so that withdrawn records and their reasons are kept, against the nexus-forms default of 365 days (its open decision P8); a member’s erasure request is still honoured, and the withdrawal log then keeps only the reason. 4. Verification by bridging uses agreement across community sites, not Community Notes’ viewpoint model, because inferring members’ viewpoints from their ratings would be profiling of political opinion; the matrix-factorisation model stays out unless counsel and the owner choose it. 5. The ranking and limit parameters in content/contributions/contributions.json (weights 1, 0.5, 0.25; a burst of 5 low-trust votes within an hour held; 5 records a day, 1 for a new account, 20 a week). 6. Whether events of the kinds religious and remembrance may be shared at all, given the risk to people at events that states watch; recommended: yes, only when the organiser announced them in public, with a steward’s check.
记录 Owner, 2026-10-23, delegated to the agent: "confirm and decide as expert in context, choose best and latest and most powerful UN based and legally safe and technically robust on open standards and codes and data". Chosen: sealed entries are kept 1,095 days after a record is withdrawn or expires (data minimisation), while the public card stays as a link; stewards hold rights on their own community site only; a record is verified without a steward only when checks agree across at least two community sites, never by inferring viewpoints (no profiling of political opinion, GDPR Article 9); the vote weights (1, 0.5, 0.25) and limits (5 a day, 1 for a new account, 20 a week) stand; religious and remembrance events may be shared when a named public body or registered organisation holds them, described factually and checked like any record, with contested dates showing every side.
D32 已决定 2026-10-23
May the Site Kit refresh official feeds automatically, which changes published pages without a new build?
建议 Yes, under a strict rule, switched on by the owner source by source. Only sources APPROVED in feeds/sources.json with a registerRecord. Only official bodies (governments, their agencies and intergovernmental bodies). Items keep the title, date, link to the official record and, for alerts, the severity: never bodies, images or personal data. Refresh is server-side on WP-Cron, hourly; the browser never calls a source. Alerts are shown only while less than three hours old and never from a build snapshot; other items for at most seven days, then the build’s fallback returns. Feeds are off by default (Tools > Official feeds, or wp pf-kit-feeds). Feeds of heads of state and government can carry political statements, so each is checked against rule 5 before approval.
记录 Owner, 2026-10-23, delegated to the agent: "confirm and decide as expert in context, choose best and latest and most powerful UN based and legally safe and technically robust on open standards and codes and data". Chosen: the rule as recommended, and feeds of heads of state, heads of government and political parties are neither refreshed nor shown (non-partisan, rule 5); agencies only: statistics, health, alerts and weather, immigration, education, culture and international bodies. Extended 2026-10-24 for city pages: a city’s general official newsroom may be refreshed and shown; feeds of a mayor’s office, a council or elected officials are marked political, never refreshed and only linked.
D33 已决定 2026-10-23
Which standards decide countries, areas, names, subdivisions, languages and scripts
建议 UN first, then open international standards.
记录 Owner, 2026-10-23, delegated to the agent: "confirm and decide as expert in context, choose best and latest and most powerful UN based and legally safe and technically robust on open standards and codes and data". Countries and areas: UN M49 (UN Statistics Division); an entry M49 lists as its own country or area is not a subdivision of another. Names: UNTERM and UN usage, with a neutrality note where usage is contested. Subdivisions and placements: OCHA Common Operational Datasets (administrative boundaries, HDX), then UN SALB, then ISO 3166-2. Languages: ISO 639 and CLDR. Scripts: ISO 15924. Dates: the Gregorian calendar plus the community calendars, computed by rule. Every page’s sources section states these standards.
D34 已决定 2026-10-23
Fallback language when a page has no version in the reader’s language
建议 English, except where a language is a variety of a network language that its readers read.
记录 Owner, 2026-10-23, delegated to the agent: "confirm and decide as expert in context, choose best and latest and most powerful UN based and legally safe and technically robust on open standards and codes and data". Chosen: Dari (prs) falls back to Persian, then English, as CLDR treats Dari as Persian of Afghanistan. Every other language falls back to English. No Kurdish, Azerbaijani or other community language falls back to a state language: that choice would be political.
D35 已决定 2026-10-23
Official bodies of Afghanistan, Iran, Syria and Venezuela in the service directories
建议 List practical public services only, with a safety note; follow UN practice on representation.
记录 Owner, 2026-10-23, delegated to the agent: "confirm and decide as expert in context, choose best and latest and most powerful UN based and legally safe and technically robust on open standards and codes and data". Chosen: Afghanistan lists international bodies only, following the UN credentials practice. Iran, Syria and Venezuela list statistics offices and civil-registration or consular services only, each marked ‘listed for practical services; listing is not endorsement’ with a link to protected participation. No political, security or party bodies are listed. Linking is not a transaction under the sanctions reviewed in D26.
D36 已决定 2026-10-23
Licence decisions for outside sources
建议 Approve only sources with an explicit open licence, for the uses their entry states; keep every other source under review.
记录 Owner, 2026-10-23, delegated to the agent: "confirm and decide as expert in context, choose best and latest and most powerful UN based and legally safe and technically robust on open standards and codes and data". Chosen: APPROVED for the stated use (titles, dates and links of items; codes and names; open layers as credited) are sources under an explicit open licence: Open Government Licence v3.0, US public domain (17 U.S.C. 105), Licence Ouverte / Etalab 2.0, CC BY 4.0, CC BY 3.0 IGO, CC0, Statistics Canada Open Licence, Datenlizenz Deutschland Namensnennung 2.0, and geoBoundaries gbOpen datasets without share-alike. Excluded: any source marked ‘to verify’, share-alike datasets, and political feeds (D32). Each approval names this decision in its registerRecord. Rule 6 of CLAUDE.md is amended so that an agent sets APPROVED only on the owner’s written instruction, quoted in the registerRecord.
D37 已决定 2026-10-23
One header on built pages
建议 The platform header carries the navigation; the theme header keeps the logo and the account.
记录 Owner, 2026-10-23, delegated to the agent: "confirm and decide as expert in context, choose best and latest and most powerful UN based and legally safe and technically robust on open standards and codes and data". Chosen: on built pages the BuddyX Pro header keeps the logo, search and account (sign-in and registration work through it) and hides its menu links; the platform header (mega menu, language switcher) is the navigation. Theme pages (BuddyPress, Tutor, /login/) keep the theme menu, which follows the language choice.
D38 已决定 2026-10-23
Organisation names in languages the charter does not name
建议 Keep the official name as written; never invent a translation.
记录 Owner, 2026-10-23, delegated to the agent: "confirm and decide as expert in context, choose best and latest and most powerful UN based and legally safe and technically robust on open standards and codes and data". Chosen: where the charter gives a name in a language, pages use it; elsewhere the official name stays as written, marked with its language and direction, and the owner adds charter names over time.
D39 已决定 2026-10-23
Language platform: data licences, endangerment sources and media listings
建议 Attributed permissive data stays; share-alike data waits for review; UN sources first; no sanctioned media.
记录 Owner, 2026-10-23, delegated to the agent: "confirm and decide as expert in context, choose best and latest and most powerful UN based and legally safe and technically robust on open standards and codes and data". Chosen: Glottolog (CC BY 4.0) and Unicode CLDR and UCD (Unicode licence) stay on pages with attribution; PHOIBLE inventories (CC BY-SA 3.0) and Wikimedia Commons audio show only after their register entries are approved. Endangerment shows UNESCO first (the UN source, marked to verify until the Atlas is read) beside Glottolog, with both sources. Media under UN, EU or US sanctions are not listed (IRIB is under EU and US sanctions); other public and international broadcasters are listed with a note that listing is not endorsement.
D40 已决定 2026-10-24
Places: units without a code, and the spelling of place names
建议 Show only units with an ISO 3166-2 code or a UN OCHA COD-AB entry. Spell place names by the UN geographical names standards (UNGEGN) and the official national form.
记录 Owner, 2026-10-23, delegated to the agent: "confirm and decide as expert in context, choose best and latest and most powerful UN based and legally safe and technically robust on open standards and codes and data". Chosen: a unit with no ISO 3166-2 code and no UN list entry stays off the pages; Georgia’s "Provisional Administration" unit is held, as the most neutral choice. Place names follow UNGEGN and the official national spelling with its own letters (for example Diyarbakır, not Diyarbakir); the translation phase applies this.
D41 开放
Adoption of the editorial, conduct and safety texts (/institution/: editorial standard, sources and labels, fact-checking, corrections, translation and AI, neutrality, conflicts of interest, code of conduct, community guidelines, safeguarding), and confirmation of the charter text they rest on (the charter page returned not found on 2026-10-24)
建议 The owner restores the charter page or supplies its text; the Council proposes the texts and the General Assembly adopts them through the Work Program. Until then the pages say proposed.
D42 开放
Conflicts of interest: what is declared, the gift and hospitality threshold, the declaration form, and where declarations are kept and published. Chapters keep an integrity lead for neutrality and conflicts of interest, but the rules are not yet set
建议 Declare financial, personal, institutional and political interests and any gift or hospitality from a party to a decision; a low value threshold per country; declarations kept by the Chapter integrity lead and escalated to KCO integrity bodies; a summary without personal details published where safe.
D43 开放
A confidential channel to the safety team, separate from the general contact form
建议 A dedicated, end-to-end encrypted reporting route with an address the owner publishes, staffed by people the Council names; until then reports go through the contact page.
D44 已决定 2026-10-29
May the platform sell courses or monetise learning, knowledge or content?
建议 No. An open academy and open knowledge, free to every learner, under open licences and published standards.
记录 Owner, 2026-10-29, in writing: "no selling courses or monetizations at any form we are publishing hardcore open academy and open knowledge and open source in all areas but powerfuly and legally and standardized". The Site Kit keeps Tutor LMS monetisation disabled on every site (includes/tutor.php).
D45 已决定 2026-10-30
May the non-profit networks reuse code from the ellipi repository (the commercial Nexus Observatory, observatory.global), including its 3D scene engines?
建议 Yes, under a written grant from the owner of both, with provenance recorded on every copied file.
记录 Owner, 2026-10-30, in writing: "yes i grant licence to reuse ellipi code". Scope: code in saeedvaladbaygi/ellipi (for example packages/scenes/obs-*.js on branch claude/zealous-volta-lb8w8o), reused and adapted in this repository. Each copied file keeps a header naming its source repository, branch, commit and path, and the grant (D45). Assets, data, device or provider registers and third-party material inside ellipi keep their own licences and are reused only where those allow it. three.js stays self-hosted; no CDN.
D46 已决定 2026-10-30
Which visual design does the platform use, and how are design changes made?
建议 The greenfield design kit in design/kit/, approved by the owner. Visuals are black, white and red only, as realistic 3D renders. Design work follows kit first, owner approval, then application everywhere.
记录 Owner, 2026-10-30, in writing: "approved for now but those hero visuals and geometric shapes and overal visals need replacements in black/white/red only and in super realistic 3d model. go witththe kit and build it fully". Earlier, in writing: "WHY YOU ARE NOT BUILDING A DESIGN KIT FIRST GET APPROVAL AND THEN APPLY ALL OVER SO WE DONT WASTE CREDITS AND EXPERIMENTS". The header keeps icons with translated hover tooltips and little text; pages are trimmed, not essays. The kit replaces the earlier layout and its visual tokens. The hero visuals and geometric shapes in the kit are placeholders until the black, white and red 3D renders replace them.
D47 已决定 2026-10-30
How are heritage stories built?
建议 Each chapter is a full immersive story of 6 to 12 scenes with Play chapter and Play whole story, narration-ready, built from a reusable library of models, camera paths, templates and period kits, with every scene sourced to academic and museum references.
记录 Owner, 2026-10-30, in writing: "our stories are substantial with so many scenes and details so make one full story for each chapter so users can go throuh each or play full chapter to see all in actions"; "build scenes and stories and designs so we can reuse them in similar period and stories and al forfuture work so they can be reused by future agents and humans in our libraries"; "design your best based on actual and factual and imageries and all you have from all academic and meuseums and all sources so they get as close to realities as we can get". The layout follows the scroll explainers of the Nexus Observatory (D45 grant). The first story is Cyrus the Great and Babylon, 539 BCE. Voice narration connects later; no voice service is added without a feeds/ register record.
D48 已决定 2026-10-30
Where do the platform’s WordPress plugins and themes come from until BuddyX Pro is replaced?
建议 From the estate branch claude/serene-rubin-6zyvft in saeedvaladbaygi/nexus-wp, always the latest, localised for this network through wordpress/manager/estate-sync.mjs. Visual changes install only after owner approval.
记录 Owner, 2026-10-30, in writing: "you must always fetch latest from latest plugins and themes upgraded and fixes since they all use buddyxpro as parent theme and using its properties to power our native themes for now until we completly replace buddyxpro. claude/serene-rubin-6zyvft". The estate’s single platform plugin is localised for this network once it is complete. Addendum, 2026-10-30. The source branch is now claude/zealous-cerf-aahjqh (wordpress/manager/estate.json). Owner, in writing: "fetch latest plugin and theme codes form claude/zealous-cerf-aahjqh and all other PRs and update yours. you still dont have any of those plugins and the features and all for governance, gamipress, tutor and all for all community pages including accounts and all". And: "we need ALL plugins and features built for nexus including knowledge base and all others for our sites. fetch codes and contextualize and localize FAST and ship all." Vendored at ba79b90d1 (wordpress/estate/vendor.json). Where a plugin overlaps the Site Kit, its overlapping part is off (wordpress/plugin/includes/estate.php).
D50 开放
Adopt the estate stack for KCO: the estate child theme (buddyxpro-child, with this network’s layer) and the estate plugins nexus-forms, nexus-community, nexus-dashboard, nexus-app, nexus-consent, nexus-accessibility, nexus-suite, nexus-governance and nexus-transition, installed over REST by the site manager in the order of docs/site/ESTATE.md. With it: when to move recognition from GamiPress to nexus-recognition, whether to bring in nexus-access and nexus-passport (held), and the outbound licence of the estate plugins, which declare LicenseRef-Nexus-Proprietary.
建议 Adopt the stack on staging first, site by site, after the owner reviews the screenshot sheet. Keep the Site Kit as owner of member protection (D29), sign-in at /login/, the language contract and the network chrome (D37); the estate plugins take the member screens, dashboard, app, forms, consent records, accessibility tools and charter bodies. Keep GamiPress until the nexus-recognition importer has run on a staging copy and the counts match; keep nexus-access and nexus-passport held. Confirm the licence under which the estate plugins may sit in this private repository.
D51 已决定 2026-10-30
Sanctions screening of sign-in and registration: which countries and regions are blocked? The owner’s instruction of 2026-10-30 asks for "automatic blocking from countries sanctioned under UN/US/Canada/EU". Iran is under comprehensive United States measures and sectoral Canadian and European Union measures, and Kurds in Iran take part in this network; Syria matters to this network, and its United States programme was revoked in 2025. Options: (a) block every place under comprehensive measures, Iran included; (b) block the comprehensively sanctioned places but keep Iran open for free participation, relying on the United States authorisation of personal communication services (former General License D-2), subject to counsel; (c) block nothing until counsel reviews. Syria: keep open, or block.
建议 Option (b), with Syria open. Block North Korea, Cuba, Crimea, Sevastopol and the occupied areas of Donetsk and Luhansk by default; every jurisdiction stays switchable in Network Admin > Sign-in. Counsel confirms the list and the Iran position before launch.
记录 Owner, 2026-10-30, in writing: "you must use /login and /register for account dropdowns and everywhere as wordpress urls is blocked by deflect so you must create most professional login and register pages with most enterprise looking and all needed for login and register pages with automatic blocking from countries sanctioned under UN/US/Canada/EU and all we need for most secure and robust login and register and experience". Owner answers of the same day (question dialog): Iran: "Allow Iran (Recommended)", that is, block the other comprehensively sanctioned places (for example North Korea, Cuba, the occupied regions of Ukraine) and keep Iran open for free participation; counsel confirms later. Syria: "Allow Syria (Recommended)", keep Syria open while its current status is verified from official sources. Decided for Iran and Syria. Still open: source verification of the remaining list (labels in content/network/sanctions.json) and counsel review.
D52 已决定 2026-10-30
Where the visitor is: may the platform read the visitor’s country from the edge (Deflect) and from a local IP-to-country database, and the member’s own place from their profile, so the maps and the place spine centre on the visitor instead of a default country? Nothing is stored; only the member sees their own values.
建议 Yes: read the edge country header when present, else the DB-IP country file (CC BY 4.0, feeds register dbip-country-lite), else the browser’s time zone and language in the page; a member’s profile country and city first. Print only a country code as page data; keep no log of it.
记录 Owner, 2026-10-30, in writing: "i decide and approve using all deflect and all you can get to get precise locations and all we need". The feeds register entry dbip-country-lite is set APPROVED on this instruction (D36).
D53 已决定 2026-10-30
Which of the sources proposed for the service areas on 2026-10-30 (jobs, scholarships, grants, courses, collections, corpora, rights bodies, development data, news) may be read and shown?
建议 Those whose stated licence allows non-profit reuse with attribution: open licences (CC0, CC BY, CC BY-NC-SA, Open Government Licence, the European Commission reuse policy, public domain works of governments), open data programmes and non-commercial API terms. Sources whose terms could not be read stay in legal review; keyed sources need their key in the environment.
记录 Owner, 2026-10-30, in writing: "our projects and pages are all non profits, sources and licenses that allow should be used and codes can be shared from repos all those we created". Applied by the agent to the register entries whose licence text allows it; each entry quotes the instruction (D36).
D54 已决定 2026-10-31
May the Site Kit resolve a visitor’s city and coordinates from the IP address, so that pages open on the visitor’s own city rather than a time-zone or hub city?
建议 Yes, with DB-IP City Lite (CC BY 4.0) read server-side inside the Site Kit, Deflect edge headers taking precedence where they carry a city, and the member’s account place above both. The packed file travels in the plugin package, never in the repository; no IP is logged or stored; the attribution "IP Geolocation by DB-IP" appears on the privacy page.
记录 Owner, 2026-10-31, in writing, after the agent set out the options (DB-IP City Lite, edge headers): "implement and use if its open source and works with deflect and our stack and its best options". Earlier the same day: "i decide and approve using all deflect and all you can get to get precise locations and all we need" (D52). Recorded by the agent.
D55 开放
Move kurds.global to the nexus-wp native stack (OD-54): the nexus-estate theme with the nexus-site-core and nexus-foundry plugins, in place of BuddyX Pro, Youzify, New User Approve, MinervaKB, GamiPress, iubenda and Google Analytics, site by site
建议 Proposed. Staging copy first. Then the master site, Learn, the other areas and the country subsites, one at a time, each after the owner approves its rendered pages. Turn on admission in the community module before New User Approve goes. Keep BuddyPress and Tutor LMS. Keep the vendor plugins installed and inactive until each migration is verified. Order and steps: docs/site/NATIVE_STACK.md
D56 开放
Recognition on the native stack: serve the recognition framework (content/network/credentials.json) with the nexus-foundry recognition module instead of GamiPress, when kurds.global moves to the native stack (nexus-wp OD-54)
建议 Proposed, after D12 and D14. Keep GamiPress while the site runs the current stack. On the native stack, load dist/lms/nexus-recognition.json as drafts (wp pf-kit nexus-recognition, then wp nxf recognition definitions –dry-run). Foundry holds awards and credentials, and they reach only accounts the member links to Foundry (OD-60b). Learning credits stay counts with no money value. Decide whether to keep the two participation badges that have no native trigger (account activated, profile ready) as manual awards or to drop them
D57 已决定 2026-11-01
Flag sources for countries, regions and cities: flag-icons (MIT), Wikidata flag statements (CC0) and Wikimedia Commons flag files (each file under its own licence, recorded in feeds/flags/manifest.json)
建议 Approve the three register entries flag-icons, wikidata-flags and commons-flags; keep the flags held for disputed places out until the owner reviews them; show the neutral mark where no approved file exists.
记录 Owner, 2026-11-01, in writing: "approve flag sources flag-icons, wikidata and commons". Approved on that instruction; recorded by the agent under D36; decision D57.
D58 开放
Autopilot jobs: may the droplet’s cron run the eight Site Kit jobs (`wp pf-kit feeds-refresh`, `data-chunks`, `expire`, `prune`, `digest`, `links`, `queue-sort`, `p2p-match`) on the schedules in docs/site/OPERATIONS.md, and with which thresholds?
建议 Proposed. Yes: system cron calls WP-CLI on the main site URL, each job is idempotent, locked, logged and safe to rerun, and uses only sources APPROVED with a register record (D36, D53). Proposed thresholds, all changeable through the filter pf_kit_ops_config: feed items leave a slot after 60 days, a source is not refetched within 50 minutes, the run log keeps 300 lines or 90 days, 40 items per place or hub chunk. The owner confirms the schedules and the thresholds, and confirms how the pull deployer calls `wp pf-kit deploy-stamp` (the hosting note on the droplet was not available to the agent that wrote this)
D59 开放
Moderation queues: what must a steward approve, and how long are queue records kept?
建议 Proposed. Contributions, listings, Community Cell requests, reports and offers of help enter one queue per site, so each community’s stewards (D30) see only their own. Automatic checks (source present, licence known, duplicate, spam signals, personal data) only sort the list into lanes. Nothing reaches a public page without a steward’s approval; an item with personal data, an unsafe source or no source cannot be approved, and a flagged item needs an override with a note. Nobody acts on what they shared. Every action is kept in an append-only audit trail. A record withdrawn for 1,095 days (D31) is reduced to a tombstone (kind, reason, dates, audit); a resolved report or request loses its reporter reference after 365 days. The queue serves public listings only when the owner sets the option pf_kit_queue_publish (off by default). Stewards need the capability pf_moderate_queue, or nexus_forms_manage
D60 开放
Peer to peer help (mentoring, language exchange, newcomer help, skills): which consent steps, limits and reputation rules?
建议 Proposed. Five steps, each the member’s own consent: list an offer (nothing is listed without the box ticked; a private profile cannot be listed; new or limited accounts wait for a steward), ask one suggested offer (shows the asker’s random handle to that helper only), the helper accepts, declines or blocks, the asker confirms, and both mark it done. Messages open only after both agree and carry no contact details; notes with email, phone, links or ads are refused. Limits: 3 offers, 5 open requests, 3 asks a day, 10 pending asks, a 30-day pause after a decline. Reputation is a band (new, active at 1 completed exchange, trusted at 5 with an account over 30 days), never a score or a list, counted only when both sides mark an exchange done, with a pair cap (2 in 90 days), a daily cap (3), and an account age of 7 days. Points reach GamiPress only when the owner names a points type with no money value (option pf_kit_help_points_type); the owner chooses the type and whether it belongs in the recognition framework (D12, D56)
D61 开放
Digest notifications: what may a member opt in to?
建议 Proposed. Off by default. A member chooses daily or weekly. The plain-text mail holds counts of help requests waiting, public records stewards verified in the member’s community, and upcoming official events from the stored place chunk; never a name, a request or a message. One mail per member and period, none when there is nothing to say, a signed one-click unsubscribe link and List-Unsubscribe headers, and logs that hold counts only. Mail is sent with wp_mail, so the owner sets the sender and the mail service
D62 开放
Link checks: how politely, and when is a link broken?
建议 Proposed. Weekly, 100 links a run (never checked first, then the oldest), HEAD first and GET only when the server refuses HEAD, one request a second to a host, https and http only, through wp_safe_remote_*, with a user agent that names the site. A link is broken after two failed checks, or at once on 410. A broken source flags its queue item and never changes its state; a steward decides. Results are forgotten after 120 days without a check
D63 开放
Status endpoint for the hosting monitor: how is it authenticated, and what does it show?
建议 Proposed. GET /wp-json/pf-kit/v1/status, for a network administrator’s application password over https, or a bearer token held only in the environment variable PF_KIT_STATUS_TOKEN (never in a file, an option or a log). It shows counts, ages and source ids only: job health, feed health, queue sizes, help counts, link health, pages per site and language, the last deploy. No member data and no queue content. ?strict=1 answers 503 when a job is failing or overdue. The owner or the host sets the token and the monitor
D64 已决定 2026-11-01
Support for the organisation: may it accept donations?
建议 No. The organisation accepts no donations in any form (money, gifts, in kind, crowdfunding, recurring giving). Sponsorship is the only form of support. Every page, form, legal text, translation and component says so; no donate button, donation form, donor wall or giving prompt is built or shown; outside sources that describe donors as a fact about others stay as cited facts.
记录 Owner, 2026-11-01, in writing: "for all the context and legal docs and all you are building : we dont accept donations in any form. only form of support is sponsorship". Recorded by the agent; decision D64.
D65 开放
Zazaki, Southern Kurdish and Gorani: amend D18 and D19 so labelled AI drafts for native review may be built in these three languages, as for the network languages?
建议 Proposed for the owner. Today D18 and D19 say these languages get an interface only from native translators, never from machine translation. The localisation brief asks for every network language, including these three. Nothing was done: no catalogue, message file or page exists for them, and none will be made until the owner decides. If the owner amends D18, the same pipeline applies (segments and messages skeletons, validated merges, review state needs-native-review), after adding each language to locales/locales.json with a fallback chain in content/site/languages.json (Kurmanji or Sorani, as the owner chooses). For: one rule for every language, and readers get something in their language now. Against: machine translation is weakest for these three languages, on a subject where a wrong word can be read as taking a side, and D18 was a deliberate protection. Native reviewers would still approve every page before it counts as reviewed
D66 开放
The Work programme (34 pages), the Decisions register and the Story library exist only in English. Translate them, or keep them in English and label the links to them as English?
建议 Proposed for the owner. They are planning and governance documents, not among the page types the localisation brief lists (main site, service sites, country sites, region and city pages, Academy, calendar, heritage, language pages, account screens). Every network language now links to them from the About page, and those three links show the language tag of the page they land in. That is the only fallback link left in the network languages (3 per language). Translating them is about 35 more pages per language, and the decisions text changes often, so a translation would go stale. Keeping them in English with the existing language tag is the smaller change
D67 开放
Country-programme languages (Danish, Greek, Finnish, Hebrew, Armenian, Georgian, Norwegian Bokmål, Dutch, Swedish): keep them to each country’s own pages, or build the whole network in them?
建议 Proposed for the owner. Today each of these languages has the pages of its own country site (12 to 33 pages, none missing, 0 missing strings). Every one of those pages links to the shared network (main site, the other country sites, the area sites), which does not exist in these languages, so about 93 to 95 percent of their internal links land in English and carry the language tag (4,314 of 4,534 for Danish). Zero fallback links would mean building the main site, 35 country sites and 8 service sites in each of the 9 languages, about 2,000 pages and some 9,000 interface strings and 12,000 segments per language, every one an AI draft needing native review. Keeping them to the country’s own pages, with the existing fallback to English, is the smaller change and matches the brief’s wording ‘on each country’s own pages’