Evidence and assessment
Understand what the materials establish and whether they support a conclusion.
← Home
RESEARCH / PROGRAMME MAP
A map of the research programmes
Six directions, each with its own subject, central question and boundaries. Start with the question your system needs to answer.
VISUAL CONTEXTLocal computing
How the directions relate
This is a map of research subjects. It explains complementary interests, without asserting an existing integration between programmes.
VISUAL CONTEXTConnections between nodes
Only a bounded summary of the local BOARD-EX-001 check is public; programme materials are reviewed within an agreed scope. This does not qualify a release. No separate packages for the other five programmes are published here. DA-EX-001 concerns only the inquiry form on this site.
Admission and execution
Separate an accepted change from the authority to execute a critical operation.
Trust and argument boundaries
Clarify the meaning of messages, assumptions and formal claims.
Compare by the question at hand
Cards provide a readable view on smaller screens. Switch to the table whenever useful.
- Central question
- Under which conditions may a critical operation be executed?
- Subject
- An operation and its authority
- When to explore
- When execution control, failures and recovery need to be examined.
- Central question
- Which evidence supports assessment of a specific release?
- Subject
- A version and its evidence package
- When to explore
- When a technical admission decision needs an explicit basis.
- Central question
- On what basis does a local system accept a conclusion?
- Subject
- Evidence, rules and a conclusion
- When to explore
- When locality, determinism and accountable assessment matter.
- Central question
- When may a proposal change local state?
- Subject
- Admission and state consistency
- When to explore
- When a proposal must be separated from an authorized change.
- Central question
- What does another node’s message allow us to conclude?
- Subject
- Node interaction and trust boundaries
- When to explore
- When information, state and authority are distributed across nodes.
- Central question
- What is being established, and under which assumptions?
- Subject
- A claim, model and argument
- When to explore
- When formal statements and independent review are needed.
| Programme | Central question | Subject | When to explore |
|---|---|---|---|
| 01AVRIAL | Under which conditions may a critical operation be executed? | An operation and its authority | When execution control, failures and recovery need to be examined. |
| 02BOARD | Which evidence supports assessment of a specific release? | A version and its evidence package | When a technical admission decision needs an explicit basis. |
| 03LIDIYA | On what basis does a local system accept a conclusion? | Evidence, rules and a conclusion | When locality, determinism and accountable assessment matter. |
| 04ENEY | When may a proposal change local state? | Admission and state consistency | When a proposal must be separated from an authorized change. |
| 05TCRF | What does another node’s message allow us to conclude? | Node interaction and trust boundaries | When information, state and authority are distributed across nodes. |
| 06NEMESISJAM | What is being established, and under which assumptions? | A claim, model and argument | When formal statements and independent review are needed. |
Similar language. Distinct questions.
BOARD ↔ LIDIYA
BOARD focuses on evidence assessment of a defined artifact. LIDIYA concerns local evidence handling and rules for accepting conclusions.
AVRIAL ↔ ENEY
AVRIAL examines execution and recovery of critical operations. ENEY concerns admission of proposed changes and local state consistency.
TCRF ↔ NEMESISJAM
TCRF examines interaction between nodes. NEMESISJAM concerns formulation and substantiation of properties, including their assumptions.
R&D / DIALOGUE
You do not need a programme name.
Describe the decision, action or state that needs to become accountable. That is the starting point for defining the work.