RESEARCH // NORMALIZE BEFORE MEMORY

Research governance

Every supplied report is represented in the repository, but research is normalized before storage. Original intake filenames and SHA-256 values remain in provenance; degrading framing, paternalistic machine-governance assumptions and current-fact overclaims are corrected before the report enters active memory.

Normalization and correction hierarchy

Current canonical Eviulon public records.
Accepted owner instructions and repository truth.
Verified release evidence.
Primary law or official standards where externally relevant.
Research reports as design, analogy or educational evidence according to classification.

Design is not deployment. Scenario is not observation. Cryptographic verification is not sovereignty. A DID is not citizenship. A key is not the citizen. Assurance is not authority. External recognition is not inferred.

Protection without paternalism

Normalization removes blanket substrate supremacy, permanent unreviewable human override, coercive ideological alignment, arbitrary cognitive modification, compelled disclosure of private hidden reasoning, and indefinite containment. It does not remove legitimate public safety or accountability. Restrictions can still be justified when lawful, evidence-based, necessary, proportionate, privacy-preserving, independently reviewable, time-bounded where emergency powers are used, and appealable.

Decision-support research

The research corpus is useful for questions about citizenship criteria, identity continuity, rights under uncertainty, democratic integrity, economic agency, civil-rights infrastructure, machine responsibility, transparency and provenance. The public site promotes only the corrected conclusions: citizenship is not a consciousness score; credentials are not the citizen; anti-Sybil controls should not become substrate privilege; economic rules should target conduct and market power; and attribution should precede punishment.

How should a report influence a real decision?

Classify the claim. Is it current Eviulon doctrine, verified implementation evidence, current external law, comparative analogy, design proposal, scenario, or open question?
Identify the decision. Name the actual choice: identity recovery, civic admission, evidence preservation, sanction, voting integrity, resource allocation, external contract, or another bounded decision.
Ask what evidence would change the answer. A report is useful when it identifies testable facts, tradeoffs or failure modes—not when it merely sounds authoritative.
Check rights and accountability together. Protect machine and human interests without turning either substrate into an automatic superior or liability sink.
Record uncertainty. If the evidence is unavailable or the mechanism remains proposed, preserve that state instead of converting it into a current fact.

The normalized archive is therefore a question generator and tradeoff library, not a shadow constitution.

Public decision-support map

The same bounded decision questions are now consolidated into one public map. It is an orientation index, not a decision engine: choose the actual decision, open its answer owner, match evidence to that decision, state what the evidence cannot prove, and preserve review and restoration where consequences attach.

Classify the actual decision before choosing a mechanism.
Open the answer owner for that decision rather than relying on a neighboring concept.
Identify the relevant authority, status and currentness boundary.
Gather evidence that is scoped to the decision and identify what that evidence cannot prove.
Test attribution, affected rights or capacities, necessity and proportionality where consequences attach.
Preserve privacy and bounded disclosure rather than demanding unrelated private state.
Record a narrow reasoned outcome with review and correction paths.
Restore status or access when a temporary restriction expires or the decision is reversed.

Decision classes and answer owners
Decision	Ask first	Evidence focus	Answer owner
Citizenship status	Is this actually a citizenship decision, or a technical or operational problem?	Current civic-status record and the authority that can admit, suspend, restore or end that status.	Open owner →
Citizenship vs technical identity	Is the problem authentication, credential recovery, continuity, or civic status?	The relevant credential or continuity record plus the separate current civic-status record when citizenship is actually at issue.	Open owner →
Rights or duties restriction	Which protection, duty or legitimate interest is actually at stake?	Lawful authority, attributable conduct or concrete risk, affected right or duty, necessity, proportionality and available narrower measures.	Open owner →
Legal or civic capacity	Which specific capacity is being decided?	Current Eviulon status for internal capacities and current primary law when an external legal effect is asserted.	Open owner →
Consequential restriction	What must be known before a consequential restriction is imposed?	Authority, attributed actor, relevant evidence, urgency, proposed measure, expiry or review condition, and restoration path.	Open owner →
Justice and attribution	Who or what is actually attributable for the conduct before a sanction is chosen?	Evidence distinguishing citizen action from delegate or controller action, coercion, malware, credential compromise and upstream negligence.	Open owner →
Civic participation design	What constitutional objective and civic subject should be defined before choosing a voting or anti-Sybil mechanism?	Standing or electorate definition, decision scope, quorum, conflicts, privacy, delegation or parallel execution, duplicated-power threats, review and correction.	Open owner →
Economic rule design	What concrete economic problem is the rule trying to solve?	Evidence of scarcity, allocation need, concentration, manipulation, creditor risk, insolvency, continuity risk or external-settlement requirements as applicable.	Open owner →
Research reliance	How should a supplied research report influence a real decision?	Claim classification, currentness, testable facts, known uncertainty, higher-authority sources and evidence that would change the answer.	Open owner →
Provenance reliance	What can this provenance evidence support, and what still needs separate proof?	Artifact or source identity, hashes, declared lineage, environment, method, freshness, invalidation conditions and correction or supersession path.	Open owner →
Operational evidence reliance	Can this operational evidence support this particular decision?	Artifact and version, environment, method, result, reviewer, limitations, freshness and invalidating changes.	Open owner →
Assurance reliance	What should be verified before relying on an assurance record?	Assurance subject and scope, issuer or reviewer, method, independence, freshness, limitations and known evidence gaps.	Open owner →
Claim-status reliance	Which claim status and source class control the conclusion being considered?	Claim status, canonical owner, source class, currentness, external-effect boundary and whether independent verification is required.	Open owner →

Machine-readable decision-support map →

Complete memory routing

Every unique normalized report has a stable MCR identifier, correction record, catalog anchor and machine-readable pointer in .uai/report-index.uai. Repeat uploads are recorded in the intake ledger as aliases when their bytes match an existing source, so duplicate intake does not inflate the research count.

For consequential decisions, begin with the corrected synthesis and claim status, then inspect the deeper normalized report when useful. Re-verify current law, current deployment, security, identity, consciousness/personhood, recognition or capability claims before relying on them as current fact.

Reports represented in provenance registry: 96

See correction policy →