Skip to content

docs: clarify TrustSignal/DeedShield relationship in README repo context#76

Closed
Copilot wants to merge 1 commit intocm/readme-links-masterfrom
copilot/sub-pr-71-another-one
Closed

docs: clarify TrustSignal/DeedShield relationship in README repo context#76
Copilot wants to merge 1 commit intocm/readme-links-masterfrom
copilot/sub-pr-71-another-one

Conversation

Copy link
Copy Markdown
Contributor

Copilot AI commented Mar 23, 2026

Summary

  • Updates "Current Repository Context" section in README.md to explicitly describe TrustSignal as the core platform and DeedShield as the initial property-record verification wedge/module built on top of it
  • Clarifies that DeedShield-named docs, monitoring rules, and watcher services in this repo scope to that property-record module only — not the broader platform

AI Disclosure (optional)

  • AI-assisted changes are included in this PR

Review Checklist

  • Human review requested
  • Tests added or updated where appropriate
  • No secrets, tokens, cookies, or raw PII were added to code, logs, fixtures, or docs
  • Security impact and remaining risks are described

📱 Kick off Copilot coding agent tasks wherever you are with GitHub Mobile, available on iOS and Android.

@vercel
Copy link
Copy Markdown

vercel bot commented Mar 23, 2026

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
api Ready Ready Preview, Comment Mar 23, 2026 8:26pm
trustsignal Ready Ready Preview, Comment Mar 23, 2026 8:26pm

Copilot AI changed the title [WIP] Fix repo-relative links in README docs: clarify TrustSignal/DeedShield relationship in README repo context Mar 23, 2026
Copilot AI requested a review from chrismaz11 March 23, 2026 20:24
@chrismaz11
Copy link
Copy Markdown
Collaborator

Closing as redundant. This draft sub-PR carries no unique diff beyond the existing README clarification already tracked on #71.

@chrismaz11 chrismaz11 closed this Mar 23, 2026
@chrismaz11 chrismaz11 deleted the copilot/sub-pr-71-another-one branch March 27, 2026 22:12
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.

2 participants