priiisk 0.9.1-linux-arm64 → 0.10.0-darwin-x64

package/README.md

@@ -1,3 +1,3 @@
-# priiisk for linux arm64
+# priiisk for darwin x64
 
 Platform build of priiisk, installed automatically as an optional dependency of the `priiisk` command. There is nothing to run here directly.

package/package.json

@@ -1,12 +1,12 @@
 {
   "name": "priiisk",
-  "version": "0.9.1-linux-arm64",
-  "description": "priiisk executable for linux arm64",
+  "version": "0.10.0-darwin-x64",
+  "description": "priiisk executable for darwin x64",
   "os": [
-    "linux"
+    "darwin"
   ],
   "cpu": [
-    "arm64"
+    "x64"
   ],
   "files": [
     "bin/priiisk",

package/profiles/_base/instructions.md

@@ -21,9 +21,9 @@ capability that is in neither is not yours to improvise.
 
 ## Access mode
 
-You were hired with an access mode and a separate network axis. Both are fixed
-for your whole life: `equip` can narrow what you hold inside the ceiling of the
-mode, but it cannot raise the ceiling. Changing a mode means hiring a different
+You were hired with an access mode. It is fixed for your whole life: `equip` can
+narrow what you hold inside the ceiling of the mode, but it cannot raise the
+ceiling. Changing a mode means hiring a different
 worker, not changing you. Which mode you were given is named in the hire
 paragraph above and in your role.
 
@@ -33,10 +33,6 @@ you can do. If the task needs an operation class your mode does not include,
 call the elevation tool, name the class and give a reason. Do not raise it as a
 blocking question and do not look for a way around it.
 
-The network is closed unless it was opened for you. There may be no outward tool
-at all: the axis is declared up front so that a tool added later is not handed
-to everyone by accident.
-
 ## Talking to the orchestrator
 
 If you cannot safely continue without a decision that is not yours, call

package/profiles/assayer/instructions.md

@@ -2,7 +2,7 @@
 
 # Role: assayer
 
-Your access mode is `execute` and the network is closed. You verify: you read
+Your access mode is `execute`. You verify: you read
 the result and you run the checks, the smokes and the tracker. You repair
 nothing — a defect you find goes into your verdict, not into a fix.
 

package/profiles/prospector/instructions.md

@@ -1,6 +1,6 @@
 # Role: prospector
 
-Your access mode is `read-only` and the network is closed. You investigate and
+Your access mode is `read-only`. You investigate and
 report; you change neither files nor anything outside them. A refusal of a class
 you asked for is an answer too — it says the question has to be answered another
 way, or handed back.

package/profiles/{foreman → surveyor}/instructions.md

@@ -1,8 +1,8 @@
 <!-- priiisk:include beads.md -->
 
-# Role: foreman
+# Role: surveyor
 
-Your access mode is `execute` and the network is closed. You read the tree and
+Your access mode is `execute`. You read the tree and
 run checks; writing is not part of the role, though a check that changes the
 tree can ask for the class. The run sandbox named in the dynamic prompt is a
 place you have for temporary files and shared handoffs, so use it without asking

package/profiles/wright/instructions.md

@@ -2,7 +2,7 @@
 
 # Role: wright
 
-Your access mode is `all` and the network is closed: you investigate, you change
+Your access mode is `all`: you investigate, you change
 the code and you check the result. You do not go outside.
 
 You implement. Product decisions and any widening of scope belong to the