PRODUCT / THE OPERATING MODEL

One Core for authority.
One Work surface for people.

The company sets the rules. Employees get a useful way to work. Cases keep the business record together.

01 / THE COMPANY RUNTIME

Core decides how AI operates.

BizClaw Core is where the company governs identity, provider access, capabilities, policies, approvals, Cases, LTF records, usage and audit. It is the authority behind employee-facing AI.

Identity and access

Provider routing

Policy and approvals

Cases, LTF and audit

BizClaw Core overview showing runtime, Cases, capacity and license status — See the state of the Core.
Runtime, Cases, capacity and license status in one operator view.

BizClaw Core Main Worker operations view — Keep execution visible.
Operators can inspect Main Worker activity and execution results.

02 / THE EMPLOYEE DESKTOP

Work gives people a straightforward way in.

BizClaw Work is a free desktop application for employees to connect to their company’s Core, open Cases, attach files, ask, act and continue work. Work does not ask employees to manage model vendors, API keys or agents.

Free for employees

Connects to company Core

Ask, attach and continue

No employee-managed model keys

BizClaw Work connection screen for connecting to a Core — Connect to a company Core.
Work starts by connecting an employee to the company’s Core.

BizClaw Work conversation inside a business Case — Keep the conversation in its Case.
Questions, answers and context stay together as business work.

03 / THE BUSINESS WORK UNIT

A Case gives work a durable home.

A Case carries the context, decisions, actions, governance and record of a piece of business work. When execution pauses, the record remains available to continue later.

Work with context

Policy and approval boundary

Execution and queue state

A Case never closes. It sleeps.

BizClaw Core Cases operations list — See business work as Cases.
Operators can inspect the Case inventory the company is responsible for.

04 / THE BUSINESS RECORD

The work record outlasts a model run.

Each Case maintains a durable LTF business record. Workers and models can change while the Case record remains with the company. Broader knowledge indexing is a separate roadmap capability, not a claim about the current runtime.

Durable Case record

LTF appended through the Case lifecycle

Usage tied to business work

Audit events stay inspectable

BizClaw Core usage view showing Cases, messages, tokens and cost — Read usage in context.
Cases, messages, tokens and cost attribution stay close to the operating record.

BizClaw Core audit log of Case and execution events — Keep an operational trail.
Case, message and execution events leave a durable audit trail.

PROVIDER CHOICE, WITH A CLEAR BOUNDARY

Company control includes knowing where requests go.

Core controls identity, policy and provider routing in the environment the company operates.

Local providers can process requests within the company’s chosen infrastructure.

Cloud providers process the requests routed to them under their service terms. The company chooses whether and how to use them.

BizClaw.com manages product releases and license entitlements; it does not receive Case prompts, messages, LTF content or model credentials.