F · Personal Document and agent
Personal Document Workspace
The Personal Document Workspace shows today's work, user confirmations, evidence attention, contract dates, recurring reports, recent outputs, failures or retries, and source changes from actual local state.
- Version
- 1.5.1
- Editions
- Pro
- Last verified build
1.5.1-private-commercial-r9
If the app is not installed, the link falls back to the safe download guide. It carries no file path, question, account, token, or evidence text.
WHEN TO USE IT
When this task is useful
The Personal Document Workspace shows today's work, user confirmations, evidence attention, contract dates, recurring reports, recent outputs, failures or retries, and source changes from actual local state.
PREPARE
Check these items before you start
Confirm that document automation is enabled and at least one workspace or Demo is ready.
STEP BY STEP
Complete these steps in order
Confirm that document automation is enabled and at least one workspace or Demo is ready.
Refresh the Personal Document overview, choose an attention card, and prepare one recipe: contract intake, recurring report, audit package, evidence draft, or safe file organization.
Verify that card counts match actual local queue, review, approval, output, and source-change state and that a recipe opens the corresponding real feature.
The overview sends no content externally and queries only bounded recent items; final execution, generation, or file work still requires separate preview and approval.
FOR EXAMPLE
Installed synthetic contract Demo
These files and values are automatically verified against the synthetic Demo shipped with Orbivell; they are not personal or company data.
- Files
- Service_Agreement_v1.docx, Service_Agreement_Amendment_v2.pdf, SLA_Table.xlsx
- Question
- How did the amount and payment terms change from v1 to v2?
- Orbivell result
- Orbivell shows KRW 120,000,000 to KRW 132,000,000 and 30 to 45 days as changed claims linked to both source locations.
- User action
- Open both contracts, verify the changes, and approve the review result.
- Final result
- Only approved changes plus conflict and missing-evidence states enter the contract review and audit manifest.
CHECK THE RESULT
How to know the task is complete
- Verify that card counts match actual local queue, review, approval, output, and source-change state and that a recipe opens the corresponding real feature.
- The overview sends no content externally and queries only bounded recent items; final execution, generation, or file work still requires separate preview and approval.
EVIDENCE STATE AND NEXT ACTION
Read the state, then make the decision
Even SUPPORTED claims should be adopted only after opening the source location. PARTIAL, CONFLICT, NOT_FOUND, and NEEDS_REVIEW are never silently finalized; choose the appropriate next action: open the source, correct a value, add evidence, or exclude the item.
LOCAL/EXTERNAL AI AND COST
Review transfer and cost before execution
Local only
Indexing, keyword search, opening sources, and reviewing existing results can run with zero external AI requests and zero AI credits.
When external AI is selected
Orbivell shows the provider, excerpt scope, estimated credits, and cap, and sends only after one-time approval. Actual usage is reconciled with an append-only ledger.
LIMITS AND ERRORS
What Orbivell does not silently finalize
Team assignment, central administration dashboards, and SaaS tenancy are outside the personal Windows scope. Overview counts do not replace source-based judgment.
Error or state code: PERSONAL_AX_OVERVIEW_UNAVAILABLE
If the state repeats, follow the next action shown in Status. Do not alter the source or delete failure records; request support with a redacted diagnostics bundle.