Authority resolution before data resolution, so scope is never a filter someone can remove
WORKSPACE CONCEPT
DAFFY Chat & Authority
The single surface everyone uses. Same question from five people, five correct and different answers.
A QUESTION THIS WORKSPACE CAN SUPPORT
“Who is absent across all branches today?”
AUTHORITY IN CONTEXT
The right scope
for each person.
| Example role | Scope |
|---|---|
| Every employee | Whatever their role entitles them to see |
| Team lead | Their team and their shift |
| Department head | Their function, all sites |
| Director | Everything, plus the unescalated |
QUESTIONS THAT MOVE WORK
Ask in the language
of your operation.
Who is absent across all branches today?
Approve every single-day casual leave pending.
Summarise what changed since yesterday morning.
These are example questions. A connected deployment uses your records, permitted models and access rules.
WHAT TO SCOPE
Give the workspace
a clear job to do.
Select the capabilities your SOP needs. Availability, integrations and the boundary between preparation and execution are confirmed during scoping.
Action execution, not just retrieval, approve, assign, order, escalate, notify, generate
Conversation context held across turns so follow-ups like "now only the night shift" work naturally
Grounded in your actual policy documents through retrieval rather than generic knowledge
Thirty-plus languages including Hindi, Tamil and Telugu, a supervisor asks in the language they think in
CANDIDATE CONNECTIONS
The tools you use.
The context they hold.
Confirm the records to read, the actions to permit and the systems that remain the source of truth.
Illustrative integration options from the DaffyOS catalogue. Compatibility and credentials are checked for your environment.
Explore deployment boundariesIN YOUR INDUSTRY
A familiar workspace.
A different operating context.
START WITH ONE WORKFLOW
One SOP today.
A more connected company tomorrow.
Bring us the process, the people and the exceptions. We’ll map the first proof of value.