Skip to content

feat(ai): a document-reading AI feature carries its reference to hermiq, and is refused before sending without one - #3629

Merged
rubenvdlinde merged 40 commits into
developmentfrom
build/dq-l6-6
Oct 12, 2026
Merged

rubenvdlinde merged 40 commits into
developmentfrom
build/dq-l6-6

Conversation

@rubenvdlinde

Copy link
Copy Markdown
Contributor

What

A case type's AI feature that reads a document now carries the document's reference to hermiq, and a request without one is refused before anything is sent (ai-features-on-the-case-consume-hermiq 3.1, REQ-AIC-03, design D-3).

  • src/services/caseAiFeatureGateway.js:
    • runFeatureOnDocument({feature, documentReference, instruction}) posts to hermiq's POST /api/ai-features/{slug}/run-on-document (hermiq#1148).
    • A missing or non-numeric reference throws an AiFeatureRefusal with gate missing-reference, and no request is made.
    • A 400/403/404/422 from hermiq comes back as a refusal carrying hermiq's gate and sentence. A transport failure is passed through as the failure it is.
  • refusalSentence() names the feature and the reason ("Samenvatting will not read a document that has not been redacted."). Four en/nl strings.

Why the browser and not dossiq's backend: hermiq reads the document in the signed-in person's Files. dossiq's backend talks to hermiq as the hermiq service account, so the document would be read with the service account's access instead of the handler's. The path first written in tasks.md (lib/Service/Ai/CaseAiFeatureGateway.php) is corrected in this PR.

Still open: 3.2, the panel on the case that calls this and renders the sentence (board DqZaakAssistent). Until then the gateway has no UI caller.

Stack

Stacked on #3625 (build/dq-l6-5), then #3607, then #3583. Needs hermiq#1148 on the instance before it can run live. origin/development is merged in.

Verified locally (targeted, decision 149)

  • tests/vitest/caseAiFeatureGateway.spec.js 5/5 (vitest, --maxWorkers=2).
  • eslint on both files: exit 0. check-l10n: exit 0.
  • hydra-gates --scope-to-diff against build/dq-l6-5: every gate passes except gate-23 (or-abstraction-anti-patterns: Tenant and state-machine classes this PR does not touch, so inherited) and the warning-only gate-68.
  • The full npm chain was not run: both build slots were saturated (slot rule). CI is the full check.

Twelve schemas declare a curated x-openregister-mcp block, so OpenRegister
derives 20 read tools (dossiq.case.search, dossiq.statusRecord.search, ...).
The hand-written DossiqToolProvider and its helpers are deleted, so nothing
shadows the derived tools. OpenRegister RBAC is the only gate.

Archives dossiq-mcp-adoption; live tasks 4.1-4.4 stay owed (decision 139).
A change outside properties/required/authorization only reaches an instance
when the schema version moves (SchemaVersionFloorTest). Digests regenerated.
…nd workload figures

First IMcpScannableServices opt-in (DossiqScannableServices, registered under
OpenRegister's per-app alias). Curated #[McpTool] reads: getDeadlineDashboard,
getDoorlooptijdMetrics, getKpiOverview, getWorkload (ReportingTools),
listAvailableTransitions (CaseTools) and listOverdueComplaints on
ComplaintService, a projection that never carries the complainant. Each tool
runs the gate its controller runs, then calls the owning service.
…creens.md for the touched specs and the archived change
# Conflicts:
#	lib/Settings/dossiq_register.json
#	lib/Settings/register.d/60-termijnbewaking.json
#	tests/schemas/schema-version-digests.json
# Conflicts:
#	lib/Settings/dossiq_register.json
#	lib/Settings/register.d/60-termijnbewaking.json
#	tests/schemas/schema-version-digests.json
…them without a grant

Every curated read (deadline dashboard, lead times, KPIs, workload, available
transitions, overdue complaints) now declares reach: 'user'. Without it a
two-segment id resolves to external and needs an explicit grant.
Needs openregister build/dep-dossiq-mcptool-reach on the instance first.
… and work its terms

Curated write tools, each on the service its controller calls:
transitionCase (StatusTransitionService, guards and status record intact),
reassignCase (new CaseAssignmentService::reassign, coordinators only, the
receiver is notified), completeTask (the engine's complete verb),
extendDeadline/pauseDeadline/resumeDeadline (new TermTools: the term is read
and its CASE must be changeable by the caller before the term services run).
Refusals come back as envelopes with the service's own rule and sentence.

WIP: AppointmentTools and BeschikkingTools are listed but not written yet.
…chikking

AppointmentTools (scheduleAppointment, cancelAppointment; external reach: the
resident is told) run AppointmentController's case checks and call
AppointmentService. BeschikkingTools offers draftBeschikking only, through
BeschikkingService::compose(); approving, signing and sending stay with the
caseworker. A test holds the tool classes off ObjectService.

hermiq-ai-tooling 3.1-3.3 ticked; the spec names the services as found.
# Conflicts:
#	lib/Settings/register.d/60-termijnbewaking.json
#	tests/schemas/schema-version-digests.json
# Conflicts:
#	.debt-baseline.json
#	appinfo/info.xml
#	lib/Settings/dossiq_register.json
#	lib/Settings/register.d/60-termijnbewaking.json
#	tests/schemas/schema-version-digests.json
# Conflicts:
#	lib/Settings/register.d/60-termijnbewaking.json
#	tests/schemas/schema-version-digests.json
…duleAppointment (phpmd finds nothing without it)
…s no approval floor

Decision 176 (Q-dossiq-L6-2): REQ-MCP-206 now says hermiq decides which AI
writes wait for a person. dossiq declares readOnlyHint: false and a scope on
every write so hermiq can gate it, and ships no grant or waiver. CHANGELOG
entry for the curated tools (task 4.3).
…siq.fileCase

dossiq.fileCase carries the citizenIntake mark with scope and action create,
which is how hermiq now recognises an intake tool (decision 177). It writes
through the create form's own path: one save on the case schema as the caller,
so the schema, the intake requirements, the duplicate policy and RBAC all run,
and a refusal is thrown so hermiq hands the resident to a person. No
intermediate intake object (decision 179). The six curated reads carry
outsideAgent for hermiq's outbound surface.

ai-features-on-the-case-consume-hermiq 5.1, 5.2; screens.md added.
caseType.aiFeatures (register fragment 43) maps hermiq's feature slug to
case, intake or none, and holds no provider, model or residency. Register
0.20.25, info.xml bumped, en/nl strings. Ticks ai-features 1.1, and 1.2/2.1
with the files that already carry them.
…spelled-out alias (gate 57 could not see AppointmentTools)
…y in CaseIntakeFiling (phpmd), REQ-MCP-206 anchor follows the rewritten heading (gate 46)
…its group is read on the case

A case type declares grouping as aiFeatures["report-similarity"]. hermiq's
evaluation adds the report to a group, so asking twice would count the same
resident twice: a created case is placed once, off the request, by
ReportGroupingJob as the background service account, and the group id is kept
on the case (case.reportGroupId, register fragment 44, register 0.20.26).
GET /api/report-group reads the group as it now stands, with the count and the
near-duplicates, and never places the case again. A group reduces no
confirmation of receipt: confirmationsOwed() counts the reports.

Ticks ai-features 2.2 (HermiqAiFeatureClientTest, absent hermiq over the real
client) and 4.2; 4.1 backend built, the render on the case is open. Records
the schema digests for fragments 43 and 44.
# Conflicts:
#	tests/schemas/schema-version-digests.json
…iq, and is refused before sending without one

src/services/caseAiFeatureGateway.js runs a case type's feature on a case
document through hermiq's run-on-document endpoint (hermiq#1148), in the
handler's own session, so hermiq reads the document as the handler. A request
without a usable file id is refused before any request; hermiq's refusal
comes back carrying its gate, and refusalSentence() names the feature and the
reason. Ticks ai-features 3.1.
@github-actions

Copy link
Copy Markdown
Contributor

Quality Report — ConductionNL/dossiq @ 98e3dc1

Check PHP Vue Security License Tests
lint ✅
phpcs ✅
phpmd ✅
psalm ✅
phpstan ✅
phpmetrics ✅
eslint ✅
stylelint ✅
build ✅
check-manifest ✅
check-vue3-compile ✅
test-l10n ✅
format ✅
check-schema-l10n ✅
check-l10n-js ✅
check-debt-ratchet ❌
check-types-e2e ✅
composer ✅ ✅ 109/109
npm ✅ ✅ 659/659
app:check-code ⏭️
info.xml ✅
REUSE ❌
lockfile sync ✅
PHPUnit ❌ 7051/7052 · 3 skipped
Newman ⏭️
Playwright ⏭️ deferred: E2E runs locally and on the promotion path only. This pull request targets development, so the suite is asked once per promotion into beta and main rather than once per push per open pull request. Run it locally with npx playwright test, or from the Actions tab on a branch with no open pull request into development.
Hydra gates ❌

Quality workflow — 2026-10-10 17:02 UTC

Download the full PDF report from the workflow artifacts.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant