MCP Path

Semantic Priority Login vor CMP vor Repeat

Semantic Priority Login vor CMP vor Repeat is a public reference for knowledge signals, learning candidates, and explainable orientation. It names the signal, policy, or flow an agent should understand before choosing a concrete tool.

Catalog path

Reference page for a documented MCP capability path.

Type: MCP path
Family: Learning & Knowledge Evolution
Effect: sensitive
Status: Reference
Path: 11.15

Purpose

What this entry explains

What it does

This reference explains Semantic Priority Login vor CMP vor Repeat for knowledge signals, learning candidates, and explainable orientation. It is kept as a named reference so agents can cite the flow without inventing a tool name.

Use when

Use this entry when an agent needs to handle the sensitive path "Semantic Priority Login vor CMP vor Repeat" for knowledge signals, learning candidates, and explainable orientation.
Use it as a reference path when the catalog describes a capability but no single public tool name is explicit.
Use it before chaining follow-up tools so the next step is based on current evidence.

Reference Use

How agents should cite and apply this area

Examples are maintained at family level and use only public tool names or reference paths already present in the catalog.

Signal, gate, behavior, boundary

Semantic Priority Login vor CMP vor Repeat describes a gate for knowledge signals, learning candidates, and explainable orientation. The path shows which signal, gate, behavior, or boundary must be checked before choosing a concrete tool.

When agents cite it

An agent cites this path when it needs Semantic Priority Login vor CMP vor Repeat as context for a decision, block, target check, or follow-up tool choice.

Why no callable name

The public source does not name one callable tool for this path. The documentation therefore keeps it as a reference path and does not invent a callable name.

Signals and rule

Relevant response signals: login_wall, consent_cmp, risky_repeat. Safety axes: Page interaction, Sensitive, User confirmation. The reference path alone is not permission to execute. Before acting, check current MCP discovery, visible target, scope, and the actual response.

Family example

A task touches data, identity, or permissions in knowledge signals, learning candidates, and explainable orientation that may be used only with clear purpose.

The agent starts with nova.learn_suggest, reads the current response or reference, and only then chooses the concrete next tool.

nova.learn_suggest nova.learn_generate nova.learn_promote

Sensitive values stay in current scope; they are not guessed, logged, or copied into other contexts.

Contract

Inputs and important response fields

This page is a public reference. Agents and integrators should still read current MCP tool discovery before execution, because schemas can be gated by settings or version.

Inputs

No stable public input field is derived from the catalog source for this path. Read current MCP discovery before execution.

Response field	Explanation
`login_wall`	Response field named by the catalog source. Treat it as current evidence for the next decision.
`consent_cmp`	Response field named by the catalog source. Treat it as current evidence for the next decision.
`risky_repeat`	Response field named by the catalog source. Treat it as current evidence for the next decision.

Safety

Boundary before execution

Effect

May touch sensitive data, permissions, credentials, identity, or external connection paths. Use only with explicit scope and visible user control.

Agent rule

Treat stored knowledge as guidance only. Before any action, confirm the current page, target, scope, and visible evidence again.

Human control

For humans, this entry marks the sensitive surface in knowledge signals, learning candidates, and explainable orientation and keeps permission, credential, or external-connection handling explicit.

High-Impact Review

Execution boundary and recheck hints

Review category: Auto-apply/mutating flows

Execution boundary

Mutating steps may run only with confirmed target, expected effect, user control, and result check.

Typical false assumption

False assumption: a guard or auto-apply signal replaces current target and result checks.

Visible user control

The user must be able to review action, target, approval, block signal, and visible result.

Agent rule

Execute only the intended step, then verify state and stop on warning, block, or target change.

Abort or recheck

Recheck if candidate budget, gate, visible state, or expected effect do not line up.

Safety Axes

How this path can affect work

Axes are stable catalog signals for humans, agents, and LLM discovery. One path can carry several axes.

Page interaction page_interaction

Clicks, types, selects, uploads, or interacts with visible page elements.

Execute only with a visible target, expected effect, and a follow-up result check.

Sensitive sensitive_data

Touches cookies, storage, clipboard, credentials, tokens, user content, identity, or private data.

Use only with bounded purpose and visible user control; do not guess, log, or forward sensitive values.

User confirmation user_confirmation

Requires visible confirmation, target review, approval, or deliberate user control.

Do not proceed until the required confirmation is visible or unambiguous in the current context.