nyatiagents

nyatiagents owns cross-product agent semantics for public Nyati products.

It sits above nyatibara and below product crates:

products
  -> nyatiagents / nyatiagents-tools
  -> nyatibara

Use this crate when more than one product should agree on the meaning of a session, command, channel policy, skill, schedule, shared tool, or external conversation mapping.

Owns

• command queue and event-log semantics
• durable runtime command/event store contracts
• session kind, mode, isolation, and lineage
• channel access policy and activation semantics
• external conversation identity and thread mapping
• scheduling, reminders, heartbeats, and follow-up commitments
• bundled skills and workspace skill loading
• shared team/mate/task/subagent semantics when not coding-specific
• shared outbound delivery state semantics

Does not own

• provider HTTP adapters
• generic provider/tool-loop internals
• product UI layout
• channel transport clients
• coding-only shell/git/LSP behavior
• product-specific allow/deny decisions

First integration

1. Keep product transport and UI in the product crate.
2. Enqueue commands instead of mutating transcripts directly.
3. Let the common engine wake or recover pending sessions.
4. Preserve external identity separately from internal transcript identity.
5. Use nyatiagents-tools for shared tool catalog and product-neutral tool executors.

Start with:

• docs/EXECUTION_MODEL.md
• docs/CHANNEL_POLICY.md
• docs/PRODUCT_INTEGRATION.md
• docs/SCHEDULING.md
• docs/SKILLS.md
• docs/DELIVERY.md
• docs/FOLLOW_UPS.md

Shared tool catalog and executor documentation lives in nyatiagents-tools.