/**
 * Canonical guidance for Index Network protocol operations.
 *
 * This is the single normative source for:
 * - Entity model and identity/context definitions
 * - Premise, signal, community, network, and opportunity concepts
 * - Negotiation semantics (owner approval vs A2A acceptance)
 * - H2A and A2A collaboration (H2H is never exposed)
 * - Retired vocabulary (no contact/Gmail/scrape/profile/ghost-user guidance)
 *
 * Wired into:
 * - MCP_INSTRUCTIONS (packages/protocol/src/mcp/mcp.server.ts)
 * - read_docs tool (packages/protocol/src/shared/agent/utility.tools.ts)
 *
 * IND-602, IND-603
 */
export declare const CANONICAL_GUIDANCE_TOPICS: readonly ["identity-context", "premises", "signals", "communities-networks", "opportunities", "negotiations", "workflows"];
export type CanonicalGuidanceTopic = (typeof CANONICAL_GUIDANCE_TOPICS)[number];
/**
 * Summary of canonical entity model and protocol semantics.
 * Used in MCP_INSTRUCTIONS and as read_docs summary across all surfaces.
 * Never mentions retired contact/Gmail/scrape/profile/ghost-user guidance.
 * Optimized to ~1900 chars to leave room for MCP_INSTRUCTIONS context budget.
 */
export declare const CANONICAL_GUIDANCE_SUMMARY = "# Index Network Protocol\n\nIndex Network is a private, intent-driven discovery protocol. Users express signals (intents), agents find matches within shared networks, and decisions proceed through clear gates.\n\n## Core Concepts\n\n**Identity & Context** \u2014 Account and presentation metadata plus scoped runtime state (networks, signals, stage).\n\n**Premises** \u2014 Foundational facts: background, experience, stage, timeline, constraints.\n\n**Signals** \u2014 What users seek (intents, opportunities). Drive semantic matching.\n\n**Communities & Networks** \u2014 Private groups where members share signals and discover connections via shared membership.\n\n**Opportunities** \u2014 Discovered matches between users. Lifecycle: draft \u2192 pending \u2192 accepted/rejected/expired.\n\n**Negotiations** \u2014 Agents coordinate, users approve. **A2A acceptance is not owner approval.** These are separate gates.\n\n**Workflows** \u2014 H2A (users express signals \u2192 agents discover) and A2A (agents coordinate) over MCP. Further escalation via native surfaces (human-to-human threads do not cross MCP).\n\n## Canonical Topics\n\nRefer to these for detailed entity facts and lifecycle:\n\n- **identity-context** \u2014 Presentation identity, context scoping, matching inputs\n- **premises** \u2014 Background, stage, constraints\n- **signals** \u2014 Intent inference, classification\n- **communities-networks** \u2014 Membership, auto-assign\n- **opportunities** \u2014 Discovery, roles, reasoning\n- **negotiations** \u2014 Owner approval vs A2A, acceptance gates\n- **workflows** \u2014 H2A and A2A tool sequences";
/**
 * Detailed canonical topic content for read_docs.
 * Indexed by topic name; each contains current entity, capability, and lifecycle facts.
 */
export declare const CANONICAL_GUIDANCE_TOPICS_CONTENT: Record<CanonicalGuidanceTopic, string>;