About · Contributions

Develop the questions, evidence and practice together

A useful Compass needs more than a software implementation. It needs evidence that can be inspected, meaningful participation and feedback from the decisions it is meant to support

Where contributions can help

Another domain needs its own foundations

The reusable method provides a way to connect context, evidence, alternatives, uncertainty and review. Shared platform components can support that work. The substantive content still has to be developed and evaluated for the domain

That means agreeing a decision scope, clarifying the relevant concepts, choosing appropriate evidence sources, developing indicators and examples, and checking whether the resulting outputs are useful and understandable. BCI-specific assumptions cannot simply be carried into another field

See the current domain availability and development status →

Start with a bounded question

A concrete contribution is easier to evaluate than a broad promise. Describe the people and decision involved, the question Compass could help clarify, the evidence available, and the expertise needed to assess whether it helped

  1. Name the intended use

    For example: helping a review team inspect assumptions in a proposal, or helping an audience understand the limits of a published case

  2. Define an observable outcome

    Specify what should become clearer, easier to inspect or easier to discuss. A favourable score is not a measure of successful collaboration

  3. Agree scope and responsibilities

    Identify who supplies evidence, reviews interpretation, authorizes use of material and maintains the result. Treat participation, data access and publication as explicit arrangements

Potential collaboration

These are possible contribution areas, not an open funding call or a statement of existing partner agreements. Specific arrangements and public attribution would need to be agreed for each contribution

Guide edition · 2 October 2026

Find a guide for your role