MD File links Sweep

Author: brian-brewer

README.md

@@ -1,7 +1,7 @@
 # Data Trust Engineering (DTE)
 
-[![GitHub Stars](https://img.shields.io/github/stars/datatrustengineering/DataTrustEngineering)](https://github.com/[YourUsername]/DataTrustEngineering/stargazers)
-[![GitHub Forks](https://img.shields.io/github/forks/datatrustengineering/DataTrustEngineering)](https://github.com/[YourUsername]/DataTrustEngineering/network)
+[![GitHub Stars](https://img.shields.io/github/stars/datatrustengineering/DataTrustEngineering)](https://github.com/datatrustengineering/DataTrustEngineering/stargazers)
+[![GitHub Forks](https://img.shields.io/github/forks/datatrustengineering/DataTrustEngineering)](https://github.com/datatrustengineering/DataTrustEngineering/network)
 [![MIT License](https://img.shields.io/badge/License-MIT-blue.svg)](/LICENSE.md)
 [![#DTERevolution](https://img.shields.io/badge/Join-%23DTERevolution-brightgreen)](https://x.com/hashtag/DTERevolution)
 
@@ -36,7 +36,7 @@ The **DTE Trust Dashboard** kicks off our open-source journey, visualizing AI go
 
 Find it in `/tools/data-trust-dashboard/DTE_Trust_Dashboard.html`. More artifacts—like data quality patterns and trust evals—are on the way!
 
-Explore [UseCases.md](UseCases.md) to see how to apply DTE principles with open-source code.
+Explore [USE_CASES.md](/docs/patterns/USE_CASES.md) to see how to apply DTE principles with open-source code.
 
 ## Getting Started
 
@@ -68,7 +68,7 @@ Explore [UseCases.md](UseCases.md) to see how to apply DTE principles with open-
 
 - `/Manifesto.md`: The *Data Trust Engineering Manifesto*.
 - `/tools`: Artifacts like `/tools/data-trust-dashboard`.
-- `/docs`: Case studies, patterns (e.g., `/docs/patterns/data-quality-guide.md`).
+- `/docs`: Case studies, patterns (e.g., `/docs/patterns/USE_CASES.md`).
 - `/community`: Contribution guidelines, code of conduct.
 - `/LICENSE.md`: MIT License.
 
@@ -79,6 +79,7 @@ Help shape DTE’s future! Contribute:
 - **Artifacts**: Data quality scripts, lineage trackers, or AI tools to `/tools`.
 - **Manifesto Updates**: Refine principles in `/Manifesto.md`.
 - **Case Studies**: Share success stories in `/docs/case-studies`.
+- **Use Cases**: Explore [USE_CASES.md](/docs/patterns/USE_CASES.md) to see how to apply DTE principles with open-source code.
 
 Start with “good first issues” (e.g., typo fixes) or discuss ideas in GitHub Discussions. See [CONTRIBUTING.md](/community/CONTRIBUTING.md) and [CODE_OF_CONDUCT.md](/community/CODE_OF_CONDUCT.md).
 

SECURITY.md

@@ -16,7 +16,7 @@ At **Data Trust Engineering (DTE)**, we prioritize the security of our artifacts
 - **Do Not**: Disclose vulnerabilities publicly (e.g., GitHub Issues, Slack) until resolved.
 
 ## Community Guidelines
-- Follow our [CODE_OF_CONDUCT.md](/community/CODE_OF_CONDUCT).
+- Follow our [CODE_OF_CONDUCT.md](/community/CODE_OF_CONDUCT.md).
 - For general inquiries, use [Slack](https://join.slack.com/t/datatrustengineering/shared_invite/zt-3br05le6v-pxGSBeJGLpVgOsNM9ejGuw) or a [Contact issue](https://github.com/datatrustengineering/DataTrustEngineering/issues/new?template=contact.yml).
 - Visit [datatrustmanifesto.org](https://datatrustmanifesto.org) for more.
 

SUPPORT.md

@@ -4,7 +4,7 @@ title: Support
 
 # Support for Data Trust Engineering (DTE)
 
-Welcome to **Data Trust Engineering (DTE)**! We’re here to help you engage with our community, contribute to artifacts like the [DTE Trust Dashboard](/tools/data-trust-dashboard/DTE_Trust_Dashboard), or learn about our mission to certify data systems by use case, risk, and value. Here’s how to get help:
+Welcome to **Data Trust Engineering (DTE)**! We’re here to help you engage with our community, contribute to artifacts like the [DTE Trust Dashboard](/tools/data-trust-dashboard/DTE_Trust_Dashboard.html), or learn about our mission to certify data systems by use case, risk, and value. Here’s how to get help:
 
 ## How to Get Support
 - **Community Questions**:
@@ -17,10 +17,10 @@ Welcome to **Data Trust Engineering (DTE)**! We’re here to help you engage wit
   - Report bugs via a [Bug Report issue](https://github.com/askbrdatatrustengineering/DataTrustEngineering/issues/new?template=bug_report.md).
   - Suggest features via a [Feature Request issue](https://github.com/askbrdatatrustengineering/DataTrustEngineering/issues/new?template=feature_request).
 - **Security or Code of Conduct Issues**:
-  - Report privately via our [security form](https://forms.gle/BkMJNgfbMuavkUKc8). See [SECURITY.md](/SECURITY).
+  - Report privately via our [security form](https://forms.gle/BkMJNgfbMuavkUKc8). See [SECURITY.md](/SECURITY.md).
 
 ## Guidelines
-- Follow our [CODE_OF_CONDUCT.md](/community/CODE_OF_CONDUCT) for respectful interactions.
+- Follow our [CODE_OF_CONDUCT.md](/community/CODE_OF_CONDUCT.md) for respectful interactions.
 - Check [CONTRIBUTING.md](/community/CONTRIBUTING) for contribution details.
 - Visit [datatrustmanifesto.org](https://datatrustmanifesto.org) for more resources.
 

community/CONTRIBUTING.md

@@ -2,7 +2,7 @@
 title: Contributing to Data Trust Engineering (DTE)
 ---
 
-Welcome to the **Data Trust Engineering (DTE)** community! We're building a movement to replace traditional data governance’s 70-80% failure rate [Gartner, 2025] with engineering-driven trust, certification, and AI-readiness. Inspired by the [DataTrustManifesto.org](https://datatrustmanifesto.org)’s agility and collaboration, DTE invites data professionals, enterprises, SMBs, and hyperscalers to contribute to our open-source ecosystem. Whether you're enhancing the [DTE Trust Dashboard](/tools/data-trust-dashboard/DTE_Trust_Dashboard), proposing new artifacts, or sharing case studies, your contributions shape the #DTERevolution.
+Welcome to the **Data Trust Engineering (DTE)** community! We're building a movement to replace traditional data governance’s 70-80% failure rate [Gartner, 2025] with engineering-driven trust, certification, and AI-readiness. Inspired by the [DataTrustManifesto.org](https://datatrustmanifesto.org)’s agility and collaboration, DTE invites data professionals, enterprises, SMBs, and hyperscalers to contribute to our open-source ecosystem. Whether you're enhancing the [DTE Trust Dashboard](/tools/data-trust-dashboard/DTE_Trust_Dashboard.html), proposing new artifacts, or sharing case studies, your contributions shape the #DTERevolution.
 
 This guide explains how to contribute to the `DataTrustEngineering` repository, ensuring a productive, inclusive community. Join us at [datatrustmanifesto.org](https://datatrustmanifesto.org) or our [Slack org]([Slack Invite Link]).
 
@@ -17,25 +17,26 @@ This guide explains how to contribute to the `DataTrustEngineering` repository,
 
 ## Code of Conduct
 
-All contributors must follow our [CODE_OF_CONDUCT.md](/community/CODE_OF_CONDUCT), based on the Contributor Covenant. Be respectful, constructive, and focused on DTE’s mission to certify data systems by use case, risk, and value. Harassment, off-topic rants, or disruptive behavior will be addressed by maintainers to keep our community welcoming.
+All contributors must follow our [CODE_OF_CONDUCT.md](/community/CODE_OF_CONDUCT.md), based on the Contributor Covenant. Be respectful, constructive, and focused on DTE’s mission to certify data systems by use case, risk, and value. Harassment, off-topic rants, or disruptive behavior will be addressed by maintainers to keep our community welcoming.
 
 ## What Can You Contribute?
 
-DTE is a community-driven movement, and we welcome contributions that align with our [Manifesto](/Manifesto) and advance trust, engineering rigor, and AI-readiness. Examples include:
+DTE is a community-driven movement, and we welcome contributions that align with our [Manifesto](/Manifesto.md) and advance trust, engineering rigor, and AI-readiness. Examples include:
 
 - **Artifacts**: Tools and scripts for data quality (e.g., Great Expectations configs), lineage (e.g., Apache Atlas scripts), or AI governance (e.g., Fairlearn integrations). See `/tools`.
 - **Manifesto Updates**: Refine or propose principles in `/Manifesto.md` to strengthen DTE’s vision.
 - **Case Studies**: Share real-world DTE applications (e.g., “Reduced AI bias by 15%”) in `/docs/case-studies`. Use our [template](/docs/case-studies/template).
 - **Patterns and Guides**: Document DTE best practices (e.g., data quality patterns) in `/docs/patterns`.
 - **Trust Dashboard Enhancements**: Add metrics, APIs (e.g., Evidently AI, MLflow), or UI improvements to `/tools/data-trust-dashboard`.
 - **Documentation**: Improve clarity, fix typos, or add tutorials in `/docs`.
+- ** Contribute Code**: Explore [USE_CASES.md](/docs/patterns/USE_CASES.md) to see how to apply DTE principles with open-source code.
 
 **Good First Issues**: New to DTE? Start with issues tagged “good first issue” (e.g., typo fixes, adding a case study). These are great for building skills and joining the #DTERevolution!
 
 ## How to Contribute
 
 1. **Explore the Repo**:
-   - Read the [README.md](/README) and [Manifesto.md](/Manifesto) to understand DTE’s goals.
+   - Read the [README.md](/README.md) and [Manifesto.md](/Manifesto.md) to understand DTE’s goals.
    - Check `/tools` and `/docs` for existing artifacts and inspiration.
 
 2. **Discuss Your Idea**:
@@ -69,7 +70,7 @@ We review PRs to ensure alignment with DTE’s principles (trust, certification,
 
 2. **Review Process**:
    - Maintainers will review within 5-7 days, checking for:
-     - Alignment with the [DTE Manifesto](/Manifesto).
+     - Alignment with the [DTE Manifesto](/Manifesto.md).
      - Code/documentation quality (e.g., markdown linting, functional scripts).
      - Relevance to DTE’s goals (e.g., supports certification, cloud-native architectures).
    - Expect feedback (e.g., “Can you add an example for SMBs?”). Revise as needed.
@@ -87,7 +88,7 @@ We review PRs to ensure alignment with DTE’s principles (trust, certification,
 - **Stay On-Topic**: Contributions should support DTE’s focus on certifying data systems for trust, AI-readiness, and cloud scalability. Off-topic ideas (e.g., unrelated tech policies) may be redirected.
 - **Be Collaborative**: Engage in GitHub Discussions or Slack (#contributions) before submitting large PRs to align with community goals.
 - **Respect Feedback**: Maintainers may request changes to ensure quality. Respond constructively to keep the #DTERevolution moving forward.
-- **Avoid Chaos**: Follow the [CODE_OF_CONDUCT.md](/community/CODE_OF_CONDUCT). Disruptive behavior (e.g., spamming issues) may lead to warnings or blocks.
+- **Avoid Chaos**: Follow the [CODE_OF_CONDUCT.md](/community/CODE_OF_CONDUCT.md). Disruptive behavior (e.g., spamming issues) may lead to warnings or blocks.
 
 ## Recognition
 

community/CONTRIBUTORS.md

@@ -7,5 +7,5 @@ Thank you to everyone shaping the #DTERevolution! Contributors are listed below:
 - [Your Name] ([GitHub Profile]): Initiated DTE, authored Manifesto.
 - [Contributor Name] ([GitHub Profile]): Added data quality guide.
 
-Want to be listed? See [CONTRIBUTING.md](/community/CONTRIBUTING).
+Want to be listed? See [CONTRIBUTING.md](/community/CONTRIBUTING.md).
 

community/GOVERNANCE.md

@@ -24,24 +24,24 @@ DTE’s governance is rooted in the manifesto’s core principles:
 - **Transparency**: Decisions are made openly, with clear rationale shared in GitHub Issues, Discussions, or Slack.
 - **Collaboration**: Contributions from data professionals, enterprises, SMBs, and hyperscalers shape DTE’s evolution.
 - **Alignment**: All decisions support DTE’s mission to certify data systems by use case, risk, and value, ensuring trust and AI-readiness.
-- **Inclusivity**: We welcome diverse perspectives while maintaining focus, as enforced by our [CODE_OF_CONDUCT.md](/community/CODE_OF_CONDUCT).
+- **Inclusivity**: We welcome diverse perspectives while maintaining focus, as enforced by our [CODE_OF_CONDUCT.md](/community/CODE_OF_CONDUCT.md).
 - **Agility**: Inspired by DataOps, we prioritize rapid feedback and iterative improvements.
 
 ## Roles and Responsibilities
 
 - **Maintainers**:
   - **Who**: Initially, Brian Brewer (bbrewer@infolibcorp.com) and future trusted contributors elevated based on active participation.
   - **Responsibilities**:
-    - Review and merge pull requests (PRs) for alignment with the [Manifesto](/Manifesto).
-    - Moderate discussions, issues, and PRs per [CODE_OF_CONDUCT.md](/community/CODE_OF_CONDUCT).
+    - Review and merge pull requests (PRs) for alignment with the [Manifesto](/Manifesto.md).
+    - Moderate discussions, issues, and PRs per [CODE_OF_CONDUCT.md](/community/CODE_OF_CONDUCT.md).
     - Make final decisions on contributions and conflicts, seeking community input where possible.
     - Update repo structure, roadmap, and governance as DTE grows.
   - **Selection**: New maintainers are nominated by existing maintainers based on consistent, high-quality contributions (e.g., multiple merged PRs) and community trust. Nominations are discussed in GitHub Discussions and confirmed by consensus.
 
 - **Contributors**:
   - **Who**: Anyone who submits PRs, issues, or participates in Discussions/Slack, from beginners to experts.
   - **Responsibilities**:
-    - Follow [CONTRIBUTING.md](/community/CONTRIBUTING) and [CODE_OF_CONDUCT.md](/community/CODE_OF_CONDUCT).
+    - Follow [CONTRIBUTING.md](/community/CONTRIBUTING.md) and [CODE_OF_CONDUCT.md](/community/CODE_OF_CONDUCT.md).
     - Propose artifacts (e.g., data quality scripts), case studies, or manifesto updates that advance DTE’s mission.
     - Engage respectfully and respond to feedback during PR reviews.
 
@@ -64,7 +64,7 @@ Decisions in DTE are made through a **consensus-driven model**, inspired by open
    - Maintainers moderate to keep discussions on-topic and respectful.
 
 3. **Decision**:
-   - For minor changes (e.g., typo fixes, small PRs), maintainers approve or reject based on alignment with the [Manifesto](/Manifesto).
+   - For minor changes (e.g., typo fixes, small PRs), maintainers approve or reject based on alignment with the [Manifesto](/Manifesto.md).
    - For major changes (e.g., new principles, governance updates), maintainers seek community input for 5-7 days via Discussions or Slack. If consensus isn’t reached, maintainers make the final call, explaining the rationale publicly.
    - Example: Adding a new manifesto principle requires 2+ maintainer approvals and community feedback.
 
@@ -73,7 +73,7 @@ Decisions in DTE are made through a **consensus-driven model**, inspired by open
 
 ## Pull Request (PR) Review and Approval
 
-PRs are the primary way to contribute to DTE (e.g., artifacts, case studies, manifesto updates). The process follows [CONTRIBUTING.md](/community/CONTRIBUTING):
+PRs are the primary way to contribute to DTE (e.g., artifacts, case studies, manifesto updates). The process follows [CONTRIBUTING.md](/community/CONTRIBUTING.md):
 
 1. **Submission**:
    - Contributors fork the repo, create a branch, and submit a PR with a clear description (e.g., “Add Great Expectations script for data quality”).
@@ -95,22 +95,22 @@ PRs are the primary way to contribute to DTE (e.g., artifacts, case studies, man
    - Rejected PRs receive polite feedback (e.g., “This is great but outside DTE’s focus on technical trust”).
 
 5. **Merge**:
-   - Approved PRs are merged into the main branch, with contributors credited in [CONTRIBUTORS.md](/CONTRIBUTORS).
+   - Approved PRs are merged into the main branch, with contributors credited in [CONTRIBUTORS.md](/CONTRIBUTORS.md).
 
 ## Conflict Resolution
 
 Conflicts may arise over PRs, principles, or community interactions. We resolve them transparently:
 - **Step 1: Discussion**:
   - Address conflicts in GitHub Issues, Discussions, or Slack (#general or #contributions).
-  - Maintainers moderate to ensure respectful dialogue per [CODE_OF_CONDUCT.md](/community/CODE_OF_CONDUCT).
+  - Maintainers moderate to ensure respectful dialogue per [CODE_OF_CONDUCT.md](/community/CODE_OF_CONDUCT.md).
 - **Step 2: Mediation**:
   - If consensus isn’t reached within 5 days, maintainers propose a solution (e.g., trial period for a new principle).
   - Community input is sought via Discussions or Slack.
 - **Step 3: Final Decision**:
   - Maintainers make the final call, documenting the rationale in the relevant Issue or Discussion.
   - Example: If two contributors disagree on a PR’s wording, maintainers may merge a compromise version after discussion.
 - **Step 4: Enforcement**:
-  - Violations of the Code of Conduct (e.g., harassment) are addressed with warnings, content removal, or bans, as outlined in [CODE_OF_CONDUCT.md](/community/CODE_OF_CONDUCT).
+  - Violations of the Code of Conduct (e.g., harassment) are addressed with warnings, content removal, or bans, as outlined in [CODE_OF_CONDUCT.md](/community/CODE_OF_CONDUCT.md).
 
 ## Community Engagement
 
@@ -119,7 +119,7 @@ DTE thrives on community input. To participate:
 - **Slack**: Join [datatrustengineering]([Slack Invite Link]) for real-time collaboration (#contributions, #trust-dashboard).
 - **X**: Share your contributions with #DTERevolution or tag @bbrewer_infolib.
 - **Good First Issues**: Start with tasks tagged “good first issue” (e.g., typo fixes, case studies) to build skills and join the community.
-- **Recognition**: Contributors are listed in [CONTRIBUTORS.md](/CONTRIBUTORS) and highlighted in Slack or X for impactful work.
+- **Recognition**: Contributors are listed in [CONTRIBUTORS.md](/CONTRIBUTORS.md) and highlighted in Slack or X for impactful work.
 
 ## Evolving Governance
 

docs/patterns/USE_CASES.md

@@ -7,7 +7,7 @@ markup: "markdown"
 
 ## Data Trust Engineering (DTE) Use Cases and Trust Dashboard
 
-Welcome to the **Data Trust Engineering (DTE) Use Cases** and **Trust Dashboard**, flagship artifacts of the Data Trust Engineering movement. These open-source tools and examples embody DTE’s principles of trust, engineering rigor, and AI-readiness as outlined in the [Data Trust Manifesto](../Manifesto).
+Welcome to the **Data Trust Engineering (DTE) Use Cases** and **Trust Dashboard**, flagship artifacts of the Data Trust Engineering movement. These open-source tools and examples embody DTE’s principles of trust, engineering rigor, and AI-readiness as outlined in the [Data Trust Manifesto](../Manifesto.md).
 ---
 
 ## Mission for Examples & Design Patterns
@@ -428,7 +428,7 @@ models:
 ---
 
 ## License
-MIT License — see [LICENSE.md](../LICENSE).
+MIT License — see [LICENSE.md](../LICENSE.md).
 
 ---