Tool Boundaries & Integrations

Niyatna can connect to company tools, but integrations should never become hidden authority.

Every tool path should be scoped by the active intent, role boundary, action class, and proof requirement.

Integration types

• Workspace access: Read or write only the approved files, records, or folders needed for the request.
• Company systems: Connect to approved business tools under role and workflow boundaries.
• Communication channels: Send status, review requests, and report-backs to the right channel.
• Scheduling systems: Create reminders, follow-ups, or recurring work within allowed scopes.
• Evidence capture: Store screenshots, source notes, reports, task records, or receipts as proof.

Tool event schema

Every tool action should return a structured event:

{
  "intent_id": "niyatna-intent-0248",
  "tool_surface": "workspace",
  "action": "prepare_report",
  "status": "staged",
  "evidence": "proof://intent-0248/report",
  "requires_review": true
}

Integration rule

If a tool cannot explain what it touched, why it touched it, and what proof it produced, it should not be part of a Niyatna workflow.