Diff: contribute.es
From 3aa7685 to 3aa7685
+0 / −0 lines
| Before | After |
|---|---|
| --- | --- |
| schema: foundry-doc-v1 | schema: foundry-doc-v1 |
| title: "Contributing to PointSav Knowledge" | title: "Contributing to PointSav Knowledge" |
| slug: contribute | slug: contribute |
| category: governance | category: governance |
| type: governance | type: governance |
| quality: complete | quality: complete |
| short_description: "How to propose additions, corrections, and new articles for PointSav Knowledge." | short_description: "How to propose additions, corrections, and new articles for PointSav Knowledge." |
| status: active | status: active |
| bcsc_class: public-disclosure-safe | bcsc_class: public-disclosure-safe |
| last_edited: 2026-05-27 | last_edited: 2026-05-27 |
| editor: pointsav-engineering | editor: pointsav-engineering |
| --- | --- |
| PointSav Knowledge is an open-content engineering wiki. Contributions from engineers, architects, technical writers, and subject-matter experts are welcome. | PointSav Knowledge is an open-content engineering wiki. Contributions from engineers, architects, technical writers, and subject-matter experts are welcome. |
| ## Content standards | ## Content standards |
| All articles in this wiki are written to institutional standard: precise, verifiable, and free of marketing vocabulary. The writing target is a technically literate reader who is not already familiar with PointSav internals — an engineer evaluating the platform, a compliance reviewer, or a financial analyst. | All articles in this wiki are written to institutional standard: precise, verifiable, and free of marketing vocabulary. The writing target is a technically literate reader who is not already familiar with PointSav internals — an engineer evaluating the platform, a compliance reviewer, or a financial analyst. |
| Key principles: | Key principles: |
| - Claims are specific and independently falsifiable. | - Claims are specific and independently falsifiable. |
| - Forward-looking statements are marked as planned, intended, or targeted. | - Forward-looking statements are marked as planned, intended, or targeted. |
| - Third-party tools and standards are named accurately, not compared by implication. | - Third-party tools and standards are named accurately, not compared by implication. |
| - Articles describe what the platform does, not how distinctive it is. | - Articles describe what the platform does, not how distinctive it is. |
| ## What to contribute | ## What to contribute |
| **New articles** should cover one of the ten categories documented in this wiki — architecture, substrate, patterns, systems, services, applications, governance, infrastructure, reference, or design-system. Check the all-pages index and the wanted articles page (both planned — auto-generated by the wiki engine) before proposing a topic that may already exist. | **New articles** should cover one of the ten categories documented in this wiki — architecture, substrate, patterns, systems, services, applications, governance, infrastructure, reference, or design-system. Check the all-pages index and the wanted articles page (both planned — auto-generated by the wiki engine) before proposing a topic that may already exist. |
| **Corrections** to existing articles are the highest-value contributions. If a technical claim is inaccurate, out of date, or underspecified, submit a correction with the corrected text and the basis for the change. | **Corrections** to existing articles are the highest-value contributions. If a technical claim is inaccurate, out of date, or underspecified, submit a correction with the corrected text and the basis for the change. |
| **Translations** (Spanish) of existing English articles are tracked under the all-pages index (planned — auto-generated by the wiki engine). Each English article should have a paired `.es.md` sibling. | **Translations** (Spanish) of existing English articles are tracked under the all-pages index (planned — auto-generated by the wiki engine). Each English article should have a paired `.es.md` sibling. |
| ## Slug discipline | ## Slug discipline |
| Article filenames are slugs — they are permanent once published. Two rules govern naming: | Article filenames are slugs — they are permanent once published. Two rules govern naming: |
| - **No legacy prefixes.** Do not name new articles `topic-foo.md`, `guide-foo.md`, or `research-foo.md`. Free-standing concept articles use plain kebab slugs (`foo-bar.md`). Nomenclature Matrix entity-type prefixes (`os-*`, `service-*`, `app-*`, `sys-adr-*`) remain required for their entity types. | - **No legacy prefixes.** Do not name new articles `topic-foo.md`, `guide-foo.md`, or `research-foo.md`. Free-standing concept articles use plain kebab slugs (`foo-bar.md`). Nomenclature Matrix entity-type prefixes (`os-*`, `service-*`, `app-*`, `sys-adr-*`) remain required for their entity types. |
| - **Zero dead links.** Every `[[wikilink]]` in a committed article must resolve to a published article or a `status: stub` placeholder. If a target article does not yet exist, create a one-sentence stub, or remove the link. See `naming-convention.md` §5.1 for the full rule. | - **Zero dead links.** Every `[[wikilink]]` in a committed article must resolve to a published article or a `status: stub` placeholder. If a target article does not yet exist, create a one-sentence stub, or remove the link. See `naming-convention.md` §5.1 for the full rule. |
| Full naming rules: [`.agent/rules/naming-convention.md`](.agent/rules/naming-convention.md). | Full naming rules: [`.agent/rules/naming-convention.md`](.agent/rules/naming-convention.md). |
| ## How to submit | ## How to submit |
| Submit contributions as pull requests to the `pointsav/media-knowledge-documentation` repository on GitHub. | Submit contributions as pull requests to the `pointsav/media-knowledge-documentation` repository on GitHub. |
| Each pull request should include: | Each pull request should include: |
| 1. The Markdown file for the new or updated article. | 1. The Markdown file for the new or updated article. |
| 2. A brief description of what changed and why. | 2. A brief description of what changed and why. |
| 3. A Spanish translation pair (`.es.md`) if the article is new. | 3. A Spanish translation pair (`.es.md`) if the article is new. |
| **GitHub:** [github.com/pointsav](https://github.com/pointsav) | **GitHub:** [github.com/pointsav](https://github.com/pointsav) |
| ## Licensing | ## Licensing |
| By contributing to this wiki, you agree that your contribution is licensed under [Creative Commons Attribution 4.0 International (CC BY 4.0)](https://creativecommons.org/licenses/by/4.0/). | By contributing to this wiki, you agree that your contribution is licensed under [Creative Commons Attribution 4.0 International (CC BY 4.0)](https://creativecommons.org/licenses/by/4.0/). |
| ## Questions | ## Questions |
| [open.source@pointsav.com](mailto:open.source@pointsav.com) | [open.source@pointsav.com](mailto:open.source@pointsav.com) |