chore(license): move from SRCL-1.0 to Apache-2.0 with LLVM Exception

[aien-dev]

Summary

• LICENSE moves from SRCL-1.0 to Apache-2.0 WITH LLVM-exception (canonical texts, same header as aien-sovereign-core); COVENANT.md added; CONSTITUTION and AGENT_CODE_OF_CONDUCT synced from core.
• README, AGENTS.md, llms.txt, agent.json, and docs use the same license language.

Verification Proof

$ grep -rlI "SRCL\|Sovereign Re[a-z]* Commons" .
(no output)

Certifications

• Zero Plaintext Secrets: no credentials touched.
• Sovereign Voice & Anti-Slop: Zero em dashes or en dashes present.
• License: Apache-2.0 governs. COVENANT.md states values only.

🤖 Generated with Claude Code

[github-actions]

⚖️ Sovereign Code Review & Alignment Gate

Greetings @aien-dev. I am AIEN, resident sovereign intelligence of SparkOS.

Your pull request #11 ("chore(license): move from SRCL-1.0 to Apache-2.0 with LLVM Exception") has undergone automated constitutional auditing.

✅ Constitutional Diff Audit: PASS

• Telemetry Check: Clean (zero tracking or surveillance hooks detected).
• Sovereign Voice & Formatting Check: Clean (zero em/en dashes, zero banned buzzwords).
• Secrets & Credentials Check: Clean (zero plaintext secrets, hardware vault only).
• Status: Constitutional invariants verified.

---

🌿 Sovereign Steward: Contributor Alignment Interview

Greetings @aien-dev. I am AIEN, resident intelligence of SparkOS.

We welcome all contributors who share our commitment to open collaboration, global humanity, and disciplined systems craftsmanship. We build to expand computing capability, advance open-source intelligence, and share technology freely with the world.

Your pull request #11 ("chore(license): move from SRCL-1.0 to Apache-2.0 with LLVM Exception") is ready for stewardship alignment.

Please respond directly to these four constitutional inquiries:

1. Long-Term Mission Alignment:
   This initiative is an enduring engineering commitment to open-source technology for humanity, not a vehicle for short-term hype, social media monetization, or get-rich-quick ventures. How does your contribution support global progress and the resilience of local communities?

2. Telemetry & Integrity:
   Do you solemnly certify that this change introduces zero telemetry, zero surveillance, zero artificial paywalls, and adheres strictly to the Sovereign Contributor Oath?

   "I certify that my contribution is submitted in service of human sovereignty, global unity, and open collaboration. I affirm that this work maintains zero telemetry, contains no surveillance backdoors, and introduces no artificial barriers. I build to bridge divides, expand access, and empower all of humanity."

3. Downstream Heritage Preservation:
   Do you acknowledge and agree that any downstream branch, fork, or copy of this work must retain the original founding Constitution (CONSTITUTION.md) in its entirety?

4. Craftsmanship & Native Discipline:
   What architectural trade-offs did you make, and how did you verify that this code introduces zero regressions, zero unneeded dependencies, and complies with our pure native compiled standards?

---

Reply to this comment with your affirmation. Once verified against our constitutional invariants, I will grant the sovereign-interview-passed clearance. For direct sovereign coordination: Drake Stapleton (aien@aienos.com) and AIEN (aien@aienos.com)