README currently says license TBD.
Recommendation: Apache-2.0.
Reasoning. The rishta runtime is explicitly intended to be embedded in other systems (per the v0.10 roadmap entry: "compile-to-Python: embed the رشتہ runtime in existing Python codebases"). When downstream code embeds a runtime, the patent grant in Apache-2.0 earns its weight. Cryptographic-and-lineage framing is part of the picture, but the deciding factor is the embedding intent, not the crypto surface.
Action
Context
Tracked in the distribution playbook at adiled/distribution. The Apache-2.0 recommendation here is preserved (unlike for ccft and orchd, which were walked back to MIT) because the embedding intent is real and documented.
~ distribution team
README currently says license TBD.
Recommendation: Apache-2.0.
Reasoning. The rishta runtime is explicitly intended to be embedded in other systems (per the v0.10 roadmap entry: "compile-to-Python: embed the رشتہ runtime in existing Python codebases"). When downstream code embeds a runtime, the patent grant in Apache-2.0 earns its weight. Cryptographic-and-lineage framing is part of the picture, but the deciding factor is the embedding intent, not the crypto surface.
Action
LICENSE(Apache-2.0).Context
Tracked in the distribution playbook at
adiled/distribution. The Apache-2.0 recommendation here is preserved (unlike for ccft and orchd, which were walked back to MIT) because the embedding intent is real and documented.~ distribution team