WORKNEL

In development · Solo founder · Pre-registration

Business procedures, ready for agents.

WORKNEL is being built to turn your company’s procedures into workflows that agents can execute — with human approval and verifiable results.

See the planned workflow Where the project stands
The WORKNEL Kernel Layers mark: two open square layers around a cobalt core.
Reading the mark
  1. Procedure. The outer layer: your real business rules, made explicit.
  2. Human approval. The inner layer: a responsible person reviews before anything changes.
  3. Verified outcome. The core: completion is reported only after the result is checked.

Your work spans documents, people, and business tools. Your automation should preserve the rules that connect them.

Every company already runs on procedures: who checks what, which information is required, when a request is really finished. WORKNEL aims to bring procedures, approvals, agent actions, and completion evidence into one workflow — so automation follows the same rules your people do.

  1. Procedure

    The steps, inputs and completion criteria your teams already follow.

  2. Approval

    A named person decides before anything is changed.

  3. Agent action

    Only the approved change is carried out.

  4. Completion evidence

    A checked result, not just a status message.

From a written procedure to a verified result.

Three planned stages take a real business process from definition to a checked outcome. The example below walks one synthetic internal request through them.

Planned product workflow Illustration only — not a working product demo. Nothing on this page runs an agent or changes data.

Stage 1 of 3

Define the procedure

Turn a real business process into a structured workflow with clear inputs, decisions, and completion criteria.

The procedure is the reference every later step is checked against.

Procedure Illustrative

Close a reviewed internal request

Inputs
Request record · review outcome · responsible person
Decisions
Is the review complete? Is any required information missing?
Completion criteria
Status is Closed, a closure note is recorded, and the stored result matches the approved change.

Stage 2 of 3

Review the proposed action

Show the person responsible what the agent plans to do and what will change.

If the target or its content changes after approval, the earlier approval is not reused.

Proposed action Illustrative

Request DEMO-001 (synthetic)

“Close this request using the review outcome.”

Current state In review
After approval Closed, with closure note
Decision
Waiting for the responsible person to approve or reject

Stage 3 of 3

Execute and verify

Run the approved action and check the outcome before reporting completion.

A rejected proposal changes nothing. An unclear outcome is never reported as complete.

Execution & evidence Illustrative
  1. ExecuteApply only the approved change, once.
  2. Re-readRead the stored result back from the system.
  3. CompareMatch it against the approved after-state.
  4. ReportMark complete only when the check passes.

A workflow core that stays with the customer.

WORKNEL is designed around a customer-hosted workflow core. For internet-connected deployments, the planned Claude integration will help interpret procedures and prepare actions for review. The application will retain responsibility for permissions, approvals, and execution state.

Customer environment

Workflow & approval core

Customer-hosted

  • Permissions
  • Approvals
  • Execution state

Agents on employee PCs

Carry out approved actions in the tools people already use.

Planned · Internet-connected deployments

Claude integration

Helps interpret procedures and prepare actions for review — only where the customer allows data transfer.

Planned · Separate path

Offline deployments

Fully offline operation is a separate planned path using local models.

Planned deployment architecture. Simplified illustration; components are in design and not yet available.

Early, and honest about it.

WORKNEL is a solo-founder project that has not yet been registered as a company. The product architecture and brand identity are prepared. A working product demo is not yet available.

  1. Prepared

    Product architecture and brand identity

    The planned workflow, the customer-hosted core and the WORKNEL identity are defined.

  2. Next milestone

    A controlled prototype with synthetic internal requests

    One synthetic request, prepared, approved, applied and verified — including what happens when a proposal is rejected or an outcome is unclear. It will not connect to real customer systems or data.

  3. Not yet available

    Working product demo

    Results will be described only once they can be shown. Founder details and contact information will be added when confirmed.