MCP Path
Bootstrap-Clear-Regeln
Bootstrap-Clear-Regeln is a public reference for edge cases, product boundaries, and robust failure paths. It names the signal, policy, or flow an agent should understand before choosing a concrete tool.
Reference page for a documented MCP capability path.
- Type
- MCP path
- Family
- Onboarding & Self-Service
- Effect
- changes state
- Status
- Reference
- Path
- 27.4
Purpose
What this entry explains
What it does
This reference explains Bootstrap-Clear-Regeln for edge cases, product boundaries, and robust failure paths. 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 carry out the bounded step "Bootstrap-Clear-Regeln" for edge cases, product boundaries, and robust failure paths.
- 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.
Bootstrap-Clear-Regeln describes a signal for edge cases, product boundaries, and robust failure paths. The path shows which signal, gate, behavior, or boundary must be checked before choosing a concrete tool.
An agent cites this path when it needs Bootstrap-Clear-Regeln as context for a decision, block, target check, or follow-up tool choice.
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.
Relevant response signals: browser_automation, system_tools. Safety axes: Read current state. The reference path alone is not permission to execute. Before acting, check current MCP discovery, visible target, scope, and the actual response.
Family example
An agent needs to change visible state in edge cases, product boundaries, and robust failure paths without guessing target or result from an earlier session.
The agent starts with nova.get_onboarding, reads the current response or reference, and only then chooses the concrete next tool.
Change only the confirmed target, then check visible state and stop on mismatch.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 |
|---|---|
browser_automation | Response field named by the catalog source. Treat it as current evidence for the next decision. |
system_tools | Response field named by the catalog source. Treat it as current evidence for the next decision. |
Safety
Boundary before execution
Can change browser, page, or workflow state. The target and expected result must be clear before execution.
Confirm the current target first, perform only the intended bounded action, and verify the resulting page or workflow state afterwards.
For humans, this entry names the browser or workflow state in edge cases, product boundaries, and robust failure paths that may change, so the action can be reviewed before and after execution.
High-Impact Review
Execution boundary and recheck hints
Review category: Auto-apply/mutating flows
Mutating steps may run only with confirmed target, expected effect, user control, and result check.
False assumption: a guard or auto-apply signal replaces current target and result checks.
The user must be able to review action, target, approval, block signal, and visible result.
Execute only the intended step, then verify state and stop on warning, block, or target change.
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.
read_current_state
Reads current state, response signals, or evidence without treating that alone as permission for a follow-up action.
Use the signal as current evidence and re-check target, scope, and visible state before any follow-up action.