Yasnora AIRU
Developers
Developers · 2026.10

Architecture and boundaries

Identity, workspace, integration and processing boundaries.

2 min read
Reviewed 2026-10-25
Bilingual article
01

Identity boundary

Yasnora ID identifies you across Yasnora products and authorized Wicsora services. Your session and workspace membership determine which data you may access.

Never share passwords, verification codes, recovery links or API keys. Deletion and retention follow the account policy; signing out is not deletion.

02

Workspace boundary

A Group brings together team members, instructions, Knowledge, agents and tools. A personal workspace and a team Group have different scopes.

WICSAI_GROUP_FORBIDDEN means membership, role or resource binding needs attention. Being signed in does not grant access to every Group.

03

Integration boundary

Authorized integrations use versioned Yasnora APIs and SDKs. Pass identity and policy context and request logical capabilities rather than hard-coding a physical provider.

For streaming, distinguish partial data from the final result and handle finish, cancel, errors and usage. Do not treat a dropped stream as successful completion or retry a write blindly.

04

Processing and data boundary

Workspace roles, processing modes and policy govern access and data handling. Generated output must be reviewed before it is trusted or used to change external systems.

Private/Local keeps work within the configured private boundary; Hybrid and External require permitted external processing. Export, retention and deletion follow workspace policy and applicable requirements.

Maintained by architecture · Edited 2026-10-25 · Documentation 2026.10