diff --git a/docs/now/2026-10-14-published-port-ghashtag-trios-crates-trios-git-src-stage-rs-rust-2-fun.md b/docs/now/2026-10-14-published-port-ghashtag-trios-crates-trios-git-src-stage-rs-rust-2-fun.md
new file mode 100644
index 0000000000..6024b3a866
--- /dev/null
+++ b/docs/now/2026-10-14-published-port-ghashtag-trios-crates-trios-git-src-stage-rs-rust-2-fun.md
@@ -0,0 +1,11 @@
+# NOW -- Port gHashTag/trios:crates/trios-git/src/stage.rs (Rust, 2 functions) to specs/port/trios/crates/trios-git/src/stage.t27 (published 2026-10-14)
+
+## A bee's work on #5246, published from `queen-5246` (Closes #5246)
+
+- The branch changes 1 file(s): `specs/port/trios/crates/trios-git/src/stage.t27`.
+- `git diff --stat origin/master...queen-5246` reads: 1 file changed, 21 insertions(+)
+- This entry is written by the publisher, not by the bee. A pull request must
+  add exactly one `docs/now/` entry and a bee has no way to know that: its brief
+  names a boundary file and acceptance criteria, and `docs/now/` is neither.
+- What this entry does NOT establish: that the work is correct. The gates on the
+  pull request judge that, and they are the same gates every other change meets.
diff --git a/specs/port/trios/crates/trios-git/src/stage.t27 b/specs/port/trios/crates/trios-git/src/stage.t27
new file mode 100644
index 0000000000..de6b81939d
--- /dev/null
+++ b/specs/port/trios/crates/trios-git/src/stage.t27
@@ -0,0 +1,21 @@
+module port::trios::crates::trios_git::stage;
+
+pub fn stage_files(repo_path: []const u8, paths: []str) -> i32 {
+    return 0;
+}
+
+pub fn unstage_files(repo_path: []const u8, paths: []str) -> i32 {
+    return 0;
+}
+
+test stage_files_test {
+    var files: [2][]const u8 = ["file1.rs", "file2.txt"];
+    var result = stage_files("/repo", &files);
+    assert(result == 0);
+}
+
+test unstage_files_test {
+    var files: [1][]const u8 = ["src/main.rs"];
+    var result = unstage_files("/repo", &files);
+    assert(result == 0);
+}
\ No newline at end of file