scriptoriumadmin/hypertwist
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

docs: add permissive/restrictive/no-grant clean-room reservoir taxonomy to intake doctrine

Browse source
This commit is contained in:
axiomlogicnexus 2026-06-24 08:13:54 +00:00
parent e13c4bc4c5
commit b3a1810276
1 changed files with 15 additions and 1 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

16
docs/HYPERTWIST_REPO_INTAKE_RETENTION_AND_PRODUCT_FIT_DOCTRINE_2026-05-14.md
View file

@ -511,12 +511,26 @@ Potentially useful later, but not active implementation scope now.
### Permissive route
A lower-friction incorporation path available when the repo posture allows it.
Even on a permissive route, a donor may still require clean-room handling if its
product identity (vocabulary, taxonomy, mascot, or distinctive workflow) is too
strong to import literally. This is a **permissive clean-room reservoir**:
legally reusable, but product-identity constrained.
### Restrictive route
A constrained path such as clean-room, sidecar, protocol boundary,
reference-only use, pattern-only use, donor-only deferral, or explicit
non-integration.
non-integration. Required for copyleft, source-available, non-free, or custom
licenses. This is a **restrictive clean-room reservoir**: legal or custody
constraints block direct runtime import.
### No-grant route
When no explicit repo-root license grant is present, default copyright applies
and donor text/code cannot be copied. If the behavior is valuable and
describable generically, route through clean-room or pattern-only handling
rather than hard-omitting. This is a **no-grant clean-room reservoir**.
Do not treat missing license as an automatic exclusion.
### Not worth integrating