Skip to content

DSOM Policy Adopter Skill

Purpose: To seamlessly ingest external architectural or governance documents and integrate them into the DSOM repository strictly adhering to the Triple-Ledger Synchronization Mandate and Core Rules.

Prerequisites

  • The user has provided an absolute path to a document (e.g., PDF or Markdown).
  • If the document is a PDF, the AI should use the view_file or pdf-text-extractor tool to read the contents first.

Execution Workflow

  1. Ingest & Extract
  2. Read the provided document in its entirety.
  3. Extract the core architectural principles, rules, and actionable constraints that apply to the DSOM ecosystem.

  4. Contextual Tailoring: Actively filter and modify the extracted constraints to fit the specific architecture of the current project (e.g., mapping remote execution steps to local T1 Windows / T2 WSL2 node configurations, removing irrelevant technology references).

  5. Draft Governance Document

  6. Create a dedicated, highly-structured Markdown file in the docs/governance/ directory.
  7. Run uv run python tools/apply_okf_frontmatter.py docs/governance/ to enforce strict OKF v0.1 YAML frontmatter schema compliance (with okf_version, type: documentation, title, timestamp, topics).

  8. Format the document strictly following the Generative Engine Optimisation (GEO) standard: Authoritative tone, verifiable statistics/quotes, H2 user-centric headings, and 200-400 word chunks.

  9. Core Engine Injection (AGENTS.md)

  10. Distill the most critical, actionable constraints from the new policy.

  11. Inject these constraints directly as a new numbered Core Rule into .agents/AGENTS.md. Be extremely precise; do not bloat the file.

  12. Dual Documentation Sync & Signature

  13. Rule 13 (Signature): Run python .agents/skills/dsom-signature-injector/scripts/inject.py docs/governance/ to inject standard DSOM ownership, timestamp, and GPL v3.0 license signatures for each changed file.

  14. Rule 14 (Dual Sync): Explicitly map the new governance document into BOTH SUMMARY.md and mkdocs.yml under the appropriate category to prevent orphaned documentation.

  15. Triple-Ledger Synchronization

  16. README.md: Add a link to the new docs/governance/ file in the "Key Documents" table with a short emoji-prefixed description.
  17. CHANGELOG.md: Add an entry under ## [Unreleased] describing the new governance policy and rule addition.

  18. HISTORY.md: Append a new entry to the universal ledger detailing the architectural integration and the exact files modified.

  19. Defensive GitOps (Commit & Push)

  20. Run git pull --rebase origin main to ensure sync.
  21. Add all changed files: git add docs/governance/... .agents/AGENTS.md README.md CHANGELOG.md HISTORY.md SUMMARY.md mkdocs.yml
  22. Commit with an atomic, conventional commit message (e.g., docs(governance): adopt [Policy Name]).

  23. Push to all active remotes (e.g., GitHub and GitLab).

  24. Closure & Walkthrough

  25. Report the successful adoption to the user, highlighting the exact architectural changes made.

Deep State of Mind (DSOM) For My AI Protocol | Harisfazillah Jamel (LinuxMalaysia) | 2026-08-20 Standard: UK English | DBP-standard Bahasa Melayu Malaysia (Piawai) | GNU General Public License v3.0