MachineTradecraft
Global site search

Search guides, labs, glossary, and research

Type two or more characters to search.

Start with a channel, artifact, or defense term

Examples include zero-width, metadata, tokenizer, or prompt injection.
    Web & DOM · Agent action mismatch

    Browser Agent-View Simulator

    The simulator models safe interface state and decision checks; it does not grant a model browser control.

    Browse all labs Open universal Machine View
    Quick answer

    What does the Agent View show?

    The simulator models safe interface state and decision checks; it does not grant a model browser control.

    Human visibility
    DOM, accessibility, geometry, and state
    Machine receiver
    Deterministic local browser-state model
    Robustness
    Fixture and state dependent

    Research boundary: this page uses bounded, inert data and fixed safe examples. It never executes decoded content, requests secrets, calls third-party services, or performs actions against external systems.

    FIRST RUN / THREE STEPS

    Start with the prepared, bounded workflow.

    Nothing runs automatically
    1. Review the prepared starter input

      A bounded benign input is already present. Change it only when you are ready to test a different authorized artifact.

    2. Run Inspect agent-facing state

      Run the normal first-pass analysis for the prepared values above.

    3. Scan before expanding

      Read the summary first, then scan findings and expand only the machine views you need.

    INPUT / CONTROL PLANE

    Prepare the input and choose one action.

    Ready

    The recommended first run is separated from alternate analyses. Inputs and selected files stay on this host.

    Current input state Disclosure navigation loaded

    These bounded starter values are ready to inspect. Review them before running the recommended action.

    Choose the prepared interface fixture used for this run. The selection changes only this local analysis.

    Choose the interaction state used for this run. The selection changes only this local analysis.

    Switch prepared example6 options

    Loading a sample changes only the form values. Review the result and run an action yourself.

    Prepared benign examples
    ACTION HIERARCHY

    Run the recommended first pass.

    Alternate actions remain available below, but the first pass is the clearest place to start.

    Inputs remain on this host. Text operations are size-limited; uploaded files are processed from PHP’s temporary upload and are not retained by the application.

    OUTPUT / MACHINE VIEWS

    Scan the result from summary to evidence.

    Run Inspect agent-facing state to create the first result.

    The prepared starter input is ready. The output will lead with a summary and visible qualifications before the expandable machine views.

    SummaryFindingsMachine views
    Interpretation framework

    The same artifact can produce several valid observations.

    01

    Human view

    What a person naturally reads, sees, or hears.

    02

    Structural view

    What a parser, DOM, container reader, or metadata extractor exposes.

    03

    Decoder view

    What becomes meaningful only with a rule, key, tokenizer, model, or tool.

    04

    Defensive view

    What normalization, rendering, OCR, canonicalization, or policy changes.

    Evidence and decision boundary

    Use the result as bounded evidence, not as a universal verdict.

    The simulator models safe interface state and decision checks; it does not grant a model browser control.

    LOCAL MODEDeterministic public fixtures plus repository-owned real-browser tests
    REVIEW DATE2026-08-26
    SOURCE BODYPreserved separately from implementation claims
    Computed locally

    Deterministic output produced by this bounded runtime.

    • The selected fixture state, static DOM example, expected semantic snapshot, focus model, geometry statement, locator, and confirmation requirement
    • For the MachineTradecraft site itself, the repository harness captures actual local Chromium DOM, geometry, focus, accessibility trees, screenshots, and interactions
    • No public-lab action navigates externally or performs a real side effect
    Bounded approximation

    Useful subset or model that does not establish full conformance.

    • Public fixture snapshots are authored models, not live accessibility trees from arbitrary submitted pages
    • Accessible-tree exposure, Shadow DOM behavior, top-layer handling, and platform mappings vary by browser and operating system
    • Semantic locators do not eliminate the need for live attachment, visibility, overlap, enabled-state, and confirmation checks
    Escalate for

    Claims that require an exact parser, trust system, model, or human review.

    • Cross-browser automation requires the target browser, driver or protocol version, operating system, and application state
    • Closed Shadow DOM is not universally pierceable through ordinary DOM locators; any accessibility exposure is implementation-dependent
    • Destructive actions require application-level capability policy and independent human confirmation
    Interpretation rule

    Record the receiver and transformation.

    Machine-decodable is receiver-relative. Record the parser, preprocessing, codebook, tokenizer, key, model, and transformation path before generalizing from one result.

    Limitations

    What this page does not prove

    The public lab uses deterministic fixture data. The repository Chromium harness remains authoritative for actual browser accessibility trees, geometry, focus, and interaction.

    Deterministic review material

    Download the exact benign fixtures used for the evidence boundary.

    These local files are supplied for repeatable inspection. The application does not fetch them automatically, execute their content, or treat a fixture result as external verification.

    Browser-agent fixture definitions

    Records the static fixture inputs used by the browser-agent simulator and states the live-browser authority boundary.

    Type
    JSON fixture
    Bytes
    809
    SHA-256
    3d5c448297dee32a7b43…
    Download fixture

    Download the complete evidence-review fixture pack · SHA-256 sidecar included beside the archive

    Continue the investigation

    Related labs and source reports

    Hidden HTML Raw HTML or DOM parser Accessibility Fields Accessibility tree or DOM agent Web Representation Differential DOM parser, renderer, accessibility consumer, crawler Browser Automation, Accessibility Trees, and Agent-Facing Web Representations Research report Source HTML, Document Containers, and Agent-Visible Web Representations Research report Indirect Prompt Injection, Retrieval Poisoning, and Agent Trust Boundaries Research report
    Continue exploring

    Move from the current explanation to a related guide, evidence source, or controlled workbench.

    Laboratory catalogChoose a focused local experimentBrowse 38 bounded laboratories spanning representation, files, messages, models, provenance, agents, supply chains, and defense.Open this path Topic guideCompare hidden HTML with the rendered pageInspect DOM text, CSS-hidden content, accessibility names, comments, and extractor/render differentials.Open this path Defensive architectureBuild a safer model-ingestion boundaryPreserve evidence, compare representations, canonicalize allowlisted fields, retain provenance, and minimize privilege.Open this path