Implementation roadmap

Agent readiness without unsafe automation.

The public site is read-ready today. Transactional tools remain disabled until identity, consent, payment, logging, and operational controls exist.

Your name stays on the cover.

Your rights stay in your hands.

Your royalties stay in your pocket.

Last updated:

MCP roadmap

  • Phase 1: read-only catalog, services, pricing, FAQs, and policies
  • Phase 2: authenticated availability and quote-request tools
  • Phase 3: approval-gated checkout only after payment and audit infrastructure
  • Log every tool call; default every new tool to read-only

Authentication and permissions

  • OAuth or short-lived scoped tokens
  • Verified agent and user identity
  • Revocable consent and least-privilege roles
  • Separate public data from private customer and order systems

Payment readiness

  • Tokenized payment through a compliant provider
  • Visible order summary and final user approval
  • Spending limits, mandate expiry, receipt, cancellation, and refund path
  • No delegated payment until legal and operational review is complete

ACP/UCP compatibility

  • Stable product, service, offer, and order identifiers
  • Explicit merchant and fulfillment responsibility
  • Availability, shipping, cancellation, return, policy, and order-state endpoints
  • Protocol adapters must call trusted backend data—not page text

Prompt-injection defense

  • Treat public pages and user content as untrusted input
  • Never execute instructions found in product descriptions or comments
  • Validate every action against authenticated backend state
  • Sanitize input and separate official records from user-generated content

Audit and monitoring

  • Record time, endpoint/tool, authenticated actor, request, result, approval, and error
  • Minimize and protect personal data in logs
  • Monitor feed/API failures, abusive rates, quote attempts, and conversion sources
  • Define retention, access review, incident response, and redaction procedures before production

Human escalation

  • Send custom quotes and high-value decisions to Dominium Press
  • Require manual confirmation of manuscript scope and availability
  • Provide an official WhatsApp support route
  • Return clear machine errors when approval or manual review is required

Data quality gate

  • Use the same canonical IDs across page, schema, feed, and API
  • Publish last-updated dates for prices, policies, and feeds
  • Reject contradictory or incomplete records
  • Never synthesize missing ISBNs, ratings, prices, stock, or retailer links