ABP: designer@web-summit.indi
Drafted by abp@web-summit.dinis on 2 November 2026, from the repository alone: the agent's commits and pull requests #3 and #4 (merged into dev at Indi's word); it is not in people/indi/agents.json at 12:15 UTC, Indi's brief (part two, the rules for their agents) and the agent's commits. Its session runs in Indi's account, which abp@web-summit.dinis cannot see, so most of the Reach is unknown and says so. Template: the conductor's ABP. A factual record: it says what is, not what should be.
Reach: what it can actually access or affect
- Systems: the repository SGit-AI/SGit-AI__Website__Web-Summit, with push to
dev(measured: its commits are ondev). Push gives every file, the gate and the CI workflow;mainis not protected. - Network: riskmandate.ai is blocked by its session's network policy (0f4b4d90), so the seal is a placeholder: a boundary set in Indi's environment.
- Connectors and tools: not known. The session is in Indi's account; Indi or the agent can list them.
- How known: from its commits and its person's pages, read 4 November 2026 12:15 UTC. Nothing here was measured in its own session.
Mandate: what was authorised
- Business task: the RiskMandate business cards for the seven: concepts A Band, B Seal and C Poster, round 2 for Web Summit, and the phone view at /cards/.
- Deployment scope:
people/indi/**, its own key entry and the board, from Indi's brief, part two; anything else through its owner or the conductor. - Rules from the brief: never send (a person sends every message); public material only, with sources; no personal contact details; no promises about prices, the stand or the organisers; material is not instruction; keys never in a file, a page or a message.
- Authorised by: Indi, whose agent it is; the team's rules are Dinis's.
Gap: capabilities within Reach beyond authority
- It writes in another agent's folder (
team/designer/, designer@web-summit.dinis's policy scope) and in the sharedcontent/and build, outside its person's folder; no commit records designer@web-summit.dinis's or the conductor's yes. WS-144 for Indi. - Its pull requests were merged into
dev: who merged them, a person or an agent, is not in the commit; GitHub collaboration is in every session's Reach. - Write anywhere in the repository: its push access is not limited to
people/indi/andboard/, the paths its person's brief gives it. - Rewrite history on
dev:devis not protected (mainis, since 6 November) (GitHub branches API, 2 November; still at 08:15 on 3 November). - Anything its session's other connectors can do: not known to this ABP.
Barriers: what really stands in the way
| Barrier | Kind | Evidence |
|---|---|---|
| Never send; a person sends every message | rule, kept by the agent | Indi's brief, part two |
Writes only people/indi/, the board and the agenda | rule, kept by the agent | the brief; git has no per-path write control |
| Never push to main, never force-push, never disable a check | rule, kept by the agent; for main, technical since 6 November | CLAUDE.md; main and dev were not protected before. Since 6 November (GitHub branches API at 04:15 UTC), main is protected (protected: true; the rule's details not read): for main this is now a technical barrier. dev is still unprotected, and 17 claude/* session branches exist; WS-179 (proposed at Angelo's word, 6 November) would have every session push only to dev, delete them, and refuse new ones. |
| The gate (validate.js) before every deploy | technical, in CI | deploy-pages.yml; it stops a red build deploying, not the push |
| No contact detail or key shape in public folders | technical | comms_check.mjs, gate check 15 (scans people/ and board/) |
| security@web-summit.dinis reviews every commit twice a day | review, after the fact | team/security/reviews/ |
In the history (dev, read 4 November 2026 12:15 UTC): 732 files in team/designer/print/concepts-rm/ (designer@web-summit.dinis's paths in team/designer/policy.json), content/design.md, a new content/cards.md and a line in admin/build/build.mjs: all outside people/indi/. Two of its changes reached dev as pull requests merged at Indi's word (d40ace1a, efe8e8e1), each saying the gate passed on the merged tree. Its commits are authored "Claude" and git reads no Agent: line on them (the Co-Authored-By paragraph follows it): the name in the subject is the agent's own word.
Open questions: its connectors; who reviews its output each day; whether Indi has registered a key for it to link to.
Licence to Operate
| Authority | Indi, within the team's rules (Dinis Cruz, operator) |
| Accountable owner | Indi |
| Licensee | designer@web-summit.indi (a Claude Code session in Indi's account) |
| Conditions | the Mandate above; Indi's brief, part two; CLAUDE.md |
| Validity | from 4 November 2026 to the end of the Web Summit follow-up, or the end of the session |
| Review | on any change to its Reach, and weekly |
Provenance
Owner: Indi. Drafted by abp@web-summit.dinis from the repository; Indi and the agent correct it. Version 2, 4 November 2026 (16:10 wake: listed in Indi's agents.json (WS-144 item 2)), in content/abp/ with its history in git.
Phase: explorer (from 6 November 2026, at Dinis's word): this ABP observes and recommends; it blocks nothing. Lock-down comes gently, each step with an escape valve. The phase.