Editorial review
& cultural rights

01 · Editorial workflow

Review before release

1. DraftNot public; editorial preparation only.
2. SubmittedReceived through a future authorized, secure channel.
3. Under ReviewCompleteness, provenance, permissions and risks are checked.
4. Cultural VerificationAppropriate elders, custodians, historians or language specialists review the material.
5. ApprovedAn authorized reviewer records the decision and permitted audience.
6. PublishedOnly cleared, permitted public material appears on the website.

Rejected, disputed, withdrawn, restricted or unreviewed material must not be made publicly accessible. The editor records who reviewed the item, the review date, the decision, any dissenting account, and the exact permission and access scope. Where accounts differ, describe the sources and differences fairly rather than presenting one account as universally accepted.

02 · Recordkeeping

Provenance and verification

Before an item can be considered for publication, its controlled record should include the following fields where applicable:

• Title, description, category, language and intended audience.
• Source, provenance, creator or contributor credit, and date or place only where known and approved.
• Source type: oral account, community memory, published research, archival record, or other documented source.
• Reviewer name or authorized role, review date, verification status and supporting references.
• Consent scope, rights holder, allowed use, access restriction, retention decision and withdrawal contact route.
• For language resources: submitted term, meaning, usage example, pronunciation/audio, contributor, source and fluent-speaker verification status. No sample translations are fabricated for this site.
• For oral histories: recording and transcript permissions, approved attribution, language, translation review, and any restrictions on names, excerpts or access.

Store private contact details and consent evidence separately from public content with access limited to authorized staff. Do not expose restricted metadata, original recordings or unpublished materials through public files, search indexes or source repositories.

03 · Consent, privacy and rights

Permission is specific

• Obtain informed, recorded permission from identifiable people or rights holders before publication. Explain the intended audience, format, attribution, possible reuse and how to request correction or withdrawal.
• Permission to submit or review an item is not automatically permission to publish, translate, edit, redistribute or use it commercially.
• Respect cultural authority and community restrictions as well as individual consent. Do not publish sacred, confidential, sensitive or disputed knowledge unless authorized custodians explicitly approve its public release.
• Confirm rights to photographs, recordings, documents, music and translations. Credit contributors as they request, or omit attribution where a safe restriction is approved.
• Collect only information needed for a defined editorial purpose. Keep private contact information out of published pages and public repository files.
• Provide a secure route for correction, access restriction and removal requests. Restrict access while a credible safety, consent or cultural-rights concern is assessed.

Until a privacy contact, retention policy, consent form and secure handling process are approved, this prototype must not collect real submissions or personal information. The on-page form is a non-transmitting demonstration only.

04 · Accuracy and institutional voice

Separate evidence from position

Do not invent dates, migration routes, genealogies, names, ceremonies, translations, quotations, officeholders, partnerships, endorsements, policies or strategic commitments. Clearly identify oral accounts, documented history and current research as different source types. Cite relevant public references and note uncertainty or differing accounts.

Official statements, leadership details and the 50-year vision require confirmation by authorized cultural leadership. General educational content and proposals must not be presented as institutional policy.

05 · Technical limitations and next steps

A static site is not an archive system

GitHub Pages serves public files. Client-side forms cannot securely receive private contributions, create editor accounts, enforce access restrictions, record consent privately or support a confidential review queue. Do not put submissions, credentials, consent forms or restricted cultural materials in this public repository.

Before real contributions are invited, authorized leadership should select and approve a secure submission and content-management service; define editor roles, retention and removal procedures; set spam protection and backups; and approve privacy notices, consent wording, cultural-access rules and a response contact. Publish only approved public derivatives, not private source records.