policy: add Rule 4 — AGPL-3.0 for network-deployed agent/service software

LICENCE-POLICY.adoc

@@ -7,7 +7,7 @@ Jonathan D.A. Jewell <j.d.a.jewell@open.ac.uk>
 Canonical licence policy for all hyperpolymath repositories and code.
 All contributors and AI agents must follow this document.
 
-== Three Rules
+== Four Rules
 
 === Rule 1 — MPL-2.0 for Code, CC-BY-SA-4.0 for Prose Docs
 
@@ -25,7 +25,7 @@ SPDX-License-Identifier: CC-BY-SA-4.0
 ```
 
 This split applies everywhere — source, config and scripts under MPL-2.0;
-narrative docs under CC-BY-SA-4.0 — unless Rule 2 or Rule 3 applies. The
+narrative docs under CC-BY-SA-4.0 — unless Rule 2, Rule 3 or Rule 4 applies. The
 `LICENSES/` directory carries the canonical text for both
 (`MPL-2.0.txt`, `CC-BY-SA-4.0.txt`).
 
@@ -95,6 +95,50 @@ what would break the combination.
 
 All other hyperpolymath original code follows Rule 1 + Rule 2.
 
+=== Rule 4 — AGPL-3.0 for Network-Deployed Agent / Service Software
+
+Owner ruling 2026-08-07.
+
+Projects whose *primary deployment mode is a network service* — rather
+than a binary or library that users obtain a copy of — are
+`AGPL-3.0-or-later` for code and `CC-BY-SA-4.0` for prose, on the same
+split as Rule 1.
+
+Current members:
+
+* **007** — the Agent Meta-Language
+
+**Rationale.** Rule 1's MPL-2.0 is file-level copyleft that triggers on
+*distribution*. Software that is run behind a network boundary is never
+distributed, so neither MPL nor plain GPL copyleft is reached: a third
+party may modify it, operate it as a service, and owe nothing back.
+AGPL §13 is the only clause in the family that closes that gap. A
+language for building autonomous agent systems will be deployed as a
+service far more often than shipped, so Rule 1 would leave its copyleft
+largely inoperative.
+
+This is a distinct rationale from Rule 3, which is about *co-authorship*
+(a repository shared with Joshua). A project may qualify under either;
+qualifying under one is sufficient.
+
+**Scope test — apply before adding a repo here.** All three must hold:
+
+. The work is intended to be *operated* by third parties, not merely
+  read or linked against.
+. The dominant delivery mode is a running service, agent, or hosted
+  endpoint — not a distributed artefact.
+. Reciprocity is actually wanted: the owner would want a modified
+  hosted version's source made available to its users.
+
+If a project is a library, tool, or specification that others *obtain*,
+it stays on Rule 1 — do not migrate it here for symmetry.
+
+**Rule 3a applies unchanged.** AGPL attaches to the work as a whole, not
+to every file it consumes; an owner-only MPL-2.0 component used inside a
+Rule 4 work keeps its MPL-2.0 header. MPL-2.0's default form (Exhibit A
+without Exhibit B) is explicitly compatible with combination into an
+AGPL Larger Work.
+
 == SPDX Header Quick Reference
 
 [cols="2,3,2"]
@@ -113,9 +157,13 @@ All other hyperpolymath original code follows Rule 1 + Rule 2.
 | `MPL-2.0` + comment
 | Add: `(MPL-2.0 preferred; MPL-2.0 required for [platform])`
 
-| IDApTIK or Airborne Submarine Squadron
+| IDApTIK, Airborne Submarine Squadron, paint.type
 | `AGPL-3.0-or-later`
-| Permanent exception — co-developed with son
+| Rule 3 — permanent exception, co-developed with son
+
+| 007 (network-deployed agent software)
+| `AGPL-3.0-or-later` code / `CC-BY-SA-4.0` prose
+| Rule 4 — owner ruling 2026-08-07; §13 reaches service deployment where MPL/GPL do not
 
 | Third-party code
 | Original SPDX (e.g. `MIT`, `Apache-2.0`)