How the method is separated
The method is kept in five distinct domains so that each answers one question and does not quietly stand in for another. Together they establish one thing — whether responsibility was fulfilled in a healthcare situation — on a basis anyone can inspect. This overview explains why they are separate and points to each. It reproduces none of them.
Constitutional truth, economic reasoning, research discipline, implementation discipline, and demonstrated knowledge are governed separately — on purpose.
Keeping them apart is what lets a claim be traced to exactly the rule that governs it, without one domain borrowing authority it has not earned. Start anywhere; each surface links back here and to the evidence overview.
Constitutional truth
Constitution
What constitutional rules govern the record?
- Governs
- Controlling definitions, the constitutional chain, separation of stages, perspective law, and evidence and verification rules.
- Does not determine
- It is not implementation documentation, a research repository, or a commercial page.
Economic reasoning
Economic method
How is an economic conclusion constructed and bounded?
- Governs
- The eight-category schema, the calculation, evidence requirements, exclusions, time boundary, and the realization-versus-verification distinction.
- Does not determine
- It is not a savings estimator, a recovery calculator, or a commercial promise.
Research discipline
Research method
How are sources ingested, reconstructed, bounded and preserved?
- Governs
- Source identity, perspective, observed problem, mechanism, responsibility versus authority, evidence, unresolved remainder, and research status.
- Does not determine
- It is not a general bibliography, a marketing authority page, or a conclusion engine.
Implementation discipline
Implementation method
How is the constitutional record implemented without changing truth?
- Governs
- Stored versus derived values, event and obligation distinctions, projection rules, validation, and implementation limits.
- Does not determine
- It does not claim that software or acceptance creates obligations, nor that product behaviour proves a live outcome.
Demonstrated knowledge
Demonstrated knowledge
What has the public product actually demonstrated, at what depth, and with what limitations?
- Governs
- Demonstrated capabilities, depth classifications, known insufficiencies, authored/live boundaries, and current proof status.
- Does not determine
- It is not a duplicate evidence overview, a general case catalogue, or an internal dashboard.