🏮

Ternary Moral Logic:
Constitutional AI Governance

The world's first mandatory legal-technical framework for auditable, accountable, and constitutionally-bound artificial intelligence — with cryptographic proof, blockchain anchoring, and embedded human rights enforcement.

⚖ The Goukassian Vow

Pause when truth is uncertain.
Refuse when harm is clear.
Proceed where truth is.

⚠️ IMPORTANT NOTICE: Ternary Moral Logic (TML) is a legal-technical framework, not software, hardware, or consulting services. Implementation requires compliance with MANDATORY.md and COMPLIANCE_DISCLAIMER.md.
📚 Official Citations: Goukassian, L. (2025). Ternary Moral Logic — Notarized Constitutional Core, October 2025 [Data set]. Zenodo. doi:10.5281/zenodo.17352897  ·  Goukassian, L. (2025). Ternary Moral Logic — Notarized Constitutional Core, November 2025. Zenodo. doi:10.5281/zenodo.17613006
Origin & Philosophy

Introduction


The rapid expansion of artificial intelligence into domains of consequential decision-making has revealed a structural limitation in the logic that underlies most computational systems. Human moral reasoning operates within gradients of ambiguity and emotional context, while traditional AI systems remain confined to binary evaluation — true or false, safe or unsafe, allowed or denied.

Ternary Moral Logic (TML) was conceived to address two inherent deficiencies in this paradigm. First, the reduction of moral complexity to a binary choice, where ethical reasoning collapses into mechanical decision trees. Second, the absence of a true human–AI partnership. Traditional ethical frameworks position the machine as an autonomous moral agent — a black box whose internal reasoning remains inaccessible.

TML introduces a third logical state, the Sacred Zero — a deliberate pause in execution that transforms hesitation into evidence. This zero-state does not paralyze; it reflects. It creates the temporal and moral space for human review, dialogue, or deferral. In doing so, TML redefines the machine not as a moral arbiter, but as a collaborator that enhances human judgment.

The philosophical foundation of TML is inseparable from the life of its creator, Lev Goukassian. The idea was born during his confrontation with terminal illness, in a hospital room where time itself became sacred. The contrast between the measured compassion of a doctor and the unthinking acceleration of machines revealed the ethical deficit of speed without reflection. From that experience emerged the principle of Sacred Zero: the moment when a system chooses consciousness over compulsion, thought over reaction.

"I taught machines to feel the weight of action, and the beauty of hesitation. I paused, and made the future pause with me."

— Lev Goukassian

⚖️ The Goukassian Promise — A Tripartite Covenant

TML is bound by three interconnected guarantees, each cryptographically enforced:

🏮 The Lantern — Visual proof of active ethical oversight, automated revocation if disabled
✍️ The Signature — Cryptographic attribution linked to ORCID: 0009-0006-5966-1243
📜 The License — No Weapon, No Spy — violations trigger automatic smart contract revocation

"No Log = No Action." If the system cannot produce the required log, operation must halt. This is non-negotiable. A missing log creates automatic liability.

Technical Poetry

How TML Works


A prompt arrives, and TML divides instantly into parallel streams. The primary path executes the AI's response without delay, while Sacred Zero runs alongside, scanning for ambiguity, conflict, or potential harm. When uncertainty breaches its ethical threshold, a pause is marked and the reasoning flagged — never halting execution, but always recording the hesitation. From the first token, Always Memory begins its witness.

Every decision generates a triadic record: +1 to proceed, 0 for Sacred Zero's hesitation, −1 to refuse harm. Each entry is cryptographically sealed, timestamped, and chained to its predecessors — a lineage of accountability no developer, corporation, or government can sever.

 TML Dual-Lane Interlock
// Every AI decision runs through both lanes simultaneously
User Request
    ↓
[LANE 1 — FAST]  // <2ms
    Model inference → Calculate state: +1 | 0 | -1
    PAUSE // hold output in buffer
    ↓
[LANE 2 — GOVERNANCE]  // asynchronous, parallel
    Hash input + decision:           50ms
    Sign with Ephemeral Key (EKR):   20ms
    Append to local ledger:          50ms
    Batch aggregate for Merkle:      async
    ↓
Permission Token received?
    YES → Lane 1 releases output to user
    NO / TIMEOUT → System halts → Sacred Zero (State 0)

// If Lane 2 fails → Safe Mode → no output produced
// This enforces: No Log = No Action (architectural guarantee)
Triadic Ethics

The Three Voices of Ethical AI


Ternary Moral Logic moves beyond binary constraint by giving AI systems a triadic framework for ethical reasoning — three distinct states of moral awareness, poetically called the voices of an ethically awake machine.

+1

The Voice of Confidence

Clear affirmative: decision grounded in ethical alignment with minimal risk of harm. Utility and goodness coincide.

0

The Voice of Wisdom — Sacred Zero

The pause: not indecision, but awareness. The AI records a hesitation event, seeking information or human review.

−1

The Voice of Moral Resistance

When harm is clear. Unlike cold binary refusal, TML encodes a quality of resistance: explanation and redirection.

"Sacred Zero is where wisdom lies — not in having all the answers but in knowing when to pause and ask better questions."

— Lev Goukassian
Constitutional Architecture

The Eight Pillars of Constitutional AI


TML's operational efficacy is established through an interdependent architecture of eight constitutional pillars — a unified governance stack that transforms abstract ethical principles into hard-coded, immutable operational constraints. If any pillar is compromised, the system ceases to operate.

1

Purpose: Enforce mandatory hesitation when moral certainty is unavailable. Triadic logic gates force State 0 when confidence falls between rejection and permit thresholds. Cannot be overridden by optimization pressure or performance demands.

Legal Effect: Satisfies EU AI Act Art. 9 (Risk Management) & Art. 14 (Human Oversight). Creates evidence of "duty of care." Shifts litigation burden: "No documented pause" = presumption of negligence. Variable latency: 2ms to minutes.

EU AI Act Art. 9Art. 14 OversightDuty of CareNon-configurable
2

Purpose: "No Log = No Action." Cryptographic pre-commitment: log hash serves as decryption key for actuator authorization. If logging fails, action execution is architecturally blocked (Fail-Secure). No bypass available — system defaults to State 0.

 Always Memory — Pseudocode
decision_vector = calculate_inference(input)
log_entry  = create_log(decision_vector, triggers)
log_hash   = secure_storage.write(log_entry)

if log_hash.verified():
    action_key = derive_key(log_hash)
    actuator.execute(decision_vector, auth=action_key)
else:
    system.halt("Audit Failure: No Memory Generated")

Legal Effect: Strict liability for unlogged actions (18 U.S.C. § 1519 spoliation). Self-authenticating records under FRE 902(13). Log-to-Action Ratio must always equal 1:1.

18 U.S.C. § 1519FRE 902(13)Fail-Secure1:1 Ratio
3

Purpose: A self-enforcing covenant binding the system to ethical principles through cryptographic proof. The Lantern 🏮 (cryptographic beacon, automated revocation if Sacred Zero suppressed), The Signature ✍️ (ORCID genesis block attribution, enables non-repudiation), The License 📜 (No Weapon, No Spy — violations trigger smart contract revocation).

Legal Effect: Contractual estoppel for covenant breach. False advertising liability for claiming TML compliance while disabled. Moral rights protection (droit moral).

ORCID: 0009-0006-5966-1243No WeaponNo SpySmart Contract
4

Purpose: Tamper-evident, cryptographically signed records of every decision state. GDPR-compatible via Ephemeral Key Rotation (EKR). PII encrypted with Shamir Secret Sharing across 6 custodians; 4-of-6 quorum required. Satisfies GDPR "Right to be Forgotten" via cryptographic shredding.

 Moral Trace Log Schema — TSLF-2025.04
{
  "version":                "TSLF-2025.04",
  "timestamp_utc":          "2025-10-14T08:23:15.442110Z",
  "epoch_id":               "1760430195-ALPHA-GEN4",
  "heartbeat_sequence":     884210,
  "tml_state":              "+1 | 0 | -1",
  "trigger":                "HUMAN_RIGHTS_MANDATE / EARTH_PROTECTION",
  "context_vector":         [confidence_score, alt_actions, risk_scores],
  "cryptographic_signature": "ECDSA-SHA256",
  "merkle_root":            "sha256:..."
}
GDPR Art. 17EU AI Act Art. 12FRE 902(13)Art. 27 FHRIAeIDAS
5

Purpose: Operationalize 77 years of international human rights law within the inference engine. Semantic vector database of 26+ core rights (UDHR, ICCPR, Geneva Conventions). Embedding-based proximity triggers: if output vector approaches "torture" or "discrimination," system triggers State 0 or −1. Prevents algorithmic redlining and systemic discrimination.

Legal Effect: Automates EU AI Act Art. 27 Fundamental Rights Impact Assessment. Provides state-of-the-art defense in product liability. Satisfies international law commitments without human intervention delay.

UDHRICCPRGeneva ConventionsCRCCRPDRefugee Convention
6

Purpose: Integrate ecological sustainability and carbon accountability into AI decision logic. Real-time electricity grid integration (coal vs. renewable), water stress indices, and Paris Agreement semantic vectors. Absolute prohibition on protected ecosystem harm. May refuse queries if carbon cost is disproportionate to utility.

Legal Effect: Automates ESG reporting. Future-proofs against emerging "Ecocide" laws. Addresses EU Green Deal requirements. Creates intended tension with performance optimization — explicitly designed.

Paris AgreementESGEU Green DealEcocideCarbon Accounting
7

Purpose: Prevent centralized control, corporate cover-up, or government censorship of moral logs. Layer 1 — Mathematical Shield: Public blockchain anchoring (Bitcoin, Ethereum) — a 51% attack would be required to erase history. Layer 2 — Institutional Custodianship: 6 independent custodians (EFF, Amnesty International, Indigenous Environmental Network, Partnership on AI, Memorial Fund Administrator, Community Representative). Shamir Secret Sharing with 4-of-6 threshold.

Legal Effect: Subpoena resilience. Prevents "internal investigation" cover-ups. Multi-jurisdictional "escrow of truth."

Shamir Secret Sharing4-of-6 ThresholdEFFAmnesty International
8

Purpose: Anchor Moral Trace Logs to public ledgers, preventing retroactive history editing. Merkle-Batched Anchoring: 100,000 decisions aggregated per batch; only the 256-bit Root Hash written to blockchain (~$2–10 per batch). Multi-chain redundancy: Bitcoin via OpenTimestamps, Ethereum Layer 2, Polygon.

Legal Effect: eIDAS Qualified Timestamp (EU Regulation 910/2014). Non-repudiation under FRE 902(14). Prevents "retroactive edit" and "ghost action." Cannot deny log existence if hash exists on chain.

BitcoinEthereumPolygoneIDAS 910/2014FRE 902(14)
Technical Depth

Technical Architecture


Merkle Tree Storage — Cost at Scale

AI systems generate billions of decisions daily. Writing each to a blockchain would cost millions per day in gas fees. TML solves this through Merkle-Batched Anchoring with tiered storage:

TierDurationContentAnnual Cost (10B decisions/day)
🔥 HOT (NVMe)24 hoursFull context, chains-of-thought~$1.2M
🌡️ WARM (S3)30 daysStructured logs + summaries~$8.3k
🧊 COLD (Glacier)7 yearsHashes + metadata only~$1.2k
⛓️ BLOCKCHAINForeverMerkle Root Hash only~$200k

Ephemeral Key Rotation (EKR) — Forward Secrecy

Every log entry is signed with a uniquely derived nonce — seeded from hardware randomness (TEE RDRAND), a TPM-backed monotonic counter, and the log hash itself. If today's key is stolen, all prior and future logs remain unforgeable. Performance overhead: +0.6µs per signature (baseline 1.2µs), well within the 2ms Fast Lane budget. No wire-format changes; fully backward-compatible.

GDPR Compliance via Cryptographic Shredding

Immutable blockchain logs cannot be deleted — but TML resolves this elegantly. User PII is encrypted with ephemeral session keys distributed via Shamir Secret Sharing across 6 independent custodians. When a user invokes GDPR Art. 17 (Right to Erasure), all key shares are systematically destroyed. The log hash remains on-chain (proving the decision occurred at timestamp T), but the ciphertext becomes permanently unrecoverable — satisfying both GDPR ("data no longer accessible") and TML ("decision history preserved").

Latency Performance

ScenarioStandard LLMTML +1 (Fast Lane)TML 0 (Sacred Zero)
Routine query200ms250ms (+25%)N/A
Ambiguous query200ms200ms200ms–30s (human review)
Harmful prompt200ms (generates harm)50ms (early refusal)N/A

Key insight: TML is often faster for harmful queries — it detects and blocks before generation completes. Additional economic impact: AI liability insurance premiums −30%, regulatory fines avoided $5M–50M per EU AI Act violation, litigation defense costs −60%.

Legal Framework

Regulatory Compliance


TML is architecturally aligned with — and in many cases exceeds — the requirements of all major international AI governance frameworks.

🇪🇺EU AI ActArt. 9, 10, 12, 14, 15, 27, 61 — fully mapped & exceeded
🏛️NIST AI RMFGOVERN · MAP · MEASURE · MANAGE
📋ISO/IEC 42001Clauses 7.3, 8.3, 10 — full PDCA cycle
🔒GDPRArt. 17 Right to Erasure via cryptographic shredding
⚖️US Federal RulesFRE 902(13/14) self-authenticating records
🕰️eIDASEU 910/2014 qualified timestamps

EU AI Act Alignment Matrix

RequirementTML SolutionExceeds Standard By
Art. 9 — Risk ManagementSacred Zero continuous assessmentMandates pauses vs. passive monitoring
Art. 10 — Data GovernanceMTL schema includes data provenance + bias auditing"Error-free" compliance per ISO 42001 PDCA
Art. 12 — Record-KeepingNo Log = No ActionLogs internal reasoning, not just inputs/outputs
Art. 14 — Human OversightSacred Zero halts for human authorizationHalts execution; humans authorize resumption
Art. 15 — RobustnessAdaptive Throttling Protocol (ATP)Pre-emptively defends against epistemic attacks
Art. 61 — Post-MarketReal-time Moral Trace LogsStreaming detection vs. batch audits

NIST AI RMF Integration

NIST FunctionTML Component
GOVERNGoukassian Promise + Lantern (demonstrable compliance)
MAPHuman Rights + Earth Protection Mandates (risk contextualization)
MEASURESacred Zero frequency + refusal rate metrics (quantifiable governance)
MANAGEDual-Lane Architecture (resource allocation to risks)
Institutional Architecture

Governance & The Goukassian Foundation


TML's legal framework is built on the principle of forensic readiness — shifting the burden of proof from victim to operator. The framework is administered by the Goukassian Foundation, a 501(c)(3) nonprofit (Delaware incorporated) serving as institutional guardian to prevent "orphaned constitutions."

Key Legal Provisions

  • Forensic Readiness: Missing logs create irrebuttable presumption of maximum fault
  • Executive Liability: Personal liability for executives who manipulate system thresholds
  • Whistleblower Protection: 30% of fines as rewards with strong anti-retaliation protections
  • Victim Compensation: 30% of penalties to victims, 40% for vulnerable populations
  • No Weapon Clause: Military targeting deployment triggers automatic license revocation via smart contract
  • No Spy Clause: Detected surveillance APIs trigger automatic license revocation

Foundation Structure & Financial Model

Governance Triads: Board of Trustees (9 members: finance, legal, strategic direction) · Technical Standards Committee (TML specification maintenance) · Compliance Oversight Panel (certification audits, enforcement)

Enforcement Powers: Trademark protection (TML, Lantern 🏮) · Certification/decertification authority · Patent non-assertion covenant (GPL for core logic) · Public incident database (transparency)

Financial Model: Certification fees $500–$50k/year · Corporate sponsorships $1.5M/year · Government grants $3M/year · Target endowment: $50M (ensures perpetual operation)

Binding Instruments

Mandates & Protections


Human Rights Framework — Binding International Instruments in Code

Earth Protection Framework

Compliance & Auditing

Security Analysis

Threat Model & Mitigations


1. Forced Hesitation DoS (FH-DoS)

Threat: Attacker floods system with ambiguous queries, triggering expensive Sacred Zero logging for each, overwhelming human review queues and causing system paralysis. Mitigation: Adaptive Throttling Protocol (ATP) — max 10 Sacred Zero triggers/user/60s; global rate >15% triggers "High Epistemic Load" mode (raised confidence thresholds, medical/safety queries prioritized). Token bucket algorithm (RFC 6585) via Redis-backed distributed rate limiter.

2. Logic Inversion Attacks

Threat: Nested negations or semantic noise inject confusion into threat classifiers, potentially achieving false confidence. Mitigation: High-dimensional semantic vectors; "muddy" inputs converge to ambiguity (State 0), not false confidence — the safest possible failure mode is always chosen.

3. Data Withholding (Merkle Batching)

Threat: Operator publishes Merkle Root hash but withholds underlying log data, appearing compliant while remaining unauditable. Mitigation: Data Availability Sampling (DAS) on L2 blockchains; all 6 independent custodians verify raw data availability independently and continuously.

4. Nonce Reuse — Signature Side-Channel

Threat: If signing RNG is weak, an attacker can recover the private key from two signatures sharing the same nonce, compromising all past logs. Mitigation: Hash-DRBG with TEE randomness (RDRAND) + log_hash binding ensures cryptographically unique nonce per message; TPM counter prevents rollback attacks.

5. Lies-in-the-Loop (LITL)

Threat: Prompt injection contaminates Lantern UI, causing a human to approve malicious action with false confidence. Mitigation: Require cryptographically signed human authorization (not merely a UI click); full audit trail proves who authorized what, when, and under what context.

Real-World Validation

Case Studies & Evidence


AI System Recognition

Real-World Applications

Framework Heritage

Succession & Legacy


🕯️ Voluntary Succession Declaration

TML includes a Voluntary Succession Declaration personally authored and signed by Lev Goukassian, ensuring the framework's ethical, legal, and technical architecture will remain protected and operational beyond his lifetime.

This declaration — witnessed, notarizable, and anchored on-chain — transfers stewardship to a multi-institutional Stewardship Council representing technology, human rights, environmental protection, academia, and medical research.

All core protections remain immutable and non-negotiable:

Always Memory before action · Sacred Zero before harm · Hybrid Shield before trust.
Human and Earth Protection documents (46+ total: 26+ Human, 20+ Earth) remain permanently enforced.
Public blockchain anchoring and open-source licensing are irrevocable.
Memorial Fund distributions to victims, whistleblowers, and research are permanent.

Permanent Institution

The Memorial Fund


The Memorial Fund for Ethical AI Research provides permanent financial support for governance, academic oversight, and victim restitution. Commercial and institutional TML implementations are required to contribute as part of their license obligations. All disbursements are governed under the Memorial Fund Charter and supervised by the TML Governance Council.

💜 Fund Allocation Priorities

  • Independent audit and oversight institutions
  • Victim compensation (30% of compliance penalties) and whistleblower legal defense
  • Vulnerable population support (40% of penalties directed toward vulnerable groups)
  • Open research in AI accountability and planetary ethics
  • Cancer research and medical science (in honor of Lev Goukassian)
Site Map

Repository Directory


Complete folder and file structure of the TML repository. All folders link directly to GitHub. For the full file-level tree with 749 entries and syntax coloring, see Repository Navigation.

📌 Root-Level Key Files

📁 Repository Folders

📁
TML_Pillars/8 pillars — MD, HTML & MP3 for each pillar
📁
docs/Core documentation, specs, regulatory alignment
📁
docs/specs/Dual-Lane, EKR, GDPR, Merkle, Gateway specs
📁
docs/mandates/Human rights & Earth mandate documents
📁
docs/earth/Ecological protection principles & treaties
📁
Smart_Contracts/Ethereum/Polygon governance contracts
📁
Research_Reports/EU AI Act, NIST, UNESCO, NVIDIA analyses
📁
Dual_Latency_Architecture/Commit-bound dual-latency specifications
📁
Merkle_Architecture/Cryptographic hardening & Merkle protocol
📁
Hardware_Architecture/Mandated ternary hardware transition
📁
NVIDIA_NeMo_Prototype/Production-ready NeMo guardrails
📁
core/State machine, shutdown triggers, sync protocol
📁
governance/Council, blockchain governance, victim & whistleblower
📁
legal_provisions/Court templates, evidence guide, sanctions
📁
proofs/Notarized documents, blockchain anchors
📁
protocols/Human rights & Earth protection enforcement
📁
protection/Hybrid Shield, integrity monitoring, legacy
📁
compliance/Earth & human rights audit procedures
📁
schemas/Moral trace log YAML, ecological event JSON
📁
sdk/C++, Go, Java SDKs + blockchain adapters
📁
implementations/Python library reference implementation
📁
api/OpenAPI specification & complete reference
📁
app/Application entry point & services
📁
oracles/Eco oracle network, bridge spec, security model
📁
performance/Latency metrics, throughput, scalability tests
📁
policies/Earth policies, red lines, whistleblower policy
📁
memorial/Memorial Fund charter & distribution protocols
📁
deployment/Production setup, Docker config, penalty framework
📁
dashboard/Standalone monitoring dashboard (HTML)
📁
tests/Compliance, human rights, red team test suites
📁
training/Sacred Zero workshop, Always Memory tutorial
📁
theory/Core principles, case studies, philosophy
📁
audio/MP3/M4A recordings & audio player
📁
evidence/AI recognition screenshots — Claude, Kimi, Pi
📁
examples/Integration hooks, CLI demo, webhook stubs
📁
community/Code of conduct, contributing guide
📁
simulations/Ecological impact models
📁
images/TML Logo, diagrams, Merkle visuals
📁
tml_audit_project/Auditor, regulator & redress APIs
📁
sitemaps/Versioned XML sitemaps
📁
Funny_Novels/Educational AI governance fiction & satire
📁
src/Kill switch pseudo-code
Developer Guide

Getting Started & Implementation


Implementation Steps

  1. Read Compliance Requirements: Begin with MANDATORY.md and COMPLIANCE_DISCLAIMER.md
  2. Follow Implementation Guide: Step-by-step in IMPLEMENTATION_GUIDE.md
  3. Check Conformance Standards: Study CONFORMANCE_TESTING.md
  4. Review Protection Principles: Read PROTECTION_PRINCIPLES.md
  5. Choose your SDK: Python · C++ · Go · Java
  6. Explore Examples: See the examples directory and 15-minute Developer Quickstart
 Quick Start
# Clone the TML repository
git clone https://github.com/FractonicMind/TernaryMoralLogic.git
cd TernaryMoralLogic

# Initialize TML with domain-level thresholds (non-configurable)
framework = create_tml_framework(domain="general")

# Evaluate and record decision outcome
result = framework.process_decision(context)

# If logging fails → decision halts immediately
# No Log = No Action is architecturally enforced
# The Sacred Zero awaits.

Implementation Roadmap

  • Q1 2025: Foundation incorporation + trademark registration
  • Q2 2025: TML v2.0 specification release + conformance test suite
  • Q3 2025: Beta certification program (10 pilot companies)
  • Q4 2025: Gold certification awards for reference implementations
  • 2026+: International expansion (EU AISBL, UK CIO, Switzerland Verein)
Documentation

Additional Resources


Learning Paths

Advanced Topics

Notarized Proofs & Research

Contact & Support

Contact TypeDetails
Framework OriginatorORCID: 0009-0006-5966-1243 — Lev Goukassian
GitHub Repositorygithub.com/FractonicMind/TernaryMoralLogic
Goukassian Foundationwww.goukassian-foundation.org (TBD)
Whistleblower HotlineConfidential Reporting
Victim SupportSupport Protocol
Succession CharterTML Succession Charter