Upgrade GitHub trust, documentation, and contribution system

[MEHuggins]

Purpose

Rebuild the public GitHub experience around the verified scale, operating safeguards, trust methodology, and human-controlled review model of the 4th Wave AI feed system.

This is a documentation and repository-governance upgrade only. It does not change collector code, source configuration, generated feeds, workflows, production output, or main directly.

Changes

• Rewrites README.md around the full intelligence system rather than the outdated five-frontier framing.
• Replaces shrinking workflow-run-count language with durable evidence guidance.
• Documents the verified July 28, 2026 registry snapshot of 111 intelligence areas and 650 configured source entries.
• Adds TRUST.md with source authority, runner reachability, parser compatibility, freshness, health, product quality, claim discipline, and falsifier rules.
• Adds docs/ARCHITECTURE.md with the registry-to-feed pipeline, single-writer discipline, health model, branch model, and rollback design.
• Adds docs/OPERATIONS.md with safe repair, live-testing, README-truth, health-response, artificial-womb audit, post-merge, and decision-ledger procedures.
• Strengthens CONTRIBUTING.md with evidence requirements and generated-file discipline.
• Adds SECURITY.md.
• Adds a forensic pull-request template.
• Adds evidence-based issue forms for source proposals and broken/degraded sources.

Exact diff

Nine intentional files:

1. .github/ISSUE_TEMPLATE/broken-source.yml
2. .github/ISSUE_TEMPLATE/source-proposal.yml
3. .github/PULL_REQUEST_TEMPLATE.md
4. CONTRIBUTING.md
5. README.md
6. SECURITY.md
7. TRUST.md
8. docs/ARCHITECTURE.md
9. docs/OPERATIONS.md

No generated feeds, compressed outputs, health snapshots, archives, registry changes, or Python cache files are included.

Relationship to PR #10

This PR does not merge, modify, close, or absorb PR #10. The new README accurately describes PR #10 as a separate unmerged observability repair. Merge order should be reviewed because public health links and status language may evolve after the PR #10 decision.

Validation performed

• Compared the branch against current main.
• Verified the branch is ahead by nine documentation-only commits and behind by zero.
• Verified the diff contains exactly the nine files listed above.
• Verified all new README relative links point to files included in this branch or existing repository paths.

Needs review

• Confirm the July 28, 2026 snapshot language and whether source entries should be described as “configured,” “reviewed,” or another approved term.
• Confirm the public coverage-family wording.
• Confirm the BSL-to-Apache description against the exact license text.
• Validate GitHub issue-form YAML through CI or GitHub rendering.
• Decide whether this PR should merge before or after the feed-health observability decision.

Falsifier

This upgrade fails if the public README or governance documents make a material claim that cannot be traced to the current registry, workflows, repository state, or a dated verified snapshot.

Rollback

Close this draft PR without merging. main remains unchanged.

Approval gate

Draft only. No merge or publication without Michael’s explicit approval.