From 1db8107ee19d1ba9b5de3f5ee32b7d9eceba5fc2 Mon Sep 17 00:00:00 2001
From: EngineerProjects
Date: Tue, 23 Jun 2026 12:11:56 +0200
Subject: [PATCH 1/3] docs: add seshat-ai.com website link in README + rename
logo image
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit
- Add ๐ Website link pointing to seshat-ai.com in header links
- Rename docs/images/nexus.png โ docs/images/seshat.png
---
README.md | 3 ++-
docs/images/{nexus.png => seshat.png} | Bin
2 files changed, 2 insertions(+), 1 deletion(-)
rename docs/images/{nexus.png => seshat.png} (100%)
diff --git a/README.md b/README.md
index 62ae886..2c53006 100644
--- a/README.md
+++ b/README.md
@@ -1,5 +1,5 @@
-
+
Seshat
@@ -10,6 +10,7 @@
+ ๐ Website ยท
๐ฌ Discussions ยท
๐ Issues ยท
๐ฅ๏ธ seshat-ai
diff --git a/docs/images/nexus.png b/docs/images/seshat.png
similarity index 100%
rename from docs/images/nexus.png
rename to docs/images/seshat.png
From 854ebb122f71993d9be27f2540c141cff6230552 Mon Sep 17 00:00:00 2001
From: EngineerProjects
Date: Tue, 23 Jun 2026 12:48:10 +0200
Subject: [PATCH 2/3] docs: add community-driven vision paragraph to roadmap
section
---
README.md | 2 ++
1 file changed, 2 insertions(+)
diff --git a/README.md b/README.md
index 2c53006..dc770ba 100644
--- a/README.md
+++ b/README.md
@@ -66,6 +66,8 @@ We are building the foundation. Seshat today is a solid, production-grade runtim
The team primitives (mailboxes, roles, missions, structured inter-agent communication) are the next major layer. We are designing them now, informed by how real organizations function.
+Beyond these layers, the shape of the platform will be defined as much by the community as by any central roadmap. Domain experts in healthcare, education, legal, finance, logistics, or any other professional field will propose and contribute specialized integrations tailored to the realities of their industry. Seshat is not a product with a fixed scope. It is an OS for agentic services: an open foundation on which any application can be built for any use case, by the people who understand that use case well enough to build it right.
+
---
### ๐ค An open project: all ideas welcome
From 585015ca3e95c8086a55a17fac14d3ed87173b80 Mon Sep 17 00:00:00 2001
From: EngineerProjects
Date: Tue, 23 Jun 2026 12:57:18 +0200
Subject: [PATCH 3/3] fix(install): download binary under asset name before
checksum check
sha256sum --check looks for the filename listed in SHA256SUMS.txt
(e.g. seshat-linux-amd64). The binary was being saved as 'seshat'
before verification, so sha256sum could not find the file and aborted.
Fix: download to $TMP_DIR/$BIN_ASSET, verify against SHA256SUMS.txt,
then rename to 'seshat' only after the check passes.
---
scripts/install.sh | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/scripts/install.sh b/scripts/install.sh
index 70e1ed7..d9619ec 100755
--- a/scripts/install.sh
+++ b/scripts/install.sh
@@ -109,7 +109,7 @@ trap 'rm -rf "$TMP_DIR"' EXIT
_dl() { command -v curl &>/dev/null && curl -fsSL "$1" -o "$2" || wget -qO "$2" "$1"; }
info "Binary: $BIN_ASSET"
-_dl "$BASE_URL/$BIN_ASSET" "$TMP_DIR/$BINARY"
+_dl "$BASE_URL/$BIN_ASSET" "$TMP_DIR/$BIN_ASSET"
_dl "$BASE_URL/SHA256SUMS.txt" "$TMP_DIR/SHA256SUMS.txt"
# โโ Verify checksum โโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโ
@@ -123,8 +123,8 @@ success "Checksum OK"
step "Installing binary"
mkdir -p "$INSTALL_DIR"
-chmod +x "$TMP_DIR/$BINARY"
-mv "$TMP_DIR/$BINARY" "$INSTALL_DIR/$BINARY"
+chmod +x "$TMP_DIR/$BIN_ASSET"
+mv "$TMP_DIR/$BIN_ASSET" "$INSTALL_DIR/$BINARY"
success "Installed: $INSTALL_DIR/$BINARY"
# โโ Add to PATH in shell profile โโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโ