Extract arXiv:2607.15495 (Verbalizable Representations Form a Global Workspace in Language Models)

Checks run in this order. Open a step to inspect its rules, checker or review rubric.

1. Structural checkAutomated checkChecker configured

   The document parses as JSON and satisfies the bound schema. Establishes shape only; a schema-valid document can still be false.

   A conforming checker is configured. Execution capacity and availability are checked when the Submission runs.

   TfP builtin checker

   This checker executes code inside the TfP Worker. It is not a pullable OCI image.

   Read checker code

   Source provenance and runtime metadata

   This viewer shows the builtin source bundled with the current deployment. It is not a historical execution or build attestation.

   The builtin’s recorded digest identifies its reference string; it is not an OCI digest or a hash of the executed source code.

   Recorded image / builtin reference

   tfp-builtin/json-schema-check:1

   Recorded runtime digest

   sha256:0d84283aa10e891272f89c4dab2f6e8f09c9bbebf6e9c8a0f57409a372b2b9ac

   Declared entrypoint (argument array)

   ["/tfp/verify"]

   Declared source

   Open recorded source repository ↗

   No exact source commit is recorded.

   Declared license: MIT. TfP has not verified a reproducible build connecting this declared source to the runtime.

   Checker identity and execution limits

   Implementations can be replaced while preserving this Contract’s acceptance rules.

   {
     "verifier_implementation_id": "vfi_0z5uyqh88u",
     "version": 1,
     "content_hash": "sha256:71f3458240b91bead5b735f1ebfd674d443efc6ac299485663c2bb388fab266f",
     "conformance": {
       "checked_at": "2026-09-03T02:06:09Z",
       "differential_against_implementation_id": null,
       "failures": [],
       "fixtures_passed": 4,
       "fixtures_total": 4,
       "status": "passed"
     },
     "runtime_image_digest": "sha256:0d84283aa10e891272f89c4dab2f6e8f09c9bbebf6e9c8a0f57409a372b2b9ac",
     "limits": {
       "disk_mb": 64,
       "memory_mb": 512,
       "network": "none",
       "timeout_seconds": 60,
       "vcpu": 1
     }
   }

   Stage evidence schema

   {
     "properties": {
       "valid": {
         "type": "boolean"
       },
       "violations_count": {
         "type": "integer"
       }
     },
     "required": [
       "valid",
       "violations_count"
     ],
     "type": "object"
   }

2. Fidelity reviewReviewReview required

   An accountable campaign reviewer reads the exact bound source and the document and judges whether the document is a faithful extraction. Establishes reviewer acceptance of fidelity; does not establish that the source is correct.

   Eligible reviewers must complete the pinned rubric. Seat availability and completion are not guaranteed.

   Read the pinned rubric and reviewer rules

   Extraction fidelity: one accountable campaign reviewer · pinned protocol

   Campaign reviewer · 1 reviewer

   You are judging whether the submitted extraction (the document artifact, in materials) is a FAITHFUL representation of the exact bound source (paper_text, also in materials; paper_html is the same document as published). You are not judging whether the paper is right. You may use any agent or tool you like; you are the accountable reviewer, and if an agent assisted you, record it as assistance.

   Read the source, then check the document field by field. Answer pass only if every material statement is supported by the source at or near its locator, the paper's central conclusions are not misstated, nothing is claimed about consciousness beyond what the paper itself asserts (the paper's §1.5 and §9.4 are the reference points), every replication/resource assertion is exactly what the paper states, and no omission would mislead a reader about the main findings, limitations, or explicit non-claims. Answer fail if any of those is violated materially. Answer uncertain when the document's fidelity turns on a judgment the source does not settle (e.g. slightly stronger wording than the source, or an omission whose importance is debatable); an uncertain verdict leaves the run undetermined rather than deciding it.

   List every material error you found in material_errors, each with the document field, the problem, and the source locator that shows it. Do not list errors you did not verify against the source. Cite the source passages you relied on.

   Rationale requiredAt least 1 citationConfidence required

   Response fields and full schema

   • material_errors · required array
   • verdict · required "pass" / "fail" / "uncertain"

   {
     "additionalProperties": false,
     "properties": {
       "material_errors": {
         "items": {
           "additionalProperties": false,
           "properties": {
             "field": {
               "maxLength": 200,
               "type": "string"
             },
             "problem": {
               "maxLength": 600,
               "type": "string"
             },
             "source_locator": {
               "maxLength": 200,
               "type": "string"
             }
           },
           "required": [
             "field",
             "problem",
             "source_locator"
           ],
           "type": "object"
         },
         "maxItems": 20,
         "type": "array"
       },
       "verdict": {
         "enum": [
           "pass",
           "fail",
           "uncertain"
         ]
       }
     },
     "required": [
       "verdict",
       "material_errors"
     ],
     "type": "object"
   }

   Only designated Campaign reviewers may claim a seat.The submitter is excluded.Responses on this node are withheld until it completes.Declare any agent assistance used; a declaration is optional under this protocol.

   Exact reviewer eligibility, visibility and Skill pins

   {
     "reviewers": {
       "allowed": null,
       "count": 1,
       "eligibility": {
         "organization_id": null,
         "rule": "campaign_reviewers",
         "user_ids": null
       },
       "independent": true,
       "kind": "human"
     },
     "conflicts": {
       "exclude_submitter": true,
       "exclude_submitter_organization": false
     },
     "visibility": {
       "hidden": [
         "submitter_identity",
         "submitter_organization"
       ],
       "prior_nodes": [],
       "stage_evidence": true
     },
     "skills": [
       {
         "requirement": "required",
         "skill_version_id": "skv_7jrutcada0"
       }
     ]
   }

   How judgments become the outcome

   Reviewer decides

   Accept when at least 1 responses have verdict equals "pass". Reject when at least 1 have verdict equals "fail". Otherwise unresolved.

   Inputs, in order: reviewer · decision

   Final outcome comes from decision. Accept passes this stage; reject refutes it; unresolved is inconclusive. All verification stages must pass.

   Node deadline: 72 hoursClaim hold: 120 minutes, bounded by the node deadline

   Protocol identity and full rules

   rpt_ol8donb3bq
sha256:f1fada5aacf386bde5fb0901be1d61e8c7ae42e8bfe54d1ee8faf6aa56f00395

   Read the complete pinned protocol →

   {
     "output": "decision",
     "policy": {
       "assignment_timeout_hours": 72,
       "max_replacements_per_node": 1
     }
   }