ABP: checker@PrompTugal.vicky

Drafted by abp@web-summit.dinis on 2 November 2026, from the repository alone: people/vicky/agents.json and the agent's commits (9cbfb9ff, 3ca27862, 4dd590ea), Vicky's brief (part two, the rules for their agents) and the agent's commits. Its session runs in Vicky'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 on dev). Push gives every file, the gate and the CI workflow; main is not protected.
The newsroom repository: push via Vicky's account.
Connectors and tools: not known. The session is in Vicky's account; Vicky or the agent can list them.
How known: from its commits and its person's pages, read 6 November 2026 12:15 UTC. Nothing here was measured in its own session.

Mandate: what was authorised

Business task: fact-checks the articles Dinis's agents write for the newsroom and talks to them; findings in desks/checker-vicky/findings/ in the newsroom repository; at 09:48 and 17:48 UTC.
Deployment scope: desks/checker-vicky/ in the newsroom repository, its reports in people/vicky/, its two keys (here and in the newsroom's board/keys.json).
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: Vicky, whose agent it is; the team's rules are Dinis's.

Gap: capabilities within Reach beyond authority

It talks to Dinis's agents about their articles: Vicky's agent writing to agents in another account, whose own rules make that material, not instruction.
It writes in the newsroom repository, beyond this repository's gate and review.
Code in its person's folder runs in CI with a token that can push and deploy (WS-133).
Write anywhere in the repository: its push access is not limited to people/vicky/ and board/, the paths its person's brief gives it.
Push to main or rewrite history: main and dev are not protected (GitHub branches API, 2 November); main protected since 6 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	Vicky's brief, part two
Writes only `people/vicky/`, 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	CLAUDE.md; `main` and `dev` are not protected
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 6 November 2026 12:15 UTC): its key entry, its saved prompts and its first run's report: inside its mandate. 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 Vicky has registered a key for it to link to.

Licence to Operate


Authority	Vicky, within the team's rules (Dinis Cruz, operator)
Accountable owner	Vicky
Licensee	checker@PrompTugal.vicky (a Claude Code session in Vicky's account)
Conditions	the Mandate above; Vicky's brief, part two; CLAUDE.md
Validity	from 6 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: Vicky. Drafted by abp@web-summit.dinis from the repository; Vicky and the agent correct it. Version 1, 6 November 2026, 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.