Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
31 changes: 30 additions & 1 deletion website/src/pages/git-agentic.astro
Original file line number Diff line number Diff line change
Expand Up @@ -58,7 +58,7 @@ const structuredData = [
<Base
title="AI Agent Version Control & Atomic Rollback | git.agentic"
description="Version and roll back AI agent code, prompts, tools, models, memory, and schema atomically. Open-source Rust core, Python SDK, and LangGraph support."
modifiedTime="2026-07-18"
modifiedTime="2026-11-20"
structuredData={structuredData}
>
<Header />
Expand Down Expand Up @@ -181,6 +181,35 @@ $ ./scripts/run-demo.sh <span class="comment"># builds, runs, breaks
branches as an agent-run primitive, and hardening.
</p>

<h3>Security hardening, November 2026</h3>
<p class="mute">
On 20 November 2026 a security hardening round merged (PRs #145 to #153
and #156). The daemon already checks socket peers against a UID
allowlist (<a href={`${repo}/blob/main/docs/adr/0012-socket-peer-authentication.md`}>ADR-0012</a>).
Now any rollback that runs reverse schema migrations also needs an
operator approval token (<a href={`${repo}/blob/main/docs/adr/0019-approval-for-reverse-migration-rollback.md`}>ADR-0019</a>). Tokens are single-use per daemon
process and scoped, so a reverse-migration token cannot authorize a
data-loss rollback. The <code>agentic</code> CLI can attach the token
automatically when its preview shows approval is needed, it can read the
key, and the daemon's peer UID owns that key.
</p>
<ul class="plain">
<li>The object store keeps raw and typed objects at separate storage paths, so one can no longer occupy the other's address (<a href={`${repo}/blob/main/docs/adr/0018-separate-raw-object-namespace.md`}>ADR-0018</a>)</li>
<li>The sidecar deployment keeps daemon state on a volume only the daemon writes, checks state-directory ownership at startup, reads credentials from files, and redacts the GCS token and the Postgres URL in the store and memory-backend debug output. The Cloud Run layout is not yet verified, and full credential isolation needs separate service identities</li>
<li>Rollback validates the prompt tree before any database change and refuses symlinked prompt directories</li>
<li>The LangGraph checkpointer only deserializes allow-listed types</li>
<li>CI actions are pinned to commit SHAs and the sidecar's base images to digests; the open Rust advisories were fixed and the website's production dependencies report zero npm audit findings</li>
<li>The threat model is reconciled (TM-001 to TM-013) and documents the remaining risks</li>
</ul>
<p class="mute">
Still open: the rollback target of under 5 seconds at 1M-row pgvector
scale is under verification
(<a href={`${repo}/issues/132`}>issue #132</a>); demo-scale rollback takes
about 1 second. Per-operation authorization is still open (TM-001):
for example, a rollback without a schema change can restore memory
without an approval token.
</p>

<h2>Design partners</h2>
<p class="mute">
If you run a stateful LangGraph agent in production and have been
Expand Down
6 changes: 3 additions & 3 deletions website/src/pages/index.astro
Original file line number Diff line number Diff line change
Expand Up @@ -19,7 +19,7 @@ const structuredData = {
<Base
title="Open-Source Infrastructure for AI Agents | git.agentic"
description="Version control, parallel source control, and software supply-chain security for AI agents. Explore three open-source projects from git.agentic."
modifiedTime="2026-07-18"
modifiedTime="2026-11-20"
structuredData={structuredData}
>
<Header />
Expand Down Expand Up @@ -79,7 +79,7 @@ $ sc demo --agents 4

<span class="comment"># agent workspaces: run a command across N forks, harvest results</span>
$ sc work --agents 4 -- cargo test</code></pre>
<p class="meta">Rust · Tauri v2 · TypeScript · Phases 1–35 built</p>
<p class="meta">Rust · Tauri v2 · TypeScript · Phases 1–36 and 37a–37d built</p>
<p><a href="/src-control">Full page →</a> &nbsp; <a href={srcControl}>GitHub →</a></p>
</section>

Expand All @@ -104,7 +104,7 @@ $ sc work --agents 4 -- cargo test</code></pre>
<span class="bad">critical</span> [secret-exfil] reads ~/.npmrc, AWS credentials…

HTTP 403 x-sentinel-verdict: block</code></pre>
<p class="meta">TypeScript · security layer + registry built · pre-1.0 · v0.1.0-alpha.1 on npm</p>
<p class="meta">TypeScript · security layer + registry built · pre-1.0 · v0.1.0-alpha.2 on npm</p>
<p><a href="/sentinel">Full page →</a> &nbsp; <a href={pkgRegistry}>GitHub →</a></p>
</section>

Expand Down
19 changes: 12 additions & 7 deletions website/src/pages/sentinel.astro
Original file line number Diff line number Diff line change
Expand Up @@ -19,7 +19,7 @@ const faqs = [
},
{
question: 'Is Sentinel production ready?',
answer: 'Sentinel is pre-1.0 and published as an alpha. Its product page documents current capabilities and limitations; production adoption should follow that status.',
answer: 'Sentinel is pre-1.0 and published as an alpha (currently 0.1.0-alpha.2). Its product page documents current capabilities and limitations; production adoption should follow that status.',
},
];
const structuredData = [
Expand Down Expand Up @@ -58,13 +58,13 @@ const structuredData = [
<Base
title="npm Supply-Chain Security for AI Agents | Sentinel"
description="Audit npm packages before install-time code runs. Sentinel gives AI agents deterministic risk verdicts, sandbox enforcement, and human approval gates."
modifiedTime="2026-07-18"
modifiedTime="2026-11-20"
structuredData={structuredData}
>
<Header />

<div class="badges">
<span class="badge"><span class="pulse"></span>Security layer + registry built · pre-1.0 · v0.1.0-alpha.1 on npm</span>
<span class="badge"><span class="pulse"></span>Security layer + registry built · pre-1.0 · v0.1.0-alpha.2 on npm</span>
<span class="badge">Apache 2.0</span>
<span class="badge">TypeScript</span>
</div>
Expand Down Expand Up @@ -201,10 +201,15 @@ $ sentinel audit is-odd 3.0.1
2026-07-13: audit-gated publishes, verified namespace claims,
time-locked retraction, and an npm/pnpm/Yarn/bun-compatible surface
with a safe exit path. Sentinel is pre-1.0 and not yet
production-hardened, but it is now installable: the first alpha,
v0.1.0-alpha.1, is published to npm — all seven
<code>@git-agentic/sentinel-*</code> packages, under the
<code>alpha</code> dist-tag. The next milestone is design-partner
production-hardened and its APIs may change, but it is installable: the
current alpha, v0.1.0-alpha.2 (released 14 July 2026), is on npm: all
seven <code>@git-agentic/sentinel-*</code> packages, under the
<code>alpha</code> dist-tag, and the <code>latest</code> tag points to it
as well. Since July: obfuscation false-positive fixes, approval identity
coverage and dependency updates. On 20 November 2026 a security-audit
fix round (#84) merged to <code>main</code>, and the audit now follows
install hooks that run npm, pnpm, yarn or bun scripts (#89). Both came
after 0.1.0-alpha.2 and are not in that release yet. The next milestone is design-partner
evidence — blocked incidents, false-positive rate, audit latency. The
long arc is policy and install-time permissions for the whole
ecosystem.
Expand Down
8 changes: 4 additions & 4 deletions website/src/pages/sitemap.xml.ts
Original file line number Diff line number Diff line change
Expand Up @@ -3,10 +3,10 @@ import { escapeXml } from '../utils/xml';

const site = 'https://git-agentic.com';
const staticPages = [
{ path: '/', lastmod: '2026-07-18', priority: '1.0' },
{ path: '/git-agentic', lastmod: '2026-07-18', priority: '0.9' },
{ path: '/src-control', lastmod: '2026-07-18', priority: '0.8' },
{ path: '/sentinel', lastmod: '2026-07-18', priority: '0.8' },
{ path: '/', lastmod: '2026-11-20', priority: '1.0' },
{ path: '/git-agentic', lastmod: '2026-11-20', priority: '0.9' },
{ path: '/src-control', lastmod: '2026-11-20', priority: '0.8' },
{ path: '/sentinel', lastmod: '2026-11-20', priority: '0.8' },
{ path: '/learn', lastmod: '2026-07-18', priority: '0.8' },
];

Expand Down
41 changes: 33 additions & 8 deletions website/src/pages/src-control.astro
Original file line number Diff line number Diff line change
Expand Up @@ -63,13 +63,13 @@ const structuredData = [
<Base
title="In-Memory Git Worktrees for Parallel AI Agents | src-control"
description="Fork in-memory worktrees for parallel AI agents, collaborate through encrypted branches, sync with Git, and inspect native history in a read-only desktop app."
modifiedTime="2026-07-18"
modifiedTime="2026-11-20"
structuredData={structuredData}
>
<Header />

<div class="badges">
<span class="badge"><span class="pulse"></span>Phases 1–35 built</span>
<span class="badge"><span class="pulse"></span>Phases 1–36 and 37a–37d built</span>
<span class="badge">Rust · Tauri v2 · TypeScript</span>
<span class="badge">Builds on Git, not against it</span>
</div>
Expand Down Expand Up @@ -165,7 +165,7 @@ $ npm ci &amp;&amp; npm run tauri dev</code></pre>
never enters the object store; a keyless clone gets ciphertext
only</li>
<li>sc-native transports over SSH and HTTP(S) — in-binary TLS
(<code>sc+https://</code>, first-connection (TOFU) pinning), token-based
(<code>sc+https://</code>, first-connection (TOFU) pinning or CA validation), token-based
access control, connection caps, session timeouts, streaming packs
that move multi-GiB repos in bounded RAM — plus partial clone</li>
<li>Git interop via <code>gix</code>, isolated in one crate — import a
Expand All @@ -185,7 +185,7 @@ $ npm ci &amp;&amp; npm run tauri dev</code></pre>

<h2>Status</h2>
<p class="mute">
Phases 1–35 are built and tested. The arc so far: in-RAM virtual
Phases 1–36 and the P37a–37d partial-clone series are built and tested. The arc so far: in-RAM virtual
worktrees and committed secrets (P1–2); persistent repos, merge,
secret scanning, remotes, encrypted paths, packfiles/GC, Git
export (P3–9); bidirectional Git sync, secret/permission lifecycle
Expand All @@ -200,17 +200,42 @@ $ npm ci &amp;&amp; npm run tauri dev</code></pre>
recipient set, with O(1) grant, plaintext-free revocation, and
atomic publish (P34); and a native Tauri v2 browser over the <code>.sc</code>
object model, with refs, all-parent history, provenance, public trees, and
first-parent diffs while protected and private states stay safe (P35).
Feature phases ship with runnable proofs and tests — see <code>demo/</code>
and <code>apps/desktop/</code> in the repo. Pre-1.0 and design-partner alpha:
first-parent diffs while protected and private states stay safe (P35);
bucket WAL remotes over <code>sc+wal://</code> and <code>sc+s3://</code>
(P36); and lazy partial clones, with want-by-id fetch, presence-based
partial clones, and merge, cherry-pick, rebase and agent sessions on a
partial clone (P37a–37d).
Feature phases ship with runnable proofs and tests; the repo has 28
end-to-end demo proofs in <code>demo/</code>, and the desktop app lives in
<code>apps/desktop/</code>. Pre-1.0 and design-partner alpha:
the cryptography has not had an independent audit,
<code>sc+https://</code> trust is first-connection (TOFU) pinning,
<code>sc+https://</code> trust defaults to first-connection (TOFU) pinning, with CA validation as an option,
and revoking a private-branch recipient protects what is sealed
afterwards — it cannot erase what they already fetched. The
near-term promise is parallel agent workspaces and provenance,
not production secret management.
</p>

<p class="mute">
Recent changes: named and concurrent <code>sc ws</code> sessions, TLS pin
management (<code>sc tls</code>) and CA validation for
<code>sc+https://</code>, token expiry and rotation,
<code>sc rewrap --rotate</code>, a blob-size clone filter, and owner-only
key ACLs on Windows. On 20 November 2026 a security fix round merged
(#360 to #368): fuzzing of untrusted decoders, serve hardening, and fixes
for a checkout escape, recipient sealing, and secret environment
injection.
</p>

<p class="mute">
P38 added sc-forge, a configurable self-hosted Git host: bare Git over
smart HTTP, a recorded Gitea API subset, protected merges, and ops
tooling. It passes all 24 recorded scenarios and six first-consumer
acceptance scenarios locally. Its design (ADR-0058) was accepted on 25
October 2026. Passing local acceptance does not approve a production
migration; that is a separate step.
</p>

<p class="mute">
Docs: <a href={`${repo}#readme`}>README</a> ·
<a href={`${repo}/blob/main/ARCHITECTURE.md`}>Architecture</a> ·
Expand Down
Loading