In this article

Start with an accepted command

Consider an observation placed on a fingerprint image. A person selects the feature, adds a note and chooses to record it. An agent might reach the same operation through an image crop and a structured tool call. Both need to identify what they are referring to and the examination state on which their contribution depends.

The tempting implementation is to give the browser one save function and the agent another. That is easy to begin and expensive to maintain. A rule added to one route can be absent from the other: a changed dependency, a withheld source or a stage that has already been submitted. The interface then determines which record is possible.

PROFAS instead treats recording as an explicit command. It identifies the examination and record, the expected examination head and record revision, a stable operation identity and the proposed content. The head represents the accepted sequence of the examination. The record revision identifies the particular contribution being created or changed.

These fields make the basis of the request inspectable. A highlighted annotation or a completed text field remains local work until the server accepts it. The response supplies the accepted head, revision and server acceptance time, giving the client a definite result to reconcile with its draft.

Two adapters, one acceptance decision

The browser enters through an authenticated recording mutation. It resolves the examination and checks its owner before handing the command to the shared acceptance function. The agent enters through a scoped connection and an internal recording adapter, which checks the connection’s authority for that examination and recording action.

The adapters have different preparation work. The agent adapter can translate coordinates from a registered returned image and constructs connection-bound authorship context. Neither adapter gets to replace the common decision about whether the proposed record belongs in the examination.

That shared decision checks the pinned module and permitted tools, the examination stage, source availability and exact dependencies. A comparison finding must cite observations on both questioned and reference material. Evaluation follows a submitted Comparison basis. Earlier-stage contributions cannot be quietly revised from a later stage.

This is a useful boundary for development. Adding an interface requires an adapter into the command contract rather than another version of the examination rules. The common path still has to be read carefully: centralising authority reduces duplicated logic, but the correctness of its rules remains an engineering responsibility.

ENGINEERING NOTE

Different interfaces, one accepted contribution

  1. Browser or scoped agent

    A local draft or a structured tool request identifies its examination basis.

  2. Interface adapter

    Authenticate, check resource access and resolve any registered image frame.

  3. Shared acceptance

    Check stage, source, exact dependencies, expected head and record revision.

  4. Accepted receipt

    Retain the contribution, revision and event; return its accepted identity.

Each adapter establishes its own identity and input context before invoking the common recording authority.

Coordinates belong to the source

A position on a screen is incomplete evidence. The same original image can occupy a small pane, a large monitor or a tightly cropped view. Saving a browser offset would make the annotation depend on the arrangement of the interface rather than the material being examined.

Image annotations in PROFAS use original source pixels. For an agent, preparing an image region returns a registered view with its crop, output dimensions and mapping back to the source. The registration binds that view to the examination, connection and original source hash. A later recording request can name that frame explicitly.

For example, an agent may inspect a reduced crop instead of the entire image. Its selected point is mapped through the recorded transformation before acceptance. The accepted geometry therefore remains meaningful if another reader opens the full original at a different zoom. Measured surfaces and DNA signals have their own native-frame requirements rather than borrowing this raster convention.

Preparing a view also has a narrower meaning than observing it. The system records that the image was prepared; it cannot establish that a model attended to a particular ridge or that a person perceived a feature. Keeping that distinction prevents a delivery trace from acquiring an unwarranted psychological interpretation.

Retries and disagreements need different answers

Suppose a connection drops after the server accepts an observation but before the client receives its receipt. Resending the same command should retrieve the accepted result rather than add a second observation. PROFAS stores the operation identity with a digest of the request and its receipt.

An exact retry returns that receipt with a duplicate indication. Reusing the same operation identity for different content is rejected. This separates uncertainty about the response from an intention to create a new contribution, and gives both browser and agent clients a deliberate recovery action.

A stale examination head is a different problem. If another accepted operation has advanced the examination, a new request based on the old head must refresh and reconcile. The same applies when the expected record revision has changed. Silently accepting an overwrite would conceal that the proposed edit was made against an earlier basis.

Acceptance updates the current record projection and retains a revision and event. The projection serves the current workspace; the retained history supports inspection of development. These are complementary responsibilities. Neither a convenient current view nor a long event list is sufficient unless the references between them remain explicit.

The examination record provides a view of retained contributions and their development. The displayed history was prepared to demonstrate the interface.

Shared authority does not require identical capabilities

An agent connection is a bounded interface. It can read permitted material and record supported contributions under its grant. Stage submission, peer disclosure and source uploads are deliberately absent from this connection. Sharing the acceptance path does not require exposing every action available in the human workspace.

Authorship follows the authenticated route. An ordinary browser command cannot assert that it came from an agent connection. Agent recording retains its connection and tool context. A supplied model name or client time remains declared metadata; it is not promoted into an independently verified fact.

This distinction also matters for speech. A machine recording cannot claim that a human reviewed a transcript merely by supplying the corresponding fields. The acceptance path preserves the boundary between a machine contribution and the separate human actions that establish a reviewed audio-backed note.

The general engineering lesson is to share the rules that establish an accepted record while keeping capabilities explicit at each entry point. That makes another interface practical without making it an exception to the examination. The resulting record supports inspection of what was contributed, by which route and on what basis; scientific correctness remains a separate question.