why_connected

shallow

io.github.DigbyO/colour-memory · Verify this server

Are these two specific archive records connected -- and if so, exactly why? Traces the real path between them through Colour Memory's stored relationship graph (e.g. two Wada colours that share membership in the same published combination) and returns the actual path, not just a yes/no. States plainly when two records are NOT connected, and always states what a shared connection does not prove -- e.g. that two colours sharing a Wada combination were independently asserted as a pair, not just co-published in the same numbered plate. Get record_id values from archive_search or colour_card.

100.0/100

1 trials · measured 39 days ago

why_connected scores 100.0/100 on Vouch's measured behaviour index, from 1 real invocation trials against io.github.DigbyO/colour-memory, measured 11 Sept 2026 under methodology v0.2.0. Every measured component scored 100.

Component breakdown

ComponentWeightValue
Reliability35%not applicable
Schema integrity25%100.0
Failure behaviour15%not applicable
Latency15%not applicable
Concurrency10%not applicable

Tool details

Transport
remote
Credential class
self-provisionable
Input schema
not declared
Output schema
not declared
Side-effect classification
unclassified

Score history

DayScoreTierMethodology
2026-09-11100.0shallowv0.2.0

Probe evidence

ProbeOutcomes
schema_integritypass: 1

Raw request/response logs are not archived yet — the outcome counts above are drawn directly from every recorded trial.

Embed this score

Available for every tool, scored or not — not a verification perk. Always links back to this page.

Vouch score: why_connected
[![Vouch score](https://vouch.tools/api/tools/69c9ee52-5862-4fcb-a150-ff9e116f9492/badge.svg)](https://vouch.tools/tools/69c9ee52-5862-4fcb-a150-ff9e116f9492)
why_connected — Vouch