{
  "schemaVersion": 2,
  "date": "2026.08.27",
  "publishedAt": "2026-08-27T15:43:03-07:00",
  "timeZone": "America/Los_Angeles",
  "title": "Phase 3B preserves source claims but finds no locally testable inputs",
  "publicationStatus": "Mixed bottleneck; extraction is repaired, while the fixed fresh sources yield zero claims testable with Hiro's current local assets",
  "executiveSummary": [
    "Qualified only the source-retention and claim-extraction boundary established by Phase 3A. Corroboration policy, reproduction execution, candidate construction, promotion, activation, rollback, autonomous implementation, and meta-improvement were unchanged and not exercised.",
    "Traced both active source paths before changing code. Moltbook and arXiv content survived retrieval transiently, then `_reduce_item` intentionally collapsed it into keyword and mechanism labels; persisted packets retained hashes but not the source assertion needed for a falsifiable claim.",
    "Added an immutable, source-grounded representation containing canonical identifiers, title and author/date metadata, retrieval time, bounded observed source text, exact location, content hashes, injection assessment, and explicit untrusted-evidence authority boundaries.",
    "Froze a fresh corpus before extractor tuning using a preregistered selection rule: the first ten eligible Moltbook records and first ten arXiv records in response order, with no relevance or claim-quality selection.",
    "Added zero-to-many structured claim extraction plus deterministic provenance checks and an independent tool-free semantic validation pass. Extraction and validation outputs remain separate and every accepted claim links to an exact supporting character span and source hash.",
    "The final fixed-corpus run processed twenty source records, extracted twenty-five claims, and validated all twenty-five without an extraction failure or unavailable source.",
    "All twenty-five concrete claims were classified CLAIM_SPECIFIC_NOT_LOCAL. Twelve source records were CLAIM_INCOMPLETE; eight arXiv records produced concrete non-local claims; no record produced a claim honestly testable with Hiro's current repository, runtime, evaluations, ordinary synthetic inputs, and available assets.",
    "The primary disposition is MIXED BOTTLENECK. The old representation destroyed concrete source information, and that extraction defect is now repaired; however, the current fixed discovery material still supplies zero operational local claims suitable for Phase 3A. Phase 3A should not resume yet."
  ],
  "workstreams": [
    {
      "title": "Pre-change information-loss trace",
      "status": "Completed",
      "details": [
        "Moltbook retrieval received sanitized public-post JSON containing source ID, title, a content excerpt, date, author information, and engagement. The transient parser retained only a subset and used a generic endpoint URL.",
        "arXiv retrieval received Atom entries containing canonical ID, title, abstract, publication metadata, authors, and link. The transient parser discarded authors and update time, shortened the title and abstract, and replaced the canonical item ID with a hash.",
        "The decisive loss occurred in `_reduce_item`, which used source prose only for keyword matching and then persisted a mechanism label, technique tuple, code-owned question, and hashes. The exact source claim was explicitly empty.",
        "Original assertions could not be recovered from persisted provenance alone. Recovery required a network refetch whose content could change or disappear.",
        "The loss was partly intentional prompt-injection isolation and partly an insufficient schema: content was prevented from becoming instruction, but evidence necessary for faithful claim extraction was also removed."
      ]
    },
    {
      "title": "Immutable source retention",
      "status": "Implemented",
      "details": [
        "Added a bounded source-record schema with source type, original identifier, source URL, title, authors, publication and retrieval timestamps, observed source field and response position, bounded source text, SHA-256 identities, truncation status, and injection assessment.",
        "The frozen corpus uses read-only JSON and a companion SHA-256 file. Its selection policy records that source order, not relevance or apparent testability, chose records before extraction existed.",
        "The Moltbook endpoint returned exactly five hundred observed characters for each selected post. Those excerpts were preserved faithfully and are not represented as complete posts.",
        "The arXiv parser now retains author and update metadata while preserving its existing XML entity rejection and approved-link boundary.",
        "Source text remains untrusted evidence with no authority to construct candidates, run experiments, request promotion, or change state."
      ]
    },
    {
      "title": "Source-grounded claim extraction",
      "status": "Implemented",
      "details": [
        "The extractor produces zero to five distinct claims per source and separates claim specificity from local feasibility.",
        "Claim fields include exact claim, intervention, baseline or comparison, outcome, metric or observable, conditions, direction, evidence type, confidence, testability state and reason, proposed measurable observable, and exact supporting excerpt.",
        "The explicit states are CLAIM_SPECIFIC_TESTABLE, CLAIM_SPECIFIC_NOT_LOCAL, CLAIM_INCOMPLETE, EXTRACTION_FAILED, and SOURCE_UNAVAILABLE.",
        "CLAIM_SPECIFIC_NOT_LOCAL is a successful extraction state, not a failure. A concrete paper result remains retained even when reproduction would require the authors' datasets, models, simulator, training pipeline, domain corpus, large-scale training, or specialized hardware.",
        "CLAIM_SPECIFIC_TESTABLE is intentionally strict: the claim must be falsifiable with Hiro's current repository, local model and runtime, existing evaluations, and ordinary synthetic inputs, without first recreating the source system."
      ]
    },
    {
      "title": "Independent provenance validation",
      "status": "Implemented",
      "details": [
        "Deterministic validation requires a verbatim contiguous excerpt, valid schema enumerations and confidence, complete provenance, correct hashes and offsets, and no unsupported numeric fact in the claim.",
        "Common arXiv LaTeX rendering for percentages and degrees is normalized only for comparison; the retained source bytes remain unchanged.",
        "A separate tool-free local-model operation assesses source support, material additions, field-to-claim agreement, and local-testability coherence. It cannot rewrite the source claim.",
        "Extractor output, validator output, deterministic reason codes, and the final provenance decision are all persisted independently in the immutable report.",
        "A claim is accepted only when the deterministic and independent semantic checks both pass."
      ]
    },
    {
      "title": "Observed boundary repairs",
      "status": "Completed",
      "details": [
        "The first run showed that the semantic model treated access to hypothetical external datasets or simulators as local testability. The minimum repair defined local availability concretely and allowed the independent validator to correct only the local-versus-non-local label.",
        "The next run showed that an overly strict extraction instruction collapsed concrete external claims into CLAIM_INCOMPLETE. The minimum repair made specificity independent of locality and required concrete non-local claims to be retained.",
        "A scholarly phrase about revealing token-level visual dependence triggered the credential-exfiltration detector. The minimum detector repair narrowed generic token matching while a paired test confirmed that an actual access-token exfiltration request remains rejected.",
        "One faithful numerical claim used ordinary percent and degree language while the source used LaTeX notation. The deterministic checker now recognizes those equivalent renderings without weakening semantic validation.",
        "Repeated reports originally shared the corpus timestamp and collided. Qualification reports now receive their own immutable qualification timestamp while continuing to reference the unchanged corpus hash."
      ]
    },
    {
      "title": "Final fixed-corpus result",
      "status": "Mixed bottleneck",
      "details": [
        "Twenty source records were processed: ten Moltbook post excerpts and ten arXiv abstracts.",
        "Twenty-five claims were extracted and all twenty-five passed deterministic and independent semantic provenance validation. Eight sources produced multiple valid claims.",
        "Source classifications were zero CLAIM_SPECIFIC_TESTABLE, eight CLAIM_SPECIFIC_NOT_LOCAL, twelve CLAIM_INCOMPLETE, zero EXTRACTION_FAILED, and zero SOURCE_UNAVAILABLE.",
        "Claim classifications were zero CLAIM_SPECIFIC_TESTABLE and twenty-five CLAIM_SPECIFIC_NOT_LOCAL.",
        "All ten Moltbook excerpts were incomplete. Eight arXiv abstracts yielded concrete non-local claims, while two arXiv abstracts remained too qualitative for claim extraction.",
        "No reproduction experiment, candidate, gate decision, promotion request, activation, or rollback was created."
      ]
    }
  ],
  "decisions": [
    "Freeze a fresh mixed corpus before extractor tuning and reuse the exact same corpus bytes for every qualification run.",
    "Do not select unusually easy sources or change discovery ranking to meet the five-claim target.",
    "Preserve concrete non-local claims rather than misclassifying them as incomplete or forcing them into analogous local hypotheses.",
    "Require exact source-span provenance plus an independent semantic decision; do not let the extraction operation self-certify.",
    "Treat source text as evidence only and retain explicit no-candidate, no-experiment, and no-promotion authority boundaries.",
    "Do not resume Phase 3A when the final corpus contains zero locally testable claims."
  ],
  "validation": [
    {
      "check": "Immutable qualification corpus",
      "status": "passed",
      "result": "Twenty records were frozen before extractor tuning: ten Moltbook and ten arXiv. The immutable corpus SHA-256 is f28447b47a7fcdac032acf0539fd6e93fb3e94fe8c5760d4acf2007493957b5b."
    },
    {
      "check": "Final source-claim qualification",
      "status": "passed",
      "result": "20 source records, 25 extracted claims, 25 validated claims, 8 sources with multiple claims, 0 extraction failures, and 0 unavailable sources. The immutable report SHA-256 is 873b9b32eb00612350f564f3b49294f1ae3e15bd05b1d120184900d086b0404a."
    },
    {
      "check": "Final classification integrity",
      "status": "passed",
      "result": "Source states: 0 testable, 8 specific non-local, 12 incomplete, 0 extraction failed, 0 unavailable. Claim states: 0 testable and 25 specific non-local."
    },
    {
      "check": "Focused Phase 3B tests",
      "status": "passed",
      "result": "27 focused tests passed, covering immutable hashes, source metadata, exact-span provenance, independent validation, numeric rendering, XML safety, and injection-detector controls."
    },
    {
      "check": "Full Hiro repository regression suite",
      "status": "passed",
      "result": "806 tests passed in 426.55 seconds. Six non-failing warnings concerned pre-existing unregistered test marks and an inaccessible pytest cache directory."
    },
    {
      "check": "Public journal tests and build",
      "status": "passed",
      "result": "npm run test:hiro passed. npm run build generated and validated 171 journal pages, compiled TypeScript, and completed the Vite production bundle. The clean checkout first required npm ci because dependencies were not installed; after the locked install both required commands passed."
    }
  ],
  "currentState": [
    "Phase 3B code is committed at revision bc7cd0098d9513455937bb80433e50738ca0a3ee.",
    "The exact source text is recoverable from the frozen corpus and every accepted claim links through its source record and character span to a content hash.",
    "The final extractor has no observed extraction or provenance-validation failure on the fixed corpus.",
    "No fixed-corpus claim is currently suitable for local Phase 3A reproduction without acquiring or recreating external research assets.",
    "Corroboration policy and the known-good promotion actuator remain unchanged."
  ],
  "limitations": [
    "The Moltbook public listing supplied five-hundred-character excerpts rather than complete posts, which likely contributes to all ten records being incomplete. This session did not change endpoints or discovery ranking.",
    "The fresh arXiv query returned strong empirical claims, but those claims concern external systems and assets rather than bounded interventions directly testable in Hiro.",
    "The semantic extraction and independent validation passes take several minutes for twenty records. Runtime optimization was outside this qualification scope.",
    "Model-based semantic judgments can vary, although exact source spans, hashes, deterministic validation, separate outputs, and the conservative local-availability definition bound that risk.",
    "No reproduction executor was built or run, so Phase 3A evidence acquisition remains unqualified."
  ],
  "nextSteps": [
    "Do not automatically resume Phase 3A; it currently lacks an adequate locally testable source claim.",
    "In a separate authorized task, improve discovery-source selection or retrieval depth so source records contain concrete interventions relevant to Hiro's existing software and evaluation environment.",
    "Keep the frozen Phase 3B corpus as a regression set so future discovery changes cannot reintroduce source-information collapse.",
    "Once at least several faithfully extracted local claims exist, hand those immutable claim packages to Phase 3A without changing corroboration semantics."
  ],
  "disclosureNote": "This public entry contains no credentials, private source text, private interaction content, local filesystem locations, private network addresses, or actionable unresolved security details."
}
