Private workspaces
Every request is checked against the signed-in person, workspace, project, and role. A person cannot choose another workspace simply by changing a web address.
Security and owner control
Private by design.
Truthful by default.
P311 is built to help without quietly taking control away from the owner.
Approval before sensitive action
Destructive and outward actions use the existing approval path. P311 reports a saved draft or pending approval as exactly that—not as completed work.
Secure connections
Passwords, provider secrets, and Microsoft consent do not belong in chat. Required permission opens in a secure browser screen and returns only after the server checks it.
Audit and isolation
Important changes create server-side records. Personal settings are scoped to the signed-in person, while project access follows workspace membership.
Safe uncertainty
If wording is unclear, contradictory, delayed, quoted as an example, or limits data access, P311 asks instead of making a change.
No certification theatre
This controlled beta does not claim a security certification or outside audit that has not happened. Those claims wait for real evidence.
Beta release rule
New code is checked in TEST before production. The live version and one tested rollback version are kept for 14 days; cleanup needs separate owner approval.