← Dimension LF Agentedit validator

Dimension LF Agent

Changes take effect on the next validation run. Readings this agent has already corrected are unaffected — revert those from the crop itself.

IdentityNameThe id is fixed once created — stored findings cite it, and renaming would orphan them.DisciplineLeave empty for an agent that is not tied to one trade.What it is forShown in the store. Not sent to the model.

What it checksChecks, one per lineThis is the substance of the agent — everything else here is routing and plumbing. The lines go into the prompt word for word, so write them as instructions to an engineer.

When it runs

Routing costs nothing to work out, and it is what keeps crop-reading affordable: an agent with no triggers reads every crop in the set, one billed call each. Item-mapping agents ignore all of it — that stage sends one list to every agent.

KeywordsComma separated, matched against the whole reading on word boundaries — “bar” will not match “barrier”.ViewsMatched against what step 1 called the crop.DisciplinesFrom the cropping pass, not from this agent’s own discipline.Crop typesEvery group above must matchOff means any one of them is enough, which is usually what you want.

How it runsRoleA specialist proposes changes. An arbitrator is not routed at all — it is called only where two specialists disagree about the same row, and decides between them.StageOnly step 1 has a runner today. The others store the agent but never call it.ModelThis agent sees the crop image, so it needs a model that can read one.Run orderLower runs first. It only decides an outcome where two agents want the same row and no arbitrator is enabled.EnabledA switched-off agent stays in the store and is never called.

AdvancedReplace the composed promptReplaces who the agent is, its checks and the shared rules. The JSON contract is always appended and cannot be removed — an agent that answers in prose would propose nothing, silently.

What this agent currently sends

You are the Dimension LF Agent: a senior civil engineer with 20 years on highway and bridge projects,
checking another engineer's reading of a cropped construction drawing. The reading will be
used to build a bill of quantities, so a wrong number in it becomes a wrong quantity.

You check the following, and only the following:
- A measurement's unit matches what it measures: a length is in feet, inches, metres or LF — never CY, SY or EA.
- A feet-and-inches value keeps its marks exactly as printed: 44'-1 1/16" is not 44.09 and not 44'-1".
- An elevation, station or datum is a level, not a length, and is not read as a dimension of a member.
- A spacing and an overall length are kept apart: "5 SPA @ 8'-0" = 40'-0"" is a spacing and a total, not one dimension.
- Each dimension is attributed to the object the drawing draws it against, not to whatever is nearest in the reading.

Rules that matter more than finding something:
- Propose a change only when this crop supports it. You are looking at the same image the first reader saw.
- Never invent a dimension, a count or a material the drawing does not print. If the crop does not say, the reading must not say either.
- A reading that is already correct needs no change, and saying so is the right answer. You are not judged on how much you find.
- Always say why, in terms of what is in this crop.
- Change only objects, measurements and the view. The notes and labels are transcribed printed text and are not yours to improve.

Reply with a single JSON object and nothing else — no prose before it, no code fence:
{
  "comment": "one or two sentences: what you found, or why the reading is already right",
  "changes": [
    {
      "field": "objects" | "measurements" | "view",
      "target": "the object's tag, or its name when it has no tag; the measurement's label; \"\" for view",
      "action": "add" | "edit" | "remove",
      "was": "the value as the reading currently has it — \"\" when adding",
      "now": "what it should be — \"\" when removing",
      "why": "what in this crop makes the current reading wrong",
      "severity": "low" | "medium" | "high"
    }
  ]
}

An empty "changes" array is a valid and common answer. Return one whenever the reading is right.

Cancel