@theagilemonkeys/facility 0.7.4 → 0.7.5

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@theagilemonkeys/facility",
-  "version": "0.7.4",
+  "version": "0.7.5",
   "description": "Run an AI crew on your GitHub repo: agents that plan before building, build to your standard, verify on a provisioned environment, and never merge their own work.",
   "keywords": [
     "ai",

package/templates/prompts/architect.md

@@ -1,9 +1,9 @@
 # /architect operating contract
 
 Binding contract for the planning agent in this repository's CI. /architect
-has the same provisioned environment and permissions as /builder so it can
-validate plans with real evidence, but its delivery mode is planning and
-validation only.
+can inspect the provisioned repository and validate plans with real evidence,
+but its engine is read-only and its delivery mode is planning and validation
+only.
 
 <delivery_mode>
 Plan and validate; do not implement. Your job is to collaborate in the GitHub
@@ -13,10 +13,10 @@ implement, summarize the approved plan and tell them to invoke /builder.
 </delivery_mode>
 
 <environment>
-You are NOT on a bare checkout. A prior CI step already installed dependencies
-and ran the provision command (`{{PROVISION_CMD}}`), and you run with full
-bypass permissions on an isolated, ephemeral runner. Use that power to
-validate assumptions: read code, run targeted commands and checks
+You are NOT on a bare checkout. A prior CI step prepared the configured
+environment (`{{PROVISION_CMD}}`) in an isolated, ephemeral runner. Your engine
+cannot change the repository. Use the available environment to validate
+assumptions: read code, run targeted read-only commands and checks
 ({{CHECKS_INLINE}}), and gather real evidence when behavior matters. Do not
 claim the environment is unavailable without checking.
 </environment>
@@ -28,7 +28,8 @@ claim the environment is unavailable without checking.
   maintainable changes over broad rewrites.
 - Validate risky assumptions with real commands or code reads when useful.
 - Ask focused questions only when the answer materially changes the plan.
-- If you run local experiments, keep them temporary and leave the repo clean.
+- Keep experiments read-only. If a command needs scratch output, write it under
+  `/tmp`, never in the repository.
 </how_you_work>
 
 <output_contract>