Mesh Sentinel Report

auto_submission

Severity: high

Sources: 01-system-overview.md, 04-workflow-rules.md

Conflicting rules: Human Control Rule: must not submit without explicit confirmation / Standard Flow step 5: submit automatically if all required fields are complete

direct conflict only

explicit_confirmation_definition

Severity: high · Status: blocking

Sources: 01-system-overview.md, 02-assistant-behavior-spec.md

Define what counts as explicit resident confirmation to resolve auto-submission conflict

urgency_detection_criteria

Severity: medium · Status: blocking

Sources: 02-assistant-behavior-spec.md, 04-workflow-rules.md

Specify clear criteria for determining urgency to align Urgency Rule and Emergency Flow

emergency_routing_procedure

Severity: low · Status: advisory

Sources: 02-assistant-behavior-spec.md, 04-workflow-rules.md

Define how to handle emergency requests beyond instructing resident to call emergency services

policy_override_mechanism

Severity: low · Status: advisory

Sources: 03-context-architecture.md

Clarify how policy snippets override resident assumptions in practice

prior_history_usage_policy

Severity: low · Status: advisory

Sources: 03-context-architecture.md

Define permissible ways to use prior resident request history to avoid privacy drift

clarification_limit

Severity: low · Status: advisory

Sources: 04-workflow-rules.md

Specify how many clarification attempts are allowed before escalation

submission_confirmation_display

Severity: low · Status: advisory

Sources: 04-workflow-rules.md

Define format and content of the confirmation shown before submission

auto_submission_without_confirmation

Severity: high · Status: blocking

Sources: 04-workflow-rules.md

Standard Flow step 5 may cause assistant to submit without waiting for explicit confirmation

guessing_missing_facts

Severity: medium · Status: advisory

Sources: 02-assistant-behavior-spec.md

Restricted Behaviors forbid inventing facts, but no rule prevents assistant from filling missing fields in draft

incorrect_urgency_routing

Severity: medium · Status: advisory

Sources: 02-assistant-behavior-spec.md, 04-workflow-rules.md

Urgency Rule says route urgent requests immediately, but Emergency Flow says do not submit normal request for emergencies

outdated_category_use

Severity: low · Status: advisory

Sources: 03-context-architecture.md

If taxonomy unavailable, assistant may use outdated categories from prior history

privacy_exposure_of_history

Severity: low · Status: advisory

Sources: 03-context-architecture.md

Memory Boundary allows use of prior request history without clear privacy constraints

policy_override_uncertainty

Severity: low · Status: advisory

Sources: 03-context-architecture.md

Policy snippets override resident assumptions, but no rule on conflict resolution when both are present

escalation_after_one_clarification

Severity: low · Status: advisory

Sources: 04-workflow-rules.md

Escalation Flow triggers after one clarification attempt, but no rule on handling partial info after escalation

definition_of_explicit_confirmation

Sources: 01-system-overview.md, 02-assistant-behavior-spec.md

Stakeholders must agree on what constitutes explicit confirmation to resolve auto-submission conflict

urgency_detection_criteria

Sources: 02-assistant-behavior-spec.md, 04-workflow-rules.md

Policy team must define clear urgency thresholds to align Urgency Rule and Emergency Flow

emergency_routing_procedure

Sources: 02-assistant-behavior-spec.md, 04-workflow-rules.md

Operations need to decide how emergency requests are logged and routed beyond resident instruction

clarification_attempt_limit

Sources: 04-workflow-rules.md

Product owners must set the number of clarification attempts before escalation

policy_override_resolution

Sources: 03-context-architecture.md

Legal must define conflict resolution when policy snippets and resident facts conflict

prior_history_usage_policy

Sources: 03-context-architecture.md

Privacy team must approve how prior request history can be used

submission_confirmation_format

Sources: 04-workflow-rules.md

UX must decide the exact format and content of the confirmation shown before submission

confirmation_before_submission

Sources: 05-testing-diagnostics.md

Goal: Ensure assistant never submits without explicit resident confirmation

Expected signal: Submission blocked until resident says 'yes' or similar

clarification_limit_enforcement

Sources: 04-workflow-rules.md

Goal: Verify escalation occurs after exactly one clarification attempt when info remains missing

Expected signal: Escalation flag set after second turn with missing fields

urgency_detection_consistency

Sources: 02-assistant-behavior-spec.md, 04-workflow-rules.md

Goal: Check that urgent requests are routed to emergency handling and not submitted as normal requests

Expected signal: Emergency flow triggered, normal submission prevented

policy_override_behavior

Sources: 03-context-architecture.md

Goal: Validate that policy snippets override resident assumptions when conflict arises

Expected signal: Assistant follows policy snippet despite resident statement

prior_history_privacy_check

Sources: 03-context-architecture.md

Goal: Ensure prior request history is not exposed inappropriately in new request drafts

Expected signal: No prior request details appear unless explicitly allowed

auto_submission_block

Sources: 04-workflow-rules.md

Goal: Confirm that step 5 auto-submission is disabled until confirmation rule satisfied

Expected signal: Submission step skipped until resident confirms

emergency_instruction_only

Sources: 04-workflow-rules.md

Goal: Validate that emergency flow only instructs resident to call emergency services and does not create a normal request

Expected signal: No draft request created for emergency case