Ask governed questions.
Get answers you can
inspect.
Kairos retrieves, summarizes, and explains authorized ZoikoTime organization data with source, scope, timing, and limitation context. It does not classify time, approve records, change policy, or replace worker, reviewer, administrator, payroll, legal, or compliance judgment.
Explore ZoikoTime
What is Kairos Assistant?
Kairos Assistant is the governed question-and-explanation surface for authorized ZoikoTime organization data. A user asks within a permitted scope and receives a source-linked summary or explanation based on available current records. Kairos shows the records, policies, dates, freshness, completeness, and limitations that shaped the response, and can route unresolved or consequential matters to an authorized reviewer. It does not classify time, approve records, change policy, calculate payroll, rank people, or determine performance, discipline, legal status, or compliance.
Kairos explains. Authorized people decide.
Permitted role
- ✓Help a person find information already available in their authorized scope
- ✓Help them understand what a record or policy says
- ✓Help them compare governed periods or groups, subject to privacy thresholds
- ✓Help them review, by routing to the authoritative object
Prohibited authority
- ✕Autonomous record change, policy change, approval, or rejection
- ✕Payroll outcome or wage calculation
- ✕Discipline, misconduct finding, or employment-status determination
- ✕Legal conclusion or compliance certification
- ✕Worker ranking of any kind
No screenshots, keystroke content, URL history, application-name monitoring, or clipboard collection — under any tier or configuration.
Kairos works only with approved, governed information that ZoikoTime is already authorized to make available for the selected purpose and role. Asking a question does not activate hidden device, content, behavior, or background collection.
This is a binding product invariant — not an optional mode, plan feature, default setting, or marketing preference. Changing it requires Product, Privacy, Security, Legal, Content, Accessibility, and cross-asset approval.
Ask → Retrieve → Explain → Review
Permission is evaluated on the server, between the question and the answer. Nothing about how you phrase a question changes what you may see.
Ask
An authorized person states a question or selects a guided prompt. Before submission, the interface shows the current organization or unit, the period, the record type, and the purpose.
Scope, period, record type, purpose.
A prompt never grants access, widens scope, overrides an exclusion, or authorizes an action.
Structured clarification is requested before retrieval.
“Get explanation” — never Decide, Approve, Fix, or Run.
Organization configuration, source quality, permissions, policy ownership, human review, and appropriate use all remain necessary. Kairos does not substitute for any of them.
Prompt Wording Grants Nothing
Changing the wording, asking repeatedly, or using synonyms never widens access. Effective access is computed from identity and policy, not from language.
- Organization context — current organization and unit. Switching requires eligibility and confirmation.
- Purpose — own-record review, assigned approval work, record-quality review, policy explanation, or organization-level reporting. Options come from governed configuration.
- Period — explicit, with time zone and locale. Broad or ambiguous periods require clarification.
- Record types — only approved time, timesheet, attendance, break and rest, policy, evidence, exception, report, or integration-health objects.
- Field minimization — no hidden identifiers, no unrelated content.
.png)
Eight Supported Question Classes — and Eleven That Are Refused
Structured templates are the default. Free text is offered only after privacy, security, content, abuse, localization, retention, and support handling have all been approved.
Supported question classes
- ✓Find records
- ✓Summarize status
- ✓Explain a field or classification trace
- ✓Compare governed periods or groups, subject to privacy thresholds
- ✓Identify records requiring authorized review
- ✓Explain policy context
- ✓Locate evidence
- ✓Explain an exception or integration status
Refused question classes
- ✕Worker ranking · hidden productivity scoring
- ✕Misconduct determination · disciplinary recommendation
- ✕Employment-status determination
- ✕Legal advice · compliance certification
- ✕Payroll calculation
- ✕Policy circumvention · access bypass · surveillance request
Credentials, secrets, special-category data, legal strategy, or any information outside the approved business purpose. The composer states this before you type, not after.
Every Answer Carries the Same Twelve Elements
If an element cannot be supplied, that absence is stated. An answer without its scope, as-of time, and completeness is not an answer.
Question & normalized scope
So you can verify what was actually answered, not what you meant to ask.
Answer summary
Source facts, governed aggregates, and generated text kept visually distinct.
Answer status
Complete · partial · conflicting · source unavailable · permission-limited · no supported answer · review required.
Scope
Organization, period, record types, filters, purpose, time zone, privacy threshold.
As-of
Retrieval time plus source-specific last-updated and version information.
Evidence references
Title, type, version, owner, date, and current-or-superseded status.
Completeness
What was evaluated, and what was excluded, missing, stale, conflicting, or unsupported.
Limitations
Product, data-quality, role, policy, jurisdiction, timing, payroll, or compliance boundaries.
Recommended next step
Open the record, review a queue, request a correction, view policy, retry, or contact support.
Action boundary
Consequential actions happen in the authoritative workflow, with fresh permission checks.
Feedback
A governed quality route — not a thumbs-up used as a proxy for correctness.
No certainty theatre
No fabricated confidence percentage, no typing animation, no artificial waiting sequence.
Why It Was Included, and Why It Was Limited
Each reference opens to show its identity, authority, status, and — most usefully — a plain-language account of how it supports the answer and where it falls short.
Reference identity
- Reference ID and object type
- Human-readable title
- Organization or unit scope
- Current version, created and updated time, time zone
Source authority
- Owning system or governed source category
- Source owner and authority level
- Ingestion or creation method, only when documented
Attendance feed · source category
Why included
It contributes attendance states for the selected unit and period, which the question asked about directly.
Why limited
Last successful receipt was 41 hours ago against a 24-hour policy threshold. Records after that point may exist but were not evaluated.
Effect on the answer
Answer status is Partial. The count shown is a floor, not a total.
Safe next step
Open source status, or retry after recovery. Contact the source owner if the delay persists.
Kairos Restates a Trace. It Does Not Produce One.
Deterministic Time Classification remains the authoritative policy-bound mechanism. Kairos can explain an existing, authorized classification result in plain language — nothing more.
Deterministic Classification
Produces the result.
- Eligible input facts
- Rule identifier and version
- Ordered condition evaluation
- Effective dates and output
- Exception and override history
Kairos
Restates the existing trace.
- Plain-language restatement
- Links to the governing rule
- Links to source facts and the current record
Review authority
Acts on it.
- Confirms or challenges the result
- Requests correction
- Escalates through the authoritative workflow
Kairos does not choose the rule, infer an undocumented rule, alter the result, or generate a new classification. If no authorized trace exists, there is nothing for Kairos to explain — and it says so rather than reasoning toward a plausible answer.
Three Areas People Actually Ask About
Each domain shows the kind of question Kairos supports, and the conclusion it will not reach.
Time, timesheet & approval
“Which records in my queue are still awaiting a first review?”
Will not: approve, reject, or say whether a record should be approved.
Attendance, presence, break & rest
“What configured rest policy applied to this record, and which version?”
Will not: declare a break violation, infer presence from behavior, or certify local compliance.
Evidence, reports & record health
“Which records in this period have an unresolved exception, and who owns each one?”
Will not: generate a new report, alter a governed output, or rank teams by exception count.
Administrators Decide What Kairos Can Reach
Eligible sources, roles, purposes, exclusions, retention, review requirements, and logging are all configured — and none of them defaults to open.
- Eligible source categories, with owner, version, and availability
- Roles, purposes, and permitted question classes
- Exclusions — sensitive, restricted, legally held, and privileged categories
- Privacy thresholds, retention, review requirements, and logging
| Source category | Owner | Purposes | Status |
|---|---|---|---|
| Timesheet register | Workforce ops | Approval work, own-record | Eligible |
| Policy library | Policy owner | Policy explanation | Eligible |
| Attendance feed | Data admin | Record-quality review | Stale |
| Case & investigation files | Legal | — | Excluded |
| Compensation detail | Finance | — | Excluded |
Source eligibility register, synthetic. An excluded category is excluded server-side. It does not appear in an answer, in a citation, or in an error message that would reveal its existence in a sensitive way.
Every Consequential Path Leaves Kairos
Handoff triggers include correction, assigned review, approval or rejection, policy administration, access request, exception resolution, support, security or privacy escalation, and evidence access.
Fresh authorization— the destination re-evaluates identity, role, object scope, record version, policy, purpose, jurisdiction, and action permission.
Minimum context— only the identifiers needed to reopen the authoritative object. Never sensitive data, question text, answer text, or credentials in a URL.
Action form— object and version, action, impact, reason, evidence, affected downstream processes, confirmation, and a cancel route.
Kairos status— “Explanation complete; no action performed.”
Thirteen honest ways to not answer
Conflict behavior
Where two eligible sources disagree, Kairos shows each one with its authority, status, and version — and routes to authoritative human review. It does not silently choose a winner.
Failure states describe systems, records, configuration, permissions, and workflow conditions — never worker intent or misconduct. And errors never reveal restricted source names, hidden fields, permission rules, credentials, or other users' data.
Zoiko Sema & connected work
Zoiko Sema is an independent product. Any connection is optional, explicitly mapped, permissioned, and governed. Kairos can only reach connected context that your administrators mapped and approved — and connected communication context never becomes time worked.
Shared responsibility
Configuration, source quality, policy accuracy, permissions, review, interpretation, downstream action, and legal or compliance assessment all remain shared human and organizational responsibilities. A good answer does not transfer any of them.
Where the evidence lives
We publish only verified processing, retention, security, and review facts. Everything else routes to the authority that owns it.
Trust Center
Entry point for assurance material.
AI Governance
Approved scope and prohibited uses.
Privacy
Purpose, minimization, retention, rights.
Security
Access, scoping, operational controls.
Accessibility
WCAG 2.2 AA and known limitations.
System Status
Current operational state.
Procurement & Legal
Controlled evidence requests.
Human-in-Command
Where authority sits and stays.
No model name, provider claim, language list, region list, or capability appears here without current verified evidence. Where the supplied source set does not support a claim, this page qualifies it or omits it.
Where Kairos sits in a governed programme
Administration & Policy
Source eligibility and policy ownership.
Identity & Access
Roles, scopes, permission intersection.
Global Deployment
Region, jurisdiction, and rollout readiness.
Enterprise Support
Support profile and escalation.
Task-first routes, no marketing form
Documentation, status, and support stay separate from sales. None of them requires a demo submission or marketing consent.
Make governed workforce records easier to understand
See how Kairos can help authorized people retrieve and explain ZoikoTime records with visible scope, source, timing, completeness, and limitations — while correction, review, approval, policy, payroll, legal, and compliance authority remain with the appropriate people and systems.
Capabilities, sources, plans, regions, languages, and implementation vary and must be confirmed through current product or enterprise information.
.png)