8000 docs: establish MIGI project registry and version-control policy by QSTARMIGI · Pull Request #16 · QSTARMIGI/MIGI · GitHub
[go: up one dir, main page]

Skip to content

docs: establish MIGI project registry and version-control policy - #16

Draft
QSTARMIGI wants to merge 3 commits into
mainfrom
docs/version-control-audit-v1
Draft

QSTARMIGI wants to merge 3 commits into
mainfrom
docs/version-control-audit-v1

Conversation

@QSTARMIGI
Copy link
Copy Markdown
Owner

Summary

Establishes an evidence-based starting point for the MIGI version-control audit.

Changes

  • Add MIGI_PROJECT_REGISTRY.md with the inspected canonical repository facts, branch snapshot, PR evidence, account-repository inventory, architecture-to-repository mapping, and audit backlog.
  • Add docs/engineering/version-control-policy.md with branch, semantic-versioning, PR acceptance, reproducibility, release, provenance, and recovery rules.

Truth-audit boundaries

  • Repository metadata and README/package metadata were inspected through GitHub.
  • The registry explicitly labels unverified ownership, upstream/fork provenance, CI, tags, and cross-project integration as needing audit.
  • Historical PR merge descriptions are marked for re-verification rather than presented as freshly confirmed.
  • No source code or existing default-branch content is changed by this PR; it adds documentation on a separate branch.

Review checklist

  • Check inventory and stale references for accuracy.
  • Verify PR merge states and branch divergence.
  • Audit CI, tests, tags, dependency lockfiles, and repository provenance.
  • Approve and merge only after review.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant

0