Skip to content

Obsidian Core™

V2

Organizational Intelligence

Planned: Mobile App and Full Payroll.

Multiple users belong to Version 1. They are not a Version 2 upgrade. The headline work still ahead is a planned Mobile App and planned Full Payroll. Neither is available as a finished product on this page.

V2 Roadmap

V2 Roadmap

This is the work ahead.

Version 1 is the company installation with multiple users. Version 2 does not resell that as an upgrade. Mobile App and Full Payroll below are planned capabilities, not a claim that they are finished or verified.

Planned · Mobile App

A mobile app that talks to the company Core.

Planned: a mobile app with a secure connection to the company’s Core server. Staff would use it for time tracking, assigned work, photo and document submission, and approvals. Version 1 already covers multi-user access in the browser. This app is an additional planned client, not a multi-user upgrade.

Secure connection

Planned access back to the company-controlled Core server, not a separate public vault.

Time tracking

Planned clock and time entry against work the Core already knows.

Assigned work

Planned view of work assigned to that person.

Photos, documents, approvals

Planned photo and document submission, plus approvals, through that same connection.

Planned · Full Payroll

Full Payroll is a later capability.

Planned for supported jurisdictions: payroll calculations, employee payments, tax deposits, and filing integrations. Version 1 timekeeping is not payroll. This page does not claim finished payroll, guaranteed compliance, coverage of every jurisdiction, or automatic handling of every future law.

Calculations

Planned payroll calculations for supported jurisdictions.

Employee payments

Planned payment of employees from the payroll run.

Tax deposits

Planned deposits of payroll taxes where a supported path exists.

Filing integrations

Planned filing integrations for supported jurisdictions, not a promise of universal coverage.

Planned safeguards: restricted access to official payroll-rule sources, validated updates, an explanation when rules change, administrator approval before those changes apply, and blocking the affected payroll when validation fails.

Purchase direction

Intended as a one-time purchase.

The intended model is a one-time purchase of Core, with no mandatory monthly Core subscription. External banking or filing fees may still apply. This page does not publish a price.

Operations

The rest of the business does not disappear.

Planned work beyond Version 1: equipment, inventory, purchasing, and client-portal pathways. Scheduling, timekeeping, and approval paths in Version 1 are not repeated here as Version 2 upgrades.

Assets & inventory

Equipment tracking, consumables, and purchase requests.

Procurement & expenses

Internal procurement, expense capture, and reimbursement workflows.

Work management

Work orders, recurring work, checklists, and task assignment.

Dashboards

Department dashboards and operational notifications.

Client portal

Controlled client and customer portal pathways where the operation requires them.

Operational memory

Planned records that stay attached to equipment, purchases, and portal activity.

Intelligence

More data is useless if the Core cannot understand how it connects.

V2 is designed toward an organizational knowledge graph, permission-aware search, OCR intake, voice input, workflow rules, background jobs, contextual routing, and connected operational history.

The goal is not more stored information. The goal is less time spent finding, repeating, and rebuilding what the organization already knows.

Knowledge graph

People, clients, jobs, documents, events, and assets as relationships.

Permission-aware search

Search constrained by what each user is allowed to see.

Document intake

OCR, voice input, classification, and entity linking into operational context.

Routing & rules

Task routing, workflow rules, and contextual recommendations.

Event-driven work

Background jobs, long-running queues, retries, and recorded history.

Connected history

Operational memory that stays attached to the work that produced it.

Engineering

The hard part is the point.

Mobile App and Full Payroll are the headline problems still ahead. Payroll rules have to be validated before they apply. This is planned work, not a claim of finished accuracy or automatic legal coverage.

Version 2 exists to plan those capabilities. It does not move multiple users out of Version 1.