@amalgm/shell 0.1.164-preview.44185399271 → 0.1.164-preview.44991101539

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (1032) hide show
  1. package/dist/accepted-fold.js +0 -36
  2. package/dist/accepted-tail.js +0 -3
  3. package/dist/accepted-view.js +0 -1
  4. package/dist/agent-execution.js +0 -2
  5. package/dist/agent-instructions.js +0 -6
  6. package/dist/apply-attempt-memory.js +0 -5
  7. package/dist/apply-control.js +0 -50
  8. package/dist/apply-displaced-tree.js +0 -51
  9. package/dist/apply-durability.js +0 -16
  10. package/dist/apply-enter-build.js +2 -46
  11. package/dist/apply-enter-plan.js +0 -59
  12. package/dist/apply-fingerprint.js +0 -21
  13. package/dist/apply-git-held.js +4 -90
  14. package/dist/apply-git-storage.js +2 -38
  15. package/dist/apply-kept.js +0 -40
  16. package/dist/apply-local-work.js +0 -12
  17. package/dist/apply-map.js +18 -122
  18. package/dist/apply-showing.js +0 -71
  19. package/dist/apply-shown-again.js +0 -22
  20. package/dist/apply-spelling.js +0 -31
  21. package/dist/apply-trash-keep.js +5 -28
  22. package/dist/apply-window-cargo.js +0 -55
  23. package/dist/apply-window-ground.js +9 -71
  24. package/dist/apply-window-host.js +42 -421
  25. package/dist/apply-window-lane.js +0 -73
  26. package/dist/apply-window-line.js +0 -33
  27. package/dist/apply-window-recovery.js +0 -26
  28. package/dist/apply-window-reveal.js +0 -32
  29. package/dist/apply-window-rows.js +0 -53
  30. package/dist/apply-window-saves.js +0 -184
  31. package/dist/apply-window-store.js +0 -61
  32. package/dist/apply-window-verify.js +0 -42
  33. package/dist/authority-binding.js +0 -28
  34. package/dist/authorization/device-key.js +0 -1
  35. package/dist/authorization/index.js +0 -2
  36. package/dist/authorization/issuer.js +0 -1
  37. package/dist/authorization/key-store.js +0 -1
  38. package/dist/authorization/native-keyring.js +0 -1
  39. package/dist/authorization/recovery-client.js +0 -2
  40. package/dist/authorization/recovery-host.js +0 -1
  41. package/dist/authorization/recovery.js +0 -3
  42. package/dist/authorization/registration-http.js +0 -2
  43. package/dist/authorization/secret-process.js +0 -2
  44. package/dist/authorization/setup-http.js +0 -1
  45. package/dist/automations-cli-host.js +0 -2
  46. package/dist/background-error.js +0 -5
  47. package/dist/baseline-content.js +0 -3
  48. package/dist/billing/cli.js +266 -0
  49. package/dist/billing/mount.js +33 -0
  50. package/dist/billing/tools.js +138 -0
  51. package/dist/boot-identity.js +0 -12
  52. package/dist/browser-host.js +0 -15
  53. package/dist/builtin-agents.js +0 -8
  54. package/dist/capture-work.js +0 -9
  55. package/dist/captured-rows.js +4 -6
  56. package/dist/cargo-group.js +0 -48
  57. package/dist/cargo-journal.js +0 -36
  58. package/dist/channel-session.js +0 -9
  59. package/dist/chat-composition.js +0 -4
  60. package/dist/chat-host.js +0 -4
  61. package/dist/chat-toolbox.js +0 -2
  62. package/dist/chat-tools.js +0 -3
  63. package/dist/cli-arguments.js +17 -3
  64. package/dist/cli-commands.js +272 -0
  65. package/dist/cli.js +36 -72
  66. package/dist/construct-apply-host.js +0 -24
  67. package/dist/construct-door.js +3 -15
  68. package/dist/construct-ledger.js +3 -21
  69. package/dist/construct-products.js +0 -7
  70. package/dist/content-cache-collection.js +1 -27
  71. package/dist/content-cache-fences.js +0 -30
  72. package/dist/content-cache-host.js +0 -216
  73. package/dist/content-cache-index.js +0 -24
  74. package/dist/content-cache-namespace.js +0 -52
  75. package/dist/content-cache-partials.js +0 -23
  76. package/dist/content-cache-retention.js +1 -53
  77. package/dist/content-capture-pool.js +6 -134
  78. package/dist/content-capture-worker.js +4 -14
  79. package/dist/content-clock.js +1 -177
  80. package/dist/content-direct.js +0 -39
  81. package/dist/content-failure.js +0 -8
  82. package/dist/content-qualification.js +0 -56
  83. package/dist/content-wire-codec.js +0 -8
  84. package/dist/credentials-host.js +0 -2
  85. package/dist/derived-relocation.js +0 -27
  86. package/dist/detection/accepted-result.js +0 -14
  87. package/dist/detection/admission-save.js +0 -10
  88. package/dist/detection/admission-units.js +3 -93
  89. package/dist/detection/alias-discovery.js +0 -19
  90. package/dist/detection/alias-examination.js +0 -22
  91. package/dist/detection/apply-ownership.js +4 -52
  92. package/dist/detection/basis-advanced.js +0 -11
  93. package/dist/detection/cached-replay.js +0 -20
  94. package/dist/detection/capture-outcome.js +0 -20
  95. package/dist/detection/container-membership.js +0 -19
  96. package/dist/detection/detect-cancelled.js +0 -3
  97. package/dist/detection/directory-proof.js +0 -20
  98. package/dist/detection/dispositions.js +0 -29
  99. package/dist/detection/examinations.js +0 -32
  100. package/dist/detection/ground-proof.js +20 -130
  101. package/dist/detection/ground-reader.js +0 -9
  102. package/dist/detection/identity-discovery.js +15 -60
  103. package/dist/detection/maintenance-sweep.js +1 -73
  104. package/dist/detection/notebook-basis.js +1 -5
  105. package/dist/detection/owed-examinations.js +0 -4
  106. package/dist/detection/owed-selection.js +14 -40
  107. package/dist/detection/policy-owed.js +165 -26
  108. package/dist/detection/racy-close.js +46 -0
  109. package/dist/detection/reconciliation-coverage.js +0 -4
  110. package/dist/detection/repository-state.js +6 -56
  111. package/dist/detection/reveal-save.js +0 -2
  112. package/dist/detection/root-examination.js +32 -105
  113. package/dist/detection/root-walk.js +98 -295
  114. package/dist/detection/runtime.js +57 -153
  115. package/dist/detection/scope-frame.js +1 -37
  116. package/dist/detection/scoped-identity-port.js +0 -21
  117. package/dist/detection/sealed-folders.js +57 -0
  118. package/dist/detection/skip-policy.js +185 -0
  119. package/dist/detection/spelled-lookup.js +0 -19
  120. package/dist/detection/storage-holder.js +60 -0
  121. package/dist/detection/thread-database.js +0 -9
  122. package/dist/detection/unread-content.js +0 -13
  123. package/dist/detection/unreadable.js +0 -3
  124. package/dist/detection/walk-law.js +0 -20
  125. package/dist/detection/walked-roots.js +0 -6
  126. package/dist/detection/withheld.js +0 -46
  127. package/dist/development/fly-guest.js +0 -3
  128. package/dist/development/fly.js +2 -11
  129. package/dist/development/profile.js +0 -8
  130. package/dist/drive/cloud-files/asks.js +5 -48
  131. package/dist/drive/cloud-files/binding.js +0 -14
  132. package/dist/drive/cloud-files/contents.js +14 -57
  133. package/dist/drive/cloud-files/door.js +5 -45
  134. package/dist/drive/cloud-files/paths.js +4 -37
  135. package/dist/drive/cloud-files/populated.js +0 -14
  136. package/dist/drive/cloud-files/reconcile.js +18 -97
  137. package/dist/drive/cloud-files/sync-root.js +7 -21
  138. package/dist/drive/cloud-files/turns.js +0 -25
  139. package/dist/drive/cloud-files/writes.js +19 -122
  140. package/dist/drive/computer.js +0 -19
  141. package/dist/drive/fuse-opens.js +0 -31
  142. package/dist/drive/fuse.js +23 -43
  143. package/dist/drive/kept.js +32 -80
  144. package/dist/drive/kernel.js +12 -24
  145. package/dist/drive/layout.js +31 -20
  146. package/dist/drive/mount.js +53 -125
  147. package/dist/drive/mountpoint.js +0 -19
  148. package/dist/drive/names.js +17 -0
  149. package/dist/drive/nfs/apple-double.js +4 -29
  150. package/dist/drive/nfs/attributes.js +3 -19
  151. package/dist/drive/nfs/handles.js +0 -37
  152. package/dist/drive/nfs/mount3.js +0 -4
  153. package/dist/drive/nfs/nfs3.js +4 -65
  154. package/dist/drive/nfs/rpc.js +0 -19
  155. package/dist/drive/nfs/server.js +0 -14
  156. package/dist/drive/nfs/xdr.js +0 -15
  157. package/dist/drive/nfs.js +34 -90
  158. package/dist/drive/operations.js +46 -120
  159. package/dist/drive/shelf.js +0 -12
  160. package/dist/drive-maps.js +54 -0
  161. package/dist/drive-program/client.js +128 -0
  162. package/dist/drive-program/ports.js +49 -0
  163. package/dist/drive-program/program.js +82 -0
  164. package/dist/drive-program/protocol.js +2 -0
  165. package/dist/durability-barrier.js +0 -60
  166. package/dist/entity-access-wire.js +0 -9
  167. package/dist/entity-channel-holdings.js +0 -17
  168. package/dist/entity-grant-watch.js +0 -8
  169. package/dist/entity-record-observability.js +0 -4
  170. package/dist/entity-record-saves.js +0 -23
  171. package/dist/entity-record-store.js +0 -51
  172. package/dist/error-facts.js +1 -3
  173. package/dist/faults/drain.js +2 -32
  174. package/dist/faults/queue.js +0 -22
  175. package/dist/faults/show.js +0 -6
  176. package/dist/file-time.js +21 -0
  177. package/dist/files-browser-host.js +15 -7
  178. package/dist/files-mcp-host.js +0 -6
  179. package/dist/files-observability.js +0 -1
  180. package/dist/files-program/client.js +90 -320
  181. package/dist/files-program/journeys.js +0 -4
  182. package/dist/files-program/program.js +67 -162
  183. package/dist/files-program/protocol.js +0 -5
  184. package/dist/files-register-host.js +8 -56
  185. package/dist/files-trace.js +0 -39
  186. package/dist/files-watch-host.js +226 -0
  187. package/dist/filesystem.js +0 -39
  188. package/dist/flush.js +0 -37
  189. package/dist/forward.js +0 -8
  190. package/dist/gateway.js +0 -9
  191. package/dist/git/ground-owners.js +0 -11
  192. package/dist/git/held-package.js +0 -43
  193. package/dist/git/home.js +79 -67
  194. package/dist/git/marker.js +0 -9
  195. package/dist/git/named-objects.js +0 -32
  196. package/dist/git/objects.js +0 -23
  197. package/dist/git/play.js +0 -42
  198. package/dist/git/quarantine.js +0 -47
  199. package/dist/git/rail.js +55 -286
  200. package/dist/git/read-state.js +8 -70
  201. package/dist/git/repository.js +0 -43
  202. package/dist/git/write-files.js +16 -84
  203. package/dist/git-binding.js +58 -80
  204. package/dist/git-cat-file.js +0 -18
  205. package/dist/git-command.js +1 -71
  206. package/dist/git-index-entries.js +0 -5
  207. package/dist/git-index-format.js +0 -71
  208. package/dist/git-install-lines.js +0 -2
  209. package/dist/git-launcher-process.js +0 -19
  210. package/dist/git-launcher.js +1 -33
  211. package/dist/git-proven-blobs.js +48 -0
  212. package/dist/graph-heads.js +0 -14
  213. package/dist/ground-basis.js +1 -183
  214. package/dist/ground-checkpoint-worker.js +0 -26
  215. package/dist/ground-checkpoints.js +0 -14
  216. package/dist/ground-contract.js +1 -43
  217. package/dist/ground-coordination.js +0 -82
  218. package/dist/ground-database.js +0 -88
  219. package/dist/ground-differences.js +0 -6
  220. package/dist/ground-holders.js +0 -8
  221. package/dist/ground-initialization-worker.js +0 -7
  222. package/dist/ground-initialization.js +0 -19
  223. package/dist/ground-install-saves.js +0 -15
  224. package/dist/ground-inventory-schema.js +3 -142
  225. package/dist/ground-marks.js +0 -16
  226. package/dist/ground-places.js +33 -0
  227. package/dist/ground-profile.js +0 -77
  228. package/dist/ground-reads.js +0 -58
  229. package/dist/ground-relations.js +0 -43
  230. package/dist/ground-root-index.js +0 -7
  231. package/dist/ground-row.js +5 -29
  232. package/dist/ground-save-ops.js +0 -14
  233. package/dist/ground-saver-worker.js +3 -56
  234. package/dist/ground-saver.js +0 -52
  235. package/dist/ground-store.js +10 -144
  236. package/dist/held-ground.js +60 -0
  237. package/dist/index.js +0 -1
  238. package/dist/initial-publication.js +0 -7
  239. package/dist/install-from-git.js +42 -0
  240. package/dist/installation/environment.js +8 -2
  241. package/dist/installation/lease.js +0 -3
  242. package/dist/installation/ownership.js +0 -13
  243. package/dist/installation/selection.js +0 -2
  244. package/dist/keychain/cli-io.js +0 -7
  245. package/dist/keychain/cli.js +0 -9
  246. package/dist/keychain/host.js +0 -7
  247. package/dist/keychain/http-mount.js +0 -10
  248. package/dist/keychain/key-wire.js +0 -8
  249. package/dist/keychain/presence-mac.js +0 -7
  250. package/dist/keychain/presence.js +0 -7
  251. package/dist/keychain/rail.js +0 -7
  252. package/dist/keychain/secret-apply.js +0 -11
  253. package/dist/keychain/shelf-from-ledger.js +0 -7
  254. package/dist/keychain/use-log.js +0 -6
  255. package/dist/keychain/vault-file.js +0 -7
  256. package/dist/line-judge.js +0 -41
  257. package/dist/line-loops.js +0 -3
  258. package/dist/link-target.js +0 -38
  259. package/dist/local-host.js +0 -16
  260. package/dist/loop-watch.js +0 -13
  261. package/dist/machine-host.js +36 -123
  262. package/dist/main.js +4 -5
  263. package/dist/materialize-records.js +109 -112
  264. package/dist/materialized-graph.js +0 -1
  265. package/dist/module-thread.js +0 -8
  266. package/dist/mount.js +0 -7
  267. package/dist/native/cloud-files.node +0 -0
  268. package/dist/native/windows-fs.node +0 -0
  269. package/dist/official-mcp-host.js +0 -2
  270. package/dist/on-demand-roots.js +0 -4
  271. package/dist/open-standing.js +0 -36
  272. package/dist/own-folders.js +56 -0
  273. package/dist/own-results.js +0 -31
  274. package/dist/package-pages.js +0 -13
  275. package/dist/patient-flush.js +0 -16
  276. package/dist/physical-path-witness.js +0 -28
  277. package/dist/placement-owed.js +0 -8
  278. package/dist/placement-tidy.js +0 -68
  279. package/dist/platform-product-host.js +0 -3
  280. package/dist/platform-tools.js +0 -3
  281. package/dist/process-lifecycle.js +0 -7
  282. package/dist/product-cli.js +0 -10
  283. package/dist/pty-host.js +0 -22
  284. package/dist/received-state.js +0 -46
  285. package/dist/reference-placement.js +0 -30
  286. package/dist/registry-graph.js +0 -89
  287. package/dist/registry-page-cache.js +4 -12
  288. package/dist/release-catalog.js +0 -3
  289. package/dist/root-install.js +2 -36
  290. package/dist/runtime-activity.js +0 -14
  291. package/dist/runtime-argv.js +0 -8
  292. package/dist/runtime-command-host.js +0 -17
  293. package/dist/runtime-node-flags.js +0 -10
  294. package/dist/runtime-wire-host.js +0 -4
  295. package/dist/service/adapter.js +0 -6
  296. package/dist/service/cli.js +12 -46
  297. package/dist/service/control.js +0 -3
  298. package/dist/service/index.js +0 -4
  299. package/dist/service/keepalive.js +2 -21
  300. package/dist/service/launchd.js +0 -8
  301. package/dist/service/owner.js +0 -1
  302. package/dist/service/policy.js +0 -7
  303. package/dist/service/portable.js +0 -8
  304. package/dist/service/recovery.js +0 -9
  305. package/dist/service/registration.js +0 -29
  306. package/dist/service/systemd-unit.js +0 -4
  307. package/dist/service/systemd.js +0 -9
  308. package/dist/service/windows-action.js +0 -12
  309. package/dist/service/windows-task.js +0 -10
  310. package/dist/service/windows.js +0 -4
  311. package/dist/sha256.js +0 -2
  312. package/dist/sharing-admission.js +0 -16
  313. package/dist/sharing-host.js +0 -7
  314. package/dist/sharing-mcp-host.js +0 -6
  315. package/dist/snapshot-delivery-baseline.js +0 -29
  316. package/dist/socket-marking.js +0 -9
  317. package/dist/source-proof.js +0 -29
  318. package/dist/source-signature.js +4 -93
  319. package/dist/source-witness.js +0 -6
  320. package/dist/sqlite-durability.js +0 -12
  321. package/dist/sqlite.js +0 -10
  322. package/dist/state-host.js +0 -2
  323. package/dist/state-store.js +1 -4
  324. package/dist/supervised-program/child.js +136 -0
  325. package/dist/supervised-program/messages.js +1 -0
  326. package/dist/supervised-program/parent.js +249 -0
  327. package/dist/sync-address.js +0 -16
  328. package/dist/sync-cli.js +0 -9
  329. package/dist/sync-setting.js +0 -5
  330. package/dist/tool-mcp-client.js +0 -2
  331. package/dist/toolbox-host.js +0 -2
  332. package/dist/transfer-instrumentation.js +0 -21
  333. package/dist/turns.js +0 -41
  334. package/dist/updates/artifacts.js +0 -56
  335. package/dist/updates/bootstrap.js +0 -53
  336. package/dist/updates/controller.js +1 -25
  337. package/dist/updates/isolated-command-lifetime.js +0 -13
  338. package/dist/updates/locked-packages.js +0 -5
  339. package/dist/updates/store.js +0 -11
  340. package/dist/updates/trust.js +0 -6
  341. package/dist/user-ground-host.js +162 -1501
  342. package/dist/watching/fsevents.js +3 -41
  343. package/dist/watching/git-storage.js +0 -24
  344. package/dist/watching/host.js +65 -275
  345. package/dist/watching/index.js +1 -2
  346. package/dist/watching/inotify.js +0 -31
  347. package/dist/windows-fs.js +0 -5
  348. package/dist/windows-owner-only.js +0 -17
  349. package/dist/wire-binary.js +0 -4
  350. package/dist/wire-client.js +0 -42
  351. package/dist/wire-join.js +0 -11
  352. package/dist/wire-outbox.js +0 -29
  353. package/dist/wire-request-scope.js +0 -3
  354. package/dist/wire-socket-relay.js +0 -53
  355. package/dist/workspace-add-intent.js +2 -11
  356. package/dist/workspace-add-staging.js +4 -99
  357. package/dist/workspace-host.js +0 -5
  358. package/dist/workspace-store.js +0 -6
  359. package/examinations/fixtures/private-wire-authority.js +14 -10
  360. package/examinations/native-service.mjs +1 -1
  361. package/examinations/runtime-upgrade.native-test.mjs +11 -8
  362. package/npm-shrinkwrap.json +14 -14
  363. package/package.json +8 -17
  364. package/PURPOSE.md +0 -1956
  365. package/dist/accepted-fold.d.ts +0 -51
  366. package/dist/accepted-fold.js.map +0 -1
  367. package/dist/accepted-tail.d.ts +0 -36
  368. package/dist/accepted-tail.js.map +0 -1
  369. package/dist/accepted-view.d.ts +0 -27
  370. package/dist/accepted-view.js.map +0 -1
  371. package/dist/agent-execution.d.ts +0 -83
  372. package/dist/agent-execution.js.map +0 -1
  373. package/dist/agent-instructions.d.ts +0 -7
  374. package/dist/agent-instructions.js.map +0 -1
  375. package/dist/apply-attempt-memory.d.ts +0 -13
  376. package/dist/apply-attempt-memory.js.map +0 -1
  377. package/dist/apply-control.d.ts +0 -85
  378. package/dist/apply-control.js.map +0 -1
  379. package/dist/apply-displaced-tree.d.ts +0 -63
  380. package/dist/apply-displaced-tree.js.map +0 -1
  381. package/dist/apply-durability.d.ts +0 -33
  382. package/dist/apply-durability.js.map +0 -1
  383. package/dist/apply-enter-build.d.ts +0 -91
  384. package/dist/apply-enter-build.js.map +0 -1
  385. package/dist/apply-enter-plan.d.ts +0 -79
  386. package/dist/apply-enter-plan.js.map +0 -1
  387. package/dist/apply-fingerprint.d.ts +0 -39
  388. package/dist/apply-fingerprint.js.map +0 -1
  389. package/dist/apply-git-held.d.ts +0 -29
  390. package/dist/apply-git-held.js.map +0 -1
  391. package/dist/apply-git-storage.d.ts +0 -38
  392. package/dist/apply-git-storage.js.map +0 -1
  393. package/dist/apply-kept.d.ts +0 -42
  394. package/dist/apply-kept.js.map +0 -1
  395. package/dist/apply-local-work.d.ts +0 -41
  396. package/dist/apply-local-work.js.map +0 -1
  397. package/dist/apply-map.d.ts +0 -116
  398. package/dist/apply-map.js.map +0 -1
  399. package/dist/apply-showing.d.ts +0 -104
  400. package/dist/apply-showing.js.map +0 -1
  401. package/dist/apply-shown-again.d.ts +0 -28
  402. package/dist/apply-shown-again.js.map +0 -1
  403. package/dist/apply-spelling.d.ts +0 -35
  404. package/dist/apply-spelling.js.map +0 -1
  405. package/dist/apply-trash-keep.d.ts +0 -96
  406. package/dist/apply-trash-keep.js.map +0 -1
  407. package/dist/apply-window-cargo.d.ts +0 -54
  408. package/dist/apply-window-cargo.js.map +0 -1
  409. package/dist/apply-window-ground.d.ts +0 -130
  410. package/dist/apply-window-ground.js.map +0 -1
  411. package/dist/apply-window-host.d.ts +0 -136
  412. package/dist/apply-window-host.js.map +0 -1
  413. package/dist/apply-window-lane.d.ts +0 -30
  414. package/dist/apply-window-lane.js.map +0 -1
  415. package/dist/apply-window-line.d.ts +0 -31
  416. package/dist/apply-window-line.js.map +0 -1
  417. package/dist/apply-window-recovery.d.ts +0 -5
  418. package/dist/apply-window-recovery.js.map +0 -1
  419. package/dist/apply-window-reveal.d.ts +0 -22
  420. package/dist/apply-window-reveal.js.map +0 -1
  421. package/dist/apply-window-rows.d.ts +0 -144
  422. package/dist/apply-window-rows.js.map +0 -1
  423. package/dist/apply-window-saves.d.ts +0 -224
  424. package/dist/apply-window-saves.js.map +0 -1
  425. package/dist/apply-window-store.d.ts +0 -126
  426. package/dist/apply-window-store.js.map +0 -1
  427. package/dist/apply-window-verify.d.ts +0 -65
  428. package/dist/apply-window-verify.js.map +0 -1
  429. package/dist/authority-binding.d.ts +0 -9
  430. package/dist/authority-binding.js.map +0 -1
  431. package/dist/authorization/device-key.d.ts +0 -19
  432. package/dist/authorization/device-key.js.map +0 -1
  433. package/dist/authorization/index.d.ts +0 -65
  434. package/dist/authorization/index.js.map +0 -1
  435. package/dist/authorization/issuer.d.ts +0 -11
  436. package/dist/authorization/issuer.js.map +0 -1
  437. package/dist/authorization/key-store.d.ts +0 -16
  438. package/dist/authorization/key-store.js.map +0 -1
  439. package/dist/authorization/native-keyring.d.ts +0 -8
  440. package/dist/authorization/native-keyring.js.map +0 -1
  441. package/dist/authorization/recovery-client.d.ts +0 -19
  442. package/dist/authorization/recovery-client.js.map +0 -1
  443. package/dist/authorization/recovery-host.d.ts +0 -30
  444. package/dist/authorization/recovery-host.js.map +0 -1
  445. package/dist/authorization/recovery.d.ts +0 -13
  446. package/dist/authorization/recovery.js.map +0 -1
  447. package/dist/authorization/registration-http.d.ts +0 -5
  448. package/dist/authorization/registration-http.js.map +0 -1
  449. package/dist/authorization/secret-process.d.ts +0 -2
  450. package/dist/authorization/secret-process.js.map +0 -1
  451. package/dist/authorization/setup-http.d.ts +0 -5
  452. package/dist/authorization/setup-http.js.map +0 -1
  453. package/dist/automations-cli-host.d.ts +0 -4
  454. package/dist/automations-cli-host.js.map +0 -1
  455. package/dist/background-error.d.ts +0 -4
  456. package/dist/background-error.js.map +0 -1
  457. package/dist/baseline-content.d.ts +0 -12
  458. package/dist/baseline-content.js.map +0 -1
  459. package/dist/boot-identity.d.ts +0 -1
  460. package/dist/boot-identity.js.map +0 -1
  461. package/dist/browser-host.d.ts +0 -30
  462. package/dist/browser-host.js.map +0 -1
  463. package/dist/builtin-agents.d.ts +0 -8
  464. package/dist/builtin-agents.js.map +0 -1
  465. package/dist/capture-work.d.ts +0 -8
  466. package/dist/capture-work.js.map +0 -1
  467. package/dist/captured-rows.d.ts +0 -33
  468. package/dist/captured-rows.js.map +0 -1
  469. package/dist/cargo-group.d.ts +0 -59
  470. package/dist/cargo-group.js.map +0 -1
  471. package/dist/cargo-journal.d.ts +0 -45
  472. package/dist/cargo-journal.js.map +0 -1
  473. package/dist/channel-session.d.ts +0 -60
  474. package/dist/channel-session.js.map +0 -1
  475. package/dist/chat-composition.d.ts +0 -30
  476. package/dist/chat-composition.js.map +0 -1
  477. package/dist/chat-host.d.ts +0 -30
  478. package/dist/chat-host.js.map +0 -1
  479. package/dist/chat-toolbox.d.ts +0 -10
  480. package/dist/chat-toolbox.js.map +0 -1
  481. package/dist/chat-tools.d.ts +0 -23
  482. package/dist/chat-tools.js.map +0 -1
  483. package/dist/cli-arguments.d.ts +0 -8
  484. package/dist/cli-arguments.js.map +0 -1
  485. package/dist/cli.d.ts +0 -10
  486. package/dist/cli.js.map +0 -1
  487. package/dist/construct-apply-host.d.ts +0 -64
  488. package/dist/construct-apply-host.js.map +0 -1
  489. package/dist/construct-door.d.ts +0 -39
  490. package/dist/construct-door.js.map +0 -1
  491. package/dist/construct-ledger.d.ts +0 -33
  492. package/dist/construct-ledger.js.map +0 -1
  493. package/dist/construct-products.d.ts +0 -22
  494. package/dist/construct-products.js.map +0 -1
  495. package/dist/content-cache-collection.d.ts +0 -25
  496. package/dist/content-cache-collection.js.map +0 -1
  497. package/dist/content-cache-fences.d.ts +0 -27
  498. package/dist/content-cache-fences.js.map +0 -1
  499. package/dist/content-cache-host.d.ts +0 -269
  500. package/dist/content-cache-host.js.map +0 -1
  501. package/dist/content-cache-index.d.ts +0 -59
  502. package/dist/content-cache-index.js.map +0 -1
  503. package/dist/content-cache-namespace.d.ts +0 -53
  504. package/dist/content-cache-namespace.js.map +0 -1
  505. package/dist/content-cache-partials.d.ts +0 -37
  506. package/dist/content-cache-partials.js.map +0 -1
  507. package/dist/content-cache-retention.d.ts +0 -38
  508. package/dist/content-cache-retention.js.map +0 -1
  509. package/dist/content-capture-pool.d.ts +0 -274
  510. package/dist/content-capture-pool.js.map +0 -1
  511. package/dist/content-capture-worker.d.ts +0 -7
  512. package/dist/content-capture-worker.js.map +0 -1
  513. package/dist/content-clock.d.ts +0 -68
  514. package/dist/content-clock.js.map +0 -1
  515. package/dist/content-direct.d.ts +0 -56
  516. package/dist/content-direct.js.map +0 -1
  517. package/dist/content-failure.d.ts +0 -18
  518. package/dist/content-failure.js.map +0 -1
  519. package/dist/content-qualification.d.ts +0 -72
  520. package/dist/content-qualification.js.map +0 -1
  521. package/dist/content-wire-codec.d.ts +0 -13
  522. package/dist/content-wire-codec.js.map +0 -1
  523. package/dist/credentials-host.d.ts +0 -5
  524. package/dist/credentials-host.js.map +0 -1
  525. package/dist/derived-relocation.d.ts +0 -31
  526. package/dist/derived-relocation.js.map +0 -1
  527. package/dist/detection/accepted-result.d.ts +0 -31
  528. package/dist/detection/accepted-result.js.map +0 -1
  529. package/dist/detection/admission-save.d.ts +0 -66
  530. package/dist/detection/admission-save.js.map +0 -1
  531. package/dist/detection/admission-units.d.ts +0 -78
  532. package/dist/detection/admission-units.js.map +0 -1
  533. package/dist/detection/alias-discovery.d.ts +0 -12
  534. package/dist/detection/alias-discovery.js.map +0 -1
  535. package/dist/detection/alias-examination.d.ts +0 -33
  536. package/dist/detection/alias-examination.js.map +0 -1
  537. package/dist/detection/apply-ownership.d.ts +0 -107
  538. package/dist/detection/apply-ownership.js.map +0 -1
  539. package/dist/detection/basis-advanced.d.ts +0 -15
  540. package/dist/detection/basis-advanced.js.map +0 -1
  541. package/dist/detection/cached-replay.d.ts +0 -38
  542. package/dist/detection/cached-replay.js.map +0 -1
  543. package/dist/detection/capture-outcome.d.ts +0 -16
  544. package/dist/detection/capture-outcome.js.map +0 -1
  545. package/dist/detection/container-membership.d.ts +0 -20
  546. package/dist/detection/container-membership.js.map +0 -1
  547. package/dist/detection/detect-cancelled.d.ts +0 -6
  548. package/dist/detection/detect-cancelled.js.map +0 -1
  549. package/dist/detection/directory-proof.d.ts +0 -47
  550. package/dist/detection/directory-proof.js.map +0 -1
  551. package/dist/detection/dispositions.d.ts +0 -107
  552. package/dist/detection/dispositions.js.map +0 -1
  553. package/dist/detection/examinations.d.ts +0 -33
  554. package/dist/detection/examinations.js.map +0 -1
  555. package/dist/detection/ground-proof.d.ts +0 -154
  556. package/dist/detection/ground-proof.js.map +0 -1
  557. package/dist/detection/ground-reader.d.ts +0 -29
  558. package/dist/detection/ground-reader.js.map +0 -1
  559. package/dist/detection/identity-discovery.d.ts +0 -45
  560. package/dist/detection/identity-discovery.js.map +0 -1
  561. package/dist/detection/maintenance-sweep.d.ts +0 -111
  562. package/dist/detection/maintenance-sweep.js.map +0 -1
  563. package/dist/detection/notebook-basis.d.ts +0 -24
  564. package/dist/detection/notebook-basis.js.map +0 -1
  565. package/dist/detection/owed-examinations.d.ts +0 -22
  566. package/dist/detection/owed-examinations.js.map +0 -1
  567. package/dist/detection/owed-selection.d.ts +0 -54
  568. package/dist/detection/owed-selection.js.map +0 -1
  569. package/dist/detection/policy-owed.d.ts +0 -17
  570. package/dist/detection/policy-owed.js.map +0 -1
  571. package/dist/detection/reconciliation-coverage.d.ts +0 -7
  572. package/dist/detection/reconciliation-coverage.js.map +0 -1
  573. package/dist/detection/repository-state.d.ts +0 -44
  574. package/dist/detection/repository-state.js.map +0 -1
  575. package/dist/detection/reveal-save.d.ts +0 -17
  576. package/dist/detection/reveal-save.js.map +0 -1
  577. package/dist/detection/root-examination.d.ts +0 -106
  578. package/dist/detection/root-examination.js.map +0 -1
  579. package/dist/detection/root-walk.d.ts +0 -191
  580. package/dist/detection/root-walk.js.map +0 -1
  581. package/dist/detection/runtime.d.ts +0 -144
  582. package/dist/detection/runtime.js.map +0 -1
  583. package/dist/detection/scope-frame.d.ts +0 -82
  584. package/dist/detection/scope-frame.js.map +0 -1
  585. package/dist/detection/scoped-identity-port.d.ts +0 -35
  586. package/dist/detection/scoped-identity-port.js.map +0 -1
  587. package/dist/detection/sharing-policy.d.ts +0 -19
  588. package/dist/detection/sharing-policy.js +0 -39
  589. package/dist/detection/sharing-policy.js.map +0 -1
  590. package/dist/detection/spelled-lookup.d.ts +0 -20
  591. package/dist/detection/spelled-lookup.js.map +0 -1
  592. package/dist/detection/thread-database.d.ts +0 -4
  593. package/dist/detection/thread-database.js.map +0 -1
  594. package/dist/detection/unread-content.d.ts +0 -20
  595. package/dist/detection/unread-content.js.map +0 -1
  596. package/dist/detection/unreadable.d.ts +0 -11
  597. package/dist/detection/unreadable.js.map +0 -1
  598. package/dist/detection/walk-law.d.ts +0 -25
  599. package/dist/detection/walk-law.js.map +0 -1
  600. package/dist/detection/walked-roots.d.ts +0 -17
  601. package/dist/detection/walked-roots.js.map +0 -1
  602. package/dist/detection/withheld.d.ts +0 -100
  603. package/dist/detection/withheld.js.map +0 -1
  604. package/dist/development/fly-guest.d.ts +0 -21
  605. package/dist/development/fly-guest.js.map +0 -1
  606. package/dist/development/fly.d.ts +0 -13
  607. package/dist/development/fly.js.map +0 -1
  608. package/dist/development/profile.d.ts +0 -34
  609. package/dist/development/profile.js.map +0 -1
  610. package/dist/drive/cloud-files/asks.d.ts +0 -7
  611. package/dist/drive/cloud-files/asks.js.map +0 -1
  612. package/dist/drive/cloud-files/binding.d.ts +0 -111
  613. package/dist/drive/cloud-files/binding.js.map +0 -1
  614. package/dist/drive/cloud-files/contents.d.ts +0 -82
  615. package/dist/drive/cloud-files/contents.js.map +0 -1
  616. package/dist/drive/cloud-files/door.d.ts +0 -11
  617. package/dist/drive/cloud-files/door.js.map +0 -1
  618. package/dist/drive/cloud-files/paths.d.ts +0 -42
  619. package/dist/drive/cloud-files/paths.js.map +0 -1
  620. package/dist/drive/cloud-files/populated.d.ts +0 -15
  621. package/dist/drive/cloud-files/populated.js.map +0 -1
  622. package/dist/drive/cloud-files/reconcile.d.ts +0 -17
  623. package/dist/drive/cloud-files/reconcile.js.map +0 -1
  624. package/dist/drive/cloud-files/sync-root.d.ts +0 -34
  625. package/dist/drive/cloud-files/sync-root.js.map +0 -1
  626. package/dist/drive/cloud-files/turns.d.ts +0 -9
  627. package/dist/drive/cloud-files/turns.js.map +0 -1
  628. package/dist/drive/cloud-files/writes.d.ts +0 -27
  629. package/dist/drive/cloud-files/writes.js.map +0 -1
  630. package/dist/drive/computer.d.ts +0 -19
  631. package/dist/drive/computer.js.map +0 -1
  632. package/dist/drive/fuse-opens.d.ts +0 -32
  633. package/dist/drive/fuse-opens.js.map +0 -1
  634. package/dist/drive/fuse.d.ts +0 -36
  635. package/dist/drive/fuse.js.map +0 -1
  636. package/dist/drive/kept.d.ts +0 -78
  637. package/dist/drive/kept.js.map +0 -1
  638. package/dist/drive/kernel.d.ts +0 -17
  639. package/dist/drive/kernel.js.map +0 -1
  640. package/dist/drive/layout.d.ts +0 -18
  641. package/dist/drive/layout.js.map +0 -1
  642. package/dist/drive/mount.d.ts +0 -107
  643. package/dist/drive/mount.js.map +0 -1
  644. package/dist/drive/mountpoint.d.ts +0 -14
  645. package/dist/drive/mountpoint.js.map +0 -1
  646. package/dist/drive/nfs/apple-double.d.ts +0 -6
  647. package/dist/drive/nfs/apple-double.js.map +0 -1
  648. package/dist/drive/nfs/attributes.d.ts +0 -64
  649. package/dist/drive/nfs/attributes.js.map +0 -1
  650. package/dist/drive/nfs/handles.d.ts +0 -44
  651. package/dist/drive/nfs/handles.js.map +0 -1
  652. package/dist/drive/nfs/mount3.d.ts +0 -16
  653. package/dist/drive/nfs/mount3.js.map +0 -1
  654. package/dist/drive/nfs/nfs3.d.ts +0 -27
  655. package/dist/drive/nfs/nfs3.js.map +0 -1
  656. package/dist/drive/nfs/rpc.d.ts +0 -66
  657. package/dist/drive/nfs/rpc.js.map +0 -1
  658. package/dist/drive/nfs/server.d.ts +0 -30
  659. package/dist/drive/nfs/server.js.map +0 -1
  660. package/dist/drive/nfs/xdr.d.ts +0 -44
  661. package/dist/drive/nfs/xdr.js.map +0 -1
  662. package/dist/drive/nfs.d.ts +0 -58
  663. package/dist/drive/nfs.js.map +0 -1
  664. package/dist/drive/operations.d.ts +0 -180
  665. package/dist/drive/operations.js.map +0 -1
  666. package/dist/drive/shelf.d.ts +0 -9
  667. package/dist/drive/shelf.js.map +0 -1
  668. package/dist/durability-barrier.d.ts +0 -66
  669. package/dist/durability-barrier.js.map +0 -1
  670. package/dist/entity-access-wire.d.ts +0 -33
  671. package/dist/entity-access-wire.js.map +0 -1
  672. package/dist/entity-channel-holdings.d.ts +0 -26
  673. package/dist/entity-channel-holdings.js.map +0 -1
  674. package/dist/entity-grant-watch.d.ts +0 -9
  675. package/dist/entity-grant-watch.js.map +0 -1
  676. package/dist/entity-record-observability.d.ts +0 -13
  677. package/dist/entity-record-observability.js.map +0 -1
  678. package/dist/entity-record-saves.d.ts +0 -47
  679. package/dist/entity-record-saves.js.map +0 -1
  680. package/dist/entity-record-store.d.ts +0 -60
  681. package/dist/entity-record-store.js.map +0 -1
  682. package/dist/error-facts.d.ts +0 -24
  683. package/dist/error-facts.js.map +0 -1
  684. package/dist/faults/drain.d.ts +0 -27
  685. package/dist/faults/drain.js.map +0 -1
  686. package/dist/faults/queue.d.ts +0 -46
  687. package/dist/faults/queue.js.map +0 -1
  688. package/dist/faults/show.d.ts +0 -7
  689. package/dist/faults/show.js.map +0 -1
  690. package/dist/files-browser-host.d.ts +0 -9
  691. package/dist/files-browser-host.js.map +0 -1
  692. package/dist/files-mcp-host.d.ts +0 -58
  693. package/dist/files-mcp-host.js.map +0 -1
  694. package/dist/files-observability.d.ts +0 -29
  695. package/dist/files-observability.js.map +0 -1
  696. package/dist/files-program/client.d.ts +0 -136
  697. package/dist/files-program/client.js.map +0 -1
  698. package/dist/files-program/journeys.d.ts +0 -15
  699. package/dist/files-program/journeys.js.map +0 -1
  700. package/dist/files-program/program.d.ts +0 -1
  701. package/dist/files-program/program.js.map +0 -1
  702. package/dist/files-program/protocol.d.ts +0 -180
  703. package/dist/files-program/protocol.js.map +0 -1
  704. package/dist/files-register-host.d.ts +0 -70
  705. package/dist/files-register-host.js.map +0 -1
  706. package/dist/files-trace.d.ts +0 -61
  707. package/dist/files-trace.js.map +0 -1
  708. package/dist/filesystem.d.ts +0 -38
  709. package/dist/filesystem.js.map +0 -1
  710. package/dist/flush.d.ts +0 -19
  711. package/dist/flush.js.map +0 -1
  712. package/dist/forward.d.ts +0 -11
  713. package/dist/forward.js.map +0 -1
  714. package/dist/gateway.d.ts +0 -38
  715. package/dist/gateway.js.map +0 -1
  716. package/dist/git/ground-owners.d.ts +0 -15
  717. package/dist/git/ground-owners.js.map +0 -1
  718. package/dist/git/held-package.d.ts +0 -67
  719. package/dist/git/held-package.js.map +0 -1
  720. package/dist/git/home.d.ts +0 -59
  721. package/dist/git/home.js.map +0 -1
  722. package/dist/git/marker.d.ts +0 -21
  723. package/dist/git/marker.js.map +0 -1
  724. package/dist/git/named-objects.d.ts +0 -24
  725. package/dist/git/named-objects.js.map +0 -1
  726. package/dist/git/objects.d.ts +0 -30
  727. package/dist/git/objects.js.map +0 -1
  728. package/dist/git/play.d.ts +0 -30
  729. package/dist/git/play.js.map +0 -1
  730. package/dist/git/quarantine.d.ts +0 -48
  731. package/dist/git/quarantine.js.map +0 -1
  732. package/dist/git/rail.d.ts +0 -206
  733. package/dist/git/rail.js.map +0 -1
  734. package/dist/git/read-state.d.ts +0 -49
  735. package/dist/git/read-state.js.map +0 -1
  736. package/dist/git/repository.d.ts +0 -62
  737. package/dist/git/repository.js.map +0 -1
  738. package/dist/git/write-files.d.ts +0 -29
  739. package/dist/git/write-files.js.map +0 -1
  740. package/dist/git-binding.d.ts +0 -53
  741. package/dist/git-binding.js.map +0 -1
  742. package/dist/git-cat-file.d.ts +0 -28
  743. package/dist/git-cat-file.js.map +0 -1
  744. package/dist/git-command.d.ts +0 -96
  745. package/dist/git-command.js.map +0 -1
  746. package/dist/git-index-entries.d.ts +0 -16
  747. package/dist/git-index-entries.js.map +0 -1
  748. package/dist/git-index-format.d.ts +0 -52
  749. package/dist/git-index-format.js.map +0 -1
  750. package/dist/git-install-lines.d.ts +0 -12
  751. package/dist/git-install-lines.js.map +0 -1
  752. package/dist/git-launcher-process.d.ts +0 -1
  753. package/dist/git-launcher-process.js.map +0 -1
  754. package/dist/git-launcher.d.ts +0 -70
  755. package/dist/git-launcher.js.map +0 -1
  756. package/dist/graph-heads.d.ts +0 -71
  757. package/dist/graph-heads.js.map +0 -1
  758. package/dist/ground-basis.d.ts +0 -278
  759. package/dist/ground-basis.js.map +0 -1
  760. package/dist/ground-checkpoint-worker.d.ts +0 -1
  761. package/dist/ground-checkpoint-worker.js.map +0 -1
  762. package/dist/ground-checkpoints.d.ts +0 -16
  763. package/dist/ground-checkpoints.js.map +0 -1
  764. package/dist/ground-contract.d.ts +0 -11
  765. package/dist/ground-contract.js.map +0 -1
  766. package/dist/ground-coordination.d.ts +0 -140
  767. package/dist/ground-coordination.js.map +0 -1
  768. package/dist/ground-database.d.ts +0 -40
  769. package/dist/ground-database.js.map +0 -1
  770. package/dist/ground-differences.d.ts +0 -24
  771. package/dist/ground-differences.js.map +0 -1
  772. package/dist/ground-holders.d.ts +0 -4
  773. package/dist/ground-holders.js.map +0 -1
  774. package/dist/ground-initialization-worker.d.ts +0 -1
  775. package/dist/ground-initialization-worker.js.map +0 -1
  776. package/dist/ground-initialization.d.ts +0 -38
  777. package/dist/ground-initialization.js.map +0 -1
  778. package/dist/ground-install-saves.d.ts +0 -104
  779. package/dist/ground-install-saves.js.map +0 -1
  780. package/dist/ground-inventory-schema.d.ts +0 -58
  781. package/dist/ground-inventory-schema.js.map +0 -1
  782. package/dist/ground-marks.d.ts +0 -49
  783. package/dist/ground-marks.js.map +0 -1
  784. package/dist/ground-profile.d.ts +0 -14
  785. package/dist/ground-profile.js.map +0 -1
  786. package/dist/ground-reads.d.ts +0 -86
  787. package/dist/ground-reads.js.map +0 -1
  788. package/dist/ground-relations.d.ts +0 -57
  789. package/dist/ground-relations.js.map +0 -1
  790. package/dist/ground-root-index.d.ts +0 -14
  791. package/dist/ground-root-index.js.map +0 -1
  792. package/dist/ground-row.d.ts +0 -78
  793. package/dist/ground-row.js.map +0 -1
  794. package/dist/ground-save-ops.d.ts +0 -62
  795. package/dist/ground-save-ops.js.map +0 -1
  796. package/dist/ground-saver-worker.d.ts +0 -1
  797. package/dist/ground-saver-worker.js.map +0 -1
  798. package/dist/ground-saver.d.ts +0 -103
  799. package/dist/ground-saver.js.map +0 -1
  800. package/dist/ground-store.d.ts +0 -125
  801. package/dist/ground-store.js.map +0 -1
  802. package/dist/index.d.ts +0 -22
  803. package/dist/index.js.map +0 -1
  804. package/dist/initial-publication.d.ts +0 -42
  805. package/dist/initial-publication.js.map +0 -1
  806. package/dist/installation/environment.d.ts +0 -31
  807. package/dist/installation/environment.js.map +0 -1
  808. package/dist/installation/lease.d.ts +0 -6
  809. package/dist/installation/lease.js.map +0 -1
  810. package/dist/installation/ownership.d.ts +0 -30
  811. package/dist/installation/ownership.js.map +0 -1
  812. package/dist/installation/selection.d.ts +0 -8
  813. package/dist/installation/selection.js.map +0 -1
  814. package/dist/keychain/cli-io.d.ts +0 -8
  815. package/dist/keychain/cli-io.js.map +0 -1
  816. package/dist/keychain/cli.d.ts +0 -12
  817. package/dist/keychain/cli.js.map +0 -1
  818. package/dist/keychain/host.d.ts +0 -28
  819. package/dist/keychain/host.js.map +0 -1
  820. package/dist/keychain/http-mount.d.ts +0 -16
  821. package/dist/keychain/http-mount.js.map +0 -1
  822. package/dist/keychain/key-wire.d.ts +0 -12
  823. package/dist/keychain/key-wire.js.map +0 -1
  824. package/dist/keychain/presence-mac.d.ts +0 -8
  825. package/dist/keychain/presence-mac.js.map +0 -1
  826. package/dist/keychain/presence.d.ts +0 -9
  827. package/dist/keychain/presence.js.map +0 -1
  828. package/dist/keychain/rail.d.ts +0 -19
  829. package/dist/keychain/rail.js.map +0 -1
  830. package/dist/keychain/secret-apply.d.ts +0 -22
  831. package/dist/keychain/secret-apply.js.map +0 -1
  832. package/dist/keychain/shelf-from-ledger.d.ts +0 -15
  833. package/dist/keychain/shelf-from-ledger.js.map +0 -1
  834. package/dist/keychain/use-log.d.ts +0 -7
  835. package/dist/keychain/use-log.js.map +0 -1
  836. package/dist/keychain/vault-file.d.ts +0 -12
  837. package/dist/keychain/vault-file.js.map +0 -1
  838. package/dist/line-judge.d.ts +0 -39
  839. package/dist/line-judge.js.map +0 -1
  840. package/dist/line-loops.d.ts +0 -22
  841. package/dist/line-loops.js.map +0 -1
  842. package/dist/link-target.d.ts +0 -16
  843. package/dist/link-target.js.map +0 -1
  844. package/dist/local-host.d.ts +0 -20
  845. package/dist/local-host.js.map +0 -1
  846. package/dist/loop-watch.d.ts +0 -17
  847. package/dist/loop-watch.js.map +0 -1
  848. package/dist/machine-host.d.ts +0 -249
  849. package/dist/machine-host.js.map +0 -1
  850. package/dist/main.d.ts +0 -2
  851. package/dist/main.js.map +0 -1
  852. package/dist/materialize-records.d.ts +0 -98
  853. package/dist/materialize-records.js.map +0 -1
  854. package/dist/materialized-graph.d.ts +0 -22
  855. package/dist/materialized-graph.js.map +0 -1
  856. package/dist/module-thread.d.ts +0 -9
  857. package/dist/module-thread.js.map +0 -1
  858. package/dist/mount.d.ts +0 -13
  859. package/dist/mount.js.map +0 -1
  860. package/dist/official-mcp-host.d.ts +0 -51
  861. package/dist/official-mcp-host.js.map +0 -1
  862. package/dist/on-demand-roots.d.ts +0 -31
  863. package/dist/on-demand-roots.js.map +0 -1
  864. package/dist/open-standing.d.ts +0 -8
  865. package/dist/open-standing.js.map +0 -1
  866. package/dist/own-results.d.ts +0 -37
  867. package/dist/own-results.js.map +0 -1
  868. package/dist/package-pages.d.ts +0 -41
  869. package/dist/package-pages.js.map +0 -1
  870. package/dist/patient-flush.d.ts +0 -24
  871. package/dist/patient-flush.js.map +0 -1
  872. package/dist/physical-path-witness.d.ts +0 -64
  873. package/dist/physical-path-witness.js.map +0 -1
  874. package/dist/placement-owed.d.ts +0 -28
  875. package/dist/placement-owed.js.map +0 -1
  876. package/dist/placement-tidy.d.ts +0 -57
  877. package/dist/placement-tidy.js.map +0 -1
  878. package/dist/platform-product-host.d.ts +0 -51
  879. package/dist/platform-product-host.js.map +0 -1
  880. package/dist/platform-tools.d.ts +0 -22
  881. package/dist/platform-tools.js.map +0 -1
  882. package/dist/process-lifecycle.d.ts +0 -13
  883. package/dist/process-lifecycle.js.map +0 -1
  884. package/dist/product-cli.d.ts +0 -26
  885. package/dist/product-cli.js.map +0 -1
  886. package/dist/pty-host.d.ts +0 -16
  887. package/dist/pty-host.js.map +0 -1
  888. package/dist/received-state.d.ts +0 -90
  889. package/dist/received-state.js.map +0 -1
  890. package/dist/reference-placement.d.ts +0 -26
  891. package/dist/reference-placement.js.map +0 -1
  892. package/dist/registry-graph.d.ts +0 -112
  893. package/dist/registry-graph.js.map +0 -1
  894. package/dist/registry-page-cache.d.ts +0 -15
  895. package/dist/registry-page-cache.js.map +0 -1
  896. package/dist/release-catalog.d.ts +0 -5
  897. package/dist/release-catalog.js.map +0 -1
  898. package/dist/root-install.d.ts +0 -72
  899. package/dist/root-install.js.map +0 -1
  900. package/dist/runtime-activity.d.ts +0 -20
  901. package/dist/runtime-activity.js.map +0 -1
  902. package/dist/runtime-argv.d.ts +0 -8
  903. package/dist/runtime-argv.js.map +0 -1
  904. package/dist/runtime-command-host.d.ts +0 -46
  905. package/dist/runtime-command-host.js.map +0 -1
  906. package/dist/runtime-node-flags.d.ts +0 -10
  907. package/dist/runtime-node-flags.js.map +0 -1
  908. package/dist/runtime-wire-host.d.ts +0 -17
  909. package/dist/runtime-wire-host.js.map +0 -1
  910. package/dist/service/adapter.d.ts +0 -37
  911. package/dist/service/adapter.js.map +0 -1
  912. package/dist/service/cli.d.ts +0 -8
  913. package/dist/service/cli.js.map +0 -1
  914. package/dist/service/control.d.ts +0 -38
  915. package/dist/service/control.js.map +0 -1
  916. package/dist/service/index.d.ts +0 -9
  917. package/dist/service/index.js.map +0 -1
  918. package/dist/service/keepalive.d.ts +0 -11
  919. package/dist/service/keepalive.js.map +0 -1
  920. package/dist/service/launchd.d.ts +0 -9
  921. package/dist/service/launchd.js.map +0 -1
  922. package/dist/service/owner.d.ts +0 -4
  923. package/dist/service/owner.js.map +0 -1
  924. package/dist/service/policy.d.ts +0 -36
  925. package/dist/service/policy.js.map +0 -1
  926. package/dist/service/portable.d.ts +0 -10
  927. package/dist/service/portable.js.map +0 -1
  928. package/dist/service/recovery.d.ts +0 -28
  929. package/dist/service/recovery.js.map +0 -1
  930. package/dist/service/registration.d.ts +0 -84
  931. package/dist/service/registration.js.map +0 -1
  932. package/dist/service/systemd-unit.d.ts +0 -7
  933. package/dist/service/systemd-unit.js.map +0 -1
  934. package/dist/service/systemd.d.ts +0 -5
  935. package/dist/service/systemd.js.map +0 -1
  936. package/dist/service/windows-action.d.ts +0 -18
  937. package/dist/service/windows-action.js.map +0 -1
  938. package/dist/service/windows-task.d.ts +0 -15
  939. package/dist/service/windows-task.js.map +0 -1
  940. package/dist/service/windows.d.ts +0 -2
  941. package/dist/service/windows.js.map +0 -1
  942. package/dist/sha256.d.ts +0 -1
  943. package/dist/sha256.js.map +0 -1
  944. package/dist/sharing-admission.d.ts +0 -22
  945. package/dist/sharing-admission.js.map +0 -1
  946. package/dist/sharing-host.d.ts +0 -14
  947. package/dist/sharing-host.js.map +0 -1
  948. package/dist/sharing-mcp-host.d.ts +0 -23
  949. package/dist/sharing-mcp-host.js.map +0 -1
  950. package/dist/snapshot-delivery-baseline.d.ts +0 -31
  951. package/dist/snapshot-delivery-baseline.js.map +0 -1
  952. package/dist/socket-marking.d.ts +0 -9
  953. package/dist/socket-marking.js.map +0 -1
  954. package/dist/source-proof.d.ts +0 -23
  955. package/dist/source-proof.js.map +0 -1
  956. package/dist/source-signature.d.ts +0 -157
  957. package/dist/source-signature.js.map +0 -1
  958. package/dist/source-witness.d.ts +0 -9
  959. package/dist/source-witness.js.map +0 -1
  960. package/dist/sqlite-durability.d.ts +0 -32
  961. package/dist/sqlite-durability.js.map +0 -1
  962. package/dist/sqlite.d.ts +0 -10
  963. package/dist/sqlite.js.map +0 -1
  964. package/dist/state-host.d.ts +0 -4
  965. package/dist/state-host.js.map +0 -1
  966. package/dist/state-store.d.ts +0 -15
  967. package/dist/state-store.js.map +0 -1
  968. package/dist/sync-address.d.ts +0 -16
  969. package/dist/sync-address.js.map +0 -1
  970. package/dist/sync-cli.d.ts +0 -7
  971. package/dist/sync-cli.js.map +0 -1
  972. package/dist/sync-setting.d.ts +0 -43
  973. package/dist/sync-setting.js.map +0 -1
  974. package/dist/tool-mcp-client.d.ts +0 -7
  975. package/dist/tool-mcp-client.js.map +0 -1
  976. package/dist/toolbox-host.d.ts +0 -4
  977. package/dist/toolbox-host.js.map +0 -1
  978. package/dist/transfer-instrumentation.d.ts +0 -47
  979. package/dist/transfer-instrumentation.js.map +0 -1
  980. package/dist/turns.d.ts +0 -44
  981. package/dist/turns.js.map +0 -1
  982. package/dist/updates/artifacts.d.ts +0 -66
  983. package/dist/updates/artifacts.js.map +0 -1
  984. package/dist/updates/bootstrap.d.ts +0 -94
  985. package/dist/updates/bootstrap.js.map +0 -1
  986. package/dist/updates/controller.d.ts +0 -78
  987. package/dist/updates/controller.js.map +0 -1
  988. package/dist/updates/isolated-command-lifetime.d.ts +0 -1
  989. package/dist/updates/isolated-command-lifetime.js.map +0 -1
  990. package/dist/updates/locked-packages.d.ts +0 -4
  991. package/dist/updates/locked-packages.js.map +0 -1
  992. package/dist/updates/store.d.ts +0 -47
  993. package/dist/updates/store.js.map +0 -1
  994. package/dist/updates/trust.d.ts +0 -20
  995. package/dist/updates/trust.js.map +0 -1
  996. package/dist/user-ground-host.d.ts +0 -1007
  997. package/dist/user-ground-host.js.map +0 -1
  998. package/dist/watching/fsevents.d.ts +0 -69
  999. package/dist/watching/fsevents.js.map +0 -1
  1000. package/dist/watching/git-storage.d.ts +0 -22
  1001. package/dist/watching/git-storage.js.map +0 -1
  1002. package/dist/watching/host.d.ts +0 -388
  1003. package/dist/watching/host.js.map +0 -1
  1004. package/dist/watching/index.d.ts +0 -3
  1005. package/dist/watching/index.js.map +0 -1
  1006. package/dist/watching/inotify.d.ts +0 -81
  1007. package/dist/watching/inotify.js.map +0 -1
  1008. package/dist/windows-fs.d.ts +0 -12
  1009. package/dist/windows-fs.js.map +0 -1
  1010. package/dist/windows-owner-only.d.ts +0 -6
  1011. package/dist/windows-owner-only.js.map +0 -1
  1012. package/dist/wire-binary.d.ts +0 -9
  1013. package/dist/wire-binary.js.map +0 -1
  1014. package/dist/wire-client.d.ts +0 -86
  1015. package/dist/wire-client.js.map +0 -1
  1016. package/dist/wire-join.d.ts +0 -19
  1017. package/dist/wire-join.js.map +0 -1
  1018. package/dist/wire-outbox.d.ts +0 -37
  1019. package/dist/wire-outbox.js.map +0 -1
  1020. package/dist/wire-request-scope.d.ts +0 -17
  1021. package/dist/wire-request-scope.js.map +0 -1
  1022. package/dist/wire-socket-relay.d.ts +0 -54
  1023. package/dist/wire-socket-relay.js.map +0 -1
  1024. package/dist/workspace-add-intent.d.ts +0 -41
  1025. package/dist/workspace-add-intent.js.map +0 -1
  1026. package/dist/workspace-add-staging.d.ts +0 -192
  1027. package/dist/workspace-add-staging.js.map +0 -1
  1028. package/dist/workspace-host.d.ts +0 -32
  1029. package/dist/workspace-host.js.map +0 -1
  1030. package/dist/workspace-store.d.ts +0 -8
  1031. package/dist/workspace-store.js.map +0 -1
  1032. package/skills/shell/SKILL.md +0 -175
package/PURPOSE.md DELETED
@@ -1,1956 +0,0 @@
1
- # @amalgm/shell — Purpose
2
-
3
- Amalgm Shell gives a user one dependable machine runtime assembled from the
4
- published `@amalgm/*` SDKs. An enabled installation should remain available
5
- while its host can execute, recover without opening a UI, contain a failing
6
- workload, and leave the machine's resources available for useful work. Shell
7
- owns composition, process boot, and native host effects; Core and the product
8
- SDKs own the decisions those effects execute.
9
- At the completed brick/mortar boundary, compatible bricks advance through independently selected artifacts while Shell
10
- remains the mortar; publishing a brick must not require publishing unchanged
11
- Shell code.
12
-
13
- ## Detect and Apply attribution
14
-
15
- An originating machine may resolve its own accepted publication without
16
- claiming that every local byte matches the shared result. The proof is the
17
- exact acknowledged Outbox record, its authoritative Inbox position, and the
18
- still-current admission attached to the sharing baseline. A new sharing
19
- decision invalidates the previous admission even if it returns to equal values;
20
- a metadata refresh does not. Covered member changes invalidate their repository
21
- owner's admission, while an independent nested repository head does not change
22
- the outer repository's placement. This outcome preserves physical observation,
23
- the sharing baseline, and the last verified materialization. Existing effect
24
- recovery must finish before this shortcut can resolve history. This boundary
25
- is being implemented; the full native Apply examination has not passed it yet.
26
-
27
- One read-only view of the open Apply windows, bound and not yet ended, protects
28
- every address, object and entity their receipt rows name during Detect
29
- (`src/detection/apply-ownership.ts`). The window's receipt is its row, never a
30
- file: bound before the first visible effect, ended at Verify, durable only after
31
- the revealed bytes are flushed (`src/apply-window-saves.ts`); every reveal step
32
- is idempotent against it, so a window re-entered after a crash runs the same
33
- steps again (`src/apply-window-recovery.ts`). Root and path coverage
34
- remain distinct from ownership: the walk leaves each owned cone unread inside its
35
- root and admits the root's independent units; only a cone containing the root, or
36
- a new root's first walk, defer the whole root. No deferred row is
37
- refreshed, erased, or admitted through ignore policy. A first walk rechecks exact ownership answers, including absence, alongside the physical and
38
- SQLite basis; a unit walk relies on its lease, which every later Apply effect
39
- crosses under its ground hold.
40
- Terminal commit wakes original receipt scopes before private cleanup. A self-owned
41
- capture enters original-effect cancellation; a foreign-owned capture releases its
42
- attempt and waits on the named Apply producer. Neither means the edit was recorded.
43
- Fresh Apply attempt UUIDs prevent delayed proof from acting on a replacement intent.
44
- Apply admission and terminal preparation obey that same ownership predicate;
45
- matching bytes do not release another attempt's recovery responsibility. Original
46
- participants retain protection at their currently attributed addresses. An
47
- unfinished Apply holds only its own root: identity continuity is root-local, so
48
- an object it owns is named within its binding, and an inode number it freed that
49
- the filesystem gives another root's file holds nothing back there. Detect's
50
- identity candidates are likewise one root's rows at an object, and a shared
51
- object joins admission units only within one root; an object's names across
52
- roots are hard-link aliases, examined each in its own root. Capture
53
- completion waits only on its actual Watch roots. A binding that cannot be reached
54
- now is inaccessible, not wrong: its durable intent still owns the ground bound
55
- there while its receipt, kept in that binding's control tree, waits unread. A
56
- binding proved to be another object is unsafe. Neither poisons unrelated roots.
57
- One preimage association represents source roots (including leaves) and descendant
58
- directories. Every Apply move, of a primary, a room sibling or a tidy, is one no-replace
59
- move that puts ground first and rows after. Retirement, materialized or cancelled, places
60
- each participant's rows in both inventories where its object stands, under its
61
- actual binding and the basis that read them; it changes addresses only, never a
62
- sharing result or accepted history. Admission and receipt binding share one
63
- SQLite write transaction, including physical aliases whose pathname leases do
64
- not overlap. Private unbound receipt
65
- files grant no effects and cannot be adopted as earlier effect evidence.
66
- Controlled full-ideal checks cover these recovery paths, including a stopped
67
- primary rename and a second Apply targeting a still-owned room sibling.
68
- Complete native and multi-machine convergence remain unproved.
69
-
70
- ## Operating axioms
71
-
72
- For outgoing email, Shell supplies its source computer and home directory to
73
- Channels' local adapter. Agents continue producing resource references; UI's
74
- portable link grammar derives surface URLs. This context names the source and
75
- never grants the recipient access.
76
-
77
- These are the required operating contract, not a statement that every current
78
- installation satisfies it. The [operating contract](docs/operating-contract.md)
79
- defines the terms and examinations; the [September 2026 audit](docs/operating-audit-2026-09-05.md)
80
- records implementation gaps and historical evidence.
81
- The [release environments plan](docs/release-environments-plan.md) records the
82
- agreed CI/CD and update evolution; its target behavior is not yet delivered.
83
- The owner permits temporary bundled Shell releases for brick changes during
84
- boundary cleanup. Independent brick adoption remains the target, and Engine
85
- migration is out of scope because no existing Engine users need it.
86
-
87
- - **O1 — Lifetime follows installation intent.** One installation owner keeps
88
- the enabled runtime available independently of its launching UI or terminal
89
- whenever the host can execute and the required machine state is accessible.
90
- - **O2 — Failure stays with its owner.** A failed workload degrades its own
91
- capability and declared dependants without restarting its parent or unrelated
92
- capabilities.
93
- - **O3 — The runtime is always on.** Only an operator stop ends it. Every
94
- other exit is a crash, and a crash is retried forever after a delay capped
95
- at five minutes; a slow runtime is alive, and only sustained silence ends a
96
- generation. An update is a trial: the last good release is home.
97
- - **O4 — Health observation stays available.** Local control and liveness
98
- perform bounded work independently of product readiness, cloud connectivity,
99
- and workload size. No step whose cost grows with data runs on the event
100
- loop: a walk over many files yields between them, and each file's bytes,
101
- removal and metadata go through libuv's asynchronous calls, so health
102
- answers whatever the folder size. A container Enter of 12,004 files once
103
- held the loop for 138 seconds with synchronous copies, past the
104
- supervisor's two minutes, and the runtime was restarted for being busy.
105
- - **O5 — Each decision has one repository owner.** Core owns portable kernel
106
- policy, each product owns its domain policy, and Shell supplies composition
107
- and machine effects through their public contracts.
108
- - **O6 — Resource use follows necessary work.** Every host resource has one
109
- lifecycle owner and a declared bound, and idle operation performs no work
110
- except explicitly budgeted health, lease, and reconciliation duties.
111
-
112
- The detailed axioms below remain binding. Their mechanisms must serve these
113
- operating rules; a parity-preserved behavior that violates one is a documented
114
- gap to resolve at its owning SDK, not a reason to perpetuate the violation.
115
-
116
- ## Axioms
117
-
118
- Detect observes physical truth so local files keep their identity whether or not
119
- sharing policy selects them. Record admits only a coherent selected result;
120
- Send retries that immutable promise. Physical associations and the sharing
121
- baseline are distinct inventories, with one permanent UUID domain. The physical
122
- index retains last-proven-positive associations. Unresolved disappearance keeps
123
- that association until a complete examination distinguishes a move from removal;
124
- proved removal releases it, while nonreused UUID revisions and shared history
125
- remain. An absent row never proves disk absence. Watch/coverage and Add/Apply
126
- intents own uncertainty; no parallel absent-entity inventory is introduced.
127
- Every Detect lane now reads physical identity from this index and compares changes
128
- against the separate sharing baseline. Sharing rows never supply a missing
129
- physical address or inode association. One explicit
130
- ground store derives affected dependency keys from actual before/after writes;
131
- a transaction advances each affected key once and no-op writes advance none.
132
- An unrelated content edit cannot invalidate another entity's structural basis.
133
- Every database fact used by one observation must remain jointly valid at
134
- admission, alongside its closing source proof. An adaptive observer may add a
135
- previously unread dependency in a short read transaction; it never renews an
136
- existing dependency token. Admission closes the read set and checks every token
137
- and complete query predicate together before any write. Apply
138
- invalidates old observation permission before changing bytes, while its intent
139
- retains ownership of incomplete effects. Every Detect lane implements selection
140
- before Record; native completion with excluded local Git state remains open.
141
- `ground-store.ts` now owns all projection writes and atomic slot permutations.
142
- `ground-basis.ts` records short coherent original read receipts, with per-UUID
143
- revisions that survive row removal. Broad Record checks both physical and sharing
144
- bases. The named lane now accumulates indexed path, candidate, ancestor and
145
- subtree receipts before closing the read set. Bound Apply receipts protect physical
146
- attribution. Snapshot callbacks cannot write through the same connection, and repeated reads
147
- retain their first dependency token. Scoped creation requires a never-used UUID;
148
- a missing historical UUID needs its own original expectation. Failed
149
- batches roll back even if their caller catches an individual placement error.
150
- A shared content edit does not invalidate a separate parent's namespace proof.
151
- Optional examination evidence preserves each admission batch's original and final
152
- ground rows and exact appended records after its outer commit, including B-only
153
- changes. It never reconstructs a prior admission from later database state and
154
- never becomes another product journal or admission dependency.
155
- An observation owns every capture it starts until that read settles. Capture
156
- admission backpressures the walk at its fixed concurrency; failure stops new
157
- admission and drains already started work before the attempt returns. The same
158
- capture owner serves Register without changing its enrollment or upload journey.
159
- Independent read failures survive draining; source churn cannot hide an I/O error.
160
- Publication ownership never erases known sharing lineage. A child leaving a Git
161
- parcel requires complete standalone cargo and one record even when unchanged;
162
- its selected parent transition and required records commit together.
163
- A pending logical root must have an observed physical coverage owner before
164
- broad reconciliation can settle it; a missing owner is requested for the next
165
- held pass without consuming the nested responsibility.
166
- A named observation retains its physical source evidence until Record; reading
167
- another file or sealing a repository cannot make an earlier unvalidated read
168
- safe. Closing proof checks only the retained paths and ancestry, and retains
169
- owned values rather than caller-mutable Stats objects. Re-proving unchanged
170
- content retains its already sufficient content-read timestamp; access time alone
171
- is not a projection mutation or an invalidation of another observation.
172
-
173
- Each admission closes an original source proof once at its final requested
174
- position; distinct proof owners and the physical opening/closing bracket remain
175
- separate. Later phases must recheck the same original evidence. A retained Git
176
- reuse proof rereads semantic config and stash, then closes all its original
177
- file, absence, namespace and invocation witnesses. It never replaces a failed
178
- original with a newly equal digest. Optional seal eligibility may fail without
179
- discarding independently proved full capture; required reuse failure refuses
180
- admission. No working-file content or parcel is retained by this proof owner.
181
- Ongoing broad collection may prepare a provisional reuse decision without an
182
- intermediate complete close. Its enclosing root and Record boundaries must close
183
- the retained proof, including zero-record passes. Standalone observations,
184
- optional seal writes and cold journeys retain their closed contracts.
185
-
186
- Missing Git metadata keeps the first proved missing entry beneath its original
187
- physical parent. A missing suffix needs no invented directories. If that entry
188
- appears, the original proof rejects even when a deeper entry remains absent;
189
- closing never discovers a replacement reason for absence. Obstructions and read
190
- errors are not absence, and an obstruction's bytes need not be read. Repository
191
- availability and storage association remain separate binding obligations.
192
-
193
- A repository's O row may carry one local configuration-observation stamp.
194
- It binds the original value-bearing Git answer, invocation and physical binding
195
- to that UUID and actual observed payload; it is neither shared state nor cargo.
196
- The same captured configuration supplies Card remotes, so adjacent unrelated
197
- reads cannot certify a false pair. GroundStore commits the pair atomically. Fresh installation is an explicit
198
- repository-observation input; ordinary serialized rows may retain a still-valid
199
- stamp or clear it, but cannot manufacture a new observation by changing a hash.
200
- A parcel-reuse seal must compare its original configuration and semantic stash
201
- answers with those that produced the captured result before closing. Two
202
- independently successful observations never prove that pair. Initial native
203
- binding acquisition closes once against the subsequently captured prerequisites;
204
- later ordinary-layout closes retain those original inputs. Routing only compares this
205
- original O fact with current configuration and never refreshes it. Unknown, changed or unsupported proof retains complete repository
206
- responsibility, including disappearance of the last configuration contribution.
207
- Broad parcel reuse compares its freshly proved configuration and native binding
208
- against the original O stamp too. Other Git state and storage/alias proofs remain separate. Cold journeys may
209
- leave the fact unknown; B, received packages and acknowledgements cannot supply it.
210
-
211
- Apply's capture result distinguishes a completed observation from local-only
212
- changes and unresolved evidence. Live separately checks durable Outbox protection.
213
- Local-only work retains the intent and waits for a named Detect change before
214
- further effects; observing bytes never constitutes a backup. A matching target
215
- permits Verify only when its physical identity is established and no other
216
- effect remains. Every remaining effect passes the same local-work, preimage
217
- and destination checks under the complete ground scope. An interrupted effect
218
- owns a recovery obligation, never arbitrary later edits at its address. Recovery
219
- cannot be retired until its retained versions have an explicit safe disposition.
220
- Only verified materialization settles history: Verify, or an Add's install of
221
- exactly the entities it verified present or absent. Equality with a sharing row
222
- never manufactures a current materialization proof.
223
- The exact Apply outcome commits before private recovery deletion. The same
224
- intent then owns only a finite cleanup description; restart dispatches that
225
- responsibility without current O or old cargo. Cleanup hashes survivors with
226
- bounded streaming buffers, rejects replacements and unexpected objects, makes
227
- removal durable, and acknowledges only the matching nonreused terminal token.
228
- Collision recovery records original UUID-to-address moves and refuses retirement
229
- while rows and disk disagree. Repository Verify emits only its owned frontier;
230
- independent nested heads and observed/shared projections remain separate.
231
- Verify retains the metadata and closing witness from the content read itself,
232
- and an original database basis collected before deriving its output. Terminal
233
- commit rejects changed evidence and releases only the failed attempt's lease.
234
- A container's evidence is the object holding its address: device, inode and
235
- kind. Its children commit as their own Applies, and a repository's contents
236
- close with its observation. Its mode and times are local posture, so a chmod
237
- or a child's reveal between Verify and commit never faults it.
238
- Directory identity survives content equality: a replaced directory or ancestor
239
- must be reconciled before adoption or overwrite. Private preimages retain those
240
- directory identities too. Construct Verify hands its product result to the same
241
- terminal owner with an explicit absence of filesystem cleanup responsibilities.
242
- An immutable Apply receipt bounds every resumed effect. A changed forward plan
243
- does not enlarge that authority: reconcile an explained intermediate physical
244
- placement against its original basis, commit that correction with cancellation,
245
- retain newer sharing values and unresolved Inbox, then replan on the same rail.
246
- Recovery enters through the recorded cones before depending on a new parent or
247
- package. Every original effect still needs a disposition; unexplained ground
248
- retains its owner. Exact-target adoption may reach `revealed` without effects;
249
- that phase alone cannot suppress a later local edit. The current recovery
250
- cutover has controlled full-ideal evidence, including actual named Detect during
251
- row-before-rename recovery. The scoped receipt reader, deferred coverage and
252
- post-terminal wake are integrated as described above; the complete native and
253
- multi-machine examinations remain open.
254
- These Apply guard laws and the ignore publication host integration are being
255
- completed; component evidence is not a full-host pass.
256
-
257
- The runtime alone says which products it runs, and the Files program that
258
- delivers to them acts on that word. Until the word comes, a received construct
259
- waits with no error and no clock, and the word wakes it. A computer without a
260
- product says so at once, and Apply reports that as the error it is. A computer
261
- with Apps says so only once Apps has booted, because boot starts what it finds
262
- and must not find a delivery half made.
263
-
264
- Sync has one persistent machine setting: paused or enabled. An absent setting
265
- keeps the existing enabled behavior; pausing persists an explicit choice.
266
- It lives outside package generations and changes only by explicit command.
267
- Paused startup constructs no Files sync host: no Watch, Detect, transfer,
268
- Record Send/Receive, Apply, subscription or sync retry runs. Existing ground,
269
- identities, journals and retained cargo remain intact. Sync-dependent operations
270
- report `sync_paused`; local file access and independent products remain available.
271
- Core accepts literal paused evidence without claiming cloud currency.
272
- Shell owns the authenticated Gateway connection and its reconnect lifecycle
273
- independently of Files. The switch changes only the sync host's lifetime, in
274
- place: pausing cancels its requests and waits for its workers to stop, without
275
- restarting the runtime or disconnecting its Gateway. Resume starts the existing
276
- convergence and blind-interval reconciliation in the background. One control
277
- operation persists and applies the choice; future product policy can use that
278
- same operation. Starting, pausing and failure remain explicit states.
279
- Native Watch shutdown is complete only after every stream has stopped, including
280
- streams retired during coverage repair; closing logical coverage alone is no barrier.
281
-
282
- Channel orchestration resolves an explicit thread seed through Agents for a new
283
- Chat session. The seed supplies computer, cwd, model overrides and instructions;
284
- Shell never guesses from recent activity. Existing sessions remain Chat's
285
- authority, and Channels sends carry the trusted originating session identity.
286
- Until the owner saves Email defaults, Channels suggests them from this
287
- computer's last-used preferences; Shell offers them back only when the agent
288
- is installed here, resolves with that model, and can send, keeping the
289
- suggested folder only if it exists here and otherwise the agent's own, else the
290
- Workspaces folder.
291
-
292
- Registry acceptance and public installability are separate states; publication
293
- waits for the exact examined bytes to become readable before recording success.
294
-
295
- Shell composes Channels' local-media adapter around its authenticated client.
296
- That adapter captures referenced file bytes before durable hosted admission;
297
- Shell owns neither email rendering nor a second media parser. The same client
298
- serves MCP, CLI, and automation sends, so all local entry points capture media
299
- through one contract.
300
-
301
- Workspace selection lets an agent work in an exact existing folder on the selected
302
- computer. Every Shell startup composes Live's durable folder-link registry and
303
- Core's snapshot/event projection together, including when Files has no cloud rail.
304
- One folder remains a direct link; a named group remembers its selected child;
305
- neither registration nor removal copies, moves, or deletes the linked contents.
306
- The user's `workspaces/` folder exists before an unscoped chat can use it as its cwd.
307
- It is the one default folder: agent runs, automation steps, terminals and Email
308
- start there when nothing else is chosen, and a run started there also receives
309
- every registered folder outside it as an additional directory. Shell gives Chat
310
- the same folder, so a chat whose chosen folder is gone starts there instead.
311
- Each computer keeps these local links in the user's `.amalgm/workspaces.json`
312
- and their event tail in `.amalgm/state-events.jsonl`.
313
- The registry file is authoritative. Replacement validates the complete registry,
314
- flushes private temporary bytes and atomically renames them; a failed write cannot
315
- publish uncommitted entries from memory, and corrupt state is never treated as empty.
316
-
317
- Remote HTTP requests target the same authenticated Shell mounts as loopback
318
- requests. The existing wire stream protocol preserves response status and bytes
319
- incrementally with bounded buffering. A request belongs to its original wire;
320
- subscriber cancellation or wire loss aborts only that HTTP subscription, never
321
- the product operation it observes. Product interruption requires its explicit API.
322
- Shell advertises HTTP streaming explicitly in the authenticated wire hello.
323
-
324
- A materialized row proves local observation, not completed official delivery.
325
- An independent later observation starts from a settled basis only after earlier
326
- mutations are accepted, their matching Inbox records resolve, and Apply releases
327
- their intents; finite observation flushes do not promise global delivery silence.
328
- Shutdown can interrupt an Apply-requested observation, but cannot report that
329
- observation settled. Its exact Watch generation must be proved before the
330
- capture returns successfully; otherwise the existing intent remains unresolved.
331
- Apply retry reads revisit only the requested entities through indexed lookups
332
- and the same current eligibility rule used by paged discovery; page position
333
- cannot prevent a due entity from being reconsidered.
334
-
335
- Managed package delivery starts from a clean, exact main or preview source
336
- commit. The workflow occurrence supplies only its generated version and source
337
- record; tests run against those candidate inputs before packing. Every native
338
- gate and publication use that same tarball and integrity. A candidate tag makes
339
- bytes available to release assembly; it never promotes an installed runtime.
340
- Release tooling remains available inside each owner repository so a developer
341
- or CI job never needs access to another private product repository.
342
- Registry credentials are available only to the final protected publication job,
343
- after every native examination proves the exact candidate bytes.
344
- Native examination fixtures own their process pipes and test servers independently
345
- of the installed service, and release those resources even when service removal fails.
346
- Fixture cleanup preserves the original failure and every cleanup failure; installed
347
- state remains available when its native owner cannot be removed.
348
- A fixture's process lease covers its final writes, and its native release fences
349
- cleanup after either cooperative or forced exit.
350
- Fixture termination is proved by releasing its owned native resources; an HTTP
351
- stop acknowledgement or transport failure cannot substitute for that proof.
352
- A fixture publishes file-based readiness only after its complete evidence is
353
- atomically visible to the observing process.
354
- Native certification runs independent fixture files serially on its shared host,
355
- while each fixture retains the concurrent load required by its examination.
356
- The certifying producer owns fixture orchestration and loads production adapters
357
- from the exact installed archive, without modifying that archive's bytes.
358
- An outer fixture owner removes a temporary package only after the process loading
359
- its native libraries has closed and the package's native service owners have stopped.
360
- The final examination proof includes process completion and temporary-file cleanup.
361
- Public package selection is complete only when the ordinary registry endpoint
362
- observes the authorized version and integrity within one fixed deadline; cached
363
- predecessors do not authorize another tag write or extend that deadline.
364
-
365
- Shell owns both the internal `@amalgm/shell` package and the public `amalgm`
366
- distribution. One tested build supplies both archives; only package identity,
367
- version and the root lock identity differ. Each final archive passes the same
368
- native examinations before either becomes a managed public candidate. Public
369
- metadata records the exact internal archive it was derived from; no wrapper,
370
- copied Engine implementation or second dependency graph supplies runtime behavior.
371
-
372
- At the target boundary, release assembly selects exact registry artifacts from the same managed branch
373
- into a signed installation recipe. Compatible brick changes reuse the existing
374
- Shell artifact without a Shell dependency-update PR or lockfile edit. A product
375
- owns changes to libraries embedded in its own artifact. Reconciliation preserves
376
- human edits, coalesces candidates, and never republishes unchanged components
377
- because a notification or check was repeated.
378
-
379
- 1. **The shell implements host effects; SDKs own domain decisions.** Shell
380
- assembles published capabilities, implements their native effect ports,
381
- passes configuration, and mounts routes. A portable product decision belongs
382
- in its product SDK; a portable kernel decision belongs in `@amalgm/core`.
383
- A missing SDK port is repaired in that owner before Shell consumes it.
384
- Each SDK remains usable without Shell. Live and Chat preserve their
385
- Core-free dependency boundaries; Shell injects their host capabilities.
386
- One installed runtime and command do not require one operating-system
387
- process: isolation may change the host topology without changing SDK law.
388
-
389
- Agent-task execution is one example: Agents resolves the current immutable
390
- revision, Chat owns its new durable conversation and turn, Automations owns
391
- the queued step and retry key, and Shell only connects those capabilities
392
- to the selected machine's model, auth, Toolbox, and workspace bindings.
393
-
394
- The environment controller gives each signed-in user and validated binding one
395
- OS service outside every UI bundle. It holds an OS-released lease, publishes an
396
- authenticated control endpoint and supervises one child runtime over IPC. A
397
- missing heartbeat or a remembered PID never transfers ownership. A child exits
398
- when its controller disconnects; an intentional stop drains that child before
399
- releasing ownership. Service adapters derive their names from the same binding
400
- and never operate another environment's process.
401
- Every control mutation carries the expected user, binding and owner generation;
402
- the receiving controller verifies that identity before performing the mutation.
403
- Authenticating a response after an effect cannot authorize that effect.
404
- Layer 1 keeps one usable runtime available while the OS session can execute.
405
- One always-on policy (`src/service/policy.ts`) governs the copied launcher, the
406
- controller and the Windows action alike: only an operator stop ends the runtime,
407
- and every other exit restarts after a doubling delay capped at five minutes,
408
- forever. Shell records each launch in a durable SQLite journal before spawning,
409
- so controller replacement and repeated service starts neither reset the delay
410
- nor make anyone wait twice; sustained ready IPC health, an explicit
411
- `service retry` or an authorized update resets it. Any answer to an outstanding
412
- health question proves life however late it arrives; only a long run of on-time
413
- checks left unanswered ends a generation. Intentional shutdown never launches a
414
- replacement, and every stop records its reason.
415
- Native registration belongs to the current OS account even when the installation
416
- uses another data home. Windows Task Scheduler owns a hidden action in that
417
- account's logged-in session; the action owns controller exit recovery using the
418
- same policy. Scheduler launch retries alone cannot recover a program that
419
- started successfully and then exited.
420
- The copied launcher retains a bounded result and stop reason for each controller
421
- launch role, including failures before the controller can open its own log. It
422
- upgrades itself: a launcher that finds a newer revision installed exits at its
423
- next launch boundary so the OS starts the new one.
424
- Before launching any controller, the Windows action joins its own unnamed,
425
- non-inheritable, kill-on-close Job Object; every descendant remains inside that
426
- lifetime boundary, and only action termination releases its owning handle.
427
- Failed job admission refuses launch, and stopping one action releases its parked
428
- bootstrap and descendants without discovering or signalling remembered PIDs.
429
- Native service descriptions preserve literal arguments, environment values and
430
- working directories through the owning OS parser. Each directive uses its own
431
- grammar; unrepresentable input is refused before replacing a service description.
432
- Windows Scheduler requests travel as structured stdin, and both encoded
433
- PowerShell invocations are admitted within the native command-line length bound.
434
- Native Watch opens the OS-resolved physical directory; portable or short-name
435
- aliases cannot become a second path grammar inside a kernel handle.
436
- Persistent SQLite handles use the OS namespace for the selected file, including
437
- Windows extended paths; a host API's legacy path limit cannot select another file.
438
- That namespaced name is the file's one name: every registry keyed by a ground
439
- file uses the name its connections report, so no spelling selects a second
440
- owner. Releasing a ground file settles only once no thread of the process holds
441
- it, so the final checkpoint is part of closing and Windows can remove it after.
442
- Git's environment is read with the platform's own name rules; Windows names are
443
- case-insensitive, so `Path` is PATH and an inherited `git_dir` is still Git's.
444
- Each requests F_FULLFSYNC where the platform has it, because a plain macOS fsync
445
- can leave a commit in the drive's cache. Every write to a ground file is a
446
- named save run by that file's one saver thread (`src/ground-saver.ts`): saves
447
- posted while a commit flushes form the next batch, each in its own savepoint,
448
- committed once. A save settles only once the drive holds it, except an
449
- ordered save whose truth also stands elsewhere (Detect's admission, a stamp,
450
- a received page): it commits without waiting for the drive, and the next
451
- strict commit's flush covers it, because the log only grows. Send asks for
452
- that flush before every offer, so it submits only durable Outbox rows; the
453
- main thread's ground connections only read, so it never waits for the drive.
454
- Detect reports the journal, synchronous and fullfsync settings the saver's
455
- strict commits run under.
456
- Whatever launches the runtime process names the Node flags of
457
- `src/runtime-node-flags.ts`: a bounded young generation keeps each of the main
458
- thread's garbage-collection pauses to a few milliseconds.
459
- Every file and directory flush is the operating system's own, through Node
460
- (`src/flush.ts`): fsync, FlushFileBuffers on Windows, F_FULLFSYNC on macOS.
461
- There is no weaker flush, so a write that must persist before another is
462
- flushed before the other is issued. A flush covers only what it names, so it
463
- never waits for writes it did not make, and every flush through a handle
464
- takes one of a fixed half of Node's thread pool: behind someone else's
465
- writeback a flush can wait seconds, and the other half keeps serving reads,
466
- a placed file's included. Durability acknowledgements require that
467
- flush to succeed through a handle with the access it requires; a failed flush
468
- cannot become a successful install or materialization. Each writer owns the durability of the files it creates.
469
- Content equality alone cannot acknowledge durable materialization; Verify
470
- re-establishes the affected file and directory flushes before completion.
471
- The staging barrier composes a writer's acknowledgement only while its exact
472
- physical file remains unchanged, and a retry obtains fresh writer evidence.
473
- Git materialization requires Git 2.36 or newer to establish its declared writer
474
- durability before immutable object files are closed.
475
- A lane has one layout, version 2, named by its `.amalgm-root.json`. Shell
476
- creates that manifest in a lane that holds none yet, and refuses a lane whose
477
- manifest names another version with a "Reinstall Amalgm" error before it opens
478
- any of the lane's state. It never converts an older layout.
479
-
480
- Every UI enters one finite setup operation. It serializes installation setup,
481
- selects the server-approved account, and either proves adoption without changing
482
- the runtime or acquires that account's runtime lease before enrollment. The OS
483
- service takes over only after the enrolling foreground owner has drained.
484
- The operating system selects the credential backend; choosing a data home never
485
- changes it. Examinations inject their credential store explicitly.
486
-
487
- 2. **Managed bricks arrive through the registry.** Every production/preview
488
- `@amalgm/*` dependency is an exact published npm version. Explicit local
489
- development profiles may select local built SDKs; an absent local component
490
- never silently falls back to a managed package or hosted service.
491
- Upgrading the runtime means bumping a version, not merging code. Registry
492
- proof runs under the supported Node executable that launched the gate;
493
- ambient package-manager shims are not runtime evidence.
494
- The selected Node executable also owns dependency install scripts; an OS
495
- service's ambient search path cannot substitute another Node version.
496
-
497
- 3. **Parity gates each released service.** The target begins with
498
- `amalgm-engine`'s runtime surface, then subtracts only owner-approved
499
- retirements. A service enters the signed Shell release only when its active
500
- surface answers the same requests the same way. Unreleased services may
501
- remain in the Engine, but they never run as a fallback beside a released
502
- Shell service.
503
-
504
- 4. **Each shared host capability has one scoped owner.** Shell constructs
505
- shared adapters once for their installation scope and injects them instead
506
- of letting consumers rediscover them. Product-owned resources stay behind
507
- their SDK's public API: Apps, for example, owns its app processes and store,
508
- and Shell never opens a second lifecycle owner for them. Shell is what talks
509
- to the OS: it keeps the runtime alive and boots Apps once the runtime
510
- listens. Apps is then the light server that turns on, and keeps on, every
511
- app a person left on. Portable SDK
512
- decisions receive effects explicitly and never discover ambient process
513
- state or disk on their own.
514
-
515
- 5. **Bricks release independently; one installation owner adopts the graph.**
516
- Shell carries allowed component identities and supported host contracts,
517
- without bundling brick implementations or pinning their runtime versions.
518
- A separately signed recipe selects exact compatible artifacts and dependency
519
- graphs; compatible brick changes reuse unchanged Shell and UI artifacts.
520
- Registry tags locate candidates; fresh TUF metadata authorizes adoption.
521
- Bricks never update themselves, and one coherent tested graph governs each
522
- activation and its recovery. Artifact identity is separate from process
523
- lifetime: a changed in-process implementation requires draining its actual
524
- process cohort even when Shell's bytes stay unchanged. Release proof checks
525
- actual dependency resolutions and public contracts; it never forces all
526
- consumers onto one untested Core version.
527
-
528
- Accepted transition: current Shell packages still bundle a pinned SDK graph,
529
- and the current updater stages one Shell archive. A brick change may therefore
530
- temporarily require a checked Shell release while the boundary is completed;
531
- this does not block initial delivery. The
532
- [release contract](docs/release-environments-plan.md#current-release-contract--2026-09-08)
533
- defines the required transition and distinguishes it from existing evidence.
534
-
535
- The installed runtime follows the [update axioms](src/updates/README.md).
536
- Each public managed package declares its controller, process and state-format
537
- contracts. The native bootstrap stays outside immutable packages and executes
538
- Core-authored launch intents; a single SQLite commit binds update policy to the
539
- next controller. Historical signatures identify an already installed baseline,
540
- and current TUF metadata alone authorizes its desired successor. Every candidate
541
- is staged with the locked package manager before the previous runtime drains;
542
- fenced state-format receipts decide whether recovery can safely open its data.
543
- Local profiles retain their selected sources and do not follow managed targets.
544
-
545
- 5a. **One binding selects the whole installation.** Core's validated label,
546
- exact source branch and local session select separate mutable roots,
547
- credentials, databases, process owners and endpoints; production retains
548
- `~/amalgm`, preview uses `~/amalgm-preview`, and local uses
549
- `~/amalgm-dev/<session>`. Host effects reserve physical writable roots before
550
- use, including aliases and enclosing paths, so a second installation cannot
551
- become another writer of the same ground.
552
- A local profile may share only a declared managed Supabase, for sign-in;
553
- Core validates that selection, and every execution and control endpoint
554
- remains owned by the local installation. A local profile that declares no
555
- wire composes no Files cloud rail: setup skips Files convergence, Files
556
- commands and browsing report unavailable, and the runtime is still ready.
557
-
558
- 6. **Authentication exemptions transfer authority; they do not remove it.**
559
- Every exempt prefix is explicit and narrow, and the mounted brick must
560
- authenticate the request with its own session-scoped credential before any
561
- effect runs.
562
-
563
- 7. **Retirement is measured, not hidden.** A retired Engine surface stays in
564
- the committed retirement ledger and is excluded from both routing and the
565
- active parity denominator. Removing a dead contract must never look like
566
- serving it.
567
-
568
- 8. **The shell is the production runtime for its signed release.** The `amalgm`
569
- bootstrap may install, supervise, and update the shell, but it never starts
570
- an Engine implementation beside it or falls back to copied Engine behavior.
571
- The current release is Core + Files + Agents + Tools + Chat.
572
- Tools exposes its local product adapters from the declared source graph;
573
- a partial service selection does not hide an available Apps or Browser SDK.
574
- Hosted tool products additionally require their explicit endpoint. A local
575
- host never discovers an omitted product from registry dependencies.
576
- A declared Fly development host uses an exact template image plus selected
577
- local Core, its template's explicitly selected service configuration, and
578
- the local session's issuer keys. Its separate dev app has no public service
579
- routes. Shell owns the private tunnel and renewable guest lease; shutdown
580
- destroys that guest, and loss of the owner expires it within ninety seconds.
581
- Reusing a hosted template deliberately reuses its product data authority;
582
- temporary compute does not imply an isolated database. Only the named dev
583
- machine is stopped, and its source app's machines and secrets are unchanged.
584
-
585
- 9. **Login is Core followed by Live.** Core owns authentication, credential
586
- separation, installation verification, restart proof, and readiness. Its
587
- Files step returns explicit paused evidence or calls one `@amalgm/live`
588
- user-ground convergence operation. The shell supplies filesystem, SQLite,
589
- Watch, and cloud-wire effects only. Joining ground takes its place in one
590
- save that discharges what produced it (initial-publication.ts); ground
591
- already on the delivery line keeps its own position, and no startup jumps
592
- it to a newer head. Resume retains the existing recovery,
593
- Watch and Detect/Record order to reconcile a stopped or paused interval.
594
-
595
- 10. **One wire reaches the existing authority.** The shell's Live adapter uses
596
- the authenticated `/wire` private-resource protocol already backed by
597
- Postgres and R2. A test-only bucket, local cloud, or parallel HTTP authority
598
- cannot become the production path.
599
-
600
- 11. **A clean account is the cutover examination.** Two isolated Fly machines
601
- log into the same previously unused account. Machine A conditionally
602
- publishes the complete user ground; machine B materializes the same UUID
603
- graph and bytes into a different local SQLite database before Watch. No
604
- legacy Amalgm directory is mounted into either machine.
605
-
606
- 12. **Boot is idempotent over portable state.** Starting the runtime may
607
- create state that is absent, but it never rewrites a semantically
608
- unchanged tracked file with a machine-local timestamp. A materialized
609
- user ground stays byte-exact until a real user or product mutation occurs.
610
-
611
- 13. **The signed graph bounds boot effects.** Machine readiness starts exactly
612
- the services named by the verified release. Declared directories and tool
613
- artifacts may represent later products, but an unreleased product cannot
614
- instantiate itself, create a database, or mutate user ground during login.
615
-
616
- 14. **Service commands remain service-owned.** The shell parses and routes
617
- `amalgm <service> <command>`, supplies authenticated host effects, and
618
- renders the result. `files register` and `files add` decisions live in
619
- `@amalgm/live`; adding a shell-side Files implementation is forbidden.
620
-
621
- Files browsing delegates Amalgm and local-only source decisions to Live below
622
- `/files`. Shell serves authenticated filesystem bytes only for its own computer;
623
- cloud browsing reports unavailable until its authority port is composed. Workspace
624
- links and groups persist as one validated registry replacement before events are
625
- published. Disk remains authoritative after a failed persistence acknowledgement;
626
- corrupt and unsupported documents are refused, never replaced with defaults.
627
- Each streamed response owns its source through completion or client disconnect.
628
- The installation format, declared once as `RUNTIME_FORMAT`, reads every earlier
629
- direct-link, group, and Chat journal record. Its receipt advances before any
630
- product opens writable state; a runtime built for an older format cannot recover
631
- after adoption.
632
-
633
- 14a. **Automations CLI is one service-owned command surface.** Shell discovers
634
- the selected signed-in runtime, supplies its loopback admission credential,
635
- and delegates `amalgm automations <command>` parsing, schemas, envelopes,
636
- and behavior to `@amalgm/automations`. The CLI never owns a second
637
- Automations contract and never receives the durable machine credential or
638
- device key.
639
-
640
- 14b. **Channels CLI is one service-owned command surface.** Shell discovers
641
- the selected signed-in runtime, supplies its loopback admission credential,
642
- and delegates `amalgm channels <command>` parsing, schemas, envelopes, and
643
- behavior to `@amalgm/channels`. The CLI never owns a second Channels
644
- contract and never receives the durable machine credential or device key.
645
-
646
- 14c. **An idle Automations worker waits for a notification.** Shell wires the
647
- Automations SDK's authenticated event stream and executor into one worker;
648
- it owns no work-polling timer, schedule clock, or delivery queue. Startup
649
- and reconnect establish notification coverage before claiming retained work.
650
-
651
- 15. **Cloud materialization replaces only portable ground.** When the local
652
- SQLite projection is absent, stale, or empty, the cloud graph replaces the
653
- tracked user-ground namespace while the machine-only `.amalgm` control
654
- tree remains intact. A failed install leaves a clean retry boundary, never
655
- a partial portable tree.
656
-
657
- 16. **The process that owns Watch owns its shutdown.** A running host flushes
658
- every filesystem event Watch observed, closes coverage, checks once more
659
- for queued events, and only then tears down its wire. `files register` and
660
- `files add` execute inside that same running host, so declaration, SQLite,
661
- cloud, and Watch work use the established owners rather than constructing a
662
- second lifecycle. Register waits until the authority has accepted its
663
- workspace's package and reference, with healthy coverage, before it
664
- returns. An uncapturable repository leaves its ground owed to Detect,
665
- which records nothing of it; Live's binding and reference stay durable,
666
- so a retry waits on the same workspace. No package containing a
667
- `repo.git` without its verified Card + Checkpoint transport is offered.
668
- The
669
- watcher established after authoritative materialization remains the one
670
- ongoing watcher; the CLI never creates and immediately closes a second
671
- Watch lifecycle. Closing an unchanged watcher does not invent a full scan. A
672
- gateway response belongs to the exact wire that delivered its request; if
673
- that source closes first, the late response is discarded cleanly rather
674
- than sent through a replacement or closed wire. Closing is a one-way
675
- lifecycle boundary: an in-flight rescan may finish its durable work, but it
676
- can never recreate watcher handles afterward. One logical content watcher
677
- covers each outermost materialized tree: macOS and Windows use the native
678
- recursive primitive, while Linux expands it to exactly one inotify handle
679
- per directory. Enclosed logical roots share it, and one non-recursive
680
- watcher on the outer root's parent guards the root address itself. Roots
681
- with the same parent share that address watcher. An address ring names a
682
- root whose own directory entry changed. If the directory at that address
683
- is still the same device, inode, and filesystem creation generation its
684
- content handle was opened on, that handle already covers everything inside
685
- and the ring adds nothing; a lost handle or a replaced directory retires
686
- the handle and re-establishes coverage. The blind interval could hide an
687
- effect through an alias in any root, so every root is put completely in
688
- question. Ground that left is not lost coverage (Live's absence law):
689
- every binding is declared at its physical address, and a declared root
690
- that is missing, obstructed, or unreadable holds no handle, degrades
691
- nothing, and is heard returning by its nearest listable ancestor's
692
- address handle, while every other root keeps recording; a returning root
693
- is caught up whole. Detect treats a root standing on another device than
694
- it was bound on as unavailable too (`RootOffDevice`), while one re-created
695
- on its bound device is the same workspace, read whole and compared (Live's
696
- deletion law). Watch, the binding inventory, and Detect's domain
697
- check ask one presence question (`presentDirectory`), so they never
698
- disagree about which roots are there. The route Git takes from a
699
- checkout to storage outside every root (each link it follows and each
700
- directory it leaves by `..`, a gitfile it reads, the storage, its
701
- `commondir` file, a linked worktree's common directory), resolved
702
- physically as Git resolves it up to the first name Git cannot pass, is
703
- declared to Watch as dependencies of
704
- the root holding the checkout (`watching/git-storage.ts`): a storage
705
- directory gets its own content and parent address handles, any other
706
- name is heard at its parent's address handle filtered to its own change, every
707
- ring is forwarded to `<checkout>/.git`, and absence or replacement rings
708
- that path without degrading coverage. The route is read again when
709
- repository membership changes and when a finished Detect pass read ground
710
- holding the checkout. A checkout whose route Git cannot use yet keeps
711
- declaring it as far as it reaches, so a repair anywhere on it is heard;
712
- the walks that read it report it. On macOS each handle
713
- is its own FSEvents stream through Amalgm's own binding
714
- (`native/fsevents/`), which asks for per-file events delivered without
715
- coalescing delay, so a ring reaches Detect at the platform floor and
716
- opening or closing one never interrupts another; Node's own watcher serves
717
- every handle in the process from one stream that it recreates, resuming
718
- from the present, on every change, and loses the events in between.
719
- Initialization failure or handle death on present ground is reported as
720
- degraded, retains full-root suspicion, and retries independently of Detect;
721
- it can never be reported as active coverage. A Linux descendant directory
722
- the tree cannot enter is not lost coverage: its parent hears it. One that
723
- vanished needs no handle. One this process may not read keeps any handle it
724
- already had, and Detect names that ground unavailable, until an event on
725
- its name asks again; entering it then ends an interval no handle heard, so
726
- its whole root is put in question. Only the root's own failure is lost
727
- coverage.
728
-
729
- 17. **Independent content may travel concurrently; authority remains atomic.**
730
- The host bounds parallel uploads for small immutable objects and processes
731
- large objects sequentially so repository size cannot imply unbounded
732
- memory. The registry head advances only after every referenced object is
733
- durably acknowledged.
734
-
735
- 18. **A Git repository travels through Git.** A `.git` that passes Git's own
736
- structural test, read natively without running Git (`namesGitRepository`:
737
- its storage holds a valid HEAD and its common directory holds `objects` and
738
- `refs`; a `.git` link is followed, as Git follows it), classifies
739
- `repo.git`, and the same test draws each nested boundary inside a
740
- repository's capture. One Git would refuse is no repository: its
741
- directory is a folder or workspace on the same UUID whose children travel
742
- as ordinary entities until Git can use it again. `.git` itself, usable or
743
- not, is never an entity. Past that test, a Git failure defers cloud
744
- publication for that materialized root but never demotes the entity or
745
- prevents the watching runtime and unrelated roots from becoming ready. The
746
- host asks Git to pack the declared refs against the authority's known
747
- object frontier and asks Git to index received packs. Every directory whose
748
- `.git` Git can use begins its own repository rail. Ordinary children keep
749
- their UUID rows locally and ride in the nearest repository state metadata;
750
- a nested repository and its ancestry spine remain in the cloud graph, carry
751
- their own Card + Checkpoint, and materialize after their enclosing
752
- repository. The enclosing Card keeps its own Gitlink and index truth, but
753
- its Checkpoint excludes the nested worktree because that state belongs
754
- exclusively to the nested rail. Its enclosing identity entry carries only
755
- path, UUID, and type—never the nested repository's payload head. A shallow
756
- boundary travels with that metadata and is installed before Git reads the
757
- imported objects.
758
-
759
- 19. **Live owns transfer; Shell owns transfer effects.** `@amalgm/live`
760
- decides which entity types have artifacts, which chunks are missing, when
761
- an upload manifest may commit, and when a download is verified. The Shell
762
- adapter supplies one seekable verified source — immutable cache evidence
763
- when present, otherwise the exact registered ground selected by its UUID
764
- row — plus the authority inventory probe and a machine-local
765
- content-addressed artifact cache with reusable block locators. It never
766
- discovers identity, reclassifies ground, materializes, or publishes inside
767
- those transfer effects. Upload bytes use the authenticated binary
768
- WebSocket rail. For downloads, Shell obtains the authorized resource key
769
- once per process, keeps it only in memory, batches short-lived URL-signing
770
- requests through the gateway, fetches fixed-overhead binary envelopes
771
- directly from R2, and opens them through Live's protection contract. The
772
- gateway never relays download bytes, JSON/base64 is not a content
773
- transport, and no older download rail remains.
774
-
775
- 20. **Git is the repository-transfer performance gate.** On the same source,
776
- destination inventory, machine, and network path, cold upload sends the
777
- same Git object pack as a native push and incremental upload sends only the
778
- newly missing objects. Timing comparisons use repeated runs because wall
779
- clocks are noisy; byte-work parity is exact and any fixed Amalgm metadata
780
- overhead is reported separately.
781
-
782
- 20a. **Content layout and cloud namespace advance together.** The host names
783
- the one current manifest contract on every file-block write and exact
784
- read. With no customer data requiring an older reader, a content cutover
785
- deploys the authority first and its matching clients second; obsolete
786
- namespaces, wire fields, and fallback readers are deleted rather than
787
- becoming a parallel protocol.
788
-
789
- 20b. **Compression is a wire choice, never content identity.** A bounded file
790
- batch may use fast compression only when it becomes meaningfully smaller.
791
- Hashes, manifests, caches, and R2 protection always prove the exact decoded
792
- bytes; incompressible input travels unchanged.
793
-
794
- 21. **Watch events preserve suspicion until proof.** Watch preserves the
795
- producing handle, optional path, and native evidence that widens its scope.
796
- A named event preserves that hint; loss or possible hardlink effects require
797
- one examination across every configured materialization root. Such a shared
798
- obligation settles only when every participating root completes against the
799
- same frozen Watch generation and binding set. Unavailable ground remains
800
- pending; a changed binding set requires a new complete examination. A cut
801
- frozen under it is proved by root identity, never binding instance: once
802
- every root it named is bound again and examined completely through its
803
- generation, by that examination or a returning root's own whole catch-up.
804
- A named root still away keeps the cut pending and is answered unavailable,
805
- never settled. The runtime's database is never opened a second time by its
806
- name: while its home, or a directory down to it, is not the object it was
807
- opened in, that ground is unavailable and flush says so at once; the file
808
- alone changing beneath directories that still stand is a fault. Native
809
- event IDs are diagnostics, never identities or settlement cutoffs. Unexpected
810
- coverage loss retains one episode through repeated reopen failures; its
811
- qualifying observation starts only after replacement coverage is healthy.
812
- Detect waits on the existing recovery wake while coverage is unavailable.
813
- A later coverage loss invalidates an in-flight recovery proof. Ordinary
814
- unnamed notifications retain complete covered-root suspicion. Watch does not
815
- read `.amalgmignore`, inspect `.git`, classify a file, or
816
- infer create, move, rename, and delete semantics. Detect reads live policy
817
- and repository evidence when it observes the suspicion. Only Core's fixed
818
- `.amalgm/` control subtree is structurally outside Files ground. Its named
819
- notices may be dropped only after native scope ambiguity has been preserved.
820
- A scan settles only the generations
821
- it observed, so an event received during that scan remains pending.
822
- An object's change is a change at every one of its names: a committed name
823
- whose object changed, or which left an object with another name, rings each
824
- other name the inventory holds for it, in any root, unless that alias is
825
- already recorded at the committed stat. Native alias evidence names the
826
- objects a name held (the FSEvents file ID is the inode); each such object
827
- rings every name the inventory holds for it before the cut is proved, and
828
- a hint whose objects are unknown rings the domain. Each alias is read as
829
- its own name in its own root; bytes and identities never propagate between
830
- names.
831
-
832
- 22. **Physical bytes supply worktree evidence.** Git's index describes stored
833
- blobs, not necessarily the files on disk. Shell derives a worktree leaf's
834
- type and payload from the same stable byte observation; any NUL means
835
- binary, including beyond Git's preview window. Index flags, attributes
836
- and checkout conversions cannot suppress that observation or choose its
837
- type. A Git object identity is reusable only with proof of raw byte
838
- equality. Checkpoint replay preserves those exact bytes independently of
839
- receiver settings. Git ignore never becomes Amalgm Detect policy.
840
- Observation cannot alter Git object timestamps either: source object
841
- alternates are read-only inputs, and every object-writing command runs
842
- with private storage alone. Patch writers copy only their required base
843
- blobs into that private storage first.
844
- A proof's private Git work does not grow with what changed. A tree is
845
- written from a fresh index of exactly its entries, and the same entries
846
- asked again reuse it. Changed blobs, like a patch writer's bases, enter
847
- private storage through one fast-import that takes each blob's bytes only
848
- as Git reads them. Both patches come from one diff-tree from HEAD's tree,
849
- which the Card's own HEAD question peels without replacement objects.
850
- Indexed and untracked inventory share one native-index observation, read
851
- without a Git process and versioned by what capture means by an index:
852
- its stage listing, exactly what `git ls-files --stage -z` writes
853
- (`src/git-index-format.ts`). Capture asks nothing else of an index, so a
854
- refresh that re-stamps stat data, a version change, or entries moving
855
- between a split index and its shared base leave every answer drawn from
856
- it standing; the witness keeps the bytes it decoded and decodes again
857
- only when they differ. Git lists untracked names over copied index bytes,
858
- and repository/storage bindings remain valid through closing capture. One Git binding owner retains the original effective
859
- invocation and lexical/resolved directory associations. It re-resolves
860
- through Git at each bracket; one framed batch replaces four commands, with
861
- scalar fallback preserving embedded or trailing newlines. No incomplete
862
- config-source list can authorize cached location reuse. Special index files are refused with nonblocking, no-follow
863
- reads. Only the shared base a split index names is read, from the Git
864
- directory before the index's own as Git reads it, and its checksum must
865
- match the link. Observation never freshens a shared base; that timestamp
866
- refresh remains Git's own work. Thin-pack export reads borrowed objects through the
867
- private repository without source remote configuration. Checkpoint decoding
868
- and member verification have one private preparation owner, separate from
869
- index installation and working-file effects. Replay consumes and closes that
870
- preparation; it does not maintain a second package validator. A sparse
871
- index's folder entries, each one tree outside the cone, are read as Git
872
- writes them and are their files' meaning. Git is never handed a sparse
873
- index beside borrowed objects: Git expands one by writing every tree it
874
- expands, and writing an object Git already holds refreshes the source
875
- file's time, so the read would ring the repository's own Watch and each
876
- capture would cause the next. Inventory that needs those files asks one
877
- Git tree reader over borrowed objects, and Git lists untracked names over
878
- the full index written from them in private storage, borrowing no
879
- objects. Any stderr fails either read, because Git reports a tree or a
880
- folder it cannot read yet exits 0 without it, and Shell's Git is asked for
881
- no advice. No incomplete inventory escapes, and no source index or object
882
- is written. A form Git never
883
- writes, or a required extension Git would not understand, is refused
884
- rather than guessed. A zero split link has no shared-base dependency.
885
- Fast reuse closes the complete metadata/namespace proof, whose index
886
- member is its meaning; its presence tags distinguish absent files from
887
- all possible bytes.
888
- Shared registration inspection closes its physical and boundary witnesses
889
- against that same native-index basis.
890
-
891
- 23. **Cold add never rereads a repository graph.** Download verifies and
892
- seals each content-addressed transport to a file, streams its Git pack
893
- range directly into `index-pack`, and derives local SQLite rows from the
894
- transported UUID/type/payload identity map plus filesystem stats. Nested
895
- repository rails are applied outside-in at the UUID paths certified by
896
- their enclosing identity maps. It does not buffer a complete repository
897
- parcel or reclassify checked-out files.
898
-
899
- 24. **Machine caches are disposable evidence.** A cached immutable object is
900
- reusable only when its bytes satisfy the current format and the persisted
901
- entity identity. Missing, corrupt, or obsolete cache bytes are removed and
902
- recomputed from authoritative local ground; they never become a legacy
903
- compatibility requirement and never prevent the machine from resuming.
904
- A cache name appears only over durable bytes: every writer flushes a
905
- staged file before renaming it into place, so an existing name already
906
- holds that immutable object and a rename over it replaces identical
907
- durable bytes. Windows refuses to replace a name another holder has
908
- open; that name is judged as one found before staging, adopted only when
909
- it qualifies. A staged file is flushed when it is named, not when it is
910
- written: a pass that captures a set names the cargo its Records carry once
911
- the whole set has staged and removes the rest unflushed, so its reads
912
- never wait on the drive. A Record and its cargo become durable together.
913
- The small cargo a named pass read commits in its Record's own
914
- transaction, so the log's order is its durability and the pass pays no
915
- flush; the cache names it afterward, and the journal lets it go only once
916
- the name is durable. Send reads the journal first; any other reader of an
917
- unnamed name finds it absent, which it already answers (a delta base
918
- selects the snapshot). Any other cargo is named before its Record commits,
919
- with one flush of the cache directory, off the event loop, and none when
920
- every required name is already known flushed. A crash can lose an
921
- unrecorded name, never leave a Record whose bytes stand nowhere.
922
- A pending Send consults its capture-derived manifest and the authority's
923
- immutable inventory before opening local cargo: after upload succeeded but
924
- before its acknowledgement became durable, complete cloud cargo is enough
925
- to finish the same mutation retry. Local bytes are required only for blocks
926
- the authority proves are still missing. Shell moves exactly the cargo heads
927
- named by the Record: a structural Record names no cargo and cannot resend
928
- the entity's existing bytes. When the negotiated wire supports it and all
929
- declared cargo is bounded, Shell supplies the cached manifest and blocks to
930
- Live for the same submit frame; otherwise it uses the ordinary missing-block
931
- effect. A cached manifest is read off the main thread and is only a hint:
932
- an absent or invalid one takes the ordinary obtain-or-derive path; the
933
- pending Record that names it retains it. The cloud, not Shell, owns the
934
- final seal-before-number decision.
935
- Cache bytes remain only while an unresolved durable operation names their
936
- content head, while the current verified text or repository head is the
937
- one exact base for that entity's next delta, or while a writer that will
938
- Record them holds their fence (`src/content-cache-fences.ts`). Collection
939
- is due at boot, after 1,024 new cached names, and hourly, as `git gc
940
- --auto` is; it derives what no row retains from SQLite and removes it,
941
- skipping each name fenced since its listing and that name's held parent
942
- chain, so accepted history cannot accumulate as machine storage.
943
-
944
- 25. **Each cold stage performs only its necessary byte pass.** Registration
945
- reads every ordinary text or binary file once through the bounded capture
946
- stream to classify it, derive its content head, and retain large-file
947
- manifest evidence. A Detect that plans Send seals those bytes in the
948
- disposable cache in the same read; a first publication's login walk does
949
- not also copy them there. Upload first proves which heads are already sealed,
950
- touches no source for those heads, and reads each remaining artifact once
951
- from the strongest available evidence: an existing verified cache object,
952
- otherwise its registered ground path. Every emitted block is checked
953
- against the captured head. If ground moved between capture and Upload, the
954
- unsubmitted publication is discarded and Register performs a bounded fresh
955
- capture; stale bytes never travel. Download opens each sealed R2 object
956
- once. During Add, ordinary text and binary plaintext lands directly in its
957
- resumable hidden destination; retained chunks are re-proven on recovery,
958
- so no second whole-artifact cache copy or seal pass sits on the cold path.
959
- Links, repository transports, warm cached content, and non-Add callers
960
- keep their dedicated adapter/cache rails. Because Register does not retain a
961
- text replay base solely for future edits, the first later text save may
962
- carry a full verified snapshot; that save's own capture establishes the
963
- base used by subsequent deltas.
964
-
965
- 26. **A Files effect command is not a second login.** `files add` proves the
966
- selected ready machine, authenticates to its already-running loopback
967
- runtime, and asks that runtime's existing Files host to download the
968
- selected graph. It does not run Core convergence, rescan existing ground,
969
- or create a second cloud wire, SQLite writer, or Watch host.
970
- 27. **Block identity does not dictate transport shape.** Upload may group
971
- adjacent blocks in bounded binary frames. Download asks the gateway only
972
- for authorization material and batches of short-lived object URLs; each
973
- sealed manifest or block then travels directly from R2 to the runtime.
974
- Content hashes and verification remain identical across those transport
975
- choices.
976
- 28. **Cache evidence is transactional metadata.** A partial or sealed file's
977
- block evidence is one disposable machine-local SQLite index, so a cold
978
- file never creates hundreds of marker files merely to prove resumability.
979
- 29. **Independent files overlap; memory stays bounded.** Add downloads several
980
- distinct text, binary, or link artifacts concurrently, deduplicates equal
981
- content heads before transport, and lowers each file's internal batch
982
- window so the combined cold byte window remains bounded.
983
-
984
- 30. **Files commands converge on one watching runtime.** `amalgm files
985
- register <workspace>` asks the already-running runtime to place the
986
- workspace's binding, starter policy and reference, then waits while
987
- ordinary Detect, Record and Send publish the new ground as one package
988
- record, until the authority's accepted view holds it as its own root.
989
- `amalgm files add <workspace>` asks that runtime to materialize the selected
990
- cloud graph, refresh the exact durable reference inventory in core ground,
991
- and extend its existing Watch coverage before returning. References to
992
- unselected boundaries stay dangling and create no workspace rows or bytes.
993
- The command only waits: a stop (SIGTERM, SIGINT) ends its wait at once
994
- and exits 130, while the runtime keeps the journey and the same command
995
- run again resumes it. Every failure names its stage, traced or not: the
996
- runtime's own open stage, or whether the runtime was never reached or
997
- stopped answering.
998
- Add refuses any destination that overlaps already materialized Amalgm
999
- ground, including the user's own home, so one physical tree can never
1000
- acquire two graph roles or expose staging through an existing watcher.
1001
- Add first journals one local installation intent, downloads into a private
1002
- staging directory beside the destination, and verifies the complete graph.
1003
- It then commits the exact entity rows in one transaction, atomically moves
1004
- the verified ground into place, and exposes its binding last. The intent is
1005
- removed only after healthy Watch coverage exists. Entity rows therefore
1006
- never mean "pending download": a restart resumes the one intent from
1007
- immutable authority plus locally re-proven staging and can repair any
1008
- interrupted reveal without reminting identity. Ground that was already
1009
- visible across a restart is never
1010
- accepted as an authoritative install baseline: Watch retains complete
1011
- suspicion and Detect settles that blind interval before the intent clears.
1012
- Hidden staging is untrusted resume substrate, never materialized truth.
1013
- Ordinary text and binary chunks land directly at their hidden staged
1014
- destinations, and an interrupted Add may retain them only with disposable
1015
- chunk evidence beside the ground database. Resume rereads and re-hashes
1016
- every retained chunk against the pinned manifest, downloads every missing
1017
- or corrupt chunk, and proves the ordered whole-artifact hash. Durability
1018
- is one explicit barrier over the whole staged tree — every file,
1019
- duplicate, repository and folder, each flushed through its own handle,
1020
- never the whole filesystem — that must succeed before entity rows are
1021
- committed or ground is revealed; ordinary streamed files defer their flush
1022
- to that barrier. A
1023
- failed barrier leaves the intent retained, no rows committed, no visible
1024
- destination, and staging re-proven as untrusted on retry. Links and
1025
- repository transports keep their type-specific cache and adapter rails.
1026
- One recovered Add intent that cannot currently be satisfied remains
1027
- durable and reports its exact failure, but it cannot hold unrelated machine
1028
- readiness or other Add responsibilities hostage.
1029
- Add and Add recovery read only the selected workspace's recursive closure
1030
- and the exact reference parents they must refresh; unrelated materialized
1031
- workspaces remain SQLite facts and never become the selected operation's
1032
- in-memory graph.
1033
- Staging beside the destination makes the reveal an atomic rename on every
1034
- supported filesystem. Every staged build, login install, Add and container
1035
- Enter alike (`materialize-records.ts`), copies each file from the
1036
- immutable cache with one asynchronous `copyFile` asking for a clone: the
1037
- kernel clones where the filesystem can (APFS, Btrfs, XFS, ReFS) and copies
1038
- where it cannot, on every OS the same call. Four copies run at once, the
1039
- width of libuv's thread pool, and the walk yields before each.
1040
- Register reuses identity at the same native address. Device and inode may
1041
- rescue a move only when the prior address is gone; a different address
1042
- that is still present is a collision or hard link, never the same entity.
1043
- The refreshed references and their parent container's derived membership
1044
- version enter machine SQLite in one transaction, so the authoritative
1045
- install is already internally consistent before Watch opens it.
1046
- Neither command creates a second long-lived watcher. Certification inspects
1047
- real health and handle topology rather than accepting `{ active: true }`.
1048
- A graph that `add` has just materialized and verified is the initial
1049
- baseline for that newly covered root, so Watch does not report the
1050
- downloader's own writes as user edits; every later OS notification remains
1051
- ordinary suspicion. The same verified install is Apply's materialization
1052
- baseline, committed with its rows: each installed entity resolves through
1053
- its last received record within the watermark, materialized at that record
1054
- when the install verified exactly its version, and each set-aside member,
1055
- verified absent, resolves at the same place, materialized nowhere
1056
- (`src/apply-window-saves.ts`). Every other received
1057
- record, including every later record of those entities, remains ordinary
1058
- Apply work, and the Add wakes Apply's line once it releases its ground.
1059
- Watch may establish native coverage before startup Apply is ready, but its
1060
- suspicions remain unconsumed until Apply has acquired its binding roots and
1061
- resumed durable materialization; only after Apply starts does one Detect
1062
- generation consume the rings accumulated during boot. Register
1063
- and Watch enumerate the same durable binding inventory, so a missed
1064
- notification for rendering the portable reference cannot lose a
1065
- registration. A bound root with no rows is new ground: Detect walks it
1066
- once and records it as one package on its root UUID (Live
1067
- `packageProposals`), every member keeping its own UUID inside the
1068
- package's pages, beside ordinary creations for its reference and any
1069
- folder on its way. Ground placed in the home directly is the same new
1070
- subtree, packaged by the same pass with no command.
1071
- Registering ground that encloses workspaces this machine already
1072
- materializes absorbs each one. Every identity is kept inside the new
1073
- package; only the absorbed root's own record changes: its parentUUID and
1074
- name become where the enclosing walk found it, and a `workspace` becomes
1075
- a `folder`. Ground inside a materialized workspace is refused, because
1076
- that graph already holds it. Overlapping registrations never create a
1077
- second identity family.
1078
- Register success is scoped to the selected workspace and its reference:
1079
- it suspects those two, waits for Detect to prove that cutoff, flushes
1080
- Send, and reads the accepted view until it holds both, with healthy
1081
- coverage. It never waits for unrelated Watch traffic to become silent.
1082
- Re-registering a workspace the accepted view already holds as its own
1083
- root records nothing: it proves cargo closure (31) and returns, and Watch
1084
- continues to own subsequent content changes.
1085
- 31. **Cargo closure is proved under the current contract.** A graph head
1086
- never proves cargo: a record may name content sealed only under a prior
1087
- content contract, whose namespace the current readers never touch. Only
1088
- the authority's durable seal for the exact (resource, content hash,
1089
- current content contract) proves an artifact's cargo. Before Send offers
1090
- a package, it asks the authority which of the package's artifacts and
1091
- pages are sealed and uploads exactly the remainder as one cargo stream,
1092
- the pages after the members, so a new workspace uploads once. Before
1093
- answering an idempotent re-registration, Register asks the same of every
1094
- content head the accepted workspace names and re-ships each lacking one
1095
- that its cache or ground still holds exactly. One overtaken here already
1096
- travels as its own Record; the stage names how many it could not restore.
1097
- 32. **Coverage precedes recovery, and coverage is not currency.** On process
1098
- start Watch first opens the same durable root topology, then Detect closes
1099
- the interval during which no watcher existed. Healthy handles prove that
1100
- new changes cannot be missed; a root remains `catching-up` until its saved
1101
- uncertainty has been inspected and settled.
1102
-
1103
- 33. **Restart catch-up glances before it opens.** Machine SQLite persists each
1104
- entity's device, inode, kind, size, mode, modification time, and change
1105
- time, plus the instant at which leaf content was last verified. A complete
1106
- recovery walk enumerates names and compares that stat fingerprint without
1107
- reading a stable leaf only when its modification time strictly predates
1108
- that content witness; same-tick evidence is deliberately rechecked. Stable
1109
- directories need no reclassification. New or changed entries enter the
1110
- ordinary Detect and Record path. Directory membership is reused, while
1111
- the cheap `.git` marker classification is always observed from current
1112
- ground. Repository roots re-prove Card + Checkpoint state through Git,
1113
- because `.git` is deliberately outside the entity graph — but on a complete
1114
- pass Git's own records may stand in for the conversation: each accepted
1115
- capture seals a spawn-free fingerprint of HEAD, every loose ref,
1116
- packed-refs, the stash reflog, config, the shallow boundary, and the index
1117
- file's bytes and physical identity, bound to the exact heads and identity
1118
- map it certified.
1119
- Only when the current fingerprint, the stored heads, the derived identity, and every
1120
- owned entry's stat fingerprint all still match that seal is the Git
1121
- conversation skipped. Any single doubt — including a gitfile boundary or a
1122
- Git storage layout those state files do not fully describe — asks Git in
1123
- full.
1124
-
1125
- 34. **Recovery work and evidence are root-scoped.** Each logical root reports
1126
- its own `catching-up` or `current` state, records its own scan evidence, and
1127
- commits its local projection independently. Detect yields between roots so
1128
- one large recovery walk cannot erase Watch events or hide the readiness of
1129
- unrelated coverage. A root with no current suspicion is reused without
1130
- inspection even when an old repository rail there remains incomplete; its
1131
- own next event or startup suspicion retries that rail. The portable
1132
- registry head remains one atomic graph. Catch-up holds at most one complete
1133
- evidence graph in memory; materialization membership streams from SQLite
1134
- and Detect never builds an unused second portable snapshot. Rows are
1135
- assigned to disjoint outermost roots in one path-depth-bounded pass; restart
1136
- never compares every entity against every registered root.
1137
- Command proofs use indexed existence, descendant-count, and UUID queries;
1138
- they never materialize the complete machine graph merely to answer a
1139
- selected root's yes/no or count question. Cloud publication reads only the
1140
- portable record projection from SQLite, never a second path-and-stat graph.
1141
- A committed cloud registry is likewise held as its small immutable head:
1142
- login reads the core root, Add reads the core root plus its selected
1143
- boundary, and publication carries untouched roots forward by page identity.
1144
- No operation flattens an unrelated cloud root into memory.
1145
-
1146
- 35. **Container membership is version input, never cargo.** A workspace or
1147
- folder derives its logical version from the UUIDs and names of active
1148
- direct children, while its portable and notebook `payloadVersion` remains
1149
- null. Every Shell writer stores only the derived version: each save that
1150
- changes membership derives it inside its own transaction from the children
1151
- that inventory records, so a child no save has recorded counts nowhere,
1152
- no row comparison counts a container's version, and no proof holds it: a
1153
- proof holds where a container stands and the slot it takes, so a sibling
1154
- recorded meanwhile never stales it. Live's cloud codec refuses
1155
- a container payload. An independently ordered container
1156
- receipt may therefore create, move, or rename its address, but it can never
1157
- overwrite membership already established by child UUID rows or emit a
1158
- second container mutation for that derivation. Local adapter evidence can
1159
- never masquerade as a transferable content head.
1160
-
1161
- 36. **Portable path grammar becomes a native path only at the host boundary.**
1162
- Core and Live describe path components with `/`; Shell performs portable
1163
- parent and name operations with that grammar, preserving `\\` as a literal
1164
- character, and only then resolves those components with the host platform's
1165
- path semantics for a filesystem effect. Durable records never rewrite or
1166
- mix separators accidentally. A link's target text is portable grammar
1167
- too, as in Git: it travels with `/`, and only a Windows host converts it,
1168
- `/` to `\` when writing a link and `\` back to `/` when reading one
1169
- (`src/link-target.ts`). Windows writes it through its own link call,
1170
- which keeps the text; only a target holding a literal `\`, or naming a
1171
- drive without a root (`C:x`), cannot be reproduced there.
1172
- Bindings and managed references are machine-local paths and stay native.
1173
-
1174
- 37. **Git materialization reproduces Card bytes independently of machine
1175
- preferences.** A repository created by Add disables receiver-global line
1176
- ending conversion before checkout. Platform Git configuration cannot
1177
- silently rewrite the committed object truth carried by the Card.
1178
-
1179
- 38. **The effect owner closes every native resource it opens.** Shell shutdown,
1180
- completed downloads, and examination teardown release their SQLite,
1181
- process, socket, and watcher handles before ground may be moved, deleted,
1182
- or reopened. Unix permission to unlink an open file is never used as proof
1183
- of a complete lifecycle.
1184
- A Git invocation settles after its process closes and its input producer is
1185
- released: Git's exit judges a closed input pipe, while an observed producer
1186
- failure remains a failure even after Git exits or reports no match.
1187
-
1188
- 39. **A finite CLI command leaves no transport alive after its result.** The
1189
- running runtime alone owns persistent connections; register and add close
1190
- their loopback request before the command process exits. That request is
1191
- bounded by the service result, never by a generic HTTP response-header
1192
- deadline: fresh-byte Register and Add journeys may legitimately take
1193
- minutes while their durable work continues.
1194
-
1195
- 40. **Interactive processes use the host's declared shell.** Unix reads
1196
- `SHELL`; Windows reads `ComSpec`; a test or deployment may override that
1197
- declaration, but Shell never assumes one platform's executable on another.
1198
-
1199
- 41. **Runtime admission and Files currency are independent boundaries.** Files
1200
- convergence and the ongoing Watch → Detect path alone decide whether ground
1201
- is current. Starting a runtime advertises its already-listening gateway and
1202
- waits for the authority's acknowledgement; it never forces another scan or
1203
- waits for watcher silence.
1204
-
1205
- 42. **Finite shutdown has one explicit observation cutoff.** Shell first marks
1206
- every covered root suspect, retires native Watch handles, and then performs
1207
- one final Detect/Record pass. Native events cannot make shutdown unbounded;
1208
- changes after the cutoff remain inside the blind interval that startup
1209
- catch-up is required to close. Neither can a writer that keeps changing
1210
- ground: the final pass reads again only a racy listing, whose wait is
1211
- bounded, and reports any root whose ground still moved as incomplete,
1212
- never as a wait. A systemic fault fails shutdown after teardown; ground
1213
- that cannot be read is unsettled, not a fault. Otherwise an incomplete
1214
- answer names every cause that applies, each on its own: the unfinished
1215
- Apply intents that own ground, the roots still moving, the roots that
1216
- could not be read and the roots Git refused. An intent whose binding
1217
- cannot be reached is named with that binding as unreadable ground; a
1218
- binding proved to be another object fails shutdown, and the old intent
1219
- never acts on it. One cause never erases another, and the answer does
1220
- not depend on the order in which lanes parked. Network delivery is not
1221
- part of the cutoff. Apply's last flush and Send's last delivery share one
1222
- finite network budget; once it is spent, closing the wire cancels what is
1223
- still in flight, Apply keeps its durable intent, and shutdown reports the
1224
- records still saved locally, naming those sent without an answer. It
1225
- never calls them synchronized: they send again under the same mutation
1226
- identity when Files next starts.
1227
-
1228
- 43. **Record commits evidence before Watch settles.** The host reconciles a
1229
- Watch generation against one last-verified detection notebook, writes the
1230
- exact portable Detect proposals into the local-only record outbox, and
1231
- advances that notebook in the same SQLite transaction. The materialized
1232
- `entities` table contains only ground present on this machine; the notebook
1233
- may retain the UUID and last verified evidence for missing ground so an
1234
- external disappearance cannot invent a delete or a replacement identity.
1235
- Repository boundaries own the portable changes of their enclosed children:
1236
- gaining `.git` records one Card + Checkpoint transition, while losing it
1237
- recaptures those children through their newly selected file rails. Watch
1238
- settles only after this transaction is durable and never interprets any of
1239
- these meanings itself. Filesystem observation is optimistic: the commit
1240
- compares every changed UUID with the exact notebook row the pass observed.
1241
- If Apply or another Detect advanced any basis row while the filesystem was
1242
- being read, the whole commit is refused and the retained Watch generation
1243
- observes fresh truth; stale evidence can never overwrite proof or create an
1244
- outgoing echo.
1245
-
1246
- 44. **One Detect job owns finite original Watch cutoffs.** A pass settles
1247
- only the generations it froze before reading truth. Later notifications
1248
- remain pending even when they arrive during a yielding walk. Named work
1249
- uses its closed dependency scope; identity ambiguity, lost attribution or
1250
- coverage recovery can require a complete materialization domain. That
1251
- cohort admits and settles only as a whole. Independent periodic freshness
1252
- is a separate reason to examine silent roots, never a fabricated native
1253
- notification. An explicit flush retains its original completion boundary
1254
- across older in-flight work and later recurrence. No caller waits for the
1255
- operating system to become globally silent.
1256
-
1257
- 45. **Detect scope follows its proof dependencies.** Shell holds one
1258
- prepared SQLite owner for Detect. A qualified named observation uses
1259
- indexed identity, original parent/sibling context, physical witnesses and
1260
- changed bytes. It widens when those facts cannot close attribution; an
1261
- edit through a vanished alias reaches the object's remaining names through
1262
- the object native evidence saw, even when no row ever occupied that path,
1263
- and widens only when that object is unknown. Old and new addresses reconcile
1264
- under the same complete identity law. Ordinary structural changes still
1265
- use broad reconciliation; constant-time named work is not a current claim.
1266
- A Git lock (`<path>.lock`) is a write in progress, never proof that
1267
- reading is unsafe. Detect reads the committed files and current physical
1268
- bytes and closes their normal source witnesses even while a lock exists.
1269
- A lock says only when a rung lane reads: a changed state that shows a
1270
- lock last written less than Git's longest lock wait (1 s, `@amalgm/live`
1271
- `git/locks.ts`) ago holds its repository as moving ground until the
1272
- lock's release rings or that second ends, and the held lane parks for
1273
- exactly that deadline. A lock still standing then is a command left
1274
- unfinished and travels; a cold journey reads through every lock. Moving
1275
- evidence without a known deadline retries after 250 ms. A stale lock
1276
- therefore cannot prevent completion and is never deleted by observation.
1277
- Shell's own background Git reads disable optional locks so observation
1278
- never rings itself merely by refreshing the index.
1279
- Nameless, invalid, startup, and
1280
- failed-coverage evidence also enter complete reconciliation. No ordinary
1281
- named Detect pass serializes a workspace snapshot or
1282
- enters Send; the exact outbox row is its terminal output. A scoped
1283
- repository observation retains each unaffected row once and rebuilds the
1284
- named path plus its ancestor spine once, so one UUID appears exactly once
1285
- in the assembled graph.
1286
-
1287
- 46. **The UUID is the Send/Receive channel.** Live's portable Record rail
1288
- preserves pending order for one entity UUID and may send distinct UUIDs
1289
- concurrently. Shell only supplies persistent SQLite, immutable-cargo, and
1290
- authenticated-wire effects. Neither layer assigns an official number: the
1291
- authority returns the next dense sequence for that entity across every
1292
- machine.
1293
-
1294
- 47. **The two local queues have disjoint writers.** Only Record may insert the
1295
- outbox and every retained row originated on this computer. Only Receive
1296
- may insert the inbox and every row is an authority-accepted global record,
1297
- including records that originated here. Acknowledgement stamps an outbox
1298
- receipt; it does not move or copy that row into the inbox.
1299
-
1300
- 48. **Receive follows each entity without gaps.** SQLite keys inbox rows by
1301
- `(entityId, globalSequence)` and persists one received-through cursor per
1302
- entity. A separate authority delivery cursor only discovers
1303
- changed entity channels; it has no version meaning and never decides LWW.
1304
- Shell subscribes once before cursor catch-up; thereafter an accepted-row
1305
- event wakes Live to drain from that durable cursor. Idle hosts issue no
1306
- record queries. Reconnect subscribes first and catches up second, so a
1307
- missed event costs latency but never loses a record.
1308
-
1309
- 49. **Graph publication has no queue of its own.** First login's graph is
1310
- one idempotent `ensure` of the authority's first graph; every later
1311
- change, a new workspace's package included, is an ordinary Outbox record
1312
- with its own mutation identity and retry. There is no second publication
1313
- journal, and one an older Shell left on disk is dropped at open.
1314
-
1315
- 50. **The record queues have one prepared SQLite owner.** Shell opens and
1316
- prepares the queue connection once for the rail lifetime. Receive commits
1317
- one delivered batch, its entity cursors, and its authority delivery cursor
1318
- in one transaction. No record opens the database, re-runs schema DDL, or
1319
- forces its own commit. Persistent Detect and Record owners share WAL and a
1320
- bounded busy wait rather than turning ordinary concurrent writes into
1321
- immediate failures.
1322
-
1323
- 51. **Receive wakes one Live-owned Apply rail.** An Inbox commit is the
1324
- event-driven doorbell; startup and restart also drain unresolved Inbox
1325
- work. Live selects the newest accepted result on each UUID and owns intent,
1326
- local-work protection, retry, and Verify decisions. Shell supplies one
1327
- persistent SQLite store plus type-specific filesystem, cache, and Git
1328
- effects. Apply never polls and never writes either Record queue. A failed
1329
- or conflicted lane parks: its durable intent stays, the failure is reported
1330
- with its attempt and backoff, and the lane re-runs only when that backoff
1331
- elapses, its entity's input changes, or, for a conflict, another lane's
1332
- progress may have moved the occupant. The Detect pass behind the lane's
1333
- own capture is a wake like any other and can never re-run it, so a parked
1334
- lane costs one bounded attempt at a time, never a Detect storm. An
1335
- accepted destination already held by a different recorded active entity is
1336
- a conflict named in evidence, never a local save to capture. The park timer
1337
- and attempt count are process-local: after restart, the durable intent is
1338
- re-proved once and, if still blocked, parks again from attempt one.
1339
-
1340
- 52. **Visible Apply follows durable identity.** Before any filesystem effect,
1341
- Shell persists one intent. Its first read-only preflight is optimistic and
1342
- never waits for exclusive ground. Immutable cargo is then prepared
1343
- privately beneath the materialized root's reserved `.amalgm/` control tree,
1344
- which Detect structurally excludes. A final guard, recoverable reveal,
1345
- exact reread, and one SQLite transaction then update entity rows, the
1346
- detection notebook, resolved Inbox proof, and the intent. Lock waits and
1347
- content requests are finite attempts with transient stage evidence; failure
1348
- retains the same responsibility for retry. A crash resumes the same intent;
1349
- it never invents another entity or treats private preparation as user
1350
- ground. Completed or abandoned work removes its private preparation using
1351
- the accepted plan's materialized root, including when the target entity row
1352
- is created by that same completion transaction. When an accepted result
1353
- changes an entity's address and payload together, Apply moves the verified
1354
- current entity to its accepted address before replacing its payload. The
1355
- prior address cannot survive as unmanaged ground that Detect could remint
1356
- and publish as an echo.
1357
- If an active accepted target below a still-present materialized root
1358
- disappears before Verify, raw absence is not a local lifecycle edit. The
1359
- adapter reports missing official ground, Apply reacquires the final address
1360
- cone, and the same intent reveals and verifies the accepted result again.
1361
- A missing or physically replaced root waits for the root-recovery law;
1362
- entity Apply never rebuilds a workspace piecemeal.
1363
-
1364
- 53. **Visible ground coordinates by address cone.** Detect, Register, Add, Add
1365
- recovery, and Apply each name the directory cones their filesystem plus
1366
- SQLite projection effects touch, and two effects wait for each other only
1367
- when one cone contains the other. A Detect pass leases exactly the ground
1368
- it reads, and only ground no effect holds: a name under a held cone stays
1369
- owed while its root's other names proceed, and a release rings Detect as
1370
- a write rings Watch, so that name looks again once its ground is free.
1371
- Every lane, the complete lane included, gates on the ground its cut reads
1372
- by one law: each name's subtree from its top (the first address the
1373
- index does not hold as a folder), or the repository that owns it, with
1374
- the root's policy file. Ground a proof finds it reads beyond that (Git
1375
- storage a checkout keeps elsewhere, a frame's folders, a root's whole
1376
- namespace) it takes only while no effect holds it; held, a named proof
1377
- waits for that ground and a complete-lane cut waits as its complete root.
1378
- Register holds its coverage family and core reference ground;
1379
- Add holds its destination, staging, and core ground; Apply's final guard
1380
- holds its target address, the entity's current address, and any addresses
1381
- a repository identity map relocates. Conflicting effects are served in
1382
- request order, so a stream of small effects can never starve an earlier
1383
- large one, and a timed-out waiter leaves the queue instead of poisoning
1384
- it. Unrelated cones never wait: a save applied in one workspace does not
1385
- queue behind a reconciliation of another. Apply preflights and prepares
1386
- immutable cargo without holding any cone, but its final guard, reveal,
1387
- Verify, and SQLite completion exclude Detect on the same addresses. Add
1388
- establishes singular Watch coverage before releasing its cones. A watcher
1389
- may ring throughout, but Detect observes only the complete state before or
1390
- after a transaction, never its half-written middle. When Apply's guard
1391
- finds ground Detect has not recorded, it lets its cones go first, then
1392
- rings exactly the addresses it compared, so that proof costs one named
1393
- Detect lane rather than a walk of every root. A local save observed before
1394
- or during reveal is restored and passed through ordinary Detect + Record
1395
- before accepted ground may replace it. Equal accepted truth at the same
1396
- UUID and address advances proof without a redundant write. If Detect runs
1397
- before Apply advances its notebook, an exact unresolved Inbox result may
1398
- advance local evidence but never create a second Outbox record; different
1399
- result, replay, or immutable cargo remains a real local change. Watch stays
1400
- active throughout, and its Apply-created ring settles to notebook equality
1401
- without an outgoing echo. The Inbox may know cloud-only entities that this
1402
- machine has not selected to materialize. Materialization selection is
1403
- distinct from `.amalgmignore`: that policy selects what this machine
1404
- shares, from every declaration on, and never filters cold download or
1405
- incoming Apply. Detect observes ignored ground like any other; sharing
1406
- holds an ignored identity at its last shared result. Incoming eligibility
1407
- follows materialization selection alone.
1408
-
1409
- 54. **Repository Apply is Card + Checkpoint + identity as one result.** Shell
1410
- imports the immutable Git transport chain, materializes Card and
1411
- Checkpoint, verifies the resulting repository state, and projects the exact
1412
- transported child UUID map transactionally. The accepted target type,
1413
- never the replay's cargo shape, selects that adapter: a repository rename
1414
- or move with an unchanged parcel is structural on the wire but still
1415
- prepares, reveals, repairs, and verifies through Git. Moving its checkout
1416
- carries the current repository subtree as one unit; only transported UUIDs
1417
- outside that subtree are independent relocations. Sender capture rechecks Git
1418
- identity after Card + Checkpoint capture and retries if Git crossed that
1419
- boundary, so one parcel cannot mix pre-operation worktree hashes with a
1420
- post-operation Card. A `.git` ring may arrive before its related worktree
1421
- ring, so Git's dirty tracked paths and current untracked inventory join
1422
- the same observation; those exact worktree bytes enter both Checkpoint and
1423
- identity before Record.
1424
- A delayed ring for that already-captured path is equality; transport
1425
- packaging alone can never mint another logical record. A Checkpoint path
1426
- with no UUID widens to full Detect before publication. If repository
1427
- capture must retry after local type and UUID projection, the next pass
1428
- reuses that materialized identity while still treating the absent notebook
1429
- row as unverified. Every incremental
1430
- identity delta is derived from the exact immutable parent transport, never
1431
- from the mutable SQLite projection that may already contain an
1432
- independently recorded child move. The host seals the complete identity
1433
- frontier against the transport header's identity hash and retains that
1434
- compact evidence with the current transport head, so older pack artifacts
1435
- may be pruned without replacing immutable proof with current rows. Apply
1436
- proves physical repository ground from Card + Checkpoint and that sealed
1437
- transport frontier, never from child rows whose independent entity
1438
- channels may have advanced before or after it. Missing or invalid compact
1439
- evidence falls back only to a complete immutable transport chain; if that
1440
- chain is unavailable, the next capture emits one self-contained transport
1441
- rather than guessing a delta. Cold materialization requires cloud rows and the parcel's
1442
- identity map to describe the same addresses. Hot Apply instead treats its
1443
- rows as the prior materialization: an accepted identity map may relocate
1444
- the same UUID into repository territory, keeps the prior source privately
1445
- recoverable through Verify, then projects the new address transactionally.
1446
- Apply observes Card + Checkpoint for each guard moment and never builds
1447
- a Git pack merely to prove equality. A new observation returns with its
1448
- complete source proof closed; reuse revalidates it at the later boundary.
1449
- The native inventory scan owns its before/after source checks, without an
1450
- immediate duplicate composite check. Address ownership excludes competing
1451
- Amalgm effects, not outside editors: Verify reads fresh physical evidence
1452
- after reveal. The host yields before guards and fresh Verify so completed
1453
- phases service Watch and transport; it inserts no scheduling gap between
1454
- a final guard and reveal. This does not bound a single synchronous effect.
1455
- A visible repository rewrite carries
1456
- `.git/amalgm-reveal`, naming its attempt, from its first Git mutation until
1457
- its readback proves the result, and restart resumes the same durable intent
1458
- before the marker is removed. Only that attempt's recovery reads the marker:
1459
- Detect leaves the repository unread because the attempt's receipt owns the
1460
- ground, and a marker no receipt owns holds nothing. Incremental materialization
1461
- imports only transport ranges whose declared Git tips are absent locally.
1462
- Gaining or losing `.git` keeps the containing UUID and changes only its
1463
- type rail.
1464
-
1465
- 55. **A request timeout invalidates the request wire.** Request/reply framing
1466
- cannot prove that only one response was lost. When an authenticated wire
1467
- fails to answer before its deadline, Shell rejects every request in flight,
1468
- discards that exact socket, and lets the owning portable rail retry through
1469
- a newly authenticated connection. A late frame or close from the discarded
1470
- socket can never acknowledge work or tear down its replacement. A timeout
1471
- is therefore visible continuity evidence, not permission to reuse a
1472
- possibly wedged transport.
1473
- The reply deadline begins only after the WebSocket reports that the request
1474
- left this process; a bounded queued-byte turn prevents bulk cargo from
1475
- growing memory without limit or starving gateway heartbeats. Separately,
1476
- an authenticated socket that remains open without any inbound gateway
1477
- frame across the heartbeat allowance is discarded and rejoined from the
1478
- durable cursor.
1479
-
1480
- 56. **Files timing observes boundaries; it never becomes a boundary.** An
1481
- opt-in observer may report Register, Upload, Download, Watch, Detect,
1482
- Record, Send, Receive, and Apply milestones with stable entity or workspace
1483
- identity. The evidence is transient and cannot schedule work, enter entity
1484
- SQLite, or change a protocol decision. Same-process durations use a
1485
- monotonic clock. Wall time exists only to correlate processes and machines,
1486
- so a cross-machine duration must state its clock-skew bound rather than
1487
- pretending to be more exact than its clocks.
1488
-
1489
- 57. **Directory posture is local; the ordinary-file executable bit travels.** The shell's
1490
- own private and control directories — machine SQLite, caches, staging,
1491
- every `.amalgm/` control tree — are created `0700` and re-asserted `0700`
1492
- on every touch. A fresh user-visible directory that materialization or
1493
- Apply creates gets the standard `0755` a fresh `mkdir` would give the
1494
- user, and an existing user directory keeps whatever mode the user chose;
1495
- no file effect inside a directory rewrites its parent's mode. Text and
1496
- binary files are different: capture reduces their mode to `0644` or `0755`,
1497
- the cloud record carries it, and Add, Apply, and Verify reproduce it.
1498
- Ownership, ACLs, read-only bits, and every other mode remain local.
1499
-
1500
- 58. **A materialization graph and its delivery watermark are one fact.**
1501
- Every entity-registry snapshot names the complete authority delivery
1502
- prefix already represented by its graph. Before workspace selection, Add
1503
- folds any complete later committed tail onto that verified base, producing
1504
- one current graph and watermark `N`. It installs that graph and advances
1505
- Receive and Apply through `N` in the same local adoption boundary; records
1506
- at or below `N` are retained history, never filesystem work, and only
1507
- later records may Apply. When publication folds that tail, final ancestry
1508
- in the complete prefix places every result: a container created after the
1509
- snapshot can own later children, and a result whose final ancestry lies in
1510
- another root leaves its old root's pages, so no UUID is filed in two roots;
1511
- old snapshot membership alone never chooses the result's root. That
1512
- placement serves an enclosing Register's re-rooting; it is not identity
1513
- continuity. Identity is root-local, no producer emits a same-UUID record
1514
- across independently materialized roots, and such a record is unsupported:
1515
- the fold does not carry its subtree into the other root. The settled
1516
- fold passes through the repository parcel projection exactly as publication
1517
- does: a tail that turns a container into a repository retires that
1518
- container's snapshot children into its parcel, and a tail that turns a
1519
- repository back into a folder carries the boundary retype first and each
1520
- newly independent descendant after it, whose retained latest statement
1521
- supplies its contents until its own record arrives, and a repository that
1522
- stays a repository follows every record that crosses its boundary, so
1523
- every committed delivery prefix is reconstructible and Add never selects
1524
- a graph the parcel law would not publish. Replay closure also owes a
1525
- deletion nothing else states, because the repository whose package held
1526
- it stopped being a live one. Whatever it owes carries each enclosing
1527
- ancestor up to the first that travels after the batch or is already owed:
1528
- an ancestor's own head is no proof, since a later package may have
1529
- superseded it. The first
1530
- later record on an entity UUID establishes its immediate entity predecessor
1531
- from the complete snapshot prefix, after which ordinary dense per-entity gap
1532
- checking resumes. A publisher may name only the exact locally received
1533
- and applied prefix, and authority accepts that graph only while `N` is
1534
- still the committed delivery tail under the entity-record ordering gate.
1535
-
1536
- 59. **Shell keeps the graph head without duplicating the graph.** Live
1537
- decides the immutable pages and head. Shell keeps only the head it last
1538
- read; pages are read as immutable content, never written as a second
1539
- whole-registry snapshot or rebuilt for roots no operation selected.
1540
-
1541
- 60. **Runtime binding is proved, never inferred.** A platform adapter adopts
1542
- an existing runtime only when Shell's published loopback address answers
1543
- its authenticated identity probe for the selected user, device, environment,
1544
- exact branch, local session, and process generation. A
1545
- durable ready registration with no answering runtime may be resumed; an
1546
- absent or incomplete registration requires login. A UI marker, PID, open
1547
- port, or installed executable alone is never service readiness. A stored
1548
- registration whose Files cloud rail differs from the composed one, or
1549
- whose declared Wire changed, is incomplete: fresh approved setup may
1550
- replace it, but it is never adopted or resumed.
1551
-
1552
- 61. **Browser is composed once, as the runtime's amalgm account.** Shell
1553
- owns the one `BrowserService` composition for a machine runtime, made on
1554
- first use and browsing as the signed-in amalgm account alone. A chat's
1555
- agent browses in its chat's own session, taken from the chat relay's
1556
- session stamp; viewers reach the brick's REST API and each session's
1557
- live view under `/browser`, handed over in-process once the gateway has
1558
- admitted them. Shell never implements a second browser action, registry,
1559
- profile, cookie, or authentication authority. A signed machine release
1560
- that does not declare Browser must not instantiate Browser state merely
1561
- because the SDK is installed. Native cookie adapters use Browser's separate
1562
- private credential on `/browser-adapter`, including the desktop's native
1563
- presentation link at `/browser-adapter/host`. The runtime owns website
1564
- pages; desktop viewers never acquire them. Ordinary runtime access cannot
1565
- read cookie values or join that link. Runtime publication names Browser's
1566
- computer-only `.amalgm/browser/` folder, and shutdown drains live viewers
1567
- before waiting for the gateway to close.
1568
-
1569
- 62. **PTY is one authenticated Shell host capability.** The running machine
1570
- runtime mounts the Core-owned PTY contract through Shell's native process
1571
- adapter and retains every spawned terminal until native exit, including
1572
- sessions already removed from the public catalog. Runtime close seals new
1573
- terminal admission and drains all terminals concurrently: one second permits
1574
- hangup, then forced termination must prove exit within five seconds before
1575
- close succeeds. A UI targeting
1576
- this computer connects through the published authenticated loopback
1577
- binding; only a different computer uses the remote relay. Electron never
1578
- creates a second PTY implementation. A session with no explicit working
1579
- directory starts in that signed-in user's `workspaces/` folder.
1580
-
1581
- 63. **Chat has one execution path.** Agents resolves an installed identity and
1582
- exact immutable revision; Tools resolves the selected catalog revision;
1583
- Chat owns the conversation, provider pump, journal, reconnect, usage, and
1584
- interrupt. Shell mounts Chat's public HTTP adapter in the signed
1585
- `MachineHost`; it owns no session store, event translation, or callback
1586
- driver.
1587
-
1588
- 64. **One installation device key and broker serve every local product.**
1589
- Before registration, Shell creates one P-256 private key for the physical
1590
- installation, binds its public thumbprint into the approved setup intent,
1591
- and proves possession before pinning that thumbprint across the computer's
1592
- runtime labels. The key stays in macOS Keychain or a Windows DPAPI envelope
1593
- where available (or one mode-0600 fallback file). A registered runtime
1594
- treats missing or corrupt key material as a visible failure; it never
1595
- generates a replacement during startup. Replacement is an explicit,
1596
- browser-approved recovery: Shell stages one candidate, proves its private
1597
- key, reuses it across uncertain retries, and promotes it only after the
1598
- control plane conditionally accepts the server-derived prior thumbprint.
1599
- Shell mints short-lived grants through Core's broker and creates a fresh
1600
- DPoP proof for each request. Chat, Apps, and future products never receive
1601
- the key or durable machine credential.
1602
-
1603
- 65. **A Shell release is tested as the artifact users install.** The release
1604
- gate packs Shell, installs that tarball with the exact public Amalgm
1605
- artifacts selected by the installation recipe, and exercises authorization
1606
- through Chat using package exports only. Sibling repositories and source
1607
- paths are never an integration-test dependency.
1608
-
1609
- 66. **Provider credentials never become process configuration.** Shell does
1610
- not accept a proxy token from UI, an environment variable, or a local
1611
- credential-resolution route. A product request uses an injected broker
1612
- adapter that obtains an exact short-lived grant and signs fresh DPoP while
1613
- the durable credential and device key stay inside Shell.
1614
-
1615
- 67. **Portable product deployments and machine coordination are physically
1616
- separate.** Shell gives Tools the user's `toolbox/` folder, one folder
1617
- per tool, and its computer-only `.amalgm/tools/` folder for the catalog. It
1618
- observes each `deployment.activate` operation through Tools' Live surface;
1619
- a cloud-capable composition must bind that surface, while local StateRail
1620
- events remain presentation evidence rather than cloud authority. Shell
1621
- never syncs a database, WAL, lock, or whole-catalog replacement as product
1622
- authority.
1623
-
1624
- 68. **First-party products enter agent sessions through Toolbox selection.**
1625
- Shell projects each owning SDK's MCP descriptors as an immutable system
1626
- tool, and a host source names a distinct server plus loopback route. Agent
1627
- preparation resolves only the selected exact Toolbox revision to official
1628
- ACP `McpServer[]`; no product receives ambient injection. An undeclared
1629
- product adapter may initialize only after explicit tool selection, never as
1630
- a login side effect.
1631
- Every tool type enters through one Tools-owned scoped MCP mount; Shell
1632
- owns upstream processes, sockets, and the encrypted credential vault.
1633
- The prepared selection can narrow an exact agent revision's grant but
1634
- cannot widen it or change hidden/searchable actions into direct actions.
1635
- Disconnect revokes the parent tool even in a prepared execution; saved
1636
- schemas and immutable deployments remain available for reconnection.
1637
- All selected CLI/API/GraphQL/MCP actions execute through Tools' captured
1638
- read-only view on one runtime-admitted Chat auxiliary MCP route. Only direct
1639
- descriptors and scoped search/call entry points enter the prepared bundle.
1640
- Tools owns connection admission and exposure; Shell supplies one official
1641
- MCP client effect and Core's encrypted credential vault. Upstream endpoints
1642
- and credentials never bypass that scoped action boundary.
1643
-
1644
- 69. **The MCP relay authenticates as the composed runtime.** Shell supplies
1645
- its runtime-admission token explicitly to Chat's native host. Chat gives it
1646
- only to the selected provider child for calls back through the
1647
- session-local relay. When a selected source is a guarded Shell host route,
1648
- Shell separately binds the same credential to that prepared upstream
1649
- server, and Chat applies it only on relay forwarding. Neither product tool
1650
- definitions nor process-global environment discovery own that credential.
1651
-
1652
- 70. **Every Shell MCP route speaks official JSON-RPC over HTTP.** A mounted
1653
- product SDK still owns method behavior, while the one Shell gateway owns
1654
- the transport envelope: requests require JSON-RPC 2.0, responses preserve
1655
- the exact request id, notifications return without a response message, and
1656
- failures use JSON-RPC error objects. No product route exposes its inner
1657
- result object as a private HTTP dialect.
1658
-
1659
- 71. **Hosted products remain direct and independently owned.** Automations and
1660
- Channels each run on their own service deployment. Shell uses the one Core
1661
- credential broker to mint audience-specific DPoP requests directly to
1662
- those services, exposes each owning SDK's official MCP adapter, and claims
1663
- only runs and channel messages targeted to this computer. External events
1664
- enter Automations at its hosted opaque capability URL and become durable
1665
- work before a machine is involved; Shell never exposes a webhook ingress
1666
- route. The generic
1667
- Automations executor calls qualified injected actions and its typed process
1668
- capability; Shell injects the selected machine's process host with the
1669
- user's OS home as the stable default directory. Direct command steps spawn
1670
- argv without a shell, explicit script steps own shell or language
1671
- evaluation, and neither inherits the creator CLI's directory.
1672
- `channels.notify_user` is one registered automation action, never a special
1673
- scheduling path. Gateway is not a product relay, and Shell stores no
1674
- portable Automations or Channels database.
1675
- Chat and Automations share one Toolbox whose host composition always supplies
1676
- the authenticated MCP driver for installed product routes. An automation's
1677
- run-step idempotency key crosses that loopback route as trusted execution
1678
- metadata; the owning product applies it without changing the workflow input.
1679
- Runtime credentials and trusted host headers never accompany external MCP
1680
- connections.
1681
- Channels inbound work stays hosted only until Chat durably admits its turn.
1682
- A new email conversation resolves the thread's explicit saved defaults --
1683
- agent, model settings, computer, working directory and instructions --
1684
- through Agents; an agent id alone is not an executable selection, and Shell
1685
- never guesses from recent activity. Missing defaults hold the work for
1686
- configuration, the defaults must name this computer, and the selected agent
1687
- must already carry Channels send access. Replies resume the session's latest
1688
- admitted execution, which stays Chat's authority.
1689
- The machine reconciles on every event-stream connection, so a wakeup is
1690
- never the authority. Shell preserves Chat's session id as hidden MCP
1691
- metadata and never exposes it as a model-chosen Channels argument. The
1692
- global product CLI discovers the already-running Shell and enters through
1693
- that same private loopback MCP route; it never receives a hosted access
1694
- token or the machine's DPoP key.
1695
-
1696
- 72. **Built-in agents are versioned platform installations.** Shell owns one
1697
- declared stock definition of each native built-in agent and installs it
1698
- pinned. It advances a built-in when that definition or its installed
1699
- platform capabilities change, but only while the user has not edited it;
1700
- a user's edits and pin survive every start, and built-ins are never
1701
- deleted. Every stock built-in selects the complete available first-party
1702
- Toolbox loadout, and Chat prepares that exact immutable agent revision
1703
- and tool deployment.
1704
-
1705
- 73. **Git host capture distinguishes moving state from durable conflicts.**
1706
- Git administrative storage does not identify its checkout owner. Detect
1707
- may settle a storage notice only after every affected enrolled checkout
1708
- is examined or remains explicitly pending. A named single-consumer result
1709
- closes the complete original binding and exclusion proof at Record.
1710
-
1711
- Changed native source evidence refuses capture; the mere existence of a
1712
- Git lock or a reveal marker does not (a young lock only times the read,
1713
- law 45). Amalgm's own incomplete reveal is
1714
- ground its receipt owns, which Detect leaves unread (law 54). A stable
1715
- unfinished merge is portable Checkpoint truth: Shell captures its
1716
- unmerged stages, worktree conflict bytes, and merge continuation through
1717
- Live's one repository contract, and restores ordinary stages only after
1718
- their Git objects are present. Gitlink stages are opaque commit identities
1719
- owned by the nested repository, so the parent preserves but never packs
1720
- them and never creates, replaces, or removes that nested worktree. Paused
1721
- rebase, cherry-pick, and revert state is not yet represented
1722
- by the current contract and refuses explicitly rather than being mistaken
1723
- for transient work or flattened into a clean stage-zero entry. Unchanged
1724
- ground answers that refusal every time, so Detect withholds only that
1725
- repository's unit and asks again only when its ground, Git storage
1726
- included, rings; no timer repeats the read. A fault likewise withholds
1727
- only its own repository's unit, and the pass retries it on its timer.
1728
-
1729
- Scheduling never extends source evidence. A suspended walk retains its
1730
- physical identity basis, rechecks it before repository reuse or capture,
1731
- and closes all participating source proofs at Record admission. Every
1732
- examined result carries that proof; an unexamined result authorizes no
1733
- writes. All Git dependencies precede the final physical sweep, and parent
1734
- witnesses close after their descendants. This is a bounded source check,
1735
- not an atomic filesystem snapshot or a no-traversal guarantee. Retained
1736
- validators own witnesses rather than captured content buffers. Inspection
1737
- fingerprints working files through the shared bounded reader; it never
1738
- allocates file-sized content that it does not consume. A changed
1739
- basis retries the observation without persisting its stale associations.
1740
- A native-index collection is unclosed until its owning observation checks
1741
- the original semantic binding, index meaning and fresh untracked namespace
1742
- together. Internal inventory reads keep local invocation/path and file
1743
- checks; one semantic bracket closes each public result and each later reuse.
1744
- Physical and ownership witnesses close after the last Git subprocess.
1745
- Neither returned buffers nor a caller's mutable scope may alter retained
1746
- evidence. No successful close is cached across an admission boundary.
1747
- A captured binding path disappearing or becoming obstructed is source
1748
- change and retains its original cause; access and I/O failures stay faults.
1749
- Private Checkpoint preparation proves package contents; the installer still
1750
- checks current independent repository boundaries after preparation and before
1751
- changing receiver objects, metadata or files.
1752
-
1753
- 74. **Same-slot records keep identity and derive distinct disk addresses.**
1754
- Shell never rewrites a portable name to settle concurrent identities.
1755
- Cold materialization, Apply and the placement tidy derive the same
1756
- UUID-ordered suffixes from the complete active sibling set; Detect
1757
- recognizes both the portable name and that exact derived name as the same
1758
- record. A reveal moves only the siblings standing in its target's derived
1759
- address. Every other sibling-set consequence is a placement note, written
1760
- in the transaction that changed the slot, which the placement tidy pays
1761
- off the Apply line. Each such move is one no-replace move, ground first
1762
- and rows after, never onto an address the observation inventory records
1763
- for another, so a crash leaves at most one move whose destination was
1764
- free and Detect re-proves the same portable identities.
1765
-
1766
- 75. **Ground storage has one initializer and one visible generation per root.**
1767
- A ground file's migration and its process epoch run once per file per
1768
- process, on a bootstrap thread under one owner, never on the main thread.
1769
- The outcome is known only after that thread exits and its committed result
1770
- is confirmed. Every opener requires that confirmation, and a failed start
1771
- records nothing. Both inventories are read through read-only views over
1772
- `(uuid, generation)` storage; `ground_roots` names each root's one visible
1773
- generation, and writes touch only that generation. A flat file converts in
1774
- one transaction that proves the views reproduce it exactly, or it stays as
1775
- it was. The released flat form stated each object as stat numbers: its
1776
- device and inode are the physical key exactly as stored, and its
1777
- millisecond times state neither a source signature nor a content
1778
- boundary, so a converted row holds neither and its first examination
1779
- reads every leaf again. It also stored the user's root at the route it
1780
- was given, while every root is found by its physical route (its
1781
- synchronization address, `src/sync-address.ts`), so conversion moves each
1782
- root's rows onto that route: a root left at another spelling of it
1783
- (`/var` for `/private/var`, an 8.3 short name for a long one) would never
1784
- be found again, and its ground would be declared a second time under a
1785
- new identity. A root on a volume that is not mounted keeps its route; it
1786
- has nothing to resolve now, and only the user's own root was stored
1787
- unresolved. The
1788
- qualified profile gathers no planner statistics, but statistics already
1789
- present are kept, never treated as corruption.
1790
-
1791
- 76. **Replication state belongs to the authority that ordered it.** This
1792
- machine's entity authority is named by a contract-scoped id, so a registry
1793
- contract change derives a new one and the superseded authority never again
1794
- orders anything this machine sends or receives. Before convergence reads
1795
- any of it, binding the ground to its current authority retires every
1796
- record, cursor, baseline, Apply fact and intent
1797
- of any other authority in one transaction. None of them can mean anything
1798
- to the current authority: a pending row would stall Send behind a contract
1799
- that no longer decodes, a cursor or resolution would skip the current
1800
- authority's first sequences, and an accepted result would settle a new
1801
- observation as if the current authority already held it. Files ground is
1802
- untouched; convergence settles it with the current authority exactly as it
1803
- settles ground that holds no replication state.
1804
-
1805
- ## Relationship to amalgm-engine
1806
-
1807
- Stage 1 cut the bricks out of the engine. Stage 2 proves them here, composed.
1808
- Stage 3 ships each signed service from this shell and retires its Engine copy.
1809
- The current signed release is Core + Files + Agents + Tools + Chat, with
1810
- Automations hosted independently and claimed by its target Shell. The Engine
1811
- `/events` compatibility route is retired: webhook senders use
1812
- `https://automations.amalgm.ai/e/<capability>` and never depend on the target
1813
- machine being online. Later services cross the same parity gate without
1814
- creating a second runtime for anything already released.
1815
-
1816
- ## Ongoing Files reconciliation boundaries
1817
-
1818
- The complete repository payload combines Git state and the member UUID map;
1819
- its hash is separate from the incremental package hash. Register, cold transfer,
1820
- Add and Watch setup retain their existing journeys. Their shared entity rows
1821
- use that complete payload hash. Construct product adapters and the installed
1822
- pause/resume switch keep their existing responsibilities.
1823
-
1824
- The Git effect adapter observes private versus common Git storage. Ongoing
1825
- Apply requires independent checkout storage; shared worktrees and unsupported
1826
- unfinished Git continuations are named capability waits. The enclosing
1827
- repository cannot remove an independently materialized nested repository's
1828
- identity. Its own accepted move or type change must satisfy that prerequisite.
1829
- Live's existing Apply coordinator owns the wait and wake-up; Shell supplies
1830
- physical evidence and reports the prerequisite through Files stage diagnostics.
1831
-
1832
- Git history export uses the captured object format and shallow boundary, and
1833
- packs exactly what the receiver lacks, as upload-pack does. The receiver holds
1834
- each previous tip's closure under the horizon it received, so those tips
1835
- exclude history even when the boundary changed. A boundary the new horizon
1836
- moved past (Git's unshallow) is a commit the receiver holds, if at all,
1837
- without its parents: each one this state reaches wants its parents, so the
1838
- history newly exposed beneath it travels, and each one the receiver holds is
1839
- an edge, so its tree never travels again. Patch operations are read from machine patch headers, never from a
1840
- human summary where filename bytes can resemble instructions.
1841
-
1842
- ### Notification-independent observation
1843
-
1844
- Active Files must eventually notice persistent local changes even when native
1845
- Watch is silent. Native36 and its independent raw-native complete-ground control
1846
- show missed equal-length writes through a held descriptor. Healthy handles and
1847
- an empty notification backlog are not physical freshness. The Files host
1848
- therefore runs a metadata maintenance sweep (`detection/maintenance-sweep.ts`),
1849
- paused with the Files host. One visit at a time compares a Watch root's
1850
- metadata with O and reads no bytes; each difference becomes a request in
1851
- Live's maintenance ledger that the ordinary scoped lanes serve, and the sweep
1852
- writes no row or Record. A receipt proves the comparison completed and its
1853
- work was handled, never a byte reread. Visits follow cadence C: an owner's
1854
- next visit is due one freshly drawn interval, one hour times uniform
1855
- [0.75, 1.25), after its last. That is a configured inter-visit interval, not a
1856
- mutation→Record bound; Watch's loss evidence still suspects its root
1857
- immediately, meaning immediate responsibility and scheduling, not single-pass
1858
- completion. Foreground work comes first, never forever: the longest-waiting
1859
- due owner goes first, and a root already owed a complete proof defers its
1860
- visit by at most 10 s. `UserGroundHost.requestVisit` asks for one visit that
1861
- begins after the request and settles once the lanes discharged what it found
1862
- through Detect → Record, or with a typed reason it cannot (`not-ready`,
1863
- `removed`, `stopped`, `unreadable`); it jumps the schedule within the one
1864
- slot and is never a content reread. Apply-owned ground is a gap. An empty
1865
- binding set has no owner. Native notices
1866
- keep their narrow fast path, and a later visit cannot revoke a completed
1867
- finite boundary. One frozen native batch receives service, including one
1868
- necessary widening to the complete domain. That widening is the
1869
- invocation's only immediate retry. It freezes the wider cutoff before
1870
- releasing narrow leases, then yields: the complete examination starts in its
1871
- own dispatcher activation and reads a new basis over the wider scope. Later
1872
- notices retain their own cutoffs. Failure, deferral and repeated widening
1873
- cannot replenish foreground priority. Every examination may reuse proven
1874
- content: a leaf is reused only while its signature is unchanged and its
1875
- change time precedes the boundary of a content clock stamped on the root's own
1876
- filesystem in `.amalgm/content-clock` before the reads (`content-clock.ts`).
1877
- The boundary is the stamp's change time less its profile's margin; a time
1878
- with no subsecond part stands for its whole second. A racy leaf is reread;
1879
- only that reread clears it. Every proof names the root's qualification it was
1880
- stamped under, and a root shows only proofs under its own. A stamp under another
1881
- profile, or behind the latest boundary a kept proof stands on, requalifies the
1882
- root in one write of the root, never of its rows, so no stamp file restored
1883
- from an old copy can revive a proof; a conclusion drawn before that at, above
1884
- or beneath the root fails its admission and is read again, and a unit that
1885
- consumed an identity
1886
- discovery reads and stands on that discovery's whole scope.
1887
- Directory listings close on the same rule: a racy listing names no complete
1888
- membership until a fresh listing under a later stamp, and only filesystems
1889
- `ground-profile.ts` names qualify at all. A listing is racy only while its
1890
- directory stands as walked: one changed since, by Apply's reveal or a
1891
- person's write, has moved, a cause to wait on and never a fault, and no
1892
- count of readings fails a ticket. A listing no stamp can qualify
1893
- closes only when a fresh listing taken after the whole walk names exactly
1894
- what the walk listed while the directory held still on both sides; only an
1895
- entry moved and moved back across both listings inside its directories'
1896
- clock ticks escapes that, and each such move is a later Watch generation.
1897
- The control tree carries a `.gitignore` of `*`, written once per root per
1898
- process when absent or different, so a registered repository's Git status
1899
- never shows it. Ground without a qualified clock (another device, a root that
1900
- cannot hold a stamp) is read by every
1901
- examination and closes each listing by reading it again: it loses shortcuts,
1902
- never conclusions. NTFS qualifies presence and keys, never content: a writer
1903
- sets its change time (CopyFile copies the source's), so no NTFS time proves
1904
- content or closes a listing (`timesProve`), and NTFS ground is read as ground
1905
- without a clock. Every examination therefore reads each NTFS leaf, so the
1906
- Windows performance gate is missed; no OS-specific mechanism wins that speed
1907
- back. Qualifying ReFS is unfinished.
1908
- A write through a writable `MAP_SHARED` mapping can change bytes while the
1909
- signature stays equal, through flush, unmap and fsync: that mapped-write
1910
- limitation is outside the metadata-only guarantee, and a faster stat tier
1911
- would not reveal it.
1912
- No lane preempts a complete
1913
- examination; only shutdown stops it. Detect leases hold no ground, so Apply
1914
- may reveal while collection reads. Admission runs per unit in bounded batches
1915
- and yields between them. Participating rails dispatch at most one ready work
1916
- chunk per dispatcher activation and return to the event loop before
1917
- dispatching another. Asynchronous operations do not occupy the dispatcher
1918
- while waiting. The participating rails are Detect, Send, Receive, Apply and
1919
- cache maintenance (`turns.ts`): each Detect stage, network answer, download
1920
- and capture-thread reply resumes in its own activation. The dispatcher
1921
- controls participating application continuations. It does not control all
1922
- work in a Node iteration. A long named or routing preparation continues past
1923
- an already-valid boundary (between names, between collection and
1924
- preparation, after a retained snapshot) only within its activation's budget;
1925
- admission's basis check, writes and commit, and an assessment's install with
1926
- its cutoff bookkeeping, are never split. A committed Record is an immutable
1927
- fact: finalizing its assessment and draining the next rail start in later
1928
- activations, and recheck what they publish. Each unit's
1929
- physical closure, binding, SQL-revision and source proofs close together in
1930
- its own transaction. A unit that fails them is left out and retried by timer
1931
- while the others admit. Unreadable or
1932
- Apply-owned ground is a scoped gap, never absence: it defers only the units
1933
- that need its facts, withholds the complete receipt, and never voids the other
1934
- admissions of the same domain. A protected attempt remains subject to real
1935
- source/coverage failures. This scheduling bound does not claim
1936
- short tail latency: blocking Git calls and complete closing cost remain measured
1937
- limitations. Register, Add and watcher placement retain
1938
- their journeys. Integrated correctness and cadence/service-cost qualification
1939
- are pending; this setting grants no performance pass.
1940
-
1941
- Fresh observation reads mutable content without copying unchanged files into
1942
- the cache. Only selected new content is sealed before Record, against the same
1943
- original physical proof. A leaf that publishes on its own channel is selected
1944
- even when Git tracked it: the read that seals its observed bytes also names
1945
- their Git object, and its record states the exact SHA-256 value while its
1946
- repository's package keeps the Git object. A trashed leaf known only by its
1947
- Git object stays unsealed; Restore, which would need its bytes, is not built.
1948
- Cache existence or size alone is never content proof.
1949
- Source reads refuse special-file substitutions without waiting for another
1950
- process, and release every owned resource even when another cleanup fails.
1951
- Git parcel reuse requires equal fresh worktree and Card evidence. The Card's
1952
- own stash reader supplies stash evidence; conventional reflog filenames cannot
1953
- stand in for Git's semantic answer. Effective configuration and stash reads
1954
- close before their original physical prerequisites. Internal Git owns its
1955
- piped output settings, so an interactive display preference cannot alter its
1956
- storage eligibility; unrepresented Git inputs still require full capture.