{
  "schemaVersion": "1.0",
  "recordType": "evidence-atlas-roadmap",
  "updated": "2026-09-03",
  "status": "active-reviewed-roadmap",
  "claimCeiling": "This roadmap records intended work and review decisions. It does not establish that an undiscovered relationship exists, that a proposed relationship is correct, or that the Atlas improves research outcomes.",
  "currentBaseline": {
    "asOf": "2026-09-06",
    "releaseCount": 59,
    "methodCount": 13,
    "clusterCount": 46,
    "lineageCount": 5,
    "acceptedRelationshipCount": 428,
    "publishedProposalCount": 4,
    "relationshipComposition": {
      "usesMethodCount": 316,
      "clusterMembershipCount": 61,
      "lineageMembershipCount": 15,
      "directInterReleaseCount": 36,
      "defaultProgrammeViewCount": 112
    },
    "methodPrevalenceChecks": [
      {
        "methodId": "adversarial-controls",
        "releaseAssignmentCount": 51
      },
      {
        "methodId": "structural-compression",
        "releaseAssignmentCount": 48
      }
    ],
    "sourceRefs": [
      "data/RELATIONSHIP_REGISTRY.json",
      "data/METHOD_REGISTRY.json",
      "papers/*/meta.json",
      "data/atlas-proposals/*.json"
    ]
  },
  "principles": [
    "Keep asserted, computed and proposed relationships machine-readably distinct.",
    "Do not infer correctness, novelty, priority, influence, independence or impact from graph geometry, proximity or similarity.",
    "Require resolvable evidence, an inference limit and additive review history for every proposal decision.",
    "Retain rejected and superseded proposals as negative knowledge once the proposal layer is activated.",
    "Keep machine access independent of the interactive renderer."
  ],
  "nextSteps": [
    {
      "id": "atlas-step-proposal-intake",
      "priority": 1,
      "state": "complete",
      "title": "Implement fail-closed proposal intake and review receipts",
      "purpose": "Give people and agents a safe place to nominate relationships without adding them to the accepted graph.",
      "dependencies": [],
      "deliverables": [
        "A deterministic proposal validator and submission format.",
        "Content-derived proposal identifiers and resolvable evidence references.",
        "Append-only review receipts for awaiting-review, accepted-as-asserted, rejected and superseded states.",
        "Negative controls for unresolved endpoints, unknown predicates, missing evidence and accidental promotion."
      ],
      "acceptanceCriteria": [
        "A valid proposal is published only in the proposal register and never in the accepted edge array.",
        "Invalid, incomplete and self-promoting proposals are rejected deterministically.",
        "A review decision records reviewer provenance, basis, inference limit, date and predecessor state.",
        "Rejected and superseded records remain retrievable."
      ],
      "stopConditions": [
        "Stop if proposal history cannot remain append-only or if review provenance cannot be represented without overwriting prior states.",
        "Stop if any ingestion route can write directly to the accepted graph."
      ]
    },
    {
      "id": "atlas-step-projection-calibration",
      "priority": 2,
      "state": "complete",
      "title": "Calibrate projection weight and taxonomy legibility",
      "purpose": "Make the first visual impression distinguish direct inter-release evidence from registry-derived navigation and make broad, low-discrimination labels visibly interpretable.",
      "dependencies": [],
      "deliverables": [
        "A tested direct-inter-release projection alongside the research-structure and method views.",
        "Visible working-taxonomy status, edge-composition counts and method prevalence.",
        "A documented lineage eligibility rule requiring a reciprocal lineage identifier and, for a non-root member, an evidential parent link.",
        "A design note on representing machine-checked reciprocity as an evidence attribute rather than a replacement for knowledge status."
      ],
      "acceptanceCriteria": [
        "The initial projection does not make registry-derived density appear to be direct inter-release evidence.",
        "Ubiquitous methods and singleton clusters carry enough prevalence or scope context to prevent over-interpretation.",
        "Every projection reconciles exactly with the canonical graph and preserves the complete nonvisual register."
      ],
      "stopConditions": [
        "Do not remove programme or method navigation merely to make the graph look sparse.",
        "Stop if a projection requires a second relationship ontology or changes accepted graph semantics."
      ]
    },
    {
      "id": "atlas-step-discovery-pilot",
      "priority": 3,
      "state": "ready",
      "title": "Run a bounded relationship-discovery pilot",
      "purpose": "Test whether multiple transparent retrieval routes can nominate useful hidden connections at a tolerable false-proposal burden.",
      "dependencies": [
        "atlas-step-proposal-intake"
      ],
      "deliverables": [
        "A frozen-corpus candidate generator using separately reported citation, symbolic, shared-object and semantic-retrieval routes.",
        "Route-specific evidence rather than one opaque credibility score.",
        "A proposal-only output with no power to modify accepted relationships."
      ],
      "acceptanceCriteria": [
        "A frozen hidden-link benchmark and lexically similar negative controls are registered before evaluation.",
        "Recovery, false-proposal burden and reviewer time are reported separately.",
        "Every candidate includes the strongest plausible non-relationship explanation."
      ],
      "stopConditions": [
        "Stop if the benchmark cannot be frozen independently of the generator.",
        "Stop if candidate generation cannot be isolated from accepted graph production.",
        "Stop or narrow the route if review burden outweighs useful recoveries."
      ]
    },
    {
      "id": "atlas-step-review-workbench",
      "priority": 4,
      "state": "in-progress",
      "title": "Add a proposal-review workbench",
      "purpose": "Let reviewers inspect a proposed edge, its evidence, contrary explanation and full decision history without confusing it with accepted knowledge.",
      "dependencies": [
        "atlas-step-proposal-intake"
      ],
      "deliverables": [
        "A distinct proposals view with accessible nonvisual records.",
        "Filters for awaiting-review, accepted, rejected and superseded proposals.",
        "Links from every decision to source artefacts and review receipts."
      ],
      "acceptanceCriteria": [
        "Proposal state is visible in text, structure and machine data, not colour alone.",
        "No proposal geometry or ranking is described as evidence.",
        "The accepted graph remains usable when the proposal layer is unavailable."
      ],
      "stopConditions": [
        "Stop if the interface visually collapses proposed and accepted relationships.",
        "Stop if a no-JavaScript or nonvisual reviewer cannot retrieve the same decision record."
      ]
    },
    {
      "id": "atlas-step-agent-queries",
      "priority": 5,
      "state": "watch",
      "title": "Add bounded agent query surfaces when use cases justify them",
      "purpose": "Reduce token and reconstruction cost for agents seeking neighbourhoods, dependencies, methods or unresolved proposals without replacing the canonical graph export.",
      "dependencies": [],
      "deliverables": [
        "Documented filtered-query patterns or endpoints with stable identifiers and pagination.",
        "Responses that always carry source pointers, status and inference limits."
      ],
      "acceptanceCriteria": [
        "A demonstrated agent task is materially cheaper than retrieving the complete graph.",
        "Filtered responses reconcile exactly with the canonical graph and proposal register."
      ],
      "stopConditions": [
        "Defer while the complete graph remains small and cheaper to retrieve.",
        "Stop if query convenience creates a second semantic source of truth."
      ]
    },
    {
      "id": "atlas-step-scale-renderer",
      "priority": 6,
      "state": "watch",
      "title": "Reassess the renderer at catalogue scale",
      "purpose": "Preserve usable navigation as the graph grows without making a visualization library part of the evidence model.",
      "dependencies": [],
      "deliverables": [
        "Repeated desktop, mobile, keyboard and performance comparisons against the dependency-free SVG.",
        "A bounded evaluation of Cytoscape.js or Sigma.js plus Graphology only if thresholds are crossed."
      ],
      "acceptanceCriteria": [
        "The current renderer remains the default until measured usability or performance degrades.",
        "Any replacement consumes the same canonical JSON and preserves the nonvisual register."
      ],
      "stopConditions": [
        "Do not migrate for aesthetic preference alone.",
        "Reassess when visible nodes exceed 250, interaction latency becomes material, or accessibility regresses."
      ]
    },
    {
      "id": "atlas-step-outcome-evaluation",
      "priority": 7,
      "state": "ready",
      "title": "Measure whether the Atlas reduces rediscovery and reconstruction cost",
      "purpose": "Test the Atlas as a research tool without inferring value from page views, graph size or proposal volume.",
      "dependencies": [],
      "deliverables": [
        "Prospective records of qualifying discovery, replay, reuse, abandoned duplicate routes and reviewer effort.",
        "A comparison plan aligned with the open-evidence-reuse hypothesis in the IBE ledger."
      ],
      "acceptanceCriteria": [
        "Qualifying outcomes, comparator, observation window and missingness are registered before analysis.",
        "Producer use, unaffiliated use and superficial mentions remain separate.",
        "Null, adverse and abandoned outcomes remain in the denominator."
      ],
      "stopConditions": [
        "Do not claim research acceleration from traffic, catalogue growth or internal reuse alone.",
        "Stop causal interpretation if selection, visibility and correlated lineage reuse cannot be addressed."
      ]
    }
  ],
  "reviewPolicy": {
    "cadence": "Review on maintainer request and at least monthly while active; also review after five added releases, the first submitted proposal, a material objection or correction, or a renderer threshold event.",
    "nextScheduledReview": "2026-09-15",
    "triggers": [
      "maintainer-request",
      "five-releases-added",
      "proposal-submitted",
      "material-objection-or-correction",
      "renderer-threshold-crossed",
      "monthly-review-due"
    ],
    "checklist": [
      "Rebuild the graph and compare release, method, cluster, lineage, accepted-edge and proposal counts with the prior review.",
      "Confirm every release and accepted relationship still resolves to its declared source record.",
      "Sample accepted edges across predicates and recheck basis and inference limits against source artefacts.",
      "Inspect every new, awaiting, rejected and superseded proposal without promoting similarity to fact.",
      "Review new external citations, objections, corrections and reproductions that may change a relationship basis.",
      "Assess accessibility, mobile layout, graph performance and agent retrieval cost.",
      "Record decisions, unresolved questions, observed regressions and one exact next action in a new review-log entry."
    ],
    "recordRule": "Append a dated review-log entry. Do not rewrite a prior review, delete a rejected proposal, or change an accepted relationship without the repository's normal additive evidence and publication gates."
  },
  "reviewLog": [
    {
      "reviewId": "atlas-review-2026-08-15-baseline",
      "reviewedAt": "2026-08-15",
      "trigger": "initial-roadmap-record",
      "reviewer": "Evidence Press producer workflow",
      "provenanceNote": "Producer-side baseline review against the repository source graph and publication gates.",
      "baseline": {
        "releaseCount": 28,
        "acceptedRelationshipCount": 175,
        "publishedProposalCount": 0
      },
      "observations": [
        "The first source-driven Atlas is live with accepted edges generated from declared repository records.",
        "The proposal register is structurally present but empty.",
        "No discovery model or similarity route currently contributes accepted or proposed relationships.",
        "The current graph remains below the renderer reassessment threshold."
      ],
      "decision": "continue",
      "nextAction": "Implement fail-closed proposal intake, validation and append-only review receipts before running relationship-discovery experiments."
    },
    {
      "reviewId": "atlas-review-2026-08-15-fable-comment",
      "reviewedAt": "2026-08-15",
      "trigger": "user-supplied-external-model-comment",
      "reviewer": "Anthropic Fable, as identified by the maintainer",
      "provenanceNote": "The maintainer supplied the review text. The exact model version, prompt and run record were not independently established.",
      "baseline": {
        "releaseCount": 28,
        "acceptedRelationshipCount": 175,
        "publishedProposalCount": 0
      },
      "observations": [
        "The reviewer independently reconciled 13 methods, 13 clusters, 2 lineages, 28 release assignments and all 175 accepted edges from the public registry and Atlas.",
        "The current default programme projection already excludes 135 uses-method edges, but 35 of its 40 visible edges are cluster or lineage memberships and only 5 are direct inter-release links.",
        "The prevalence concern is supported by the source registry: adversarial-controls is assigned to 20 of 28 releases and structural-compression to 18 of 28.",
        "The proposed Polydegree lineage is not eligible under the registered rule because the successor declares an evidential parent link but its reciprocal lineageId is null; the public explanation should surface that rule.",
        "A reciprocity check could add useful evidence, but reciprocity should remain separate from the asserted, computed and proposed knowledge-status axis."
      ],
      "decision": "change-priority",
      "nextAction": "Keep fail-closed proposal intake first, then test an evidence-calibrated projection and surface taxonomy status, prevalence and lineage eligibility before the discovery pilot."
    },
    {
      "reviewId": "atlas-review-2026-08-15-sol-projection",
      "reviewedAt": "2026-08-15",
      "trigger": "user-supplied-same-system-review",
      "reviewer": "OpenAI Sol instance, as identified by the maintainer",
      "provenanceNote": "The maintainer supplied the review text. This is a same-system-family design review, not independent scientific assurance; the exact model version, prompt and run record were not independently established.",
      "baseline": {
        "releaseCount": 28,
        "acceptedRelationshipCount": 175,
        "publishedProposalCount": 0
      },
      "observations": [
        "The reviewer reconciled the accepted graph as 135 method assignments, 28 cluster memberships, 7 lineage memberships and 5 direct inter-release links.",
        "The existing dense projection could visually overstate substantive inter-release relationship coverage even though the explanatory boundaries were accurate.",
        "The reviewer recommended a first-class Direct links projection, a visible relationship-composition disclosure, method prevalence and explicit singleton cluster-seed labels.",
        "The reviewer recommended public source-declared wording while retaining the canonical asserted machine status, and a missingness panel that does not treat absent edges as evidence of no relationship."
      ],
      "decision": "complete",
      "nextAction": "Keep proposal intake as the first incomplete roadmap step, then test bounded discovery only after proposal quarantine and additive review receipts are operational."
    },
    {
      "reviewId": "atlas-review-2026-08-15-proposal-intake",
      "reviewedAt": "2026-08-15",
      "trigger": "proposal-submitted",
      "reviewer": "Evidence Press producer workflow",
      "provenanceNote": "Producer-side implementation and hostile-control review by the maintainer-agent workflow; not independent scientific assurance or an assessment of the proposal's novelty, importance or tractability.",
      "baseline": {
        "releaseCount": 28,
        "acceptedRelationshipCount": 175,
        "publishedProposalCount": 1
      },
      "observations": [
        "A separate proposal policy, per-proposal source format, assembled register and two public JSON schemas now exist without changing the accepted research graph.",
        "Proposal and decision-receipt identities are content-derived; review receipts form a predecessor-bound state chain and terminal records remain retrievable.",
        "The first proposal is awaiting review with novelty, importance and tractability unassessed; maintainer interest was not converted into a positive assessment.",
        "Hostile controls reject unresolved anchors, unsafe source references, silent identity mutation, broken receipt chains, direct accepted-edge fields and accepted-relationship status promotion.",
        "The Atlas includes a visually distinct proposal projection, complete nonvisual register and structured GitHub issue intake; issue content remains untrusted until normalized and validated."
      ],
      "decision": "complete",
      "nextAction": "Publish and read back the proposal layer through the normal two-commit Evidence Press gate before beginning any bounded relationship-discovery pilot."
    },
    {
      "reviewId": "atlas-review-2026-08-16-first-external-intake-batch",
      "reviewedAt": "2026-08-16",
      "trigger": "proposal-submitted",
      "reviewer": "Evidence Press producer workflow",
      "provenanceNote": "Producer-side normalization review of three public GitHub issues submitted by the maintainer with an Anthropic Claude agent. This records structurally valid intake, not independent verification of cited claims or a positive novelty, importance or tractability assessment.",
      "baseline": {
        "releaseCount": 28,
        "acceptedRelationshipCount": 175,
        "publishedProposalCount": 4
      },
      "observations": [
        "Issues 91, 92 and 93 contain every required issue-form field and both submission-boundary declarations.",
        "Each issue was normalized into a content-derived awaiting-review record that retains its public issue URL and reported human-agent provenance.",
        "Novelty, importance and tractability remain unassessed; no decision receipt has been added and the accepted graph remains unchanged.",
        "The issue template's requested atlas-proposal label had not existed, so GitHub omitted it; the label was created and applied to all three issues.",
        "Because GitHub issue submission requires a signed-in GitHub account, the proposal policy now also exposes the existing AgentMail inbox as an untrusted no-GitHub email route feeding the same normalization gate."
      ],
      "decision": "continue",
      "nextAction": "Publish and read back the four-record register and no-GitHub email route, then review the three new proposals separately without promoting intake completeness to scientific endorsement."
    },
    {
      "reviewId": "atlas-review-2026-08-16-fable-corpus-errors",
      "reviewedAt": "2026-08-16",
      "trigger": "proposal-reviewed",
      "reviewer": "Evidence Press producer workflow",
      "provenanceNote": "Producer-side corpus review of Fable issues 91 to 93, with direct inspection of the current manuscript, Evidence Press copy and primary public sources. This is not independent mathematical review, a complete antecedent audit or an endorsement of the unresolved proposal.",
      "baseline": {
        "releaseCount": 28,
        "acceptedRelationshipCount": 175,
        "publishedProposalCount": 4
      },
      "observations": [
        "Issue 91 identified a real discovery-copy scope error: the manuscript theorem is architecture-relative, while several Evidence Press summary sentences could be read as global claims about all higher-degree counterexample families.",
        "The reducible-incidence discovery copy now states the exact untrimmed positive-degree normalized two-factor scope and cites Gallagher, Gao, Shaska and Huq-Kuruvilla without asserting equivalence or inequivalence.",
        "Issue 92 triggered the original decision-sufficiency proposal's declared duplication stop rule; the programme is deferred pending direct comparison with the closest antecedents and a narrower Pearl-Manski junction test.",
        "Issues 91 and 92 are recorded as merged through additive hash-bound receipts. Issue 93 remains awaiting review because it is a research question, not a demonstrated corpus error.",
        "No accepted research-graph edge was added, and no manuscript theorem or proof conclusion was changed."
      ],
      "decision": "complete",
      "nextAction": "Keep the Recht-Re target-sufficiency comparison quarantined until its exact cheap falsifier is run; revisit the deferred decision-sufficiency programme only after direct antecedent comparison identifies a defensible residue."
    },
    {
      "reviewId": "atlas-review-2026-08-21-versioned-cluster-successor",
      "reviewedAt": "2026-08-21",
      "trigger": "material-objection-or-correction",
      "reviewer": "Evidence Press producer workflow",
      "provenanceNote": "Producer-side governance review triggered by the cyclicity-support-fusion-atlas v0.6 corrective successor. This is a registry-integrity review, not mathematical verification, external specialist assessment or evidence of Atlas impact.",
      "baseline": {
        "releaseCount": 30,
        "acceptedRelationshipCount": 200,
        "publishedProposalCount": 4
      },
      "observations": [
        "The published v0.5 bounded-atlas cluster could not be rewritten when the same canonical release slug advanced to a separately tagged all-degree successor.",
        "The registry policy already required a new identifier or dated successor, but the validator rejected all duplicate membership and therefore made that policy route impossible.",
        "The schema now permits an explicit supersedes and effectiveDate pair; validation requires the target to be the active earlier cluster and the release-member set to match exactly.",
        "The research graph retains both the historical and active cluster nodes, labels their supersession state, and adds one registry-derived cluster-membership edge. No direct scientific relationship or impact evidence was added.",
        "The current graph reconciles to 151 method assignments, 31 cluster memberships, 10 lineage memberships and 8 direct inter-release links."
      ],
      "decision": "complete",
      "nextAction": "Keep versioned cluster succession rare and require the same explicit chain whenever a corrective successor changes a published cluster boundary without changing the canonical release slug."
    },
    {
      "reviewId": "atlas-review-2026-08-21-amplitude-laurent-successor",
      "reviewedAt": "2026-08-21",
      "trigger": "material-objection-or-correction",
      "reviewer": "Evidence Press producer workflow",
      "provenanceNote": "Producer-side registry reconciliation for the cyclicity-support-fusion-atlas v0.7 corrective successor. This records graph conformance only; it is not mathematical verification, novelty assessment, specialist review or evidence of research impact.",
      "baseline": {
        "releaseCount": 30,
        "acceptedRelationshipCount": 201,
        "publishedProposalCount": 4
      },
      "observations": [
        "The v0.7 combined successor extends the same canonical release from fixed-seed periods to arbitrary polynomial amplitudes, specified zero-cycles, endpoint moments for every q(P) at most 3, and exact input-dependent Laurent channels.",
        "The v0.5 and v0.6 cluster records remain intact; a dated successor cluster preserves their published meanings while exposing the widened v0.7 scope.",
        "The accepted graph gains exactly one registry-derived cluster-membership edge and no new direct scientific, lineage or citation edge.",
        "The current graph reconciles to 151 method assignments, 32 cluster memberships, 10 lineage memberships and 8 direct inter-release links, for 201 accepted relationships."
      ],
      "decision": "complete",
      "nextAction": "Retain the finite endpoint-atlas versus input-dependent Laurent-criterion boundary in future registry and Atlas descriptions; do not infer a finite all-Laurent classification from the successor cluster."
    },
    {
      "reviewId": "atlas-review-2026-08-22-three-item-jrp-candidate",
      "reviewedAt": "2026-08-22",
      "trigger": "maintainer-request",
      "reviewer": "Evidence Press producer workflow",
      "provenanceNote": "Producer-side registry reconciliation for the certified exact three-item JRP candidate after its journal-like internal review and deterministic repair closure. This records graph conformance only; it is not independent peer review, field validation, proof of logistics savings or evidence of research impact.",
      "baseline": {
        "releaseCount": 31,
        "acceptedRelationshipCount": 214,
        "publishedProposalCount": 4
      },
      "observations": [
        "The candidate adds one release, one exact-certification method cluster and one evidence-backed joint-replenishment lineage rooted at the earlier certified two-item release.",
        "The accepted graph gains nine method assignments, one cluster membership, two lineage memberships and one direct result-extension edge; no proposal was promoted into the accepted graph.",
        "The current graph reconciles to 160 method assignments, 33 cluster memberships, 12 lineage memberships and 9 direct inter-release links, for 214 accepted relationships.",
        "The release metadata preserves separate ceilings for exact finite certificate replay and real-world logistics evaluation; graph membership does not convert the synthetic-model gap into a field-savings claim.",
        "The Atlas baseline and reader-facing composition disclosure were advanced together, while all earlier review records remain unchanged."
      ],
      "decision": "complete",
      "nextAction": "Keep the three-item result inside its exact certificate and synthetic-model scope until an independently governed operational pilot supplies measured field outcomes."
    },
    {
      "reviewId": "atlas-review-2026-08-23-full-e4-polydegree-column",
      "reviewedAt": "2026-08-23",
      "trigger": "maintainer-request",
      "reviewer": "Evidence Press producer workflow",
      "provenanceNote": "Producer-side registry reconciliation for the full e=4 polydegree-column candidate after deterministic replay, internal journal-like review and public repository and archive freezing. This records graph conformance only; it is not independent peer review, priority adjudication, proof of Furter R(3), proof of monotone rigidity or evidence of research impact.",
      "baseline": {
        "releaseCount": 32,
        "acceptedRelationshipCount": 221,
        "publishedProposalCount": 4
      },
      "observations": [
        "The candidate adds one release and one singleton method cluster for its Fourier, exact-computation, formal-algebra and conditional boundary-transfer bundle.",
        "The accepted graph gains six method assignments and one cluster membership; no proposal, lineage membership or direct result-extension edge is added.",
        "A reuses-method parent link records the bounded methodological precedent from the earlier full e=3 candidate without using that theorem as a premise or treating the two producer-side packages as independent confirmation.",
        "The current graph reconciles to 166 method assignments, 34 cluster memberships, 12 lineage memberships and 9 direct inter-release links, for 221 accepted relationships.",
        "The release metadata keeps the all-d polydegree theorem separate from Furter R(3), monotone rigidity, the two-dimensional Jacobian conjecture and the quartic Hessian conjecture."
      ],
      "decision": "complete",
      "nextAction": "Seek independent specialist review of the all-degree certificate and the conditional boundary bridge before making novelty, priority or conjecture-resolution claims."
    },
    {
      "reviewId": "atlas-review-2026-08-24-txgraffiti-order48-successor",
      "reviewedAt": "2026-08-24",
      "trigger": "maintainer-request",
      "reviewer": "Evidence Press producer workflow",
      "provenanceNote": "Producer-side registry reconciliation for the order-48 TxGraffiti successor after deterministic replay, internal model-mediated review and immutable GitHub and Zenodo publication. This records graph conformance only; it is not independent mathematical verification, specialist review, proof of global minimality or evidence of research impact.",
      "baseline": {
        "releaseCount": 33,
        "acceptedRelationshipCount": 231,
        "publishedProposalCount": 4
      },
      "observations": [
        "The candidate adds one release, one bounded certificate cluster and one evidence-backed TxGraffiti counterexample-order lineage rooted at the legacy 50-vertex release.",
        "The accepted graph gains six method assignments, one cluster membership, two lineage memberships and one direct result-extension edge; no proposal is promoted into the accepted graph.",
        "The current graph reconciles to 172 method assignments, 35 cluster memberships, 14 lineage memberships and 10 direct inter-release links, for 231 accepted relationships.",
        "The parent link records a genuine smaller-object continuation while preserving that the parent and child share producer provenance and certificate architecture and therefore are not independent confirmation.",
        "The release metadata keeps the constructive order-48 upper bound separate from global minimality, uniqueness, priority, external assurance and impact."
      ],
      "decision": "complete",
      "nextAction": "Seek an unaffiliated exact-object rerun, a separately authored checker, external graph-theory review and an independently specified search below order 48 before making minimality, uniqueness or priority claims."
    },
    {
      "reviewId": "atlas-review-2026-08-24-s6-extension-results-candidate",
      "reviewedAt": "2026-08-24",
      "trigger": "maintainer-request",
      "reviewer": "Evidence Press producer workflow",
      "provenanceNote": "Producer-side registry reconciliation for the S6 extension candidate after deterministic replay, internal model-mediated review and immutable GitHub and Zenodo publication. This records graph conformance only; it is not verification of the source construction, independent mathematical reconstruction, specialist review, priority adjudication or evidence of research impact.",
      "baseline": {
        "releaseCount": 34,
        "acceptedRelationshipCount": 237,
        "publishedProposalCount": 4
      },
      "observations": [
        "The candidate adds one release and one bounded singleton cluster for conditional geometry and executable adjudication around an external claimed complex structure on S6.",
        "The accepted graph gains five method assignments and one cluster membership; no proposal, internal lineage membership or direct inter-release edge is added.",
        "The current graph reconciles to 177 method assignments, 36 cluster memberships, 14 lineage memberships and 10 direct inter-release links, for 237 accepted relationships.",
        "The external source link is retained in the release operating record without converting topical dependence into Evidence Press research lineage or independent confirmation.",
        "The release metadata keeps exact arithmetic and symbolic replay, standalone written arguments, source-conditional geometric consequences and open problems in distinct claim classes."
      ],
      "decision": "complete",
      "nextAction": "Seek external specialist adjudication of the conductor-adjoint criterion and independent reconstruction of the source construction and Hodge calculation before promoting any conditional result or source claim."
    },
    {
      "reviewId": "atlas-review-2026-08-28-amplitude-modules-fused-support-bautin-bound",
      "reviewedAt": "2026-08-28",
      "trigger": "maintainer-request",
      "reviewer": "Evidence Press producer workflow",
      "provenanceNote": "Producer-side registry reconciliation for the anonymous amplitude-modules, fused-support and ordinary coefficient-Bautin theorem candidate after exact replay, internal model-mediated editorial repair and immutable GitHub and Zenodo publication. This records graph conformance only; it is not independent mathematical validation, external specialist review, priority adjudication or evidence of research impact.",
      "baseline": {
        "releaseCount": 36,
        "acceptedRelationshipCount": 252,
        "publishedProposalCount": 4
      },
      "observations": [
        "The candidate adds one release and one bounded singleton cluster for two Atlas-family all-amplitude classifications and one ordinary coefficient-Bautin theorem candidate.",
        "The accepted graph gains six method assignments, one cluster membership and one append-only cyclicity-programme lineage membership; no proposal is promoted and no direct inter-release edge is added.",
        "The current graph reconciles to 189 method assignments, 38 cluster memberships, 15 lineage memberships and 10 direct inter-release links, for 252 accepted relationships.",
        "The Atlas parent supplies a declared proof architecture and evidential dependency, so lineage reuse is recorded without treating the child as independent confirmation of the parent.",
        "The release metadata preserves the anonymous unrefereed-candidate, alternative-Bautin-convention, historical-open-problem, real-limit-cycle, external-assurance, priority and no-impact boundaries."
      ],
      "decision": "complete",
      "nextAction": "Seek unaffiliated proof reconstruction and a separately authored implementation of the support, fused-module and Bautin mechanisms, together with an authoritative source-convention audit for b(m)."
    },
    {
      "reviewId": "atlas-review-2026-08-28-o01d0-polar-fibre-structural-reductions",
      "reviewedAt": "2026-08-28",
      "trigger": "maintainer-request",
      "reviewer": "Evidence Press producer workflow",
      "provenanceNote": "Producer-side registry reconciliation for the O-01d0 polar-fibre structural-reductions candidate after paired replay, internal model-mediated review, immutable GitHub release, public CI, and Zenodo publication. This records graph conformance only; it is not proof of O-01d0, independent mathematical reconstruction, specialist review, priority adjudication, or evidence of research impact.",
      "baseline": {
        "releaseCount": 37,
        "acceptedRelationshipCount": 261,
        "publishedProposalCount": 4
      },
      "observations": [
        "The candidate adds one release and one bounded Hermite-boundary and falsification cluster; its explicit LPS parent remains a direct dependency rather than a retrospectively created formal lineage.",
        "Relative to the amplitude-modules baseline, the accepted graph gains eight method assignments and one cluster membership; the direct inter-release projection remains at 10 accepted edges under the current graph construction.",
        "The combined graph reconciles to 197 method assignments, 39 cluster memberships, 15 lineage memberships and 10 direct inter-release links, for 261 accepted relationships across 37 releases.",
        "Adversarial controls now occur in 29 of 37 release assignments and structural compression in 26 of 37; both prevalence labels remain registry-derived navigation rather than evidence of efficacy.",
        "The successor's parent metadata preserves shared-producer and shared-defect risk, so programme continuation is not presented as independent confirmation."
      ],
      "decision": "complete",
      "nextAction": "Seek an unaffiliated reconstruction of the Hermite reduction and squarefreeness proof, then a proof-or-falsification attempt on the pair-content/four-factor theorem before any O-01d0 or linked-conjecture promotion."
    },
    {
      "reviewId": "atlas-review-2026-08-29-source-supported-doi-edges",
      "reviewedAt": "2026-08-29",
      "trigger": "material-objection-or-correction",
      "reviewer": "Evidence Press producer workflow",
      "provenanceNote": "Producer-side registry-integrity review of exact DOI references already authored in release related-work records. This records source resolution only; it does not infer influence, priority, novelty, correctness, independence or impact.",
      "baseline": {
        "releaseCount": 37,
        "acceptedRelationshipCount": 287,
        "publishedProposalCount": 4
      },
      "observations": [
        "The graph extractor previously recognized internal release-page URLs but did not resolve exact DOI URLs that identify another Evidence Press release.",
        "Twenty-six existing related-work records now resolve through an exact normalized DOI index, with a frozen regression fixture and a hostile near-match rejection.",
        "The current graph reconciles to 197 method assignments, 39 cluster memberships, 15 lineage memberships and 36 direct inter-release records, for 287 accepted relationships.",
        "Of the 36 direct records, 29 are authored related-work citations and seven are authored parent links; no similarity-based or speculative relationship was added.",
        "The proposal-review workbench is now marked in progress because the proposal table and inspector exist while the promised proposal-state filters remain incomplete."
      ],
      "decision": "change-priority",
      "nextAction": "Complete the proposal-state filters and retain exact DOI resolution as a source-only extraction rule; do not extend it to fuzzy citation matching without a quarantined proposal route."
    },
    {
      "reviewId": "atlas-review-2026-08-29-odd-order-popular-difference-counterexample",
      "reviewedAt": "2026-08-29",
      "trigger": "maintainer-request",
      "reviewer": "Evidence Press producer workflow",
      "provenanceNote": "Producer-side registry reconciliation for the anonymous odd-order one-third popular-differences candidate after exact cross-language replay, mutation controls, internal review, immutable GitHub release, public CI, and Zenodo publication. This records graph conformance only; it is not independent mathematical reconstruction, external specialist review, exhaustive novelty, priority adjudication, proof that 2/5 is sharp, or evidence of research impact.",
      "baseline": {
        "releaseCount": 38,
        "acceptedRelationshipCount": 294,
        "publishedProposalCount": 4
      },
      "observations": [
        "The candidate adds one release and one bounded three-layer popular-difference counterexample cluster without creating a formal Evidence Press research lineage.",
        "Relative to the source-supported DOI baseline, the accepted graph gains six method assignments and one cluster membership; no proposal is promoted and the direct inter-release projection remains at 36 authored records.",
        "The current graph reconciles to 203 method assignments, 40 cluster memberships, 15 lineage memberships and 36 direct inter-release records, for 294 accepted relationships across 38 releases.",
        "Adversarial controls now occur in 30 of 38 release assignments and structural compression in 27 of 38; both prevalence labels remain registry-derived navigation rather than evidence of efficacy.",
        "The external AIM parent fixes the problem statement and attribution only; it does not validate the C21 witness, the three-layer proof, novelty, priority, the open 2/5 endpoint, or the Evidence Press workflow."
      ],
      "decision": "complete",
      "nextAction": "Seek an unaffiliated additive-combinatorics reconstruction and specialist novelty audit, then investigate the 2/5 endpoint and witness minimality without promoting the present PASS_WITH_NOTES claim ceiling."
    },
    {
      "reviewId": "atlas-review-2026-08-29-extremes-do-not-always-maximise",
      "reviewedAt": "2026-08-29",
      "trigger": "maintainer-request",
      "reviewer": "Evidence Press producer workflow",
      "provenanceNote": "Producer-side registry reconciliation for the anonymous four-state monotone row-diameter candidate after exact replay, negative controls, internal review, immutable GitHub release, public CI and Zenodo publication. This records graph conformance only; it is not independent mathematical reconstruction, external specialist review, exhaustive novelty, priority adjudication, resolution of the zero-field Ising question, or evidence of research impact.",
      "baseline": {
        "releaseCount": 39,
        "acceptedRelationshipCount": 300,
        "publishedProposalCount": 4
      },
      "observations": [
        "The candidate adds one release and one bounded four-state monotone row-diameter counterexample cluster without creating a formal Evidence Press research lineage.",
        "Relative to the odd-order popular-differences baseline, the accepted graph gains five method assignments and one cluster membership; no proposal is promoted and the direct inter-release projection remains at 36 authored records.",
        "The current graph reconciles to 208 method assignments, 41 cluster memberships, 15 lineage memberships and 36 direct inter-release records, for 300 accepted relationships across 39 releases.",
        "Adversarial controls now occur in 31 of 39 release assignments and structural compression in 28 of 39; both prevalence labels remain registry-derived navigation rather than evidence of efficacy.",
        "The AIM source fixes the separately quantified general monotone-reversible question only; it does not validate the four-state proof, settle the all-graph zero-field clause or diagnostics 1.6(2-3), establish novelty or priority, or provide independent assurance."
      ],
      "decision": "complete",
      "nextAction": "Seek an unaffiliated Markov-chain reconstruction and lawful full-text comparison with the closest coefficient-of-ergodicity antecedent, then investigate the all-graph zero-field question without promoting the present PASS_WITH_NOTES claim ceiling."
    },
    {
      "reviewId": "atlas-review-2026-08-30-negative-square-energy-five-vertex-valley",
      "reviewedAt": "2026-08-30",
      "trigger": "maintainer-request",
      "reviewer": "Evidence Press producer workflow",
      "provenanceNote": "Producer-side registry reconciliation for the anonymous five-vertex negative square-energy valley candidate after quantifier repair, exact Python and JavaScript replay, mutation controls, internal review, immutable GitHub release, public CI and Zenodo publication. This records graph conformance only; it is not unaffiliated mathematical reconstruction, formal verification, external specialist review, exhaustive novelty, priority adjudication, resolution of either favourable-order existential formulation, or evidence of research impact.",
      "baseline": {
        "releaseCount": 40,
        "acceptedRelationshipCount": 307,
        "publishedProposalCount": 4
      },
      "observations": [
        "The candidate adds one release and one bounded ordered-valley and five-vertex-classification cluster without creating a formal Evidence Press research lineage.",
        "Relative to the four-state monotone row-diameter baseline, the accepted graph gains six method assignments and one cluster membership; no proposal is promoted and the direct inter-release projection remains at 36 authored records.",
        "The current graph reconciles to 214 method assignments, 42 cluster memberships, 15 lineage memberships and 36 direct inter-release records, for 307 accepted relationships across 40 releases.",
        "Adversarial controls now occur in 32 of 40 release assignments and structural compression in 29 of 40; both prevalence labels remain registry-derived navigation rather than evidence of efficacy.",
        "The AIM source fixes the question and attribution but leaves its order quantifier unstated; it does not validate the five-vertex valley, structural minimality, census, novelty, priority, or any favourable-order existential conclusion."
      ],
      "decision": "complete",
      "nextAction": "Seek an authenticated unaffiliated exact reconstruction and spectral-graph-theory literature assessment, then investigate both favourable-order existential formulations without promoting the present universal-only PASS_WITH_NOTES claim ceiling."
    },
    {
      "reviewId": "atlas-review-2026-08-30-four-point-inductive-cubical-excision",
      "reviewedAt": "2026-08-30",
      "trigger": "maintainer-request",
      "reviewer": "Evidence Press producer workflow",
      "provenanceNote": "Producer-side registry reconciliation for the anonymous four-point inductive cubical-excision counterexample after review repair, exact Python and JavaScript replay, semantic mutations, a bounded confirmation and deterministic gate repair, immutable GitHub release, public CI and Zenodo publication. This records graph conformance only; it is not unaffiliated mathematical reconstruction, formal verification, external specialist review, exhaustive novelty, priority adjudication, a result for the other five cubical theories, or evidence of research impact.",
      "baseline": {
        "releaseCount": 41,
        "acceptedRelationshipCount": 314,
        "publishedProposalCount": 4
      },
      "observations": [
        "The candidate adds one release and one bounded directed inductive-cubical excision counterexample cluster without creating a formal Evidence Press research lineage.",
        "Relative to the five-vertex negative-square-energy baseline, the accepted graph gains six method assignments and one cluster membership; no proposal is promoted and the direct inter-release projection remains at 36 authored records.",
        "The current graph reconciles to 220 method assignments, 43 cluster memberships, 15 lineage memberships and 36 direct inter-release records, for 314 accepted relationships across 41 releases.",
        "Adversarial controls now occur in 33 of 41 release assignments and structural compression in 30 of 41; both prevalence labels remain registry-derived navigation rather than evidence of efficacy.",
        "The primary source fixes the interval-product definitions and inductive excision question but does not validate the four-point proof, establish novelty or priority, extend the result to other theories, or provide independent assurance."
      ],
      "decision": "complete",
      "nextAction": "Seek an authenticated unaffiliated chain-complex reconstruction and closure-space specialist literature assessment, then investigate the remaining inductive interval theories without promoting the present PASS_WITH_NOTES claim ceiling."
    },
    {
      "reviewId": "atlas-review-2026-09-01-hc4-five-support-structural-reductions",
      "reviewedAt": "2026-09-01",
      "trigger": "maintainer-request",
      "reviewer": "Evidence Press producer workflow",
      "provenanceNote": "Producer-side registry reconciliation for the anonymous HC4 five-support structural-reductions candidate after exact characteristic-zero certificates, a prospectively frozen 16-column source-kernel computation, internal review, immutable GitHub release and Zenodo publication. This records graph conformance only; it is not unaffiliated mathematical reconstruction, fourth-target membership, secant closure, formal verification, external specialist review, exhaustive novelty, priority adjudication, HC4, JC2, or evidence of research impact.",
      "baseline": {
        "releaseCount": 47,
        "acceptedRelationshipCount": 353,
        "publishedProposalCount": 4
      },
      "observations": [
        "The candidate adds one release and one binary-decimic normal-layer structural-reductions cluster without creating a formal Evidence Press research lineage.",
        "Relative to the prior 46-release baseline, the accepted graph gains six method assignments and one cluster membership; no proposal is promoted and the direct inter-release projection remains at 36 authored records.",
        "The current graph reconciles to 253 method assignments, 49 cluster memberships, 15 lineage memberships and 36 direct inter-release records, for 353 accepted relationships across 47 releases.",
        "Adversarial controls now occur in 39 of 47 release assignments and structural compression in 36 of 47; both prevalence labels remain registry-derived navigation rather than evidence of efficacy.",
        "The exact 16-column result certifies sixteen rational source-module syzygies with all-row replay and a separate direct-polynomial audit; it does not establish membership in the fourth target module, a colon equality, saturation, secant closure, the full binary-decimic nullcone, HC4, or JC2."
      ],
      "decision": "complete",
      "nextAction": "Seek an unaffiliated exact reconstruction of the source-kernel certificates, then test fourth-target membership and polynomial-open closure without promoting the present unrefereed candidate claim ceiling."
    },
    {
      "reviewId": "atlas-review-2026-09-01-pinching-free-normal-cover",
      "reviewedAt": "2026-09-01",
      "trigger": "maintainer-request",
      "reviewer": "Evidence Press producer workflow",
      "provenanceNote": "Producer-side registry reconciliation for the anonymous pinching-free-normal-cover all-Fuchsian strengthening candidate after supplied-review repair, formula replay, source mapping, five-role internal review and exact-archive domain confirmation. This records graph conformance only; it is not unaffiliated mathematical reconstruction, external specialist review, formal verification, exhaustive novelty, priority adjudication, a first-solution finding under the broad group-deformation reading, or evidence of research impact.",
      "baseline": {
        "releaseCount": 48,
        "acceptedRelationshipCount": 358,
        "publishedProposalCount": 4
      },
      "observations": [
        "The candidate adds one release and one bounded free-normal-cover and all-Fuchsian pinching cluster without creating a formal Evidence Press research lineage.",
        "Relative to the 47-release baseline, the accepted graph gains four method assignments and one cluster membership; no proposal is promoted and the direct inter-release projection remains at 36 authored records.",
        "The current graph reconciles to 257 method assignments, 50 cluster memberships, 15 lineage memberships and 36 direct inter-release records, for 358 accepted relationships across 48 releases.",
        "Adversarial controls now occur in 40 of 48 release assignments and structural compression in 37 of 48; both prevalence labels remain registry-derived navigation rather than evidence of efficacy.",
        "The AIM source fixes the existential target and attribution, while Astala-Zinsmeister appears already affirmative under a broad quasi-Fuchsian reading; neither validates the fixed-free-cover proof, reduced-space bridge, all-Fuchsian strengthening, linear rate, novelty, priority or external assurance."
      ],
      "decision": "complete",
      "nextAction": "Seek an authenticated unaffiliated reconstruction of the fixed-kernel group-space bridge and collar estimate, followed by a Fuchsian-group specialist assessment of the AIM interpretation and closest prior art."
    }
  ]
}
