From 32a506ee94284926a2c3970f8f8c98b68a2ab1e8 Mon Sep 17 00:00:00 2001
From: "animus-launchapp-gitprovider[bot]"
 <4147602+animus-launchapp-gitprovider[bot]@users.noreply.github.com>
Date: Tue, 14 Jul 2026 15:31:41 +0000
Subject: [PATCH] docs: remote-node execution proof (authored on an ephemeral
 Animus node)

---
 docs/REMOTE_NODE_PROOF.md | 5 +++++
 1 file changed, 5 insertions(+)
 create mode 100644 docs/REMOTE_NODE_PROOF.md

diff --git a/docs/REMOTE_NODE_PROOF.md b/docs/REMOTE_NODE_PROOF.md
new file mode 100644
index 00000000..59ebbb77
--- /dev/null
+++ b/docs/REMOTE_NODE_PROOF.md
@@ -0,0 +1,5 @@
+# Remote Node Proof
+
+This change was authored by an autonomous agent running the Claude Code harness inside an ephemeral Railway node provisioned by the Animus environment plugin.
+
+In practice, that means no human typed these edits at a local workstation. The Animus environment plugin spun up a fresh, disposable Railway compute node on demand, cloned the repository into it, and ran the Claude Code agent harness there. The agent then made this change end to end — reading the repo, editing files, and committing — inside that remote sandbox. Because the node is ephemeral, it exists only for the duration of the work and is torn down afterward, leaving behind just the committed result as evidence that the run happened.