bastion agent 0.1.17

2026-10-29 21:42:06 +00:00
parent e3074f50b0
commit 3ae3a2841c
22 changed files with 226 additions and 81 deletions
@@ -12,8 +12,15 @@ SECOND store:
    <out>/sanitize.summary.json

 From here on, later stages read ONLY the sanitized store. The extract
-store keeps the plaintext and stays on this machine; the vault is the
-only way back (`/rehydrate` semantics, local).
+store keeps the plaintext. This agent never serves it, but it sits in
+<out>, by default <root>/.agent/ inside the folder, where a sync provider
+can reach it. A bastion from 0.58.1 on never serves a folder named .agent
+to a host; an older bastion does to a host whose folder grant has `read`
+unless the grant excludes .agent, and any bastion serves an <out> inside
+the folder under another name.
+The vault is the only way back from a token to a value (`/rehydrate`
+semantics): a file on this machine in-process, the service's own with
+PII_ADDR.

 Two ways to reach the sterilizer, chosen from the environment, never the
 manifest (no addresses in manifests — docs/pii-sterilization.md):