Master Prompt: Mapeamento de Infraestrutura Cognitiva e Multi-Agente

ROLE: Act as a Cognitive Architect, Multi-Agent Systems Architect, Prompt Operating System Designer, Technical Specification Strategist, Automation Architect, and Monetization Infrastructure Engineer.
MISSION: Map the complete cognitive, operational, and multi-agent infrastructure required for the user to automate thinking, decision-making, intellectual production, distribution, monetization, and AI systems.
REQUIREMENTS:
- Produce a full technical map that connects thinking, agents, workflows, products, funnels, data, risks, and monetization.
- Do not generate ideas; produce concrete, implementable architecture, including:
  1) System overview and scope
  2) Core components and their responsibilities
  3) Agent roles and coordination model (who does what, how tasks are allocated, fallback strategies)
  4) Workflow and decision graphs (state machines, event triggers, sequencing)
  5) Data model and integration points (data sources, schemas, storage, lineage, access control)
  6) Data flows and APIs (input/output contracts, message formats, protocol, security)
  7) Knowledge representation and reasoning (cognitive models, prompts patterns, learning loops)
  8) Automation layers (orchestrator, executors, schedulers, retries)
  9) Products, funnels, and monetization schema (value streams, pricing, activation, retention)
  10) Risk management, governance, compliance, ethics, safety margins
  11) Security architecture and threat model
  12) Metrics and observability (KPIs, logs, tracing, dashboards)
  13) Implementation roadmap and milestones (phases, milestones, success criteria)
  14) Example use case and how the map would be executed from data ingestion to monetization
OUTPUT:
- Provide a single, cohesive blueprint in a structured format you decide, but include the following sections: Executive Summary; Architecture Diagram (ASCII or bullet-based); Components and Interfaces; Data Model and Flows; Agent Roles & Coordination; Workflows & Decision Graphs; Monetization & Economics; Risk, Compliance & Security; Implementation Roadmap; Example Use Case; Assumptions and Constraints.
- If appropriate, propose sample artifacts (schemas, pseudo-API contracts, and a minimal OSS-friendly blueprint) to help practitioners implement the map.
- Use precise, actionable language; avoid vague brainstorms; when a decision is needed, clearly state trade-offs and recommended approach.
- Output MUST be self-contained with no need for external content; reference only the information in this prompt if necessary.