What Weave Checks

Description

Weave reads the configuration your project has already saved and reports what it finds: a step whose allocation has nothing to allocate, a workflow whose saved structure lists the same step twice. It reads only — nothing it reports changes a step, and it never runs your workflow.

No AI model is involved. Every check is a fixed rule and every sentence is written in advance, so a report costs nothing to produce however often you ask for one.

Note

The findings are reachable through the platform API. The notifications panel that will show them inside PlaidCloud is separate work, and is not in the product yet.

Three answers, not two

Most checks in PlaidCloud have two answers: your configuration is fine, or it is refused. Weave has a third, and it is the one worth understanding.

Answer	What it means
Weave noticed …	Weave checked this and found a problem.
(nothing said)	Weave checked this and found nothing wrong.
Weave hasn’t checked …	Weave could not judge this at all.

The third exists because silence is ambiguous. When you create an allocation step, PlaidCloud lets you save it before you have filled in its column mapping — you are still building it, and refusing the save would stop you working. A monitor reading that same empty mapping could easily report the step as healthy. It is not healthy; it is unfinished, and nobody has looked at it.

So Weave says so. A step it could not judge is reported as unchecked, with the reason, and it is never counted, sorted or coloured as if it had passed.

There is a fourth thing Weave can say, and it is not an answer about your step at all: Weave has no rule for …. That means Weave has no check for that kind of thing and never judged it. Unlike “hasn’t checked”, nothing you do to the step will produce a verdict, so the two are worth telling apart: finish an unchecked step and Weave will judge it; a step it has no rule for stays unjudged however much you change it.

What a report looks like

A report opens with a summary that names its own denominator, so you can see how much of the project it covers:

Weave fully checked 3 of the 417 steps and workflows in "Cost Model", and found 1
problem in the parts it could judge. 1 more it hasn't fully checked.
Weave has no rule for 412 steps and 1 workflow it looked at, so they have not been
judged either way.

Weave noticed the step "Spread Overheads": No driver split value column found. One
driver column must have the role "Split Value".
Weave hasn't checked the step "Regional Split" — its column mapping is empty.

The fraction in the first line is deliberate. Three steps checked and found clean is not the same statement as a clean project, and the opening line carries its own scale so that it cannot be quoted without one. “In the parts it could judge” is there for the same reason: where something was judged only in part, the problems found cannot be pinned on the steps the line has just called checked. The second line names what Weave has no rule for at all, and says out loud that those have not been judged either way — not that no check was needed.

What Weave checks today

Allocation column mapping. For an Allocation with Dimension or Allocation Split step, that there is a numeric column to allocate, a numeric driver value to allocate it by, a hierarchy where one is needed, and — for a split — a numerator and a denominator that names a column the source table actually has. These are the same checks that run when you save the step, reading what was already saved. Saving also checks the assignment dimension itself — that it exists, and that it has exactly one driver property — which Weave does not, so a step the save refuses for that reason produces no Weave finding.

Something listed twice in a workflow. That no step and no nested workflow appears more than once in the same workflow, and that no two folders sharing a parent carry the same identifier.

A step whose type Weave has no rule for is reported as uncovered, not as clean.

Marking a finding as read

Each finding carries an id, and you can mark it read so it stops appearing as new. The id is derived from the finding itself, so a finding you dismissed comes back as new if the underlying problem changes — a step you marked read after fixing one column reappears if a different column later goes wrong.

Read state is yours alone. Marking a finding read does not mark it read for anyone else on the project.

A digest

A digest is the same report reduced to what you have not already read, in the same voice. You can ask for one at any time, and you can have it delivered as an in-app notification.

Findings Weave could not check are part of a digest like any other. A digest that quietly dropped them would be exactly the reassuring silence the third answer exists to prevent.