Know what a controlled change actually changes

A new version is only the beginning

Version history tells you that a file changed. Text diff shows which characters changed. Neither establishes what changed in meaning, what depends on it, or what evidence is required before the change may be treated as closed.

EvidView separates those questions so a team can inspect the basis of each material conclusion instead of accepting a fluent summary as authority.

• File changed ≠ meaning understood
• Meaning changed ≠ downstream effect confirmed
• Finding produced ≠ human decision recorded
• Analysis complete ≠ change closed

One change, traced through its consequences

Compare an approved source-version pair. Bind material old and new meaning to exact excerpts. Evaluate dependency candidates inside a declared portfolio. Put uncertainty and policy-sensitive findings in front of an accountable reviewer.

The intended end-to-end workflow then connects accepted findings to actions, implementation evidence, approvals, and closure. Action assignment and complete closure packaging remain research direction rather than current prototype capability.

• Controlled source → Semantic Delta
• Semantic Delta → dependency paths
• Paths → bounded impact findings
• Findings → human judgment
• Research direction: judgment → action → evidence → closure

Five artifacts keep different questions separate

The target product surface uses distinct artifacts so evidence, inference, review, scope, and closure are not collapsed into one status.

• Semantic Delta — the material claim-level change and its exact before-and-after evidence. It does not prove downstream impact.
• Impact Register — affected, potentially affected, and review-required objects with paths and reasons. An inferred path remains an inference until reviewed.
• Conflict and Ambiguity Queue — evidence or meaning that cannot safely be resolved without more information or judgment.
• Unaffected Scope — successfully processed objects for which no relevant path was found inside the declared evaluation boundary. It is not a universal no-impact claim.
• Change Evidence Package — the intended record of decisions, actions, evidence, limitations, and closure state. The complete package and closure workflow are not current M0–M4 capabilities.

Inspect the path, not just the answer

The prototype can retain exact old and new evidence for semantic change records, evidence and lifecycle state for dependency candidates, and reconstructable paths for positive bounded impact findings.

Known ambiguity, stale inputs, unsupported evidence, and exhausted budgets remain visible instead of silently becoming accepted or unaffected conclusions.

Built for accountable judgment

Machine inference proposes and organizes. Deterministic rules check only what their declared scope supports. Named people confirm, correct, reject, or leave records unresolved.

EvidView is designed to reduce unnecessary review without removing the people accountable for policy, context, and approval.

Current status, without ambiguity

Implementation: M0–M4 source, semantic-change, dependency, impact, and review surfaces exist in the repository.

Verification: the recorded baseline is locally qualified with synthetic fixtures and named checks.

Availability: Prototype. No public self-service or production availability is claimed.

Evidence: thesis, synthetic cases, and one published one-path internal development benchmark. No customer, pilot, generalizable performance, or commercial-outcome claim is made.

Bring a change worth understanding

Start with a historical controlled-document revision and the downstream material your team had to assess. The first conversation needs no confidential source document.

• Bring a Change
• Become a Design Partner