Repository navigation
Description
Describe the change
Context and request
Visitors and agents need an accurate entry into MSX documentation and this repository's community defaults. Add concise, factual orientation to the public profile and correct the agent read-order description without changing its executable sequence. This delivery leaf covers one focused prose-only draft PR.
Evidence and sources
At source 0c67251812ea306543f3a14ab473ae357cfb76ac, profile/README.md:1 contains only the brand slogan. It does not identify what MSX provides or where readers find its shared standards. AGENTS.md:5 describes the root README as explaining “how its defaults are enforced,” but the root README explains GitHub fallback, documentation, and media, not an installed enforcement mechanism.
The fixed Documentation Model requires evergreen current-contract prose and distinguishes a normative contract from implementation evidence. Natural Language requires direct en-US prose and executable agent instructions. Documentation keeps context close to its subject and links canonical guidance. The pinned MSX home page and this repository's root README provide the factual source for MSX standards, ways of working, and community defaults. Apply the Writing Guide and official STEMG explanations.
Acceptance criteria
- The public profile gives concise, present-tense orientation and working canonical links to MSX documentation and relevant community-default context.
- The profile states only facts supported by the pinned MSX home page and repository evidence. It does not invent a mission, product guarantee, CI enforcement, security guarantee, or new policy.
- The brand slogan remains an accepted branding difference rather than a claimed STE-compliant technical statement. Preserve its heading/anchor unless a verified need requires a change.
AGENTS.mdretains the exact README-then-CONTRIBUTING read order and working paths. Its descriptions match the actual documents and do not claim installed enforcement..claude/CLAUDE.mdand.github/copilot-instructions.mdretain their existing thin-pointer syntax. The root README and CONTRIBUTING remain with the existing PR authors use canonical guidance without repository templates #8 owner.- The issue and PR retain before/after evidence and exact validation commands with results. The PR remains in draft; no merge or Agent merge change occurs.
Technical decisions
Owned change paths are profile/README.md and AGENTS.md; review the two agent wrappers for a no-change result. Keep the existing document shapes, identifiers, read order, and brand heading. Link canonical guidance rather than copying standards. Root README audience clarification is coordinated through #8, not duplicated in this PR. No new documentation hierarchy, generated output, tooling, dependency, or repository audit file belongs in this slice. The base has no Markdown/link validation scripts; do not describe the unmerged #12 check as enforced.
Implementation plan
- Read the owned documents, wrappers, pinned sources, and root context; capture the missing orientation and unsupported enforcement statement before editing.
- Make surgical prose changes, keep one logical change per small commit, and open the scoped draft PR early.
- Verify every factual statement against its source; verify the exact read order, wrapper resolution, heading stability, and all added links.
- Run the existing applicable checks and
git diff --check; record exact commands and results and any unavailable check, without claiming full STE conformance. - Review the final diff, update this plan with evidence, link only the delivery work it resolves, and leave the PR in draft.
Activity
MariusStorhaug commentedon Nov 4, 2026
Baseline evidence before editing
The checked source is
0c67251812ea306543f3a14ab473ae357cfb76ac. The worktree is clean. This delivery changes onlyprofile/README.mdandAGENTS.md.AGENTS.mdclaims that the README describes enforcement.Read in this order:instructionAGENTS.mdThe inline PowerShell assertions return 7/12 passed, 5 expected failures, exit
1, before any document edit. Source inspection confirms the failed claims. The baseline can also be inspected with these exact commands:All three commands succeed. The first returns only the existing slogan heading. The second contains
how its defaults are enforcedandhow a change is made and reviewed. The third links central MSX documentation.The fixed standards source is MSXOrg/docs commit
1b0d4893c8fefabe604d04393068a8ff6f848082, undersrc/docs/. The Documentation Model, Natural Language, Writing Guide, Markdown, Documentation, home page, README-Driven Context, and applicable workflow, PR, and commit sources are available and read. The official STE description, FAQ, and Issue 9 DOI record are available. The local Issue 9 PDF MD5 is9c720341c350ed77943b2c73d01c716f, which matches the official record. The local reference confirms active voice, imperative instructions, and the 25-word descriptive sentence limit. Reference files remain local; this is not a full STE conformance claim.The tree has no Markdown/link validation scripts, shared Markdown configuration, or workflow directory. No check from unmerged #12 is treated as installed or enforced. No tooling or dependency will be added. The optional parent
..\AGENTS.mdpath is absent; the repository's rootAGENTS.mdand both actual wrapper routes are available.Next verification: repeat the acceptance checks after the two prose changes; inspect each factual statement against the pinned home page and local README; inspect both added link destinations; run
git diff --check; confirm exact wrapper content, read order, headings, and the two-path diff. The draft PR closes only #17 and remains draft without merge automation.MariusStorhaug commentedon Nov 4, 2026
Implementation is persistent in a draft PR
The focused draft PR opened after the first logical commit, before the agent-description change.
ce0a2f3c7646fcbe4d06cb0fa5c857034ba164eb: the profile links MSX guidance and community defaults.5b6191d042d48503124cdfcad9a062182be546db: the agent read-order descriptions match their target documents.Only
profile/README.mdandAGENTS.mddiffer from0c67251812ea306543f3a14ab473ae357cfb76ac. The original profile heading remains exact. The two wrappers, root README, contribution guide, and PR template have no changes. The repeat acceptance run returns 12/12 passed, 0 failed, exit0. Final source, scope, and review evidence follow before handoff. The PR remains draft; no merge automation is enabled.MariusStorhaug commentedon Nov 4, 2026
Final delivery evidence
The focused draft PR retains the final source, before/after evidence, exact commands and results, standards alignment, convergence scope, and approved final-source review. The evidence below is copied from the verified PR record. The PR remains draft and unmerged.
Technical details
Scope and persistent source
The comparison is
0c67251812ea306543f3a14ab473ae357cfb76ac...e90ab70966ccfa12f7c20a486fb40f5846062c9a. The PR contains onlyprofile/README.mdandAGENTS.md: nine added lines and two removed lines. The worktree is clean.Three small commits retain the implementation sequence:
ce0a2f3c7646fcbe4d06cb0fa5c857034ba164eb: add profile context and links; open this draft before the agent edit.5b6191d042d48503124cdfcad9a062182be546db: correct both agent read-order descriptions.e90ab70966ccfa12f7c20a486fb40f5846062c9a: usefile of that typefor the default-file explanation after the source-vocabulary review.The root README, contribution guide, PR template, forms, and SECURITY/SUPPORT policies are not changed. Root README audience clarification remains with its existing owner. No tooling, dependency, generated output, or documentation structure is added.
Source and factual review
The fixed authority is MSXOrg/docs commit
1b0d4893c8fefabe604d04393068a8ff6f848082, undersrc/docs/. The source review covers Documentation Model, Natural Language, Writing Guide, Markdown, Documentation, README-Driven Context, and the applicable workflow, contribution, PR, commit, branching, and completion guidance.The official STE description, FAQ, and Issue 9 DOI record are available. The local Issue 9 PDF has MD5
9c720341c350ed77943b2c73d01c716f, which matches the official record. The review uses the relevant verb, instruction, descriptive-writing, and dictionary guidance. The manual and extraction remain local.The added prose uses en-US, present tense, active voice, and short sentences. Its plain-text sentence lengths are 14, 8, and 15 words.
Read in this order:remains imperative.Ways of workingretains the source's technical term. The existing slogan is an accepted branding difference, not a claimed STE-compliant technical statement. Neither these checks nor a word count establish full STE conformance.All required pinned MSX and official STE sources are available. The custom instruction's literal parent
..\AGENTS.mdpath is absent. The repository rootAGENTS.mdis available, was read, and is the verified destination of both actual wrappers. No source or access blocker prevents this delivery.Before and after acceptance evidence
The pre-edit record retains the baseline failures. The same 12 acceptance checks return seven passes and five expected failures before editing, then 12 passes and no failures after editing. The final wording is included in the passing run.
https://msx.no/docs/is present and returns HTTP 200.The exact read order remains
README.md, then.github/CONTRIBUTING.md. Both target files exist. Both H1 texts are identical to the baseline, so their existing heading anchors remain stable. No heading or fragment is added..claude/CLAUDE.md@../AGENTS.mdAGENTS.md.github/copilot-instructions.mdFollow the instructions in [AGENTS.md](../AGENTS.md).AGENTS.mdExact acceptance check
This PowerShell block was run before and after the edit. The baseline exits
1with five expected failures. The final source exits0with12/12 passed; 0 failed. The text assertions verify explicit content and invariant routes; the source table above supplies the factual review.Other checks and results
git diff --check 0c67251812ea306543f3a14ab473ae357cfb76acgit diff --cached --checkgit diff --check 0c67251812ea306543f3a14ab473ae357cfb76ac...HEADe90ab70966ccfa12f7c20a486fb40f5846062c9a.git diff --name-only 0c67251812ea306543f3a14ab473ae357cfb76acAGENTS.mdandprofile/README.md.git diff --exit-code 0c67251812ea306543f3a14ab473ae357cfb76ac...HEAD -- .claude\CLAUDE.md .github\copilot-instructions.md README.md .github\CONTRIBUTING.md .github\pull_request_template.mdcurl.exe --fail --location --silent --show-error --max-time 60 --output NUL --write-out 'HTTP %{http_code}; URL %{url_effective}\n' 'https://msx.no/docs/'curl.exe --fail --location --silent --show-error --max-time 60 --output NUL --write-out 'HTTP %{http_code}; URL %{url_effective}\n' 'https://github.com/MSXOrg/.github'git --no-pager status --shortBoth HTTP destinations were also read to confirm the expected content, not only a successful status. The profile uses an absolute repository link so it reaches the same context from both the organization profile and the repository view.
The following GitHub GFM render commands succeed for the final source. Shape assertions confirm one H1, two paragraphs, and two canonical links for the profile; one H1 and one two-step ordered list for
AGENTS.md. The wrapper-resolution command returns the same rootAGENTS.mdfor both paths.Markdown/link lint was not run: the baseline has no corresponding scripts, shared Markdown configuration, package manifest, or workflow directory. The availability probe finds no installed
markdownlint-cli2,markdownlint, orpymarkdowncommand. No dependency is installed. Unmerged #12 is not treated as installed or enforced validation.The probe reports all three commands unavailable. The tracked-file query returns no matches. The local/manual checks above are evidence for this delivery, not installed CI enforcement.
Standards and framework alignment
The final pass checks the applicable pinned process and writing sources against the whole diff. No mission, guarantee, policy, enforcement mechanism, or response promise is added.
profile/README.mdAGENTS.mdConvergence, plan, and review
The scoped convergence command is:
It returns delivery leaves #16, #17, and #18. The two-file diff satisfies only #17. The form and reporting-policy asks are not satisfied by this change, so no additional closing reference is added. The native blocked-by query returns an empty list.
The issue plan records source review, small commits, early draft creation, factual and route checks, and validation evidence. This PR carries the final alignment, convergence, and review record.
The explicit command
gh pr edit 20 --repo MSXOrg/.github --add-reviewer '@copilot'succeeds after the final push. The final-source review is APPROVED fore90ab70966ccfa12f7c20a486fb40f5846062c9a, with zero inline comments and no active review issues. Its remote review check completed withsuccess. This is a review result, not a Markdown/link CI result.The PR remains open and draft, assigned to its author. GitHub auto-merge is
null; Agent merge is disabled and its merge action is false. No merge or merge-automation change is made. The repository has no versioned producer route in this source tree, so no release decision block or release label is added.MariusStorhaug commentedon Nov 11, 2026
Campaign merge hold (2026-11-11): the user explicitly selected "Hold the six merges until validation is available (Recommended)". The current default branch has no authored validation workflow and this PR has no actual validation checks; manual prose/interface inspection is not counted as CI. Hold #20 until actual validation is available or a new explicit owner decision changes this hold. This is not authorization to add tooling, change rules, waive checks, or revive withdrawn validation work. Prepared source and existing PR/Agent-merge settings stay unchanged.
MariusStorhaug commentedon Nov 11, 2026
Fresh exact-head preparation - 2026-11-11
The fresh review covers head
e90ab70966ccfa12f7c20a486fb40f5846062c9aagainst actual base
0c67251812ea306543f3a14ab473ae357cfb76ac.Both live IDs are unchanged. The isolated worktree is clean and its relevant
file blobs match that exact head. The diff contains only
AGENTS.mdandprofile/README.md(9 added lines, 2 removed lines). No source, policy,settings, labels, automation, or merge change is made.
git --no-pager diff 0c67251812ea306543f3a14ab473ae357cfb76ac...e90ab70966ccfa12f7c20a486fb40f5846062c9a -- AGENTS.md profile\README.mdgit diff --check 0c67251812ea306543f3a14ab473ae357cfb76ac...e90ab70966ccfa12f7c20a486fb40f5846062c9aRead in this order:, README-then-CONTRIBUTING paths, and both exact wrapper syntaxes remain intact.markdownlint-cli2 0.24.0/markdownlint 0.42.0.Linting: 2 files. Direct library results independently return both actual file keys, each with zero violations. This is not an empty scan.curl.exeGET commands below, with the actual response bodies retained and inspected.gh api --method POST markdown --input -withmode=gfm,context=MSXOrg/.github.README.mdthen.github/CONTRIBUTING.md.The authoritative current shared config is
MSXOrg/docs at
f9b335d0b78a3eead0b7efa573936e86cb1e7265,path
.github/linters/.markdown-lint.yml,blob
d48dd486e4d3a968fceee23a62a84a71694b88c2.The retained bytes have SHA256
e20531ba6049449453700f72d8bbcb2d6ae136e016e06c022f69d30686e261dc.This blob is identical to the campaign's original pinned configuration.
The config and response/render evidence remain in session artifacts, outside
the repository. No dependency was installed and no repository validator,
configuration, test, or CI file was added.
The CLI summary
0 issues in 0 filescounts files with reported issues.The run explicitly reports
Linting: 2 files. An additional invocation ofthe same cached core linter, with the same loaded authoritative YAML config,
returns this non-empty file result set:
{ "linter": "markdownlint 0.42.0", "fileCount": 2, "violations": 0, "results": { "AGENTS.md": [], "profile\\README.md": [] } }The factual review re-reads the campaign-pinned MSX index at
1b0d4893c8fefabe604d04393068a8ff6f848082, the pinned Natural Language,Writing Guide, and Markdown guidance, and this worktree's root README and
contribution guide. The profile only describes shared guidance and GitHub
default-file behavior. Both agent descriptions match their target documents.
The accepted brand text and behavior remain unchanged.
Current review, checks, and effective protections
gh api graphql --input -confirmsreviewDecision=APPROVED,mergeable=MERGEABLE,mergeStateStatus=CLEAN, and 0 review threads,with no further thread page. Review
5768290832
is APPROVED on the exact live head. The older
5b6191d...review is DISMISSEDand is not current approval evidence. REST review comments total 0.
gh api repos/MSXOrg/.github/commits/e90ab70966ccfa12f7c20a486fb40f5846062c9a/check-runsreports one completed successful run,
copilot-pull-request-reviewer.Its action is
Running Copilot Code Review, eventdynamic. This is reviewexecution, not Markdown/link validation.
gh pr checks 20 --repo MSXOrg/.githuband the same command with--requiredboth return
no checks reported, exit 1. GraphQL's status rollup is null.The legacy status API returns
state=pendingwith 0 status contexts.There are no reported failing check runs or legacy failure contexts.
Two app check suites (
113345654978,113345656479) remain queued with nullconclusion, but each suite has 0 check runs; they are not passed checks.
The third suite is the successful review execution.
Hosted Markdown/link CI is still absent, not passed. The source tree has
no validation workflow/scripts/configuration. This local operational evidence
does not install or reinterpret a hosted required check.
gh api repos/MSXOrg/.github/branches/main/protectionreturns HTTP 404,Branch not protected, but it is not evidence that no protections apply.gh api repos/MSXOrg/.github/rules/branches/mainandgh api repos/MSXOrg/.github/rulesets/19735160confirm the active inheritedorganization ruleset GitHub Flow:
resolution requirements;
required_approving_review_count=0, with the requirements above still active;The base has no
.github/CODEOWNERS, rootCODEOWNERS, ordocs/CODEOWNERS.No code-owner identity is inferred.
current_user_can_bypassreportspull_requests_only; this capability is not used. No protection or bypasssetting is changed.
The PR is open and non-draft, with
auto_merge=null, and it is not merged.The exclusive global merge slot remains held by Process/root. This preparation
does not grant or use that slot. No genuine content decision or source/access
blocker remains.
Feature requests start with consumer needs (#15)
MariusStorhaug commentedon Nov 11, 2026
Completed by the ordinary exact-head guarded squash of #20 on 2026-11-11. Accepted head:
e90ab70966ccfa12f7c20a486fb40f5846062c9a; squash/main:c90c09d7b501edbe919cef222f7cc1ce6004b810; actual prior main:d3d56f6d40df924831d836c373c87a9680b77a08. Native exact-head approval, zero fully paginated threads, prerequisites, and effective protections were read before merge. No admin, force, bypass, alternate approval, or settings change was used. Fresh Markdown/native-render/link/interface validation was operationally accepted; hosted source-validation CI remains absent, not passed. Post-merge full-tree comparison proves that the only changes from prior main are the exact accepted AGENTS and profile README blobs; both thin wrappers and every earlier accepted README/contribution/feature/security/support blob remain exact. No snapshot suite or recognized PR template exists. Actual main integration, delivery-leaf closure, and absence of the exact remote topic branch are verified. These Git-served entry files require no invented Pages, package, live-agent, or consumer-rollout result.