Evolve AI Mastery into a curated flagship publication

.github/workflows/validate-site.yml

@@ -0,0 +1,58 @@
+name: Validate static site
+
+on:
+  pull_request:
+  push:
+    branches: [main]
+
+permissions:
+  contents: read
+
+concurrency:
+  group: validate-site-${{ github.ref }}
+  cancel-in-progress: true
+
+jobs:
+  release-gates:
+    runs-on: ubuntu-latest
+    timeout-minutes: 10
+    steps:
+      - name: Check out repository
+        uses: actions/checkout@v4
+
+      - name: Set up Node.js
+        uses: actions/setup-node@v4
+        with:
+          node-version: 20
+
+      - name: Validate route graph
+        run: node scripts/validate-site-graph.mjs
+
+      - name: Audit internal-link policy
+        run: node scripts/audit-internal-link-policy.mjs
+
+      - name: Validate editorial expansion
+        run: node scripts/validate-editorial-expansion.mjs
+
+      - name: Validate AURE experience
+        run: node scripts/validate-aure-remaster.mjs
+
+      - name: Validate publication index
+        run: node scripts/validate-publication-index.mjs
+
+      - name: Validate knowledge index and field records
+        run: |
+          node scripts/validate-knowledge-index.mjs
+          node scripts/validate-field-guide.mjs
+          node scripts/validate-self-audit.mjs
+
+      - name: Validate learning pathways
+        run: |
+          node scripts/validate-arm-pathway.mjs
+          node scripts/validate-trust-pathway.mjs
+          node scripts/validate-machine-readable-pathway.mjs
+          node scripts/validate-agentic-interoperability-pathway.mjs
+          node scripts/validate-economic-models-pathway.mjs
+
+      - name: Check patch whitespace
+        run: git diff --check

CONTRIBUTING.md

@@ -0,0 +1,68 @@
+# Contributing to AI Mastery
+
+AI Mastery accepts contributions that make its technical knowledge more accurate, reproducible, inspectable, or useful. Strong contributions include implementation patterns, benchmark records, source corrections, case evidence, and improvements to the public knowledge graph.
+
+## Before opening a change
+
+Open an issue or focused pull request that states:
+
+- the technical question or reader problem;
+- the proposed claim and the evidence supporting it;
+- what a reader can reproduce or inspect;
+- important limits, unknowns, and dependencies;
+- which existing guide, learning path, or entity the work connects to.
+
+Do not submit promotional listicles, unverified performance claims, fabricated citations, undisclosed sponsored links, secrets, private data, or code copied without compatible permission.
+
+## Content standards
+
+Write for both people and machine retrieval:
+
+1. Begin each key concept with a direct, self-contained definition.
+2. Organize the page with one `h1` and descriptive `h2`/`h3` sections.
+3. Use specific anchor text that names the destination concept.
+4. Prefer primary sources, standards, official documentation, and reproducible evidence.
+5. Separate observed facts, derived conclusions, proposals, and unknowns.
+6. Include prerequisites, implementation steps, expected outputs, failure modes, and a verification method when publishing a blueprint.
+7. Add or update the relevant JSON-LD entity relationships, sitemap entry, and `llms.txt` record for a new public route.
+
+Code examples must use placeholders for credentials and identify the runtime or dependency versions needed to reproduce them.
+
+## Evidence and corrections
+
+A case study or benchmark should include a dated observation window, method, inputs, outputs, and explicit claim boundaries. If a result cannot be independently verified, describe it as reported or proposed rather than established.
+
+For a small factual correction, open a pull request with the replacement source. For a disputed or larger correction, open an issue describing the affected URL, statement, supporting evidence, and requested change. Corrections should preserve an inspectable history rather than silently expanding a claim.
+
+## Local validation
+
+No package installation or build step is required. Preview the site from the repository root:
+
+```bash
+python3 -m http.server 4173
+```
+
+Before submitting a pull request, run the same core checks used by CI:
+
+```bash
+node scripts/validate-site-graph.mjs
+node scripts/audit-internal-link-policy.mjs
+node scripts/validate-editorial-expansion.mjs
+node scripts/validate-publication-index.mjs
+git diff --check
+```
+
+Run the pathway-specific validator for any collection you change. A pull request should explain the checks run and any validation that remains external or manual.
+
+## Pull request scope
+
+Keep each pull request centered on one coherent outcome. Include:
+
+- a concise summary of the reader-facing change;
+- routes, schemas, or scripts affected;
+- evidence and source links;
+- screenshots for meaningful visual changes;
+- validation results;
+- unresolved risks or follow-up work.
+
+By contributing, you confirm that you have the right to submit the material and that it does not expose confidential information.

README.md

@@ -45,6 +45,10 @@ Run `node scripts/validate-knowledge-index.mjs` to verify the connected domain a
 
 Mason Nguyen's professional roles and identity links are cross-referenced against his canonical [Coreweaver author profile](https://coreweaver.io/authors/mason-nguyen).
 
+## Contributing
+
+Evidence-backed corrections, implementation patterns, benchmark records, and case studies are welcome. Read [`CONTRIBUTING.md`](CONTRIBUTING.md) for the content, evidence, machine-readable metadata, and validation requirements.
+
 
 ## Reusable technical SEO operating procedure
 

audit-internal-link-policy.json

@@ -1,7 +1,7 @@
 {
-  "pages": 54,
-  "totalAnchors": 844,
-  "internalAnchors": 587,
+  "pages": 57,
+  "totalAnchors": 879,
+  "internalAnchors": 597,
   "restrictedInternalLinks": 0,
   "crawlControlFindings": 0,
   "findings": []

aure-template-demo/index.html

@@ -11,26 +11,22 @@
   <meta property="og:title" content="Purpose and Buyer Truth — AURE · AI Mastery">
   <meta property="og:description" content="Start with the buyer’s real question and define what a trustworthy answer must contain.">
   <meta property="og:url" content="https://virtualmase.github.io/ai-mastery/aure-template-demo/">
-  <link rel="stylesheet" href="../../styles.css">
-  <style>
-    .headless-page{background:#f4f1ea;color:#1e2924}.headless-shell{max-width:920px;margin:auto;padding:0 1.5rem}.headless-header{padding:1.2rem 0;border-bottom:1px solid #cfc8ba}.headless-header a{color:inherit;text-decoration:none;font-weight:800}.headless-crumbs{display:flex;gap:.55rem;margin-top:.7rem;font-size:.78rem}.headless-crumbs a{font-weight:500;text-decoration:underline;text-underline-offset:.2em}.headless-hero{padding:6rem 0 4rem;border-bottom:1px solid #cfc8ba}.headless-kicker{text-transform:uppercase;letter-spacing:.14em;font-size:.75rem;font-weight:700;color:#7d4b32}.headless-hero h1{max-width:760px;font-size:clamp(2.8rem,7vw,6rem);line-height:.94;letter-spacing:-.06em;margin:.8rem 0 1.4rem}.headless-hero p{max-width:650px;font-size:1.2rem;line-height:1.6}.headless-grid{display:grid;grid-template-columns:1.15fr .85fr;gap:1.2rem;padding:3rem 0}.headless-card{padding:1.4rem;border:1px solid #cfc8ba;background:#fbfaf6}.headless-card h2{font-size:1.5rem;margin:.4rem 0 1rem}.headless-card p,.headless-card li{line-height:1.6}.headless-boundary{border-left:4px solid #7d4b32;background:#e8e1d5;padding:1.1rem 1.3rem;line-height:1.6}.headless-footer{padding:2rem 0 4rem;border-top:1px solid #cfc8ba;display:flex;justify-content:space-between;gap:1rem}.headless-footer a{color:inherit}@media(max-width:700px){.headless-grid{grid-template-columns:1fr}.headless-footer{flex-direction:column}}
-  </style>
+  <link rel="stylesheet" href="../styles.css">
+  <link rel="stylesheet" href="../aure/aure.css">
   <script type="application/ld+json">{"@context":"https://schema.org","@type":"LearningResource","name":"Purpose and Buyer Truth","description":"Start with the buyer’s real question and define what a trustworthy answer must contain.","url":"https://virtualmase.github.io/ai-mastery/aure-template-demo/","isPartOf":{"@type":"Course","name":"AURE — Autonomous Resource Management and Evidence-led Buyer Trust"}}</script>
 </head>
-<body class="headless-page">
-  <header class="headless-shell headless-header">
-    <a href="../">AI MASTERY / AURE</a>
-    <nav class="headless-crumbs" aria-label="Breadcrumb"><a href="../">Home</a><span aria-hidden="true">/</span><a href="../aure/">AURE</a><span aria-hidden="true">/</span><span>01 / 16</span></nav>
-  </header>
+<body>
+  <header class="aure-topbar"><div class="aure-shell"><a class="aure-brand" href="../aure/">AURE <span>/ AI MASTERY</span></a><a class="aure-home" href="../">Return to AI Mastery</a></div></header>
   <main>
-    <section class="headless-hero"><div class="headless-shell"><div class="headless-kicker">AURE 01 / 16 · Learning silo</div><h1>Purpose and Buyer Truth</h1><p>Start with the buyer’s real question and define what a trustworthy answer must contain.</p></div></section>
-    <section class="headless-shell headless-grid">
-      <article class="headless-card"><div class="headless-kicker">Artifact</div><h2>Buyer-question brief</h2><p>Name the audience, decision, evidence boundary, unknowns, and one honest next action.</p><h3>Practice</h3><ul><li>Name the buyer and the decision in plain language.</li><li>List the evidence a reasonable buyer can inspect.</li><li>Mark unsupported outcomes as unknown.</li><li>Route the next decision to an accountable human owner.</li></ul></article>
-      <aside class="headless-card"><div class="headless-kicker">Boundary</div><h2>Proof, not promises.</h2><p>This teaches a method. It does not certify a system, prove a company is trustworthy, guarantee AI retrieval, or promise revenue, rankings, safety, interoperability, or conversion.</p></aside>
+    <nav class="aure-shell aure-breadcrumbs" aria-label="Breadcrumb"><a href="../aure/">AURE pathway</a> / <span>Purpose and Buyer Truth</span></nav>
+    <section class="aure-silo-hero"><div class="aure-shell aure-silo-layout"><div class="aure-silo-marker">01<small>of 16 · Learning silo</small></div><div><p class="aure-kicker">Portable lesson template</p><h1>Purpose and Buyer Truth</h1><p class="aure-lede">Start with the buyer’s real question and define what a trustworthy answer must contain.</p></div></div></section>
+    <section class="aure-shell aure-content">
+      <article class="aure-panel"><p class="aure-kicker">Working artifact</p><h2>Buyer-question brief</h2><p class="aure-outcome">Name the audience, decision, evidence boundary, unknowns, and one honest next action.</p><ol class="aure-practice"><li>Name the buyer and the decision in plain language.</li><li>List the evidence a reasonable buyer can inspect.</li><li>Mark unsupported outcomes as unknown.</li><li>Route the next decision to an accountable human owner.</li></ol></article>
+      <aside class="aure-panel aure-boundary"><p class="aure-kicker">Evidence boundary</p><h2>Proof, not promises.</h2><p>This teaches a method. It does not certify a system, prove a company is trustworthy, guarantee AI retrieval, or promise revenue, rankings, safety, interoperability, or conversion.</p></aside>
     </section>
-    <section class="headless-shell"><div class="headless-boundary"><strong>SOUL check:</strong> Who authorized it? What information may be used? What actually happened? Who owns the decision when the case gets weird?</div></section>
+    <section class="aure-shell aure-soul"><div><p class="aure-kicker">Pre-action review</p><h2>The SOUL check</h2></div><div class="aure-soul-grid"><div><strong>S / SCOPE</strong>Who authorized the action?</div><div><strong>O / OBSERVE</strong>What actually happened?</div><div><strong>U / USE</strong>What information may be used?</div><div><strong>L / LIABILITY</strong>Who owns the edge case?</div></div></section>
+    <nav class="aure-path-nav" aria-label="AURE pathway navigation"><a href="../aure/"><small>Pathway</small><strong>← Return to AURE</strong></a><a href="../aure/evidence-and-claim-boundaries/"><small>Next silo</small><strong>Evidence and Claim Boundaries →</strong></a></nav>
   </main>
-  <footer class="headless-shell headless-footer"><a href="../aure/">← Return to AURE directory</a><a href="../aure/evidence-and-claim-boundaries/">Next: Evidence and Claim Boundaries →</a></footer>
-<nav class="site-footer-links" aria-label="Site directory"><a href="../">Home</a><a href="../aure/">AURE / 16 silos</a><a href="../directory/">All pages</a><a href="../llms.txt">Machine-readable index</a><a href="../sitemap.xml">Sitemap</a></nav>
+  <footer class="aure-footer"><div class="aure-shell"><span>AURE · Evidence-led buyer systems</span><nav class="aure-footer-links" aria-label="Site directory"><a href="../aure/">AURE pathway</a><a href="../">AI Mastery</a><a href="../directory/">All pages</a><a href="../llms.txt">Machine-readable index</a></nav></div></footer>
 </body>
 </html>