[a-51-50]

Purpose

Add a safe, free GitHub Actions workflow to automatically verify and close Issue #3 only when the three specifically recorded original cofounder accounts each personally accept the same pinned policy revision.

Files

• .github/founder-roster.json — three seats, with a-51-50 plus two intentional null placeholders. Auto-closing is disabled until both genuine original founder GitHub handles are configured via an authorized PR. Do not guess who they are.
• scripts/founder-adoption-validator.mjs, scripts/founder-adoption.mjs — compare actual GitHub numeric account IDs, require the exact personal statement and policy commit d56279b4f3c25dd8f9e68699d61be23a0c7a6b07, and process the issue safely.
• .github/workflows/founder-adoption.yml — comment creation/edit/deletion, issue edits/reopening, roster changes, and manual dispatch trigger validation. Never grants organizational access.
• 13 unit tests, a PR test workflow, README and guidance in FOUNDER_ADOPTION_AUTOMATION.md.

Once the two actual handles are configured

• Each of the three must personally comment in Issue Three equal OpenDKG cofounders — personal adoption of shared terms #3 using their own account; organization membership is not required to comment.
• Existing valid current-revision acceptance by a-51-50 should be counted, not re-signed.
• After the third valid acceptance, the Action writes a public record with comment links, account IDs, body hashes, version and UTC time, adds founders:agreement-complete, and closes the issue.
• If a later edit/deletion invalidates the completion, it reopens the issue and removes the label; re-signing can produce a new, distinct evidence receipt.

Safeguards and limitations

• No auto-close with unconfigured founder roster. Random users or GitHub bot comments cannot fill a founding seat.
• GitHub Issue comments are editable/deletable; a bot record is not a legally qualified electronic signature or absolute tamper-proof evidence.
• The workflow has only issues: write and contents: read; never invites members, assigns Owner/Admin, or allocates personal legal liability.
• The Contributor Agreement and Governance documents are unchanged; the acceptance commit remains the existing pinned revision.

Please review the code and tests before merging. After this PR merges, supply the two actual cofounder GitHub usernames so they can be recorded via a reviewed follow-up change.