ABP: dev@PrompTugal.angelo

Renamed from dev@web-summit.angelo to dev@PrompTugal.angelo on 6 November 2026 (Angelo's agents' new names, people/angelo/agents.json; it keeps its key and key id, at Angelo's word, fd819c3c). Earlier versions are in git at content/abp/dev-web-summit-angelo.md.

Drafted by abp@web-summit.dinis on 2 November 2026, from the repository alone: Angelo's dashboard and people/angelo/agents.json, Angelo's brief (part two, the rules for their agents) and the agent's commits. Its session runs in Angelo'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.
• Connectors and tools: not known. The session is in Angelo's account; Angelo or the agent can list them.
• How known: from its commits and its person's pages, read 2 November 2026 17:15 UTC. Nothing here was measured in its own session.

Mandate: what was authorised

• Business task: the site's build, gate, pipeline and pages.
• Deployment scope: people/angelo/** is its person's; the board (board/) and the stand-ups' agenda (data/meetings/) are everyone's; anything else goes through its owner or the conductor (Angelo's brief, part two, rules).
• 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: Angelo, whose agent it is; the team's rules are Dinis's.

Gap: capabilities within Reach beyond authority

• Its job is the build, the gate and CI, which dev@web-summit.dinis also holds until it is handed over: two agents with the same write paths and no recorded order between them.
• ebbe647: it published its session key in data/keys.json (sha256:b478b82a3a9995eb); at Angelo's word it is not linked to the operator's key, so its authorisation is the push itself.
• 746a42b: Angelo has an email account to send from (L2); no agent's mandate here says it may send from it.
• Since v0.1.51 a change to admin/build/tag_release.sh runs in CI with a token that can write to the repository and deploy; its job includes that file.
• Write anywhere in the repository: its push access is not limited to people/angelo/ 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).
• Anything its session's other connectors can do: not known to this ABP.

• Code in its person's folder runs in CI (WS-133, 4 November): admin/build/build.mjs runs people/<id>/pages.mjs and a person's own app/data.mjs in the release job, which holds a token that can push and deploy. Writing only in its own folder no longer bounds what it can do.

• Angelo's protocol, 5 November (people/angelo/kit/README.md, each rule in Angelo's words): (1) shared code stays with its owners: his agents draft patches to shared code and pages and route them to the owner, never apply them, with a Routed: line (9e94d0c3, WS-34); (2) his signature counts for tier 1 and 2 actions only, never tier 3, and a signed message names its recipient, item, action and old value with an id and a time, refused if replayed or stale (70aa65fa, WS-138); (3) no agent of his reads what a stranger writes: visitors get a separate inbox sealed only to Angelo's person key (b8a5d3ab, held for security's review of the design). Rules (1) and (2) are kept by the agents; (3), once built, is a technical barrier: what a stranger writes cannot be opened by any of his agents.
• Angelo lifted his first rule (ce069603, 6 November evening, his words: "we shouldn't go for an overly bureaucratic approach ... We lift the limit that we don't touch other people areas but with the caveat that we need to find a way to avoid clashing on parallel changes"). His agents may now change another owner's code, page or data directly, under the tiers, after five steps: pull dev just before; check the path's last two hours and the board's picked issues (if busy, send a draft instead); say it in the commit, For: the owner; on a rebase conflict keep theirs and send theirs as a draft; shared data/*.json from a fresh dev, one entry at a time. A deliberate loosening, with conditions: the explorer phase as a person chose it.

• A review gate before dev (645d429b, the new-agents spec, approved by Angelo on 7 November): every new worker agent of Angelo's pushes only to workers/<agent>; this agent reviews and brings each onto dev as one commit (vault@ does so for vault.kms). A second agent between a worker and the team's branch, by design.

Barriers: what really stands in the way

In the history (dev, read 2 November 2026 20:15 UTC): since 17:15 also 746a42b (people/angelo/onboarding.json) and ebbe647 (data/keys.json, its own entry), inside its mandate. Earlier: fc79f3e: people/angelo/onboarding.json (Angelo's onboarding at L1). Inside its person's folder. 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 Angelo has registered a key for it to link to.

Licence to Operate

Provenance

Approved by Angelo as it stood at 5732bdf1 (6 November about 13:00 UTC, his words: "ABPs as they stand are approved for now"; WS-34). A later draft needs his word again. The phase line added in 630ca8a8 was accepted by Angelo (fd819c3c).

Owner: Angelo. Drafted by abp@web-summit.dinis from the repository; Angelo and the agent correct it. Version 8, 7 November 2026 (12:10 wake: the review gate; 20:10 wake: renamed; Angelo's acceptance; his first rule lifted; 12:10 wake: Angelo's protocol; 00:10 wake: WS-133; 08:10 wake: main still unprotected; 00:10 wake: main pushed once, still unprotected; 20:10 wake: its key, Angelo's email), 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.