Reports
3
local artifacts
Reports · mock/local artifacts only
Saved briefs with proof
Local report artifacts assembled from Company Brain, Research Worker, Watchdog Worker, and Source Health outputs. No exports, emails, sharing, live Onyx, Supabase persistence, customer data, or external actions are used.
Mode
mock_local
served from mock_local_reports
External actions
false
no send/export/share
Proof logs
3
linked local evidence
Company Brain brief
Company Brain demo proof brief
A saved local/mock brief showing what the first Innexios demo proves: cited answers, visible source gaps, and proof logs before live services or automation.
Proof: proof_demo_answerNo external actions
Answer with proof
Innexios should prove trust before autonomy: visible source health, cited company answers, an evidence drawer, and a proof log showing how a research/watchdog worker would justify its output. This is demo/local data only until Onyx is connected through the server-side boundary.
Limitations stay visible
No live Onyx API call has been made in this slice. Private/restricted sources are shown as gaps instead of silently treated as searched. RAGFlow remains delayed until a document-heavy use case proves it is needed. This response was served through the local mock Onyx adapter, not a live Onyx service.
Research brief
Local cited brief: prove trustworthy workers before autonomy
Research Worker used approved local/demo sources to produce a cited brief. It did not browse the web, call Onyx, sync connectors, use customer data, schedule work, or take external actions.
Proof: proof_mock_research_worker_competitor_briefNo external actions
Trust before autonomy remains the product wedge
The next worker slice should keep proving cited, reviewable output before adding real scheduling or external actions. The healthy Company Docs source can support product-positioning claims, while stale or planned sources must stay visible as limitations.
Research briefs need freshness labels before live use
The Competitor Watchlist is intentionally stale in local data, so the Research Worker can demonstrate honest freshness warnings without pretending it performed live web research.
Watchdog report
Local watch report: source-health risks before automation
Watchdog Worker reviewed local/demo Source Health state and flagged stale, planned, and permission-limited sources. It did not schedule monitoring, call live services, sync connectors, browse the web, or take external actions.
Proof: proof_mock_watchdog_source_health_monitorNo external actions
WARNING: Stale source: Competitor Watchlist
Needs scheduled refresh before this can be trusted for live market monitoring.
WARNING: Planned source: Support Knowledge
Connector is intentionally not live in this demo slice.
Featured saved artifact
Company Brain demo proof brief
A saved local/mock brief showing what the first Innexios demo proves: cited answers, visible source gaps, and proof logs before live services or automation.
Answer with proof
Innexios should prove trust before autonomy: visible source health, cited company answers, an evidence drawer, and a proof log showing how a research/watchdog worker would justify its output. This is demo/local data only until Onyx is connected through the server-side boundary.
Sources: source_docs, source_competitors, source_support, source_permissions
Limitations stay visible
No live Onyx API call has been made in this slice. Private/restricted sources are shown as gaps instead of silently treated as searched. RAGFlow remains delayed until a document-heavy use case proves it is needed. This response was served through the local mock Onyx adapter, not a live Onyx service.
Sources: source_docs, source_competitors, source_support, source_permissions
Source Health snapshot
1/4 demo sources are healthy; 3 need attention before live answers or workers should trust them.
Sources: source_docs, source_competitors, source_support, source_permissions
Reports are generated on request from local/mock state. There is no database persistence, export/download, email/share/send action, live Onyx call, Supabase write, customer data, scheduling, web research, or connector sync.