License hygiene before wider public promotion

[happysnaker]

Context

RDLeader is public for architecture, packaging, QA evidence, fake-data demos, and sponsorware visibility, but the repository still does not publish a project-specific root LICENSE file.

That is acceptable while the DevPlan-derived feature bundle is still being sanitized, but it becomes a blocker before broader reuse-oriented promotion because outside users need to know what they may do with the public code and docs.

Current public evidence

Decision docs already published:

• License decision note: https://github.com/happysnaker/RDLeader/blob/main/docs/public/license-decision.md
• License decision packet: https://github.com/happysnaker/RDLeader/blob/main/docs/public/license-decision-packet.md
• README license / reuse section: https://github.com/happysnaker/RDLeader#license--reuse-status
• Support / sponsor route: https://happysnaker.github.io/support/#from-rdleader
• Sponsor one-pager: https://github.com/happysnaker/happysnaker/releases/tag/v2026.07-sponsor-one-pager

Current GitHub metadata check:

gh repo view happysnaker/RDLeader --json licenseInfo --jq .licenseInfo

Expected current result: null / no recognized license.

Decision needed

Choose one posture intentionally:

1. Apache-2.0 — permissive reuse plus explicit patent grant; currently the non-binding recommendation in the decision packet if broader reuse is intended.
2. MIT — simpler permissive reuse, but no explicit patent grant.
3. AGPL / copyleft — if network/service derivatives should stay open.
4. Source-available for now — if the public repo should remain visible while DevPlan-derived code is still too sensitive to license for reuse.

Definition of done

• Choose license direction intentionally.
• If open-source reuse is intended, add a root LICENSE file.
• Make README License / reuse status match the chosen posture.
• Update docs/public/license-decision.md and docs/public/license-decision-packet.md if the recommendation changes.
• Confirm GitHub recognizes the license metadata when applicable.
• Comment here with the decision and evidence.
• Do not imply unrestricted reuse until the license is published.

Guardrails

• Do not add a root LICENSE automatically without owner decision.
• Do not imply a license grants access to private DevPlan artifacts, credentials, live integration logs, app IDs, open IDs, chat IDs, QR artifacts, or internal documents.
• If asked by contributors or curators before this is resolved, point them to the decision note and say reuse is not finalized yet.

Current recommendation

Use Apache-2.0 only if the intent is permissive external reuse of the public repository. Otherwise keep the repository source-available for now and revisit after more DevPlan sanitization lands.

This issue is a decision tracker, not a unilateral license change.

10-second support router

If you are not sure whether to tip, inspect proof, buy a review, or fund license-posture clarification, start here: https://happysnaker.github.io/support/#sponsor-router. Support does not imply RDLeader reuse rights.

Support / outreach qualification

Before posting a sponsor/support ask, tester request, or external follow-up, use the sponsor conversion scorecard: https://github.com/happysnaker/happysnaker/blob/master/docs/sponsor-conversion-scorecard.md

Classify the situation as Hot / Warm / Nurture / No-send first. No-send blocks generic donation or proof bumps when timing, proof, privacy, or license posture is weak.

Do not paste private logs, credentials, QR codes, payment screenshots, internal URLs, or raw live integration output in public issues.

[happysnaker]

Added explicit public license/reuse status in README and a decision note in docs/public/license-decision.md (commit 8f55b24). The repo now avoids implying unrestricted reuse while the final license posture is undecided.

[happysnaker]

Added a non-binding license recommendation memo in commit 44392f7.\n\nSummary:\n- If RDLeader should become a normal permissive open-source project for outside reuse, Apache-2.0 is the recommended default because it is permissive and includes an explicit patent grant.\n- If the DevPlan-derived feature bundle should remain conservative while more public-safe slices are separated, keep it source-available for now and revisit later.\n- This does not choose the license automatically; no LICENSE file was added.\n\nCI passed: https://github.com/happysnaker/RDLeader/actions/runs/28957563517