sweep4: add C-A-G-M files

Generated by Mistral Vibe.
Co-Authored-By: Mistral Vibe <vibe@mistral.ai>

Author: hyperpolymath

.github/CODEOWNERS

@@ -0,0 +1,9 @@
+# Code Owners
+
+# Default: All contributors with write access are code owners
+* @metadatastician
+
+# For specific paths, add explicit owners below
+# Example:
+# /src/* @team-lead
+# /docs/* @docs-maintainer

.github/funding.yml

@@ -0,0 +1,4 @@
+# Funding Configuration
+# See: https://docs.github.com/en/repositories/managing-your-repositorys-custom-fields/displaying-a-sponsor-button-in-your-repository
+
+github: metadatastician

GOVERNANCE.md

@@ -0,0 +1,60 @@
+# Governance
+
+## Overview
+
+This project is governed by the following principles and structures to ensure transparent, inclusive, and effective decision-making.
+
+## Roles and Responsibilities
+
+### Maintainers
+
+Maintainers are responsible for:
+- Reviewing and merging pull requests
+- Managing releases and versioning
+- Ensuring code quality and standards
+- Triaging issues and bug reports
+- Community engagement and support
+
+### Contributors
+
+Contributors are expected to:
+- Follow the code of conduct
+- Submit well-documented pull requests
+- Write tests for new functionality
+- Maintain existing tests
+- Update documentation as needed
+
+## Decision Making
+
+### Minor Changes
+- Can be made by any maintainer
+- Include bug fixes, documentation updates, dependency updates
+
+### Major Changes
+- Require discussion in issues or pull requests
+- Include new features, architectural changes, API changes
+- Need approval from at least 2 maintainers
+
+### Breaking Changes
+- Require RFC (Request for Comments) process
+- Need approval from majority of maintainers
+- Must include migration guide
+
+## Code of Conduct
+
+All participants are expected to follow our Code of Conduct. Violations can be reported to the maintainers.
+
+## Communication
+
+- **Issues**: For bug reports and feature requests
+- **Discussions**: For questions and general discussion
+- **Pull Requests**: For code contributions
+
+## Licensing
+
+All contributions are made under the terms of the repository's LICENSE file.
+By submitting a pull request, you agree to license your contributions accordingly.
+
+---
+
+*Last updated: 2026-07-18*

MAINTAINERS

@@ -0,0 +1,43 @@
+# Maintainers
+
+This file lists the current maintainers of this project.
+
+## Active Maintainers
+
+| Name | GitHub | Role | Since |
+|------|--------|------|-------|
+| Metadatastician | @metadatastician | Primary | Project Start |
+
+## Emeritus Maintainers
+
+None at this time.
+
+## Becoming a Maintainer
+
+To become a maintainer:
+
+1. Demonstrate consistent, high-quality contributions
+2. Show understanding of the project's goals and architecture
+3. Be active in code reviews and community discussions
+4. Be nominated by an existing maintainer
+5. Be approved by consensus of existing maintainers
+
+## Maintainer Responsibilities
+
+- Reviewing and merging pull requests
+- Managing releases
+- Triaging issues
+- Enforcing code standards
+- Mentoring new contributors
+- Participating in decision-making
+
+## Maintainer Expectations
+
+- Respond to issues and PRs in a timely manner
+- Follow the code of conduct
+- Be transparent in decision-making
+- Communicate clearly and respectfully
+
+---
+
+*Last updated: 2026-07-18*