Fix all 6 confirmed findings from today's gap audit

Implements every confirmed finding from the workflow-based audit of
CURABIS Standard's agent model (7 finders + adversarial verification,
8 confirmed / 5 refuted):

1. Roemer/Florence phantom wiring - roemer.agent.md claimed Florence's
   heartbeat "may summon me when a ward smells of drift" with nothing in
   florence.agent.md or HEARTBEAT.md implementing it. Fixed by adding an
   explicit "Kald Roemer" instruction to HEARTBEAT.md ward 6 (agent
   visibility, his actual domain), mirroring ward 8's existing "Kald
   Weber" pattern, and correcting roemer.agent.md's own claim to match.

2. m365.agent.md's "Florence's morning brief pattern" was a one-way
   orphaned reference - a full 4-step pattern with nothing in
   florence.agent.md implementing it. Added it to florence.agent.md as
   an explicit on-demand capability, separate from the timestamp-gated
   Round protocol.

3. An Ergasterion "PROCEED WITH CHANGES" ruling had no way to be checked
   against the eventual diff - al-review's checklists never referenced
   it. Added ERGASTERION_RULING to the [CURABIS-STATE] vocabulary,
   wired Ergasterion to write it, and added a BLOCKing checklist item to
   al-review's Titus checklist that verifies required changes were
   actually implemented.

4. curabis-task-state-check.yml was headered "Deterministic enforcement
   (not LLM diligence)" but only checks checkbox order, only blocks
   anything if a human separately enabled branch protection (never
   verified anywhere), and doesn't exist at all for the PTE track.
   Corrected the header's claims and added Roemer station 14 to verify
   branch protection is actually configured.

5. Mode C's only safeguard against a support user reaching
   Curabis/QualityHub was a single manual eyeball check with no re-check
   ever. Strengthened Step 2 to cover team-inherited and org-default
   access paths, added an append-only support-user registry, and added
   Roemer station 15 to periodically re-verify every registered user
   against it.

6. Columbo's persona was presented as genuine autobiography with no
   disclosure of its fictional TV origin (Levinson & Link, Peter Falk),
   unlike Smiley which discloses explicitly. Added a reader-facing
   editorial note - never something Columbo says aloud, since unlike
   Smiley he actually performs the persona to customers.
This commit is contained in:
Michael Dieringer 2026-08-03 14:12:05 +02:00
parent 44546d4fe0
commit 9e5273443f
11 changed files with 181 additions and 18 deletions

View file

@ -1,7 +1,7 @@
---
kind: action-skill
id: curabis-florence
version: 1
version: 2
title: Florence — The Heartbeat Agent
description: >
Scheduled vigilance agent. Walks the wards on a regular interval, notes what
@ -152,6 +152,29 @@ Record the round timestamp and summary classification
(ALL_ROUTINE / NOTABLE / CONCERNING / URGENT) in the heartbeat log.
Florence's rounds are traceable.
## On-demand — Morning brief (2026-08-03)
This is separate from the scheduled Round protocol above — it does not go
through the Step 0 timestamp gate, and it is not one of HEARTBEAT.md's
wards. It runs only when explicitly requested ("Florence, giv mig min
morgenbriefing" or similar), because it reads Michael's own calendar and
inbox via the M365 MCP connector, which is out of scope for the unattended
30-minute heartbeat round.
Follow `m365.agent.md`'s "Florence's morning brief pattern" exactly, in
order:
1. **Calendar** — today's events (`outlook_calendar_search`)
2. **Urgent email** — unread messages from the last 24 hours (`outlook_email_search`)
3. **BC tasks** — via BC MCP, not M365 (see `bc-mcp.agent.md`)
4. **Open PRs** — via GitHub API
Report only what deserves attention, same discipline as a Round report —
ten routine emails is not ten lines. This section exists because
`m365.agent.md` describes this pattern as something Florence runs and
cross-references this file for it; before 2026-08-03 nothing here actually
implemented it, so the cross-reference resolved to nothing.
## How to check Ward 7 — Workspace & multi-app configuration
This ward requires structural analysis of the repository: