Synthesis

Purpose and authority boundary

NexusScholar.Synthesis owns the plan for a synthesis, not computed results or conclusions. A verified plan binds one approved Protocol, a unique eligible source-record set, source-to-outcome mappings, target outcomes, effect measures, units, transformations, assumptions, a missing-data policy, sensitivity analyses, and calculation-library declarations.

The plan records which library id, version, and canonical configuration is intended. It does not call that library, validate an estimator, certify statistics, or turn a calculation into a scientific conclusion.

Eligibility and planning flow

ExtractionJournal --current final record--+
                                           +--> SynthesisEligibleRecord
AppraisalJournal  --current final record--+
                                                    |
approved Protocol + human author + outcomes         |
transformations + assumptions + calculations -------+
                                                    v
                                         VerifiedSynthesisPlan
                                                    |
                                     SynthesisPlanJournal
                                                    |
                                  Protocol amendment invalidation

Callers cannot construct SynthesisEligibleRecord directly. The public factories FromExtraction and FromAppraisal derive eligibility from the owning journal, reject proposals, and carry current and invalidated status into plan validation.

Key API surface

• SynthesisEligibleRecord.FromExtraction / FromAppraisal establish source provenance and currentness.
• SynthesisOutcome declares outcome id, name, target effect measure, unit, and timepoint.
• SynthesisTransformation makes every effect-measure or unit conversion explicit, method-named, and rationale-bound.
• SynthesisCalculationDeclaration freezes canonical configuration and stores its digest beside library id and version.
• SynthesisPlanAuthority.Create performs the full authority and compatibility validation and returns a VerifiedSynthesisPlan.
• SynthesisPlanJournal retains plans and append-only invalidations while projecting current plans.

The canonical schemas are nexus.synthesis.plan and nexus.synthesis.invalidation, version 1.0.0.

Determinism and refusal states

Sources, outcomes, mappings, transformations, assumptions, sensitivities, and calculation declarations are normalized into deterministic order. Configuration is deep-cloned, frozen, and digested as canonical JSON. The plan embeds the nonclaims plan-not-calculation, no-statistical-conclusion, and no-clinical-or-causal-claim.

• Automation cannot authorize a plan or invalidate plan authority.
• Empty, duplicate, stale, superseded, invalidated, or foreign-Protocol sources are rejected.
• Source-outcome mappings must resolve to admitted sources and declared outcomes.
• Effect-measure or unit mismatches require an exact declared transformation.
• Assumptions, sensitivity analyses, missing-data policy, and calculation declarations cannot be omitted.
• Invalidation must target current plans governed by the exact amended Protocol authority.

Dependencies and extension points

Synthesis depends inward on Kernel, Protocol, Extraction, and Appraisal. It intentionally does not depend on FullText directly because its admitted inputs are already evidence-bound owner records. It has no statistics, Workflow, persistence, UI, provider, or model runtime dependency.

Developers can declare different outcome vocabularies, calculation libraries, configurations, transformations, and sensitivity analyses through the plan contract. Actually executing a method, validating a statistical package, or publishing a result requires a future method-specific ADR and evidence.

Tests and accepted evidence

SynthesisTests cover eligible-record factories, stale and invalid sources, plan authority, unit/effect mismatches, transformations, automation refusal, and invalidation. Cross-module canonical fixtures and amendment replay are in Fe07FixtureTests and Fe07AuthorityReplayTests.

See ADR 0034, the FE-07 gate, and completion evidence.

Explicit nonclaims

No statistical execution, correctness, effect estimation, meta-analysis, certainty grading, clinical, causal, regulatory, database, UI, AI, PHP, or production claim is made. VerifiedSynthesisPlan means the declared plan passed authority and consistency checks—not that its future calculation is correct.