Where Hearth came from. What we carry forward. What we deliberately do differently.
Igor Jericevich
Workflow is not the centre; the concern is. Case as GPS, not railway. Lifecycle as spine. Knowledge workers at the steering wheel.
K2/SharePoint substrate coupling; pre-AI rule-based assistance; BPM-centric implementation primitive.
Concern (not Case) as central term; AI-native via Whisper; explicit ERMA design lens; substrate-agnostic.
Slicedbread / ShareDo / Clio
Concern-centred work can be expressed as configurable work types with persona-specific work surfaces, phases, tasks, portals, workflow automation, allocation, and rich operational context.
Legal and matter-centric defaults; packaging gravity around phases, tasks, workflows, and process children; AI framed more as analytics and platform readiness than visible bounded delegation.
Concern rather than matter as the default object; jobs to be done in peripheral vision; visible and interruptible Whisper delegation; explicit human-only vs delegable boundaries; job-level confidence; non-legal-first prototype discipline.