Decision Files
Harmate connects hypotheses, answers, evidence, tests, and readiness so every arbitration stays traceable.
Four markers are enough to replay the reasoning without opening a dashboard.
Product Flow
The file connects the useful product pages when a team needs to defend a reasoning path.
1. Framing
Topic, audience, signals, constraints, and expected decision frame the file without forcing a hypothesis.
2. Sources
A file explicitly links several questionnaires, without an implicit primary questionnaire.
3. Hypotheses
The team can write a hypothesis or generate deterministic suggestions from the framing.
4. Evidence
Evidence can support, weaken, contradict, or stay neutral, with weak, medium, or strong strength.
5. Tests
A draft question converts only into an explicit target questionnaire and stays open.
6. Output
Readiness, synthesis decision, PDF, and JSON schema v4 restore the trace without an automatic verdict.
Evidence Chain
One hypothesis in the center, evidence and tests around it.
Hypothesis
The team states what must be tested, with scope, criticality, and expected impact.
High criticalityResults Evidence
Evidence does not become an opaque score: it keeps its stance, strength, and segment.
Supports / strongTest Question
The question stays open and neutral before conversion into the target questionnaire.
Explicit target questionnaireReadiness
The synthesis shows decision readiness without turning evidence into a verdict.
Human decisionThe reader does not only see the result: they can replay the reasoning, recover the evidence, and challenge weak spots.
Multi-Questionnaire
Sources converge without an implicit primary questionnaire.
Questionnaire 1
Questionnaire 2
Questionnaire 3
Shared Hypothesis
Not an Oracle
A preparation state, never an automatic verdict.
The file stays exploratory until an idea has been written or accepted.
Hypotheses exist, but useful evidence or questions are still missing.
Structured material can support an arbitration, without automating the decision.
A sensitive segment or weak evidence requires review before committee.
A strong contradiction or missing test prevents the arbitration from being defended.
The status can evolve with evidence, but it never turns a signal into automatic truth.
Explicit Safeguards
The real contract stays visible.
A file can remain exploratory until an idea has been written or accepted.
Hypothesis and question suggestions are deterministic in the delivered scope.
A supported hypothesis remains an evidence-backed idea, not an automatic truth.
A converted question keeps its target questionnaire; no implicit hierarchy is recreated.
Inside the Harmate Ecosystem
Useful paths stay accessible without turning the page into a menu.
No. A file can stay exploratory. Hypotheses become useful when a team wants to test an idea, connect evidence, and prepare a defensible arbitration.
No. Current suggestions are deterministic and built from the file framing: topic, audience, signals, constraints, and decision.
Yes. A file can carry several questionnaires without an implicit primary questionnaire, and each converted question keeps its target questionnaire.
No. The system qualifies evidence and updates a status reading, but the decision remains human, contextual, and reviewable.
Create a file, attach your questionnaires, and keep the trace that will let people reread the arbitration later.