From fde7db76fe3040fc39d034b17bcbe2eefc12c712 Mon Sep 17 00:00:00 2001 From: Kishore Kumar Date: Wed, 17 Jun 2026 23:06:40 +0530 Subject: [PATCH] docs(changelog): add Jun 17 entry for the website refresh The marketing site now centers on the compounding operational-knowledge loop with a hero pipeline diagram. Add a date-disambiguated Jun 17, 2026 `` (tags What's new + UI) above the existing API gate-conditions entry, per the same-date release-template rule. Co-Authored-By: Claude Opus 4.8 (1M context) --- changelog.mdx | 13 +++++++++++++ 1 file changed, 13 insertions(+) diff --git a/changelog.mdx b/changelog.mdx index ec310ce..14130ba 100644 --- a/changelog.mdx +++ b/changelog.mdx @@ -22,6 +22,19 @@ export const STAGE_SELF_MANAGED_M66 = "$0.0001"; agentsfleet is in **stealth-mode testing** and pre-production. APIs and agent behavior may change between releases without long deprecation windows. Email [agentsfleet@agentmail.to](mailto:agentsfleet@agentmail.to) if you want a hand calibrating an agent or to join as a design partner. + + ## The website explains agentsfleet as one resident-engineer loop + + agentsfleet.net now describes the product as a single loop a resident engineer runs: a first signal becomes a recurring problem class, then a scenario and test, then a fix pull request a human reviews before merge — so the same incident recurs less often. A hero pipeline diagram draws the loop end to end, replacing the earlier deploy-failure wake-on-event framing. + + ## What's new + + - **Hero pipeline diagram** — the home page shows the loop step by step (first signal → recurring problem class → scenario and test → fix pull request → human review → fewer repeats), with the human-approval gate marked explicitly. + - **Signal source strip** — names the categories the agent reads: Signals, Telemetry, Code, and Control plane. + - **Compounding-knowledge section and competition table** — describe how recurring problem classes accrue over time and how a resident engineer differs from a wrapper around a model. + - **Unchanged paths still work** — the install copy-row, the animated terminal, the per-second pricing section, and the `/pricing` and `/agents` routes behave exactly as before. + + ## Invalid gate conditions are rejected at write time