Skip to content

Add consensus-trust learning (DynaTD) with MBFC credibility prior + e…#33

Draft
muhaiminsk wants to merge 1 commit into
IBM:mainfrom
muhaiminsk:feature/consensus-trust
Draft

Add consensus-trust learning (DynaTD) with MBFC credibility prior + e…#33
muhaiminsk wants to merge 1 commit into
IBM:mainfrom
muhaiminsk:feature/consensus-trust

Conversation

@muhaiminsk

@muhaiminsk muhaiminsk commented Jul 17, 2026

Copy link
Copy Markdown

ConTrust: Consensus Trust Learning with MBFC (Media Bias/ Fact Check) credibility prior + evaluations

Introduces ConTrust (Consensus Trust Learning) — a source-reliability layer for
FactReasoner. Contexts are weighted by an MBFC-based credibility prior blended
with a dynamically-learned reliability score (implemented as DynaTD) that updates
from evidence rather than the model's own belief, fixing a self-referential trust
pathology in the original formulation.

  • Credibility-weighted consensus targets for the DynaTD reliability tracker
    (fixes self-referential trust feedback)
  • MBFC-based credibility prior (credibility_scorer_v3)
  • Evals: 40-row state-media (frozen contexts + NLI-replay demo), AVeriTeC 423 prequential
  • Baselines: Guardian 3.3/5b, granite-4.1-8b judge, g-3.2-8b-sft-detect-v5
  • switch-4.1 adapter: negative result documented (root cause confirmed via vendor io.yaml)
  • Unit tests for trust module (feature extraction, UTD, DynaTD, BayesianTrustFusion/CredibilityTrustFusion)
  • Frozen datasets, trust states, trajectory logs for deterministic reproduction

Results (hard-fact subset, n=27): ConTrust 81.5% vs vanilla 77.8% vs Guardian-3.3 70.4%.
AVeriTeC (423 claims, gold evidence): tied at ceiling (96.7% vs 96.6%) — honest
negative result on clean evidence. Limitations (held-out dev-set non-replication,
US/English-only credibility scorer, falsified geo-independence experiment) are
documented in full in experiments/consensus_trust/RESULTS.md.

…valuations

- Credibility-weighted consensus targets for DynaTD (fixes self-referential trust feedback)
- MBFC-based credibility prior (credibility_scorer_v3)
- Evals: 40-row state-media (frozen contexts + NLI-replay demo), AVeriTeC 423 prequential
- Baselines: Guardian 3.3/5b, granite-4.1-8b judge, g-3.2-8b-sft-detect-v5
- switch-4.1 adapter: negative result documented (root cause confirmed via vendor io.yaml)
- Unit tests for trust module (feature extraction, UTD, DynaTD, BayesianTrustFusion/CredibilityTrustFusion)
- Frozen datasets, trust states, trajectory logs for deterministic reproduction

Signed-off-by: Samit Muhaimin <Samit.Muhaimin@partner.ibm.com>
@muhaiminsk
muhaiminsk force-pushed the feature/consensus-trust branch from bb5d070 to b2c6654 Compare July 17, 2026 13:26
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant