Jacquard Research | Browser-Native Agent Worlds

Choose the audience that matches your question

The page contains three selectable readings of the same subject.

Coding agent and operator assistance. Demo metrics are illustrative.

Terminal, search, lint, test, git, and more.

Remembers your codebase and team context.

Specialised agents collaborate across concerns.

Review diffs, request changes, final sign-off.

Replay any session bit-for-bit when something needs review.

Autonomous agents that write code and keep receipts

to handle network timeouts, 5xx responses, and idempotent-safe conditions. Pure helper, fully unit-tested.

No measured saving is claimed here. The claim is that the lower lane is possible.

Reviewers are gathered so everyone sees the same version.

A separate build is produced for each device class in scope.

Someone with the tool and the machine builds a first version.

The person who understands the problem writes it down.

The world was not touched by the refused request, and the refusal states which band produced it.

The channel narrows at every gate. Holding one scope never implies the next.

Anything leaving the engine is a separate grant.

Control supported time, testing and simulation functions.

Read approved content and structured documents.

Create and change permitted scene state.

What the agent may not change or invent.

What a person should be able to do there.

How light, colour and sound should read.

Three reviewer comments, every one of them pinned to a world part rather than to the sentence that asked for it.

Do not add people, signage or anything from outside the brief.

The learner walks the route and picks up one tool.

A trolley, a rack and a set of tools on the bench.

A training bay with two workstations and a marked walkway.

state the intent, then read the evidence

Add lamps along the quay and move the bench to the water.

pinned start, recorded input, named chance

the reply describes this engine, on this device, right now

The interface does not define the requested behaviour.

This device or project configuration does not provide it.

Present, but the caller does not hold the required authority.

Offered under the current world and browser contract.

Viewpoint moved to take in the new lamp row.

Material category changed to a reflective one.

open in a browser, on the machine you have

A harbour village at dusk, a bench on the quay, a walk to the water.

Six clauses, read together. None of them is a step.

Whether the change joins a reversal or a transaction.

The named reason a request was not applied.

The structured value handed back to the caller.

The world state this call is permitted to change.

The authority the caller must already hold.

The typed values and preconditions a call requires.

six lamps, a moved bench and a new water surface

The world returns to the state the change replaced.

A narrower request changes only the part you objected to.

The proposed world becomes the one everybody works from.

the same objects, the same route, the same rules, the same version

Reflection on the water and a graded evening sky.

A soft shadow under things, and a second light.

the same world, the same rules, the same version

A different named state produces a different run identity.

The same state reproduces the same sequence, mark for mark.

A branch copies the current state without consuming from it.

World systems take values from that state, in order.

The run receives an explicit random state identity.

the difference names a region, and a person names what it means

Reference frame, new capture and difference mask

the route from the square to the water resolves

four claims about state, none of them about pixels

The difference column is short because everything except the declared condition was pinned before either run began.

six of eight cells recorded no difference

The structured change is readable even where the deepest visual plan is not.

The same approved world on five machines

Closing the tab is the whole of leaving.

The same address returns you to the same world.

One link goes to everyone instead of a file each.

Follow the address and the world is there.

Four approaches, one aperture: the operation identity does not change with the caller.

application code issues the operation as an ordinary import

the harness issues the operation with no viewport at all

the agent issues the operation as a typed message

the editor issues the operation from a property field

verification available through the surface that client owns

Four parity questions asked of four callers

Four readings taken from the machine, before any plan is chosen.

What happens if the graphics device is lost and returns.

Pointer, touch and keyboard, as the world will receive them.

How much the world may hold before the plan gives way.

Which visual systems this browser actually offers.

The same four answers, on a much larger place.

A world worth being in, opened on an ordinary machine.

A change read, judged and put back in a few minutes.

A world built with no gesture anywhere in it.

The named random state the run draws from.

The scene and the simulation state at the start.

The heavy tick at the left of the rail is the declared boundary. The hatched mark at the right left the engine, so it is reported outside every bracket and never silently included.

restores the whole world to the declared boundary

restores the group a reviewer decided about, as one decision

restores the state one supported change replaced

An effect that leaves the engine is reported outside the boundary.

Return the world to a declared boundary in its history.

Apply or restore a related group as a single decision.

Restore the state captured for one supported change.

stating and deciding is the work being measured

The tile count is identical in both bands. Only the arrangement differs, and the batching band is a hypothesis the programme is set up to evaluate.

Compared against the version before it, a difference in the document is one a person can read: which object arrived, which one changed parent, which property moved.

Four moments, one artefact. Nothing here is a separate export of the world.

The browser reconstructs the accepted scene from the document itself.

A headless client loads the identical world and asserts against it.

A person reads the exact difference between two versions of the document.

The editor and the agent change structured world state through the same operations.

a path for one actor and a stated refusal for the other, from the same world

a route for one actor, a stated refusal for the other

the margin on each side, so the answer survives a later change

the shape fits, with the margin on each side

what was met first, and what was behind it and never reached

the first surface met, and what lies behind it unreached

the surface and its orientation, not a guess from the picture

A refusal is a return as well, and it names the constraint that produced it.

Is the goal reachable for an actor with these limits?

Can this shape occupy or move through this space?

What does this ray or volume encounter on its way?

Where is a stable surface here, and how is it oriented?

The seams are the same size on purpose. Each neighbour keeps its own research question.

The evidence and decision a transaction produced.

The model capacity behind that agent's reasoning.

driven directly: the harness asks for steps and receives exactly that

recorded as a gap, not replayed as steps

the tab was suspended, so the clock stopped at the ceiling and recorded the gap

the frame was late, so the clock caught up and carried the remainder

the frame arrived on time, so the clock advanced two whole steps

the accepted state becomes the reference

the accepted state becomes the reference the next intent is judged against

Accept, revise, restore or decline, and record it.

Structural, rendered and operating evidence is produced.

The agent works through permitted world operations.

The change wanted and the bounds it must stay inside.

presentation may differ, authority may not

reflection on the water and a graded evening sky, at the deepest supported drawing

a soft shadow and a second light, inside a comfortable budget

flat light and plain water, on a machine that said that is what it can manage

The ceiling is the same line in every case.

Steps taken in one frame, against the declared ceiling

advances by request, with no wall clock involved

stops at the declared ceiling and records the gap

runs bounded catch-up and carries the remainder

advances the supported number of fixed steps

The strip marks the band of the image that moved. It detects unintended change; it does not judge the result.

Can the architecture be maintained and governed?

Which browser and device classes carry the result?

Does the world meet its visual and interactive purpose?

Can people inspect, bound and reverse the work?

Can the agent complete the worldbuilding task?

No scenario is reported without the envelope it was run in, and the families that came back short are reported beside the ones that did not.

the envelope this result was produced in

the same scene, the same rules, the same approved version

the deepest supported plan this machine reported, on the same scene