📖 [Docs]: Organization-wide community defaults established

.claude/CLAUDE.md

@@ -0,0 +1 @@
+@../AGENTS.md

.gitattributes

@@ -0,0 +1,11 @@
+* text=auto eol=lf
+
+*.bat text eol=crlf
+*.cmd text eol=crlf
+
+*.gif binary
+*.ico binary
+*.jpeg binary
+*.jpg binary
+*.pdf binary
+*.png binary

.github/CODEOWNERS

@@ -0,0 +1 @@
+* @MariusStorhaug

.github/CODE_OF_CONDUCT.md

@@ -0,0 +1,83 @@
+# Contributor Covenant 3.0 Code of Conduct
+
+## Our Pledge
+
+We pledge to make our community welcoming, safe, and equitable for all.
+
+We are committed to fostering an environment that respects and promotes the dignity, rights, and contributions of all individuals, regardless of characteristics including race, ethnicity, caste, color, age, physical characteristics, neurodiversity, disability, sex or gender, gender identity or expression, sexual orientation, language, philosophy or religion, national or social origin, socio-economic position, level of education, or other status. The same privileges of participation are extended to everyone who participates in good faith and in accordance with this Covenant.
+
+## Encouraged Behaviors
+
+While acknowledging differences in social norms, we all strive to meet our community's expectations for positive behavior. We also understand that our words and actions may be interpreted differently than we intend based on culture, background, or native language.
+
+With these considerations in mind, we agree to behave mindfully toward each other and act in ways that center our shared values, including:
+
+1. Respecting the **purpose of our community**, our activities, and our ways of gathering.
+2. Engaging **kindly and honestly** with others.
+3. Respecting **different viewpoints** and experiences.
+4. **Taking responsibility** for our actions and contributions.
+5. Gracefully giving and accepting **constructive feedback**.
+6. Committing to **repairing harm** when it occurs.
+7. Behaving in other ways that promote and sustain the **well-being of our community**.
+
+## Restricted Behaviors
+
+We agree to restrict the following behaviors in our community. Instances, threats, and promotion of these behaviors are violations of this Code of Conduct.
+
+1. **Harassment.** Violating explicitly expressed boundaries or engaging in unnecessary personal attention after any clear request to stop.
+2. **Character attacks.** Making insulting, demeaning, or pejorative comments directed at a community member or group of people.
+3. **Stereotyping or discrimination.** Characterizing anyone’s personality or behavior on the basis of immutable identities or traits.
+4. **Sexualization.** Behaving in a way that would generally be considered inappropriately intimate in the context or purpose of the community.
+5. **Violating confidentiality**. Sharing or acting on someone's personal or private information without their permission.
+6. **Endangerment.** Causing, encouraging, or threatening violence or other harm toward any person or group.
+7. Behaving in other ways that **threaten the well-being** of our community.
+
+### Other Restrictions
+
+1. **Misleading identity.** Impersonating someone else for any reason, or pretending to be someone else to evade enforcement actions.
+2. **Failing to credit sources.** Not properly crediting the sources of content you contribute.
+3. **Promotional materials**. Sharing marketing or other commercial content in a way that is outside the norms of the community.
+4. **Irresponsible communication.** Failing to responsibly present content which includes, links or describes any other restricted behaviors.
+
+## Reporting an Issue
+
+Tensions can occur between community members even when they are trying their best to collaborate. Not every conflict represents a code of conduct violation, and this Code of Conduct reinforces encouraged behaviors and norms that can help avoid conflicts and minimize harm.
+
+When an incident does occur, it is important to report it promptly. To report a possible violation, email [support@msx.no](mailto:support@msx.no).
+
+Community Moderators take reports of violations seriously and will make every effort to respond in a timely manner. They will investigate all reports of code of conduct violations, reviewing messages, logs, and recordings, or interviewing witnesses and other participants. Community Moderators will keep investigation and enforcement actions as transparent as possible while prioritizing safety and confidentiality. In order to honor these values, enforcement actions are carried out in private with the involved parties, but communicating to the whole community may be part of a mutually agreed upon resolution.
+
+## Addressing and Repairing Harm
+
+If an investigation by the Community Moderators finds that this Code of Conduct has been violated, the following enforcement ladder may be used to determine how best to repair harm, based on the incident's impact on the individuals involved and the community as a whole. Depending on the severity of a violation, lower rungs on the ladder may be skipped.
+
+1) Warning
+   1) Event: A violation involving a single incident or series of incidents.
+   2) Consequence: A private, written warning from the Community Moderators.
+   3) Repair: Examples of repair include a private written apology, acknowledgement of responsibility, and seeking clarification on expectations.
+2) Temporarily Limited Activities
+   1) Event: A repeated incidence of a violation that previously resulted in a warning, or the first incidence of a more serious violation.
+   2) Consequence: A private, written warning with a time-limited cooldown period designed to underscore the seriousness of the situation and give the community members involved time to process the incident. The cooldown period may be limited to particular communication channels or interactions with particular community members.
+   3) Repair: Examples of repair may include making an apology, using the cooldown period to reflect on actions and impact, and being thoughtful about re-entering community spaces after the period is over.
+3) Temporary Suspension
+   1) Event: A pattern of repeated violation which the Community Moderators have tried to address with warnings, or a single serious violation.
+   2) Consequence: A private written warning with conditions for return from suspension. In general, temporary suspensions give the person being suspended time to reflect upon their behavior and possible corrective actions.
+   3) Repair: Examples of repair include respecting the spirit of the suspension, meeting the specified conditions for return, and being thoughtful about how to reintegrate with the community when the suspension is lifted.
+4) Permanent Ban
+   1) Event: A pattern of repeated code of conduct violations that other steps on the ladder have failed to resolve, or a violation so serious that the Community Moderators determine there is no way to keep the community safe with this person as a member.
+   2) Consequence: Access to all community spaces, tools, and communication channels is removed. In general, permanent bans should be rarely used, should have strong reasoning behind them, and should only be resorted to if working through other remedies has failed to change the behavior.
+   3) Repair: There is no possible repair in cases of this severity.
+
+This enforcement ladder is intended as a guideline. It does not limit the ability of Community Managers to use their discretion and judgment, in keeping with the best interests of our community.
+
+## Scope
+
+This Code of Conduct applies within all community spaces, and also applies when an individual is officially representing the community in public or other spaces. Examples of representing our community include using an official email address, posting via an official social media account, or acting as an appointed representative at an online or offline event.
+
+## Attribution
+
+This Code of Conduct is adapted from the Contributor Covenant, version 3.0, permanently available at [https://www.contributor-covenant.org/version/3/0/](https://www.contributor-covenant.org/version/3/0/).
+
+Contributor Covenant is stewarded by the Organization for Ethical Source and licensed under CC BY-SA 4.0. To view a copy of this license, visit [https://creativecommons.org/licenses/by-sa/4.0/](https://creativecommons.org/licenses/by-sa/4.0/)
+
+For answers to common questions about Contributor Covenant, see the FAQ at [https://www.contributor-covenant.org/faq](https://www.contributor-covenant.org/faq). Translations are provided at [https://www.contributor-covenant.org/translations](https://www.contributor-covenant.org/translations). Additional enforcement and community guideline resources can be found at [https://www.contributor-covenant.org/resources](https://www.contributor-covenant.org/resources). The enforcement ladder was inspired by the work of [Mozilla’s code of conduct team](https://github.com/mozilla/inclusion).

.github/CONTRIBUTING.md

@@ -0,0 +1,36 @@
+# Contributing
+
+The affected repository's README and repository-local contribution guidance
+define its build, test, and validation steps. Follow those local instructions
+before this organization-wide fallback.
+
+## Before making a change
+
+- Review the repository's open issues and use the MSX
+  [issue process](https://msx.no/docs/Ways-of-Working/Issues/) to propose or
+  claim substantial work.
+- Read the repository's code of conduct and applicable MSX standards.
+- Keep each change focused on one deliverable.
+
+## Agent plugin
+
+The [MSX agent plugin marketplace](https://github.com/MSXOrg/docs/tree/main/.github/plugin)
+provides Copilot CLI with skills that route work to current MSX standards and
+workflows.
+
+## Submit the change
+
+1. Create a short-lived branch from the repository's default branch.
+2. Make the smallest complete change and run the repository's relevant checks.
+3. Open a draft pull request and follow the MSX
+   [PR Format](https://msx.no/docs/Ways-of-Working/PR-Format/).
+4. Self-review the diff, request Copilot review explicitly, and address
+   in-scope feedback.
+5. Mark the pull request ready only after it satisfies the repository's review
+   gate.
+
+The canonical
+[Contribution Workflow](https://msx.no/docs/Ways-of-Working/Contribution-Workflow/)
+defines the complete delivery loop. Use the MSX
+[Review Etiquette](https://msx.no/docs/Ways-of-Working/Review-Etiquette/) when
+giving or responding to feedback.

.github/SECURITY.md

@@ -0,0 +1,26 @@
+# Security policy
+
+## Supported versions
+
+Security fixes target the affected repository's latest supported release or,
+for an unreleased project, its default branch. Repository-specific security
+policies define any additional supported versions and take precedence over this
+fallback.
+
+## Reporting a vulnerability
+
+Do not disclose a suspected or confirmed vulnerability through a public issue,
+pull request, discussion, or other public channel.
+
+Use the affected repository's **Security** tab to report the vulnerability
+privately when private vulnerability reporting is available. If that option is
+unavailable, email [security@msx.no](mailto:security@msx.no).
+
+Use the same private routes to report accidentally exposed sensitive
+information, exposed credentials, exposed secrets, and weak or unsafe security
+controls or configurations.
+
+Include the affected repository and version or commit, the vulnerability and
+its impact, steps to reproduce it, and any proof of concept or suggested
+mitigation. MSX handles reports privately, investigates them, and coordinates
+remediation and disclosure with the reporter.

.github/SUPPORT.md

@@ -0,0 +1,24 @@
+# Support
+
+For help with an MSX repository:
+
+1. Read that repository's README and documentation.
+2. Search its existing issues for a known answer.
+3. Open an issue in the affected repository for a public question.
+
+Include the repository and version, relevant environment details, expected and
+actual behavior, reproduction steps, and sanitized logs. Remove credentials,
+personal information, and other secrets before posting.
+
+Private support matters go to
+[support@msx.no](mailto:support@msx.no).
+
+## Sensitive reports
+
+Never report a security vulnerability through a public issue. Follow the
+[security policy](SECURITY.md) instead.
+
+Report community conduct concerns through the private route in the
+[code of conduct](CODE_OF_CONDUCT.md).
+
+To propose a change, follow the [contribution guide](CONTRIBUTING.md).

.github/copilot-instructions.md

@@ -0,0 +1 @@
+Follow the instructions in [AGENTS.md](../AGENTS.md).

.github/dependabot.yml

@@ -0,0 +1,10 @@
+---
+version: 2
+updates:
+  - package-ecosystem: github-actions
+    directory: /
+    labels:
+      - dependencies
+      - github-actions
+    schedule:
+      interval: weekly

.github/pull_request_template.md

@@ -0,0 +1,18 @@
+<!-- Lead with one concise paragraph describing the user-facing outcome. -->
+
+<!-- Add user-facing sections for breaking, new, changed, or fixed behavior when needed. -->
+
+---
+<details>
+<summary>Technical details</summary>
+
+<!-- Record the implementation approach, issue-plan progress, standards alignment, and convergence sweep. -->
+
+</details>
+
+<details>
+<summary>Relevant issues (or links)</summary>
+
+<!-- Use fully qualified repository references for closing and related work. -->
+
+</details>

.gitignore

@@ -0,0 +1,11 @@
+# Operating system files
+.DS_Store
+Thumbs.db
+
+# Editors
+.history/
+.idea/
+.vscode/
+*.code-workspace
+*.swp
+*~

AGENTS.md

@@ -0,0 +1,16 @@
+# Agent instructions
+
+Read nearest first, prefer documentation over memory, and always use the newest
+version.
+
+1. [README.md](README.md) — what this repository provides and how its defaults
+   are enforced.
+2. [.github/CONTRIBUTING.md](.github/CONTRIBUTING.md) — how a change is made
+   and reviewed.
+3. [`MSXOrg/docs`](https://github.com/MSXOrg/docs) — organization standards.
+   Start at
+   [`src/docs/index.md`](https://github.com/MSXOrg/docs/blob/main/src/docs/index.md)
+   or the [published documentation](https://msx.no/docs/). Store a local clone
+   at `~/.msxorg/docs`.
+4. `github.com/MSXOrg/memory` (private) — durable lessons from earlier work.
+   Store a local clone at `~/.msxorg/memory` and read `index.md` last.

README.md

@@ -1,2 +1,18 @@
-# .github
-Organization profile and default community health files for MSX.
+# MSX organization defaults
+
+`MSXOrg/.github` is GitHub's special public repository for organization-wide
+community health defaults. GitHub uses these files when an MSX repository does
+not define its own corresponding file. This repository must remain public for
+the fallback behavior to work.
+
+## Precedence and enforcement
+
+A repository-local community health file takes precedence over the fallback
+stored here. Repository-local files also remain the enforceable MSX surface for
+people, agents, and automation; these defaults are a convenience, not a
+replacement.
+
+See GitHub's guide to
+[default community health files](https://docs.github.com/en/communities/setting-up-your-project-for-healthy-contributions/creating-a-default-community-health-file)
+and the MSX
+[Organization Standard](https://msx.no/docs/Ways-of-Working/Organization-Standard/).