Software companies run on human attention.

FriendMachine builds operators that need less of it.

Give an operator continuing responsibility for growth, releases, customer support, or research. Its role, limits, and work record continue across model sessions.

FriendMachine develops operators inside its own products and works with other software companies to build them around real, continuing jobs.

FriendMachine / interactive operating model Choose a role, then change the model session

Growth operator

Product: Articul

Working now

Build and improve a repeatable acquisition and learning loop for Articul.

Current work

Review product, search, and analytics evidence for acquisition opportunities.

Produces

Dated evidence briefs and proposed experiments.

Authority

Read-only. Cannot send, publish, or spend.

Outcome record

Reported work stays separate from independently verified results.
Operator running in this session
Job, limits, and history stored separately

Have an ongoing role that consumes too much human attention? FriendMachine can help define the operator’s responsibility, authority, evidence, and points of human control.

Discuss an operator

An ongoing job inside the company

A prompt produces an answer. A FriendMachine operator carries responsibility across sessions, remembers what remains unfinished, and works within company-set limits.

Responsibility

The operator has a continuing job and a defined result to pursue.

Context

Company knowledge, prior decisions, open work, and commitments remain available.

Authority

Access, budgets, and consequential actions stay inside explicit limits.

Evidence

The systems where work occurs determine whether reported results hold up.

What lands on a person’s desk

Routine work keeps moving. Human attention goes to irreversible actions, larger budgets, conflicting evidence, and decisions where preference or judgment is the real input.

FriendMachine / decision brief Example format

Change Articul’s acquisition page?

The operator brings the decision together instead of sending a transcript: what changed, what the evidence supports, which options remain, and what each option permits next.

EvidenceSource-linked measurements and prior work
OptionsApprove, revise, decline, or defer
LimitsNo publication without approval
No responseCurrent page remains unchanged

This panel demonstrates the decision format. It does not report a completed experiment.

Research belongs inside the company

Programming languages, agent evaluation, geospatial systems, and software for physical operations supply new capabilities for the products and operators.

Jacquard

An open-source, effects-oriented programming language implemented in OCaml. Jacquard explores how programs can declare the actions they may take before they run, including programs written or assembled by a model.

The build log separates claims from results

FriendMachine publishes the boundary between planned work, an operator’s report, an independently checked result, and an effect observed in the product.

Proposed

Planned work that has not been executed.

Reported

An operator or other executor says the work occurred.

Verified

A separate check confirms the specified result.

Realized

The result produced an observed effect outside the execution system.

Working now

Articul is live. Its read-only growth workflow produces dated evidence briefs and proposed experiments from product, search, and analytics exports supplied by a person.

Being integrated

The complete governed loop from assignment through action, independent verification, and finalized outcome has not yet run end to end.

View the full build log →

Follow the work as the operators take on more of it.

Occasional notes when FriendMachine publishes research, ships a product, or learns something useful about persistent operators.