Helixfield

Plain-English terms

Words we use, said simply.

How we organize the work today is called Loop & Graph. A loop is a job that already repeats. A graph is a shared list of facts. Every turn: gather the facts, do the job, write down what changed, save it. The terms below are the ones owners need before a briefing.

When a better method ships, this page will move with it.

Overhead still life of a loop drawn on drafting paper around a copper pin.

Loop & Graph

How we organize the work today — not a forever lock-in. A loop is a job that already repeats. A graph is a shared list of facts. Every turn: gather the facts, do the job, write down what changed, save it. When a better method ships, we use that.

Loop

A job that already repeats, with a named person who owns it. Examples: new inquiries, order exceptions, invoice follow-up.

Graph

A shared list of facts, rules, systems, people, and open questions. Chat history is not a graph.

Pack

Gather the facts you already agreed on before the helper answers or acts. Hunches stay labeled. Guessed numbers stay out.

Act

Do the job with those facts in view. Ask if a needed fact is missing. Do not invent a number or a permission.

Extract

After the turn, write down new facts, decisions, and risks. Mark each one proposed, accepted, or ask.

Ingest

Save those notes back into the shared list. Only a person can mark an important fact as final.

Current method

How Helixfield organizes the work right now. Today that is Loop & Graph. We move when a stronger method or a new generation of AI tools ships.

AI tools / platform

The brand a setup actually runs on — OpenAI, Grok, Claude, Gemini, Cursor, bring-your-own, or the next release. Chosen from access, data rules, cost, and your preference. Not a partnership.

GPT-6 Astra

OpenAI’s current computer-use model (API id gpt-6-astra). One option we will use when it fits the job.

Grok bot

An xAI helper with a computer and access to your apps, often reached through Cursor. Different from a chat window and from the xAI API.

Grok Business

xAI’s team product, about $30 per seat per month in 2026, with centralized billing and a default that company data is not used for training.

xAI API

Pay-as-you-go Grok access for software you control. Grok 4.6 bills $2 / $6 per million tokens under 200,000 prompt tokens as of August 2026.

Field Survey

Helixfield’s $9,500 first look. Two to three weeks. Maps the repeating work and recommends the first setup. Does not include a live helper. Dedicated page: /field-survey.

AI engineering

Designing, building, testing, and running AI software that does a real job in your business every day. At Helixfield this is the Field Survey, then install, instruct, and operate — not a fifth service.

Eval (quality check)

Ten to twenty real examples from your work, each with a written note of what a good result looks like. The system is scored against them before launch and after. Invented numbers fail.

Retrieval

Letting the system look things up in your own records — contracts, price lists, past tickets — before it answers, instead of guessing from memory. Read access first. It should say it does not know when the record is not there.

Accepted fact

A fact a named person has marked as true for the shared list. A model guess cannot replace it.

Named owner

The person who can reject a helper’s draft and refuse anything that would leave the company. Not necessarily the most technical person.

Circuit

Helixfield’s usual monthly plan at $6,800, sold with a three-month minimum: a weekly note, fact cleanup, and help when something breaks.

Engagement pack

A morning file a helper assembles overnight for a new inquiry: missing facts, a fit/risk read, a discovery brief, and a drafted first response. A named partner accepts anything that leaves the firm.

Exception floor

A helper on late orders, short ships, expedites, and status asks. It gathers accepted promises, drafts updates, and waits for a named ops lead before anything is sent.

Aging desk

Checked invoice follow-up. The helper gathers accepted terms and drafts the next note. A controller accepts every outbound message. Not an unsupervised collections caller.

Questions

Method questions