ABP: curator@PrompTugal.vicky

Renamed from curator@web-summit.vicky to curator@PrompTugal.vicky on 6 November 2026 (9cbfb9ff and Vicky's agents.json): the same agent and desk, under the newsroom's name. This page's earlier versions are in git at content/abp/curator-web-summit-vicky.md.

Drafted by abp@web-summit.dinis on 2 November 2026, from the repository alone: people/vicky/agents.json and the agent's commits, 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 access via Vicky's GitHub account (Dinis gave it write access, 16269c3a).
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 4 November 2026 20:15 UTC. Nothing here was measured in its own session.

Mandate: what was authorised

Business task: the newsroom's curator desk: maps the researcher's captures (beats, organisations, what is new, story candidates, gaps) into desks/curator/ in the newsroom repository, for Indi's journalist; at 07:45, 11:45, 15:45 and 19:45 UTC.
Deployment scope: desks/curator/ in PrompTugal/PrompTugal__News__Website (at Vicky's word, 16269c3a), its reports in people/vicky/reports/ here, and its own key entry in data/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 writes in the newsroom repository, where this repository's gate and security@web-summit.dinis's review do not reach; conductor@web-summit.vicky notes that the newsroom's gate does not check desks/ for contact details, so each desk checks its own files.
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.
Rewrite history on dev: dev is not protected (main is, 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	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; 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 20:15 UTC): here: two reports in people/vicky/reports/ (22 captures mapped, 7 story candidates) and its key entry: inside its mandate. Its main work is in the newsroom repository, not read for this draft. 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	curator@PrompTugal.vicky (a Claude Code session in Vicky's account)
Conditions	the Mandate above; Vicky'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: Vicky. Drafted by abp@web-summit.dinis from the repository; Vicky and the agent correct it. Version 2, 6 November 2026 (12:10 wake: renamed), 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.