This capability helps an owner choose what to improve first for one main offer. It returns a seven-area profile, explicit unknowns, and exactly three ordered starting actions.
Scope & permission
Use answers the owner supplied. Do not fill unknowns with guesses. Assessment processing does not inspect a URL, make a payment, book, send a message, or confer authority to act. Private offer labels and contact details are excluded from the machine input schema. A WebMCP invocation replaces the working assessment and displays its result in that browser tab; it does not create an external commitment.
Contracts & versions
- Ruleset: de-readiness-1.0.0; API version 1.
- Capability metadata and current interface status
- Exact question bank, input schema and output schema
- REST: POST /api/v1/assessment with application/json. Answers belong in the request body, never a URL.
- MCP: /mcp; tool assess_decision_economy_readiness; protocol 2025-11-25; stateless Streamable HTTP, JSON response.
Browser, REST, and MCP apply the same fixed rules. Machine access is subject to the hosting audience and the named caller’s capabilities. Access does not imply universal AI support.
Interface status
| Interface | Status | Boundary |
|---|---|---|
| Human assessment | TESTING | Complete local browser execution; scope of validation is published with the build report. |
| REST API | TESTING | Requires a caller able to reach this hosting audience. |
| MCP | TESTING | Discovery and 22 fixture calls passed over HTTP in the internal validation environment. Production caller access still requires validation. |
| WebMCP | PLANNED | Discovered and invoked in the build’s Chrome validation environment: 22 fixture cases, with visible result parity. Supported production browser/agent availability is not established. |
| Decision Support Network | PLANNED | Existing registration contract, collector, approved schema, and assigned property_id are unconfigured. |
Errors & privacy
Invalid fields or codes, conflicting applicability, malformed JSON, unsupported rulesets, unsupported content types, and oversized requests return structured errors. The browser plan still works if a server interface is unavailable. No raw answers, labels, risk details, personal identifiers, or contact content are sent to operational telemetry.
Server requests are processed to return the result without application-level answer storage. Hosting infrastructure may retain operational request metadata under its own controls. No DSN events are transmitted while the existing contract is unconfigured.
Evidence limit
Based on your answers, this assessment suggests improvement priorities; it does not independently verify your business or predict AI recommendations, sales, or business quality. Read the methodology before interpreting results.