feat: documents and session tokens

spec/14-rights.md

@@ -2,7 +2,7 @@
 
 What a team may do with a paper depends on how it holds the paper, and AI processing is now a use that licenses name.
 Every witness carries a rights record, every stage declares the uses it needs, and a stage runs only when the rights allow them.
-Nothing here is legal advice; the defaults are proposals for counsel to set.
+Nothing here is legal advice: the defaults are a starting point that each team reviews with its own counsel.
 
 ## 14.1 The rights record
 
@@ -33,7 +33,7 @@ A policy, `scienting-policy/1`, is a project owner's signed decision: `applies_t
 It applies from `at` until `valid_until`.
 
 A node established from several witnesses takes the most restrictive of their uses: `false` if any is false, else `"unknown"` if any is unknown, else `true`.
-That combining rule is proposed for counsel to confirm.
+This is the default combining rule.
 
 ## 14.3 Stages
 
@@ -41,13 +41,13 @@ That combining rule is proposed for counsel to confirm.
 A stage may run on a processor when every listed use is `true`, the processor is among those allowed, if any are listed, and the pair `ai/<purpose>/<processor>` is `true`.
 When a check fails, the refusal lists what is lacking: a use or pair that is `false` by name, one that is unknown with a trailing `?`, and a disallowed processor as `processor:<name>`.
 
-[registry/stages/scienting-stages-default.json](../registry/stages/scienting-stages-default.json) holds the design's proposed defaults; a team replaces the file, not the code.
+[registry/stages/scienting-stages-default.json](../registry/stages/scienting-stages-default.json) holds a default set; a team replaces the file, not the code.
 Rights are checked when a stage runs and again whenever text is served.
 Every derived artifact records the rights record and use it was made under, so it can be listed and purged when a basis ends.
 
 ## 14.4 Backends and profiles
 
-A backend's code and weights can be licensed differently, and the weights decide whether a paying team may use it.
+A backend's code and weights can be licensed differently, and the weight license may exclude commercial or competing use.
 `scienting-backend/1` declares a backend's `code_license`, its `weights` with their licenses, and the `conditions` they impose:
 
 | Condition | Met when the team profile |