Helixfield

Current method

The operating system we install now.

Today that is Loop & Graph. A loop is a unit of repeating work. A graph is institutional memory. Every agent turn is pack, act, extract, ingest. A named human accepts material facts. When a stronger method, architecture, or model generation lands, Helixfield adopts it.

Useful, concrete, still teachable — and versioned. Helixfield installs the same system it runs. Client work is not frozen on last year’s metaphor.

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

Protocol

Four steps. Every turn.

  1. 01 · pack

    Pack

    Before the agent answers or acts, pull the smallest set of accepted facts, open questions, and hard rules that bear on this turn. Proposed facts stay labeled. Guessed numbers stay out.

  2. 02 · act

    Act

    Do the work with the packed graph in view: draft, configure, route, or decide. If a required fact is missing, ask. Do not invent a number, a client, or a permission.

  3. 03 · extract

    Extract

    After the turn, lift new facts, decisions, risks, and tool changes. Each item gets a status: proposed, accepted, or ask.

  4. 04 · ingest

    Ingest

    Write extracts back into the graph. Only a human principal can move a material fact to accepted. The next pack is smarter because this one closed.

  • Every dollar, date, and permission is labeled accepted, proposed, or ask.
  • A model guess cannot replace an accepted fact.
  • The graph is the memory. Chat history is not.
  • Loops have owners. Agents do not silently change a loop.
  • Client-facing output is drafted until a human says send.

Live system

Click a node. Follow a loop.

The left graph is what we install. The right view is how this practice runs.

Live system

Client Loop & Graph pattern

What Helixfield installs. The center is institutional memory. The rim is the work that repeats. Select a node. The protocol on the right is the same four steps every agent runs.

Intake loopFulfillment loopFollow-through loopLearning loopGovernance loopShared graphFront agentOps agentNamed owner

Protocol

Pack. Before the agent answers or acts, pull the smallest set of accepted facts, open questions, and hard rules that bear on this turn. Proposed facts stay labeled. Guessed numbers stay out.

  • Every dollar, date, and permission is labeled accepted, proposed, or ask.
  • A model guess cannot replace an accepted fact.
  • The graph is the memory. Chat history is not.
  • Loops have owners. Agents do not silently change a loop.
  • Client-facing output is drafted until a human says send.

Questions

Direct answers

See this on your loops.

Tell us the work that repeats. Helixfield will say whether a Field Survey is the right first move — or that it is not.

Start a briefing