Case study 2026

ClearPath OS

A human-centered operating system for organizing complex work, decisions, and operational knowledge.

Context

ClearPath OS explores how teams can bring scattered processes, documentation, decisions, and responsibilities into one understandable operating environment.

The project was created in response to a common operational problem: employees are often expected to follow complicated procedures while information is distributed across emails, documents, systems, and informal instructions.

Instead of adding another disconnected tool, ClearPath OS organizes work around the decisions people need to make.

The problem

Operational teams frequently experience

01Conflicting instructions
02Scattered documentation
03Unclear ownership
04Repeated questions
05Difficult handoffs
06Inconsistent decisions
07Limited workflow visibility

These problems increase cognitive load and make employees depend on memory or informal support.

User & operational needs

What people actually need at the moment of work

A single source of truthOne place where the current, correct procedure lives — not four inboxes and a wiki.
Guidance in contextThe right instruction surfaced for the task at hand, not a 40-page manual to search.
Clear ownershipKnowing who is responsible for each step and each decision, and who to ask.
Confidence to actEnough understanding of why a step exists to make consistent, defensible decisions.
Workflow before the solution

A task used to look like this

Step 01Search email & chat for the latest instruction
Step 02Ask a colleague to confirm it's still correct
Step 03Reconcile conflicting versions from memory
Step 04Act — and hope the judgment was right

Every step depended on tribal knowledge. Nothing was captured, so the next person started over.

Design principles

Four principles shaped the system

1 Show the user where they are in the process.
2 Present only the information needed for the current decision.
3 Explain why an action is required.
4 Keep humans responsible for important judgments.
Proposed system

Work organized around decisions, not documents

ClearPath OS models each process as a sequence of decision points. Every point carries its own guidance, ownership, and the reasoning behind it — so the system leads rather than stores.

Process mapA live view of the full workflow with the user's current position highlighted.
Decision panelOnly the information and options relevant to the decision in front of you.
Knowledge layerProcedures, ownership, and rationale attached directly to each step.
Review checkpointsExplicit human confirmation before anything is submitted or escalated.
Role of AI

AI supports users by:

  • Retrieving relevant procedures
  • Summarizing complex information
  • Suggesting next steps
  • Identifying missing information
  • Preparing documentation
  • Organizing decisions and follow-up actions

AI does not make final high-impact decisions without human review.

Human confirmation points

Important actions require a clear review step before information is submitted, escalated, or finalized.

Before submission Before escalation Before finalizing
Key screens

The system, in three views

Process map — screen placeholder
Process map. Where you are in the full workflow.
Decision panel — screen placeholder
Decision panel. Only what this decision needs.
Review step — screen placeholder
Review step. Human confirmation before commit.

Drop real screen exports or diagrams into the placeholders above.

Outcome

ClearPath OS demonstrates how AI can function as part of an operational system rather than as a standalone chatbot.

The result is a clearer experience that reduces uncertainty, improves consistency, and helps employees understand both what to do and why.

What I learned

Three takeaways

Structure beats storageOrganizing around decisions did more for clarity than any amount of better documentation.
Trust needs the "why"People followed steps more consistently once the reasoning was visible alongside the action.
AI earns its place as scaffoldingFraming AI as support — not decision-maker — made it feel dependable rather than risky.
Next iteration
  • 01Test the decision model with a live operational team.
  • 02Define how the knowledge layer stays current over time.
  • 03Design the audit trail for reviewed and confirmed decisions.
ClearPath OS Fabian Delven — 2026

Visual documentation

How the experience works.

A practical visual set for reviewing the workflow, responsibilities, system boundaries, and human-control points. Screen imagery remains upload-ready where final interface captures are not yet available.

Before-and-after workflow

From fragmented effort to one guided, reviewable sequence.

Search→Rebuild context→Act manually
Organize→Guide next step→Human confirms

User journey / service blueprint

The user journey aligned with visible system support.

User
ArriveUnderstandReview
System
GatherStructureRecord

Understandable system architecture

A high-level view of inputs, support logic, review, and output.

People + source material→Organizing layer→Review gate→Approved output

Important decision flow

Consequential actions pause for context and explicit confirmation.

Is the information complete?
No → request contextYes → human reviews
Approve, revise, or stop

Screens with annotations

Reserved for final product screens and concise callouts.

Future screen uploadAdd 3–5 interface captures with numbered annotations describing the user need, system response, and confirmation state.

Where AI helps

AI reduces repetitive synthesis without owning the decision.

Raw input→SortSummarizeSuggest→Proposal

Where humans confirm

People retain authority at every consequential boundary.

AI proposal→Check accuracy→Edit / approve→Use or share

What is intentionally not automated

The product supports judgment; it does not replace accountability.

No autonomous sending, publishing, or consequential decisionsNo silent changes to approved informationNo replacement for qualified human expertise