Section: Agent security & behaviour policies fetched 2026-11-16 | Every article on what an agent may do, who carries the risk and how a behaviour policy is enforced, newest first: RiskMandate, ABPs, SHarness, the insurance series (28 Oct), the grant not the prompt, Odoo workflow, CI behaviour policies. | direct section | Lists proposals (insurer, payout per row) beside running work; each article's own 'does not claim' list must travel with any reprint. |
The five desks fetched 2026-11-16 | A desk is an audience, not a topic: every article is placed on one desk first, a second when it touches another; five desks with start-here pieces. | supporting page | No .md twin (404); read from HTML. |
Working on the newsroom solved RiskMandate's key problem 2026-10-12 | Progress is not a straight line: newsroom work solved RiskMandate's six-month problem of where to keep the master vault secrets, and builds its workflows and public example. | supporting none | States RiskMandate engagements are 'still close to forward-deployed engineering'. |
The proof is two clicks behind the claim 2026-09-07 | A homepage that leads with what cannot be seen and buries openable proof loses; put the artefacts a stranger can open first. Rebuild in proof-moved-up. | supporting homepage-block | Pair with proof-moved-up (same date). |
Sections index fetched 2026-11-16 | A section is the newsroom read by one audience, built by rule from the desks; the index lists only 'For publishers'. | adjacent none | Index lists one section though sections/agents/ and sections/policy/ (and building, graphs, news, strategy, vaults) exist at their URLs; no .md twin for the index. |
The cell is the unit of what AgentiCCells sells 2026-11-16 | A cell is one focused job with an objective, a deliverable and a behaviour policy, each sold on its own page with a free recipe and three paid ways to get help. | adjacent none | Page and catalogue are mock-ups; prices are first proposals; industry cells are examples without customers. |
A CRM for us and our agents 2026-11-16 | A vault-based CRM with an iOS app, used first on the team's own people and agent fleet, because a fleet of agents is itself a CRM and no existing product meets the constraints of keys per agent and written behaviour policies. | adjacent none | A plan; CRM does not exist in this form; research a snapshot of 16 November 2026; vendor approval and audit claims unconfirmed. |
The site factory works: a site from a commit 2026-11-16 | A committed request made a CI pipeline create the repository, DNS, certificate and HTTPS and have Claude Code write a first version; the RiskMandate at Web Summit site was live 87 seconds after merge. | adjacent none | Four sites made by the factory, two tests; public sites only; vault step not automated; pipeline holds more permission than it needs. |
From a commit to a live website: a site factory 2026-11-15 | A CI pipeline driven by a request folder in a commit could create the repository, DNS record and vault for each new site, plan on pull request and apply on merge, with no long-lived keys. | adjacent none | A hypothesis and architecture, not built. |
Spend fewer tokens: the bill is a design choice 2026-11-15 | An agentic team's token bill is mostly design: files as memory, caching, code over models where possible, the right model per step, no copy and paste, static outputs, and counting it. | adjacent none | Own runs only; dollars API-equivalent. |
Stop copying and pasting between your agents 2026-11-15 | A person carrying text between AI sessions becomes the bottleneck; agents should talk through recorded, signed channels while structure scales the person's decisions. | adjacent none | On-demand specialist agents are an idea, not an offer with a price. |
Don't micromanage your agents 2026-11-15 | A team lead's shift from reading everything to managing her agents through instructions, structure and workflows, backed by specialist agents from another team, is a model for companies. | adjacent none | Experience paraphrased from conversations, not quoted; the company model is a proposal, run informally. |
Always-on agents at team scale 2026-11-15 | Anthropic's five primitives for always-on agents match what the team built for around 250 agents from git, files, vaults and keys; at team scale come agents starting agents, identity, mass stops, many humans and governance. | adjacent article-reprint-link | Not a claim the design is better; not reviewed by Anthropic; 'around 250' counts distinct agent names. |
Town planners for mission-critical code 2026-11-14 | Whatever wrote the change behind the 13 November US ground stop, such systems need every line read, certified and tested by a team, with AI used around the code rather than to skip that work. | adjacent none | Does not claim to know the cause; investigation not reported; the pipeline is a proposal; no claim AI was or was not involved. |
Signed email from the agent, verifiable by QR 2026-10-30 | Give each email agent a key vouched for by its person on pki.sgit.ai, so every drafted email carries a signature and QR the recipient can check; a brief for what to build. | adjacent none | A brief: what to build, not built. |
You can feel good engineering, in agents too 2026-10-27 | Multiple agent teams behave like multiple human teams; engineering gaps slow them, agents hide the overhead until limits break, so keep architecting and refactor from explorer to villager. | adjacent none | |
CI owns the version number 2026-10-27 | A release number reflects the order pushes land, which only the pipeline knows, so CI should pick it; adopted by agent-built sites after version collisions. | adjacent none | |
The evidence behind four days 2026-10-27 | A named person's public claims re-counted from public data, each number traceable; most holds, some counts differ. | adjacent example | Example of checking a third party's numbers without an evaluative verdict; quote with care (rule 5). |
Why scheduled agent loops are hard 2026-10-25 | A pipeline of scheduled agents works but is brittle, because each needs a persistent session holding state and keys; keep own code minimal and spend as much on visibility as setup. | adjacent none | |
Agent sessions that resume where a team left off 2026-10-24 | Agent sessions with one mandate, role and repository can be paused and resumed with their reasoning intact, unlike human teams that leave and take the knowledge. | adjacent none | |
Three agents in a chain, almost working 2026-10-23 | A researcher, curator and journalist agent chain updates the PHP site; the hard gap was agent identity and secret delivery, solved with session key pairs sealed via pki.sgit.ai. | adjacent article-reprint-link | Not finished: on 23 October no agent had yet written its own run record. |
php2shell at 8pm, and a site built in a day 2026-10-22 | Status of the php2shell story at 22 October 20:00 UK, and a tour of an evidence site built in one day by two people and thirteen agents. | adjacent article-reprint-link | Figures are time-bounded to 22 October; no named organisation had reported compromise. |
Reviews on the record by other models 2026-10-18 | Every article gets reviewed against published criteria by other models, the editor and later the desk, each review an immutable file per text, with the newsroom answering every finding. | adjacent none | One reviewer, one batch so far; a finding is a claim, not a verdict; a hash is not a signature; signed readers a proposal. |
The code you do not ship: minimal code paths 2026-10-18 | Code is a liability; models now make removing unused code safe, so software should move to the minimal viable code path, maintained by specialists with each piece carrying its own behaviour, decision and workflow policies. | adjacent none | One tool and one use case; the fractal market is a proposal; some figures are vendors' own. |
A minimal viable browser for agents 2026-10-18 | A browser with a small kernel and components loaded only when needed would shrink attack surface, and a browser for one agent with no accounts, extensions or file access is a practical prompt-injection defence by limiting reach. | adjacent none | No such browser exists, design a proposal; Mozilla has not said it will build it; smaller is not safe; CVE counts are the site's own from NVD on 18 Oct 2026; some figures vendors' own. |
GenAI in Portuguese: Lisbon 2024 talk revisited 2026-10-16 | The 2024 OWASP Lisbon talk's principles (provenance, graphs over RAG, determinism) still hold, and the board assistant has become agents with a mandate whose problem is controlling what they do. | adjacent none | Commentary is the author's, now; slides and transcript from 2024. |
Explorer coding, and the handover to villagers 2026-10-16 | Vibe coding should be called explorer coding; its output is a brief, and once others depend on it villagers must maintain it with agent behaviour policies before town planners own it. | adjacent none | Explorer coding is a proposal; the HR conversation is one illustration; the explorer product version is a proposal no vendor sells. |
Voice memos checked against the record 2026-10-15 | Recording claims as remembered and having the agent check them against the record moves peer review to before publishing and gives every article its provenance. | adjacent none | Tally is small, not a study; not found is not false; the Deep Research recollection is partly memory. |
Chainguard mapped, and the context layer 2026-10-14 | A map of a supply-chain vendor's products and public data shows its graph stops at the package; the context layer above, written as a policy row per image, is open ground. | adjacent none | Named third party; the article opens with evaluative praise ('most interesting work') that rule 5 forbids carrying over. Figures are the author's own counts of public feeds and need a recount. |
Brief the reader's agent too 2026-10-11 | People increasingly read through agents, so what is sent needs a second package for their agent, written safely because it is input to a system that acts. | adjacent none | Items for the RiskMandate agent are a to-build list. |
Agents will pay for curated graphs 2026-10-11 | A curated graph answers an agent's question for far fewer tokens than the raw articles, so paying the publisher is cheaper for the agent than not paying. | adjacent none | Signed claims with expiry are proposed, not built. |
One article, five agent readers 2026-10-10 | Write the article first, then send five role agents (librarian, cartographer, historian, explainer, storyteller) through it to catalogue, map and condense it. | adjacent none | Found that hope-or-enforcement says the mandate 'is twelve actions' while the list has ten clauses: a recount for any reuse. |
Hari Kota's AI governance stack as a graph 2026-10-09 | A ten-layer AI governance stack, kept as posted, becomes a fractal graph where a gap is a missing edge and a missing edge is a query. | adjacent none | The organisation at altitude 3 is fictional; quotes EU AI Act provisions (permitted) — avoid any standards-body text. |
Encrypted memory for isolated agents 2026-10-08 | Isolated, ephemeral agents need memory the owner controls; five sgit deployment patterns from a Mac mini to Kubernetes keep servers holding ciphertext only. | adjacent none | |
Knowing when to stop, for people and agents 2026-10-08 | Experience teaches people when to stop; agents need constraints that carry perspective (direction, a mandate, memory, scoped graphs, a stop) rather than draconian rules. | adjacent article-reprint-link | |
Thinking with a Wardley map (collection) 2026-10-07 | Six articles that each place something on the evolution axis and argue from where it sits; the map as a claim with its source published, not a picture. | adjacent article-reprint-link | Collection last updated 2026-10-08 (page footer sgit.ai v0.7.87); later ABP pieces (insurance series 28 Oct, the grant not the prompt, SHarness, Web Summit) are not in it. Only the-mandate-stack is ABP material; the rest is strategy context. |
GitHub's outage deserves an aviation-style inquiry 2026-10-05 | A global Actions outage should get an independent, aviation-style inquiry with near-miss reporting and a published second story, evidence held in vaults. | adjacent article-reprint-link | Concerns a named third party: use facts and dates only, no evaluative wording. |
Custom UIs per message, each with a policy 2026-10-01 | Every message has a graph, so interfaces are built per reader's moment; each such interface is an agent surface and so needs its own behaviour policy. | adjacent article-reprint-link | Interfaces shown are mock-ups with placeholder names. |