Skip to content

About

A package for manipulating and visualizing evidence strenghts and how they combine

Resources

Stars

3 stars

Watchers

0 watching

Forks

Repository files navigation

Evidence Diagrams workspace

Explore how Evidence changes the credibility of a Claim.

Core npm version DOM npm version

This workspace contains the independently versioned public packages @bycelium/evidence-diagrams and @bycelium/evidence-diagrams-dom, the private propagation-math workspace, and a standalone demonstration consumer.

Open the live demo · Download the standalone demo

Demo walkthrough

1. Open the Claim and its Evidence summary

Inquiry overview with the root claim, current credibility, and combined evidence summary.

The root card starts with the Claim and its current credibility. Open it to reveal Combined Evidence, which compares accumulated Countering, dissonance, and Supporting Evidence.

2. Expand the diagram

Open the summary to follow every Evidence step from the prior credibility band to the current result.

Expanded Inquiry diagram with every Evidence row between the prior and current credibility bands.

3. Change the starting credibility

Use the inner chevron to collapse the Evidence path while keeping the prior and current credibility bands visible. Drag a prior handle to update the Inquiry or use ↺ to restore its starting value.

Reveal the Inquiry and change its prior

4. Inspect Evidence and follow its premise

Evidence drawer with the source Contribution, conditional impact, premise credibility, and current influence.

Select an Evidence arrow to see its premise, source Contribution, conditional impact, premise credibility, and current influence. Drag the conditional-impact handle to edit the relationship in 1 dBan steps and see its current influence update. Open the premise Claim to continue into its own Evidence subtree.

Adjust an Evidence relationship's conditional impact

5. Start another Inquiry

Inquiry page with the Add a Claim action above the current root Claim.

Select Add a Claim above the current root to start an Inquiry from a Claim and description, then add Supporting or Countering Evidence with a premise and HTTP(S) source. Switching roots preserves each Inquiry while the demo is open. Shared premises and sources stay identifiable across arguments; correlation between distinct arguments is not inferred automatically.

The live legend follows the selected Claim and its prior. Read the Inquiry model, nuclear-demo source audit, and dependence proposals for details.

Development

pnpm install
pnpm build:demo
pnpm check

build:demo regenerates the standalone demo/index.html page. It runs in English and French, follows the system color preference with a light fallback, stores explicit theme choices, and remains usable offline when downloaded. To regenerate the favicon PNGs from their editable SVG source, run pnpm build:demo-assets; it requires the Inkscape CLI. check runs the project checks and both packed-consumer tests. To add a locale, implement the consuming features’ typed message domains under demo/src/i18n/locales/, then register the locale in demo/src/i18n/index.ts.

Install Chromium once with pnpm exec playwright install chromium (see Playwright browser setup). From the repository root, refresh the README screenshots, GIFs, and social preview with pnpm screenshots. The capture command defaults to the local pinned Playwright module and ffmpeg/ffprobe from PATH; non-Nix environments need both executables installed. Pass --playwright-module, --browser-path, --url, or --ffmpeg-path only to override them.

For deployment, serve demo/ as the site root so index.html, robots.txt, sitemap.xml, and the favicon PNGs are available at their root paths. The generated page remains a self-contained offline demo.

Release procedures are in docs/releasing.md.

Apache-2.0. See LICENSE and NOTICE.

About

A package for manipulating and visualizing evidence strenghts and how they combine

Resources

Stars

3 stars

Watchers

0 watching

Forks

Releases

Packages

Contributors

Languages