@3f-consulting/spec-controller-core 0.1.0-alpha.7 → 0.1.0-alpha.70

package/dist/domain/evidenceReconciliation.d.ts

@@ -1,441 +1,71 @@
-/**
- * THE EVIDENCE RECONCILIATION — canon's Layer 1, *"the whole reconciliation: all Scenario
- * Reconciliations taken together"*, and **the key concept the domain models**
- * (`double-entry-manifesto.md`). This module is its home.
- *
- * IT ARRIVED HERE FROM `reconcile/` (3F-2232). After 3F-2202/2203/2204 that module held no domain
- * rule — but it was still a named layer beside the domain doing the concept's own work, which is
- * the shape `functional-domain-modelling.md` rejects: *"orchestration is thin composition, not a
- * named layer."* Constructing a concept is the concept's business. The module's residual tell was
- * already visible — it re-exported `isBalanced` / `hasPendingItems` / `hasBrokenEvidence` FROM
- * `domain/ledger` purely to preserve importers' paths, a shell around behaviour that had already
- * gone home. Every importer now points at the module that OWNS the symbol.
- *
- * (3F-2233 completes the move: the concept's TYPE, its `Summary`, and the factory that fuses this
- * fold with the summary tally. Today this module holds the fold alone.)
- *
- * The pure obligation-vs-observation join, keyed by one flat
- * `qualityCheck` (the two-axis `(kind, level)` grid collapsed). This module is THIN
- * COMPOSITION: the domain RULES it once held moved to the
- * concept modules that own them (3F-1994) — `reconcileEvidenceObligation` (the per-obligation
- * outcome) to `domain/qualityCheckReconciliation`, `verdictFor` / `reconcilingItemsOf` (the
- * account roll-up) to `domain/scenarioReconciliation`, `isBalanced` / `hasPendingItems` /
- * `hasBrokenEvidence` (the whole-run predicates) to `domain/ledger`. `reconcile` is the fold that
- * WALKS the inputs, CALLS those rules, and BUILDS the rows; it is the orchestration, not their home.
- *
- * POSTING-DESTINATION left too (3F-2202) — WHERE an entry lands is canon's own glossary group
- * ("### Posting") and now lives on `domain/posting`: `postingOf`, the one citation route over both
- * axes (plus the no-evidence-obligation-static-check arm). The by-name half is gone (3F-2590).
- * The fold no longer DECIDES a destination anywhere — it
- * asks the rule once per credit and files the answer. What remains is assembly: which rows exist,
- * in what order, holding which items.
- *
- * Per the slice design: for each evidence obligation a scenario raises (a reconciling
- * item), present+pass → satisfied; present+fail → failing; absent →
- * missing. `reconcileEvidenceObligation` branches on the `qualityCheck === "lint"`
- * watermelon discriminator (replacing the retired `kind === "static"` split): a `lint`
- * evidence obligation reconciles against a static-check evidence observation (exists+wired → satisfied;
- * exists+unwired → watermelon; absent → missing); a runtime evidence obligation
- * reconciles against a test result matched by (scnId, quality-check).
- *
- * The scenario VERDICT is binary (superseding the earlier prioritising
- * aggregate): a scenario is `balanced` IFF every required quality-check balances;
- * otherwise `out-of-balance`, carrying the LIST of EVERY non-balanced reconciling
- * item — no prioritisation, no picked winner ("missing beats failing" was a false
- * order that hid one of two genuinely different problems). The renderers list
- * every item.
- *
- * Parent: @SCN-LDG-001.
- */
-import type { RuntimeQualityCheck, Scenario, EvidenceObservation, Ledger } from "../model.js";
-import type { UnspecifiedFitnessRow } from "./fitnessChecks.js";
-import type { ScenarioReconciliationTotals, EvidenceObligationTotals, LintTally } from "./ledger.js";
-export declare function reconcile(scenarios: Scenario[], evidenceObservations: EvidenceObservation[], untaggedScenarios?: readonly string[], 
-/**
- * The CONFIGURED ROWS the target's corpus carries no scenario for (@SCN-LNT-027, 3F-3472) — the
- * fourth population, minted below.
- *
- * IT DEFAULTS, WHERE THE TWO GATES BELOW DELIBERATELY DO NOT (3F-2875). A gate that defaults is a
- * gate a caller can forget and thereby CHANGE what the summary claims. This is a population, and
- * an omitted population is indistinguishable from an empty one in the only way that matters:
- * both mint no rows, and neither says anything about a manifest. Every caller that constructs
- * `Scenario[]` by hand has no manifest to read rows from, which is `untaggedScenarios`' own
- * argument for the default it already carries.
- */
-unspecifiedFitnessRows?: readonly UnspecifiedFitnessRow[]): Ledger;
-/**
- * The materialised test-volume totals (RMD-005) — the runtime evidence-observation kind-counts
- * the markdown's `### Test volume` identity line derives, carried AS DATA. The identity
- * `totalEvidenceObservations = onScenario + onPhantomScenario + onSuspenseScenario` holds by
- * construction (one shared `runtimeObservationTally` fold), so a JSON consumer reads the balance
- * rather than re-deriving it. The three terms are named for the SCENARIO-KIND the credit posted
- * to (the canon grouping): `onScenario` (a scenario's account), `onPhantomScenario` (an
- * invented phantom-scenario account) and `onSuspenseScenario` (the suspense scenario — includes
- * `broken`). This is an identity read off the fold, not a re-map of the outcome handles.
- */
+import type { RuntimeQualityCheck, Scenario, EvidenceObservation } from "./journal.js";
+import type { Ledger } from "./ledger.js";
+import type { ScenarioReconciliationTotals, EvidenceObligationTotals, FitnessTally } from "./ledger.js";
+import type { ScenarioCodeError, ScenarioCodePopulation } from "./scenarioCodeError.js";
+export declare function reconcile(scenarios: Scenario[], evidenceObservations: EvidenceObservation[], untaggedScenarios?: readonly string[]): Ledger;
 export interface TestVolumeTotals {
     totalEvidenceObservations: number;
     onScenario: number;
     onPhantomScenario: number;
     onSuspenseScenario: number;
 }
-/**
- * The materialised static-check totals (RMD-005) — the static-check kind-counts the
- * markdown's `### Static checks` line derives, following the census shape exactly:
- * `runningStaticCheckCount` (the volume of running static checks) and `uncitedStaticCheckCount` (how many
- * of THOSE no `@lint` cites — a subset of the first, @SCN-LNT-033). The named count is IMPLICIT
- * (`running − uncited`) and is not carried (every named static check is already a reconciled
- * `@lint` sub-row); drawn from one population under one membership rule, it cannot go below nil.
- */
-export interface StaticCheckTotals {
-    runningStaticCheckCount: number;
-    uncitedStaticCheckCount: number;
+export interface FitnessFunctionTotals {
+    runningFitnessFunctionCount: number;
+    uncitedFitnessFunctionCount: number;
 }
-/**
- * ONE STEP THAT IS THE RECONCILER (@SCN-USG-014) — the step, as the report names one, and which
- * half of the reconciler it is.
- *
- * TWO ROLES RATHER THAN A BARE LIST, because the two are different facts about a pipeline and a
- * consumer reading the report is owed both: one step RUNS the reconciliation these books are, and
- * one WRITES the step record that run reads. Collapsing them would say only that two steps were
- * set aside, which is the shape of a claim nobody can check.
- *
- * BESIDE `BehaviouralRunner` FOR THE REASON THAT ONE IS HERE: it is carried on the summary and the
- * renderer reads it off there. Neither is a tally — the question a reader has is which step was
- * accounted for as what, and a count answers none of it.
- */
 export interface ReconcilerStep {
-    /** The step, named as every section of the report names one (`parse/stepNames`). */
     readonly step: string;
-    /** Which half of the reconciler it is — the run itself, or the record that run reads. */
     readonly role: "reconciles" | "records";
 }
-/**
- * ONE STEP RECOGNISED AS THE RUNNER OF ONE TIER (@SCN-USG-011) — the tier the target named it
- * for, the runner it named, and the step GitHub itself displays it as.
- *
- * BESIDE `StaticCheckTotals` RATHER THAN IN THE PARSE THAT PRODUCES IT, for the reason that one
- * is here: it is carried on the summary, and the renderer reads it off there. It is not a tally —
- * a recognition names a step, and a count of them would answer none of the questions a reader has
- * about which step was recognised as what.
- */
 export interface BehaviouralRunner {
-    /** The tier key the target named this runner under — `unit`, `integration`, `e2e`, `performance`. */
     readonly tier: string;
-    /** The runner's name, as the target wrote it. */
     readonly runner: string;
-    /** The step's identity — its `name:`, else the action it `uses:`, else the first line of its `run:`. */
     readonly step: string;
 }
-/**
- * ONE JOB OF ONE WORKFLOW THIS RUN READ (@SCN-USG-020) — where the steps came from, and how many
- * of them there were.
- *
- * BOTH FIGURES, because either alone is satisfiable by a reader that is wrong about the other.
- * `steps` says what was in front of the tool and nothing about what it did with them; `candidates`
- * is the figure already on the report, re-cut. It is the PAIR, per job, that lets a consumer see a
- * whole job pass through discovery contributing nothing and ask why.
- *
- * BESIDE `ReconcilerStep` AND `BehaviouralRunner` FOR THE REASON THOSE ARE HERE: it is carried on
- * the summary and the renderer reads it off there. It is not a tally of the ledger — no row exists
- * for a job, and the question a reader has is which files and which jobs the numbers came from.
- *
- * THE SOURCE IS OPTIONAL BECAUSE THE CORE HOLDS NO FILESYSTEM. Workflow names arrive as data from
- * the CLI edge (`parse/stepNames`), so a run given none for a source can name no file for its jobs
- * — and dropping those jobs would be the silence this axis exists to end, so the row survives
- * without the half of its name nobody supplied.
- */
+export interface WrongKindEntry {
+    readonly entry: string;
+    readonly is: string;
+    readonly reads: string;
+}
 export interface JobDiscoveryScope {
-    /** The workflow file the job was read from, absent where the run was given no name for it. */
     readonly source?: string;
-    /** The key the job is written under in that workflow's `jobs:` mapping. */
     readonly job: string;
-    /** How many steps this run read from it. */
     readonly steps: number;
-    /** How many of those steps are candidate fitness checks. */
     readonly candidates: number;
 }
-/**
- * WHAT BECAME OF EVERY STEP THIS RUN READ (@SCN-USG-018) — the population, the four dispositions,
- * and the total those four come to.
- *
- * BOTH TOTALS, AND `accountedFor` IS THE ONE THAT HAS TO BE CARRIED. A consumer of this structure
- * could add the four dispositions up for themselves, and a consumer that did would be measuring
- * their own arithmetic: they would agree with any four figures a reader happened to produce,
- * including four produced by a reader that had lost a step on the way. The sum is the READER's
- * answer to "how many did you account for", stated beside "how many did you read" so the two can
- * be compared rather than reconstructed. The identity `accountedFor === stepsRead` is the axis's
- * first non-negotiable — nothing seen is dropped — made checkable.
- *
- * IT IS A CARDINALITY INSTRUMENT, WHICH IS WHY NO OTHER MEMBER HERE CAN STAND IN FOR IT. Every
- * account beside it names steps that BECAME something — a runner, the reconciler, an exclusion, a
- * row on the books. A step dropped on a branch nobody enumerated becomes nothing, names nothing
- * and posts nothing, so there is no list it is missing from: only a count of the population
- * against the dispositions can see it at all.
- *
- * BESIDE `JobDiscoveryScope` FOR THE REASON THAT ONE IS HERE: it is carried on the summary and the
- * renderer reads it off there. It is not a fold of the ledger — three of its four dispositions
- * post no row by definition, so there is nothing for it to be derived from.
- */
 export interface StepAccounting {
-    /** How many steps of the target's pipeline this run read. */
     readonly stepsRead: number;
-    /** How many of them are candidate fitness checks. */
     readonly candidates: number;
-    /** How many of them run a runner the target named. */
     readonly runners: number;
-    /** How many of them are the reconciliation or the step record it reads. */
     readonly reconciler: number;
-    /** How many of them the target names non-checks. */
     readonly excluded: number;
-    /** The four above, added up by the reader that counted them. */
     readonly accountedFor: number;
 }
-/** The materialised summary — the totals (manifesto: "the aggregate of the trial balance"). */
 export interface Summary {
     scenarioReconciliations: ScenarioReconciliationTotals;
     evidenceObligations: EvidenceObligationTotals;
-    /**
-     * The Pending Items tally (@SCN-PND-011) — the count of Pending Items across the
-     * reconciliation (one per deferred `<quality-check>pending` obligation, evidence-manifesto §11B),
-     * SEPARATE from the scenario balanced / out-of-balance counts and the evidence-obligation counts.
-     * A Pending Item is deferred, NOT out-of-balance, so it is NEVER folded into
-     * `OUT_OF_BALANCE_OUTCOMES` (never a leaf of its own, at any leaf count — the constraint is
-     * categorical, not arithmetic) nor into `evidenceObligations` — its own tally.
-     * Counts Pending ITEMS, not scenarios-carrying-pending (mirroring the out-of-balance
-     * decomposition, which counts obligations, not scenarios). Always present (a pure balance derive,
-     * like `lint`); reads 0 when no scenario raises a pending obligation.
-     */
     pending: number;
-    /** The runtime test-volume kind-counts (RMD-005) — present when the evidenceObservations read is threaded. */
     testVolume?: TestVolumeTotals;
-    /**
-     * The re-homed raw per-quality-check evidence-observation totals (@SCN-RMD-003, 3F-2102) — a
-     * materialised headline the Ledger folds (`runtimeObservationTally`), testVolume-adjacent. It
-     * RE-HOMES onto `summary` the raw totals the retired `evidenceObservations` section used to
-     * carry: a legitimate aggregate headline (per the done-criterion's fold-vs-store test — three
-     * derived totals, not a parallel store of the posted credits). Present exactly when `testVolume`
-     * is (both gated on the observation read being threaded).
-     */
     rawByRuntimeQualityCheck?: Record<RuntimeQualityCheck, number>;
-    /** The static-check kind-counts (RMD-005) — present when the guard read is threaded. */
-    staticChecks?: StaticCheckTotals;
-    /** The static-only lint evidenceObligation tally (RMD-005) — always present (a pure balance derive). */
-    lint: LintTally;
-    /**
-     * The scenarios ON the fitness axis that no configured row NAMES (@SCN-LNT-020) — the corpus's
-     * half-converted checks, in corpus order.
-     *
-     * NOT A LEDGER FOLD, and it says so by being the one member here that is not. It is a fact about
-     * the CORPUS — what a scenario said about itself and what no row said back — which the Ledger
-     * cannot hold: such a scenario raises nothing, so nothing about it reaches a row except the
-     * degenerate `both-missing` item its emptiness earns, and that item's own gloss is about a
-     * scenario carrying no `@SCN`. It rides beside `staticChecks` for the reason that one does: the
-     * report's `### Static checks` section is where a half-entry the run saw and nothing owed is
-     * named, and this is that same class of half-entry on the other side of the books.
-     *
-     * PRESENT ONLY WHEN NON-EMPTY, so a target that has converted nothing — every target today —
-     * renders and serialises exactly as it did before.
-     */
-    unconfiguredFitnessScenarios?: readonly string[];
-    /**
-     * THE STEPS RECOGNISED AS BEHAVIOURAL RUNNERS (@SCN-USG-011), in the order the pipeline runs
-     * them — what the target named, found where its pipeline invokes it.
-     *
-     * NOT A LEDGER FOLD, and it rides here for the reason `unconfiguredFitnessScenarios` does: it is
-     * a fact about what the reader SAW, not about anything the books hold. A runner raises no
-     * obligation and posts no credit — it is the disposition a step gets INSTEAD of reaching the
-     * ledger — so there is no row for it to be derived from and it has to be carried.
-     *
-     * PRESENT ONLY WHEN NON-EMPTY, so a target that has named no runners renders and serialises
-     * exactly as it did before.
-     */
+    fitnessFunctions?: FitnessFunctionTotals;
+    fitness: FitnessTally;
     behaviouralRunners?: readonly BehaviouralRunner[];
-    /**
-     * WHAT THE TARGET SAID ABOUT EACH TIER (@SCN-USG-016) — `specController.runners` as written: the
-     * runner's name where it named one, and `null` for a tier it says it has none. A tier the block
-     * OMITS is absent from this record, and that third state is the whole reason the field exists.
-     *
-     * NOT `behaviouralRunners`, which is the other half of the same subject and is easy to mistake
-     * for it. That one is what a run RECOGNISED — tier, runner and the step it was found at, a fact
-     * about the pipeline. This one is what the target SAID, a fact about the manifest, and the two
-     * disagree whenever a named runner runs at no step this reader could see.
-     *
-     * PRESENT ONLY WHEN NON-EMPTY, so a target that has named no runners renders and serialises
-     * byte-identically to before.
-     */
     runnerTiers?: Readonly<Record<string, string | null>>;
-    /**
-     * THE RUNNER BLOCK'S KEYS THAT ARE NOT ONE OF THE FOUR CANON TIERS (@SCN-USG-019) — what the
-     * target wrote that this tool does not recognise, in the order the manifest wrote it.
-     *
-     * IT CARRIES A NON-EVENT, WHICH IS WHY IT HAS TO BE CARRIED AT ALL. An unrecognised key
-     * recognises no step, excludes no step and posts no row, so nothing anywhere else in this
-     * structure differs between a manifest that wrote it and one that did not. Without this field
-     * the consumer's entry is simply gone — and a consumer who wrote something and believes it took
-     * effect is the same fault as a step dropped in silence, reached from the configuration side.
-     *
-     * NOT `runnerTiers`, which is the block's other half: that one is what the target said about a
-     * tier that EXISTS, and every entry in it can be run against a pipeline. Nothing in here can be.
-     *
-     * PRESENT ONLY WHEN NON-EMPTY, so a target whose block is keyed correctly — every target today —
-     * renders and serialises byte-identically to before.
-     */
     unrecognisedRunnerKeys?: readonly string[];
-    /**
-     * THE specController.* KEYS THIS READER HAS RETIRED (@SCN-USG-021) — the top-level keys a
-     * manifest carries that this tool no longer reads, in the order the manifest wrote them.
-     *
-     * NOT unrecognisedRunnerKeys, which names a key the target INVENTED. This one names a key
-     * the target wrote CORRECTLY, under a name this reader once read and has since stopped
-     * reading — `checkRegistry` first. Its entries reach no candidate, resolve no citation, and
-     * are simply not there for anything downstream to find; naming the key is the only way a
-     * consumer who wrote it in good faith learns that none of it is taking effect.
-     *
-     * AND A BAR A CONFIGURED ROW STILL CARRIES (@SCN-LNT-035), named with its row —
-     * `fitnessChecks[SCN-XXX-NNN].atLeast` / `.atMost` — in the same account, in manifest order.
-     * The row itself still reaches the books, credited by its step's outcome; only the bar is unread.
-     *
-     * PRESENT ONLY WHEN NON-EMPTY, so a target that carries no retired key — every target today
-     * that has never written one — renders and serialises byte-identically to before.
-     */
-    retiredKeys?: readonly string[];
-    /**
-     * THE STEPS THE TARGET NAMES NON-CHECKS (@SCN-USG-015) — `specController.notChecks`' entries
-     * that named a step of the pipeline this run read, each as the consumer wrote it.
-     *
-     * IT CARRIES A DISPOSITION, WHICH IS WHY IT IS CARRIED AT ALL. An excluded step reaches no
-     * observer and posts no row, so nothing else in this structure differs between a run that
-     * excluded it and a run that never saw it — and those are the two things a reader most needs
-     * told apart. A step that simply vanished on the consumer's own instruction is the silence this
-     * axis exists to end, arriving with their signature on it; naming it is what makes the exclusion
-     * a disposition rather than a drop, and correctable in one line of their own configuration.
-     *
-     * PRESENT ONLY WHEN NON-EMPTY, so a target that names no non-checks — every target today —
-     * renders and serialises byte-identically to before.
-     */
+    wrongKindConfiguration?: readonly WrongKindEntry[];
+    unknownConfigurationKeys?: readonly string[];
     excludedSteps?: readonly string[];
-    /**
-     * THE STEPS THAT ARE THE RECONCILER (@SCN-USG-014) — the step running this reconciliation and
-     * the step writing the record it reads, in the order the pipeline runs them.
-     *
-     * NOT `excludedSteps`, AND THE DIFFERENCE IS THE WHOLE REASON THIS IS A SEPARATE MEMBER. That
-     * one is a list the consumer wrote about their own pipeline; this one is nobody's list. A
-     * `notChecks` pair naming these two steps produces the same books, and a report folding them
-     * together would credit a consumer's configuration for an exclusion that holds over a manifest
-     * saying nothing — which is every consumer's first run.
-     *
-     * PRESENT ONLY WHEN NON-EMPTY, so a target whose pipeline does not run this tool renders and
-     * serialises byte-identically to before.
-     */
     reconcilerSteps?: readonly ReconcilerStep[];
-    /**
-     * THE `notChecks` ENTRIES THAT NAMED NO STEP (@SCN-USG-015) — in the order the manifest wrote
-     * them, and the other half of a total partition with `excludedSteps`.
-     *
-     * A LINE THAT MATCHES NOTHING IS A STALE EXCLUSION. The consumer renamed a step and the entry
-     * now hides nothing, or is about to hide the wrong thing the next time a step is renamed onto
-     * it. Either way it is a fact about their manifest that only this run can see, and dropping it
-     * is the same fault as dropping a step: something was written, it took no effect, and nothing
-     * anywhere says so.
-     *
-     * NOT `excludedSteps`, and the two are easy to mistake for one another. That one names a step
-     * this run READ; every entry in here named none, so nothing in the pipeline corresponds to it.
-     *
-     * PRESENT ONLY WHEN NON-EMPTY, for the reason its twin is.
-     */
     unmatchedNotChecks?: readonly string[];
-    /**
-     * THE SCOPE THIS RUN RANGED OVER (@SCN-USG-020) — one entry per job of every workflow `--ci`
-     * resolved, sorted by workflow and then by job.
-     *
-     * IT CARRIES THE PROVENANCE OF EVERY OTHER FIGURE ON THE REPORT, which is why it has to be
-     * carried at all. The census above states how many checks ran; nothing anywhere states how many
-     * jobs, in how many files, that number came from — so a consumer whose second job holds three
-     * checks reads exactly what a consumer with three checks in one job reads, and a consumer
-     * pointed at the wrong file has nothing that says so. The tool makes no judgement about whether
-     * a scope is the right one; stating it is the answer.
-     *
-     * NOT THE ACCOUNTING IDENTITY, which is a separate claim over the same steps (@SCN-USG-018).
-     * That one asserts the dispositions sum to the steps read, so nothing was dropped; this one
-     * asserts WHERE the steps came from. A reader satisfies either alone.
-     *
-     * PRESENT ONLY WHEN NON-EMPTY, so a run that read no CI configuration at all renders and
-     * serialises byte-identically to before.
-     */
     discoveryScope?: readonly JobDiscoveryScope[];
-    /**
-     * WHAT BECAME OF EVERY STEP THIS RUN READ (@SCN-USG-018) — the population, the four dispositions
-     * and the total they come to, so the axis's first non-negotiable is a figure a reader can check
-     * rather than a sentence they have to take on trust.
-     *
-     * IT IS THE ONLY MEMBER HERE THAT CAN SEE AN ABSENCE. `behaviouralRunners`, `reconcilerSteps`,
-     * `excludedSteps` and the static-check census each name what a step BECAME; a step dropped on a
-     * branch nobody enumerated became nothing, so it is missing from no list and every one of them
-     * reads exactly as it would have read had the step never existed. Counting the population
-     * against the dispositions is what makes the drop visible, and it is the whole reason this
-     * member is a set of counts rather than another list of steps.
-     *
-     * NOT `discoveryScope`, which counts the same population for a different question. That one
-     * asserts WHERE the steps came from — which files, which jobs; this one asserts that none of
-     * them went missing between being read and being accounted for. A reader satisfies either alone.
-     *
-     * PRESENT ONLY WHEN THE RUN READ A STEP, so a run handed no CI configuration renders and
-     * serialises byte-identically to before.
-     */
     stepAccounting?: StepAccounting;
 }
-/**
- * THE EVIDENCE RECONCILIATION — canon's Layer 1. `summary` carries the totals, `ledger` the detail.
- *
- * NOT the report. The run's PROVENANCE (when, where, which SHA) and the presentation metadata
- * (feature titles) are the report's framing and live on the render payload, not here: canon is
- * explicit that rendering this concept into various formats PRODUCES the report, which "draws its
- * substance from it". "Ledger" is a REJECTED ALIAS for this concept — the ledger is the grid
- * WITHIN it, which is why both fields are named rather than the whole thing collapsing to one.
- */
 export interface EvidenceReconciliation {
     summary: Summary;
     ledger: Ledger;
+    scenarioCodeErrors?: readonly ScenarioCodeError[];
+    scenarioCodePopulation?: ScenarioCodePopulation;
 }
-/**
- * Materialise the summary totals from the balance — the aggregate the markdown's trial-balance
- * table derives, carried AS DATA so a later render-from-saved-JSON rebuilds it with zero
- * computation (the MATERIALISE ruling). THIN COMPOSITION (3F-2000): the LEDGER-PURE totals
- * (`scenarioReconciliations`, `evidenceObligations`, `pending`, `lint`) come from `ledgerTally`
- * — the Ledger owns its own totals ("the summary is its totals") — and are MERGED here with the
- * census pass-throughs (`testVolume`, `staticChecks`), which are NOT Ledger-pure. The keys are
- * assembled in DOCUMENT ORDER (…, testVolume?, staticChecks?, lint) so the JSON stays
- * byte-identical.
- */
-export declare function summaryOf(ledger: Ledger, withRuntimeObservations: boolean, withStaticChecks: boolean): Summary;
-/**
- * BUILD the Evidence Reconciliation from the journal — THE FACTORY (3F-2233).
- *
- * Journal inputs in, whole concept out: the fold posts every entry into the Ledger, and the tally
- * totals it. They are ONE act, not two stages a caller sequences — which is the point. While
- * `reconcile()` and `buildSummary()` were separate, an adapter held a Ledger and derived its own
- * totals, so "the procedure can sum the wrong rows" (`why-ddd-for-spec-controller.md`) was a
- * REACHABLE state. Here there is no such seam: you cannot obtain a summary except from the concept
- * that owns the rows it counts.
- *
- * The two flags are GATES, not data — they state whether the runtime-observation and static-check
- * axes are in play for this run; the counts themselves are always folded from the Ledger.
- *
- * WHY THE TRAILING THREE ARE REQUIRED AND CARRY NO DEFAULTS (3F-2875). A gate that defaults to
- * `false` is a gate a caller can forget to state, and forgetting it CHANGES THE REPORT — the
- * summary then claims neither axis is in play, silently and plausibly. That is not a hypothetical:
- * when the defaults were removed, eleven call sites turned out to have been leaning on them. Every
- * one wanted exactly what it had been getting, so nothing moved; what changed is that each now says
- * so. A default is the wrong shape for an argument whose omission is indistinguishable from a
- * deliberate `false`.
- */
-export declare function evidenceReconciliationOf(scenarios: Scenario[], evidenceObservations: EvidenceObservation[], untaggedScenarios: readonly string[], withRuntimeObservations: boolean, withStaticChecks: boolean, 
-/**
- * The CONFIGURED ROWS the corpus carries no scenario for (@SCN-LNT-027, 3F-3472) — passed
- * through to `reconcile`, which mints one row apiece. It defaults for the reason given there, and
- * that reason is NOT the trailing three's: a population omitted mints nothing and claims nothing,
- * where a gate omitted silently changes what the summary says is in play.
- */
-unspecifiedFitnessRows?: readonly UnspecifiedFitnessRow[]): EvidenceReconciliation;
+export declare function summaryOf(ledger: Ledger, withRuntimeObservations: boolean, withFitnessFunctions: boolean): Summary;
+export declare function evidenceReconciliationOf(scenarios: Scenario[], evidenceObservations: EvidenceObservation[], untaggedScenarios: readonly string[], withRuntimeObservations: boolean, withFitnessFunctions: boolean): EvidenceReconciliation;
 //# sourceMappingURL=evidenceReconciliation.d.ts.map

package/dist/domain/evidenceReconciliation.d.ts.map

@@ -1 +1 @@
-{"version":3,"file":"evidenceReconciliation.d.ts","sourceRoot":"","sources":["../../src/domain/evidenceReconciliation.ts"],"names":[],"mappings":"AAAA;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;GAgDG;AAEH,OAAO,KAAK,EACV,mBAAmB,EACnB,QAAQ,EAGR,mBAAmB,EAInB,MAAM,EACP,MAAM,aAAa,CAAC;AAiBrB,OAAO,KAAK,EAAE,qBAAqB,EAAE,MAAM,oBAAoB,CAAC;AAMhE,OAAO,KAAK,EACV,4BAA4B,EAC5B,wBAAwB,EAExB,SAAS,EACV,MAAM,aAAa,CAAC;AAyXrB,wBAAgB,SAAS,CACvB,SAAS,EAAE,QAAQ,EAAE,EACrB,oBAAoB,EAAE,mBAAmB,EAAE,EAC3C,iBAAiB,GAAE,SAAS,MAAM,EAAO;AACzC;;;;;;;;;;GAUG;AACH,sBAAsB,GAAE,SAAS,qBAAqB,EAAO,GAC5D,MAAM,CA6BR;AAcD;;;;;;;;;GASG;AACH,MAAM,WAAW,gBAAgB;IAC/B,yBAAyB,EAAE,MAAM,CAAC;IAClC,UAAU,EAAE,MAAM,CAAC;IACnB,iBAAiB,EAAE,MAAM,CAAC;IAC1B,kBAAkB,EAAE,MAAM,CAAC;CAC5B;AAED;;;;;;;GAOG;AACH,MAAM,WAAW,iBAAiB;IAChC,uBAAuB,EAAE,MAAM,CAAC;IAChC,uBAAuB,EAAE,MAAM,CAAC;CACjC;AAED;;;;;;;;;;;;GAYG;AACH,MAAM,WAAW,cAAc;IAC7B,oFAAoF;IACpF,QAAQ,CAAC,IAAI,EAAE,MAAM,CAAC;IACtB,yFAAyF;IACzF,QAAQ,CAAC,IAAI,EAAE,YAAY,GAAG,SAAS,CAAC;CACzC;AAED;;;;;;;;GAQG;AACH,MAAM,WAAW,iBAAiB;IAChC,qGAAqG;IACrG,QAAQ,CAAC,IAAI,EAAE,MAAM,CAAC;IACtB,iDAAiD;IACjD,QAAQ,CAAC,MAAM,EAAE,MAAM,CAAC;IACxB,wGAAwG;IACxG,QAAQ,CAAC,IAAI,EAAE,MAAM,CAAC;CACvB;AAED;;;;;;;;;;;;;;;;;GAiBG;AACH,MAAM,WAAW,iBAAiB;IAChC,8FAA8F;IAC9F,QAAQ,CAAC,MAAM,CAAC,EAAE,MAAM,CAAC;IACzB,2EAA2E;IAC3E,QAAQ,CAAC,GAAG,EAAE,MAAM,CAAC;IACrB,4CAA4C;IAC5C,QAAQ,CAAC,KAAK,EAAE,MAAM,CAAC;IACvB,4DAA4D;IAC5D,QAAQ,CAAC,UAAU,EAAE,MAAM,CAAC;CAC7B;AAED;;;;;;;;;;;;;;;;;;;;;GAqBG;AACH,MAAM,WAAW,cAAc;IAC7B,6DAA6D;IAC7D,QAAQ,CAAC,SAAS,EAAE,MAAM,CAAC;IAC3B,qDAAqD;IACrD,QAAQ,CAAC,UAAU,EAAE,MAAM,CAAC;IAC5B,sDAAsD;IACtD,QAAQ,CAAC,OAAO,EAAE,MAAM,CAAC;IACzB,2EAA2E;IAC3E,QAAQ,CAAC,UAAU,EAAE,MAAM,CAAC;IAC5B,oDAAoD;IACpD,QAAQ,CAAC,QAAQ,EAAE,MAAM,CAAC;IAC1B,gEAAgE;IAChE,QAAQ,CAAC,YAAY,EAAE,MAAM,CAAC;CAC/B;AAED,+FAA+F;AAC/F,MAAM,WAAW,OAAO;IACtB,uBAAuB,EAAE,4BAA4B,CAAC;IACtD,mBAAmB,EAAE,wBAAwB,CAAC;IAC9C;;;;;;;;;;OAUG;IACH,OAAO,EAAE,MAAM,CAAC;IAChB,8GAA8G;IAC9G,UAAU,CAAC,EAAE,gBAAgB,CAAC;IAC9B;;;;;;;OAOG;IACH,wBAAwB,CAAC,EAAE,MAAM,CAAC,mBAAmB,EAAE,MAAM,CAAC,CAAC;IAC/D,wFAAwF;IACxF,YAAY,CAAC,EAAE,iBAAiB,CAAC;IACjC,wGAAwG;IACxG,IAAI,EAAE,SAAS,CAAC;IAChB;;;;;;;;;;;;;;OAcG;IACH,4BAA4B,CAAC,EAAE,SAAS,MAAM,EAAE,CAAC;IACjD;;;;;;;;;;;OAWG;IACH,kBAAkB,CAAC,EAAE,SAAS,iBAAiB,EAAE,CAAC;IAClD;;;;;;;;;;;;OAYG;IACH,WAAW,CAAC,EAAE,QAAQ,CAAC,MAAM,CAAC,MAAM,EAAE,MAAM,GAAG,IAAI,CAAC,CAAC,CAAC;IACtD;;;;;;;;;;;;;;;OAeG;IACH,sBAAsB,CAAC,EAAE,SAAS,MAAM,EAAE,CAAC;IAC3C;;;;;;;;;;;;;;;;OAgBG;IACH,WAAW,CAAC,EAAE,SAAS,MAAM,EAAE,CAAC;IAChC;;;;;;;;;;;;;OAaG;IACH,aAAa,CAAC,EAAE,SAAS,MAAM,EAAE,CAAC;IAClC;;;;;;;;;;;;OAYG;IACH,eAAe,CAAC,EAAE,SAAS,cAAc,EAAE,CAAC;IAC5C;;;;;;;;;;;;;;OAcG;IACH,kBAAkB,CAAC,EAAE,SAAS,MAAM,EAAE,CAAC;IACvC;;;;;;;;;;;;;;;;;OAiBG;IACH,cAAc,CAAC,EAAE,SAAS,iBAAiB,EAAE,CAAC;IAC9C;;;;;;;;;;;;;;;;;;OAkBG;IACH,cAAc,CAAC,EAAE,cAAc,CAAC;CACjC;AAED;;;;;;;;GAQG;AACH,MAAM,WAAW,sBAAsB;IACrC,OAAO,EAAE,OAAO,CAAC;IACjB,MAAM,EAAE,MAAM,CAAC;CAChB;AAED;;;;;;;;;GASG;AACH,wBAAgB,SAAS,CACvB,MAAM,EAAE,MAAM,EACd,uBAAuB,EAAE,OAAO,EAChC,gBAAgB,EAAE,OAAO,GACxB,OAAO,CAuDT;AAED;;;;;;;;;;;;;;;;;;;;GAoBG;AACH,wBAAgB,wBAAwB,CACtC,SAAS,EAAE,QAAQ,EAAE,EACrB,oBAAoB,EAAE,mBAAmB,EAAE,EAC3C,iBAAiB,EAAE,SAAS,MAAM,EAAE,EACpC,uBAAuB,EAAE,OAAO,EAChC,gBAAgB,EAAE,OAAO;AACzB;;;;;GAKG;AACH,sBAAsB,GAAE,SAAS,qBAAqB,EAAO,GAC5D,sBAAsB,CAQxB"}
+{"version":3,"file":"evidenceReconciliation.d.ts","sourceRoot":"","sources":["../../src/domain/evidenceReconciliation.ts"],"names":[],"mappings":"AAAA,OAAO,KAAK,EACV,mBAAmB,EACnB,QAAQ,EAER,mBAAmB,EAGpB,MAAM,cAAc,CAAC;AAEtB,OAAO,KAAK,EAAE,MAAM,EAAE,MAAM,aAAa,CAAC;AAmB1C,OAAO,KAAK,EACV,4BAA4B,EAC5B,wBAAwB,EAExB,YAAY,EACb,MAAM,aAAa,CAAC;AAMrB,OAAO,KAAK,EAAE,iBAAiB,EAAE,sBAAsB,EAAE,MAAM,wBAAwB,CAAC;AA8NxF,wBAAgB,SAAS,CACvB,SAAS,EAAE,QAAQ,EAAE,EACrB,oBAAoB,EAAE,mBAAmB,EAAE,EAC3C,iBAAiB,GAAE,SAAS,MAAM,EAAO,GACxC,MAAM,CAoBR;AAED,MAAM,WAAW,gBAAgB;IAC/B,yBAAyB,EAAE,MAAM,CAAC;IAClC,UAAU,EAAE,MAAM,CAAC;IACnB,iBAAiB,EAAE,MAAM,CAAC;IAC1B,kBAAkB,EAAE,MAAM,CAAC;CAC5B;AAED,MAAM,WAAW,qBAAqB;IACpC,2BAA2B,EAAE,MAAM,CAAC;IACpC,2BAA2B,EAAE,MAAM,CAAC;CACrC;AAED,MAAM,WAAW,cAAc;IAC7B,QAAQ,CAAC,IAAI,EAAE,MAAM,CAAC;IACtB,QAAQ,CAAC,IAAI,EAAE,YAAY,GAAG,SAAS,CAAC;CACzC;AAED,MAAM,WAAW,iBAAiB;IAChC,QAAQ,CAAC,IAAI,EAAE,MAAM,CAAC;IACtB,QAAQ,CAAC,MAAM,EAAE,MAAM,CAAC;IACxB,QAAQ,CAAC,IAAI,EAAE,MAAM,CAAC;CACvB;AAED,MAAM,WAAW,cAAc;IAC7B,QAAQ,CAAC,KAAK,EAAE,MAAM,CAAC;IACvB,QAAQ,CAAC,EAAE,EAAE,MAAM,CAAC;IACpB,QAAQ,CAAC,KAAK,EAAE,MAAM,CAAC;CACxB;AAED,MAAM,WAAW,iBAAiB;IAChC,QAAQ,CAAC,MAAM,CAAC,EAAE,MAAM,CAAC;IACzB,QAAQ,CAAC,GAAG,EAAE,MAAM,CAAC;IACrB,QAAQ,CAAC,KAAK,EAAE,MAAM,CAAC;IACvB,QAAQ,CAAC,UAAU,EAAE,MAAM,CAAC;CAC7B;AAED,MAAM,WAAW,cAAc;IAC7B,QAAQ,CAAC,SAAS,EAAE,MAAM,CAAC;IAC3B,QAAQ,CAAC,UAAU,EAAE,MAAM,CAAC;IAC5B,QAAQ,CAAC,OAAO,EAAE,MAAM,CAAC;IACzB,QAAQ,CAAC,UAAU,EAAE,MAAM,CAAC;IAC5B,QAAQ,CAAC,QAAQ,EAAE,MAAM,CAAC;IAC1B,QAAQ,CAAC,YAAY,EAAE,MAAM,CAAC;CAC/B;AAED,MAAM,WAAW,OAAO;IACtB,uBAAuB,EAAE,4BAA4B,CAAC;IACtD,mBAAmB,EAAE,wBAAwB,CAAC;IAC9C,OAAO,EAAE,MAAM,CAAC;IAChB,UAAU,CAAC,EAAE,gBAAgB,CAAC;IAC9B,wBAAwB,CAAC,EAAE,MAAM,CAAC,mBAAmB,EAAE,MAAM,CAAC,CAAC;IAC/D,gBAAgB,CAAC,EAAE,qBAAqB,CAAC;IACzC,OAAO,EAAE,YAAY,CAAC;IACtB,kBAAkB,CAAC,EAAE,SAAS,iBAAiB,EAAE,CAAC;IAClD,WAAW,CAAC,EAAE,QAAQ,CAAC,MAAM,CAAC,MAAM,EAAE,MAAM,GAAG,IAAI,CAAC,CAAC,CAAC;IACtD,sBAAsB,CAAC,EAAE,SAAS,MAAM,EAAE,CAAC;IAC3C,sBAAsB,CAAC,EAAE,SAAS,cAAc,EAAE,CAAC;IACnD,wBAAwB,CAAC,EAAE,SAAS,MAAM,EAAE,CAAC;IAC7C,aAAa,CAAC,EAAE,SAAS,MAAM,EAAE,CAAC;IAClC,eAAe,CAAC,EAAE,SAAS,cAAc,EAAE,CAAC;IAC5C,kBAAkB,CAAC,EAAE,SAAS,MAAM,EAAE,CAAC;IACvC,cAAc,CAAC,EAAE,SAAS,iBAAiB,EAAE,CAAC;IAC9C,cAAc,CAAC,EAAE,cAAc,CAAC;CACjC;AAED,MAAM,WAAW,sBAAsB;IACrC,OAAO,EAAE,OAAO,CAAC;IACjB,MAAM,EAAE,MAAM,CAAC;IACf,kBAAkB,CAAC,EAAE,SAAS,iBAAiB,EAAE,CAAC;IAClD,sBAAsB,CAAC,EAAE,sBAAsB,CAAC;CACjD;AAED,wBAAgB,SAAS,CACvB,MAAM,EAAE,MAAM,EACd,uBAAuB,EAAE,OAAO,EAChC,oBAAoB,EAAE,OAAO,GAC5B,OAAO,CAsBT;AAED,wBAAgB,wBAAwB,CACtC,SAAS,EAAE,QAAQ,EAAE,EACrB,oBAAoB,EAAE,mBAAmB,EAAE,EAC3C,iBAAiB,EAAE,SAAS,MAAM,EAAE,EACpC,uBAAuB,EAAE,OAAO,EAChC,oBAAoB,EAAE,OAAO,GAC5B,sBAAsB,CAGxB"}