Precedent Database

“Those who do not learn from prior rulings are doomed to re-litigate them.”
— The Honorable Lucius J. Morningstar

This document serves as the authoritative index of precedent-setting decisions made by the Court of MORNINGSTAR. Consult this database before deliberating on any matter to identify relevant prior rulings.

Table of Contents

How to Use This Database

Before Deliberation

  1. Identify keywords related to the matter at hand
  2. Search this index for related cases
  3. Review cited transcripts for relevant prior rulings
  4. Apply or distinguish precedent during arguments

During Deliberation

  • Any personality may cite precedent: “See Case 2026-ARCH-003-001 where the court ruled…”
  • The citing party must explain why the precedent applies
  • Opposing parties may argue the precedent is distinguishable

Precedent Weight

Status Weight Meaning
BINDING Full Must be followed unless overruled
PERSUASIVE Significant Should be considered but not mandatory
DISTINGUISHED Limited Applied to different facts
OVERRULED None Explicitly reversed by later ruling
RECONSTRUCTED Reduced Transcript was recovered, not original

Precedent Index

Master Index

Case ID Date Matter Ruling Vote Implications Status
2026-INFRA-001-001 2026-02-15 Framework Enhancement Analysis 10 enhancements adopted 4-0-0 Establishes infrastructure improvement process BINDING
2026-INFRA-002-001 2026-02-15 Second Enhancement Deliberation 10 enhancements adopted (operational excellence) 4-0-0 SME failures, dissolution, glossary, handoff, onboarding, portal, runbook, edge cases BINDING
2026-ARCH-001-001 2026-02-15 Agent Structure (CrewAI-Style Attributes) Optional frontmatter adopted: role, goal, backstory, allow_delegation, response_format 4-0-0 Agent schema doc; extend all three agents; inter-agent protocol note BINDING
2026-ARCH-002-001 2026-02-15 Aegis Protocol Enhancements 15 enhancements adopted for integration, semantics, escalation 4-0-0 Inter-agent protocol, aegis_core, rogue semantics, chaos injection, meta-deliberation BINDING
2026-DEL-002-001 2026-02-17 Gap Analysis (Phase 2–4) Hybrid affirmed; i18n added to registry; matter-triage to procedures; F4+ pilot 5-0-0 i18n domain, matter-triage in procedures, specialist pilot for data/locale matters BINDING
2026-DEL-003-001 2026-02-17 Bench Trial — 15 Expert Domains 15 new domains adopted to experts.yaml 6-1-0 data_privacy, observability, resilience, incident_response, devops, documentation, design_systems, frontend, mobile, ai_ml, data_engineering, cost, sustainability, ethics, qa_automation BINDING
2026-DEL-004-001 2026-02-17 Skills to Add to Each Agent Skills index at docs/agent-skills.md; agent files reference index 5-0-0 Single source of truth for skills; morningstar, octavius, aegis, lil-jeff slates adopted BINDING
2026-CONT-001-001 2026-02-15 Xenon Contempt Hearing No finding of contempt; style vs conduct distinction 1-4-0 Precedent: “Xenon problem”—polish as armor; distinguish tone from obstruction BINDING
2026-DOC-001-001 2026-02-19 Case Naming & Numbering Format Canonical format YYYY-CATC-NNN-DDD; core/case-format.md; case registry 4-1-0 Single source of truth for case IDs; category codes; grandfather legacy BINDING
2026-FEAT-001-001 2026-07-25 Agentic Production Mutation Controls Adopt APMS — default deny unsupervised prod mutations; HITL + kill switch 7-0-0 Proposal vs authorization planes; Level-4 runbooks capped; Sentinel optional BINDING
2026-DEL-005-001 2026-07-25 Open-Weight Frontier Export Controls Adopt Staged Capability Governance (SCG) for dual-use relevant open weights 6-0-1 Tiered eval-gated release; Tier-3+ compliance review; Compact aspirational BINDING
2026-DEL-006-001 2026-07-25 Agent-Authored Legal Filings Authentication Adopt AFAP — agents assist, never file of record; citation ledger + human attestation 7-0-0 Duty of candor cannot be delegated; privilege-preserving model routing BINDING
2026-SEC-003-001 2026-07-25 Special Inquiry: Agentic Cyber Attribution Six findings on attribution degradation, escalation, civilian entanglement N/A (hearing) Prohibit offensive cyber tasking; segment research vs actuation agents BINDING (findings)

Index by Category

Architecture (ARCH)

Case ID Date Matter Ruling Vote
2026-ARCH-001-001 2026-02-15 Agent Structure (CrewAI-Style Attributes) Optional frontmatter adopted 4-0-0
2026-ARCH-002-001 2026-02-15 Aegis Protocol Enhancements 15 enhancements adopted 4-0-0

Features (FEAT)

Case ID Date Matter Ruling Vote
2026-FEAT-001-001 2026-07-25 Agentic Production Mutation Controls Adopt APMS — default deny unsupervised prod mutations 7-0-0

Infrastructure (INFRA)

Case ID Date Matter Ruling Vote
2026-INFRA-001-001 2026-02-15 Framework Enhancement Analysis 10 enhancements adopted 4-0-0
2026-INFRA-002-001 2026-02-15 Second Enhancement Deliberation 10 enhancements adopted 4-0-0

Bugs (BUG)

Case ID Date Matter Ruling Vote
No entries yet

Maintenance (MAINT)

Case ID Date Matter Ruling Vote
No entries yet

Documentation (DOC)

Case ID Date Matter Ruling Vote
2026-DOC-001-001 2026-02-19 Case Naming & Numbering Format Canonical format; core/case-format.md; case registry 4-1-0

Deliberation (DEL)

Case ID Date Matter Ruling Vote
2026-DEL-002-001 2026-02-17 Gap Analysis (Phase 2–4) Hybrid affirmed; i18n, matter-triage, pilot 5-0-0
2026-DEL-003-001 2026-02-17 Bench Trial — 15 Expert Domains 15 domains adopted 6-1-0
2026-DEL-004-001 2026-02-17 Skills to Add to Each Agent Skills index at docs/agent-skills.md 5-0-0
2026-DEL-005-001 2026-07-25 Open-Weight Frontier Export Controls Adopt Staged Capability Governance (SCG) 6-0-1
2026-DEL-006-001 2026-07-25 Agent-Authored Legal Filings Authentication Adopt AFAP 7-0-0

Contempt (CONT)

Case ID Date Matter Ruling Vote
2026-CONT-001-001 2026-02-15 Xenon Contempt Hearing No finding of contempt 1-4-0

Special Inquiry / Security (SEC)

Case ID Date Matter Ruling Vote
2026-SEC-003-001 2026-07-25 Special Inquiry: Agentic Cyber Attribution Six findings recorded N/A (hearing)

Precedent Categories

By Subject Matter

Tag Description Example Matters
#api-design API structure decisions REST vs GraphQL, versioning
#database Database schema and queries Normalization, indexing
#security Security architecture Auth patterns, encryption
#performance Optimization decisions Caching, query optimization
#architecture System structure Microservices, monolith
#testing Testing strategy Coverage, test types
#deployment Deployment patterns CI/CD, environments
#error-handling Error management Retry logic, fallbacks
#infrastructure Framework/tooling Build systems, frameworks
#process Development process Workflow, procedures

By Outcome Type

Tag Description
#approved Motion passed
#rejected Motion failed
#deferred Decision postponed
#modified Passed with amendments
#overruled Reversed prior precedent

Entry Schema

Full Precedent Entry

Each significant ruling should have a full entry in this format:

***
### [CASE-ID]: [Brief Title]

**Date:** YYYY-MM-DD  
**Feasibility:** F[3-5]  
**Vote:** X-Y-Z  
**Status:** BINDING | PERSUASIVE | DISTINGUISHED | OVERRULED  
**Tags:** #tag1 #tag2 #tag3  
**Transcript:** [courtroom/transcripts/YYYY-MM-DD-slug.md](path) — Filename per [core/case-format.md](../core/case-format.md)

#### Matter

[1-2 sentence description of what was being decided]

#### Ruling

[1-2 sentence summary of the decision]

#### Rationale

[Key reasoning that led to this decision]

#### Risk Accepted

[What risk was acknowledged in making this decision]

#### Implications

[How this affects future decisions]

#### Key Quotes

> "[Significant quote from deliberation]"  
> — [PERSONALITY]

#### Related Precedent

- [CASE-ID]: [Relationship]

***

Index-Only Entry

For minor precedents, include only in the index table:

Case ID Date Matter Ruling Vote Implications Status
[ID] [Date] Matter Ruling [Vote] [Brief implication] [Status]

Full Precedent Entries

2026-INFRA-001-001: Framework Enhancement Analysis

Date: 2026-02-15
Feasibility: F4 (Critical)
Vote: 4-0-0 (Unanimous)
Status: BINDING
Tags: #infrastructure #process #approved
Transcript: courtroom/transcripts/2026-02-15-framework-enhancement-analysis.md

Matter

The court conducted a comprehensive analysis of the MORNINGSTAR framework infrastructure to identify the top 10 enhancements needed to improve operability.

Ruling

The court adopted 10 specific enhancements addressing navigation, personality definitions, state validation, session templates, transcript integrity, error recovery, precedent tracking, metrics, and inter-agent protocols.

Rationale

The current infrastructure is comprehensive in rules but incomplete in operability. Users cannot easily navigate, operators lack recovery paths, and the boundary between deliberation and implementation is undefined.

Risk Accepted

Enhancement implementation may create temporary inconsistency between documentation and practice. Mitigated by implementing in dependency order.

Implications

  1. Sets standard for infrastructure review processes
  2. Establishes priority framework for enhancements (dependency-aware ordering)
  3. Demonstrates unanimous consensus is achievable on operational matters
  4. Prophet proposals may be deferred without rejection

Key Quotes

“The framework assumes good-faith operators. The system trusts. Perhaps that is its greatest vulnerability—and its greatest strength.”
— Edward Cullen (Consultant)

“The mundane work before the extraordinary.”
— MORNINGSTAR::PROPHET (explaining YES vote)

2026-INFRA-002-001: Second Enhancement Deliberation

Date: 2026-02-15
Feasibility: F4 (Critical)
Vote: 4-0-0 (Unanimous)
Status: BINDING
Tags: #infrastructure #process #approved #operational
Transcript: courtroom/transcripts/2026-02-15-second-enhancement-deliberation.md

Matter

The court identified and ratified a second slate of 10 enhancements focused on operational excellence, discoverability, and cross-agent coherence (SME failures, dissolution protocol, glossary, precedent citation, OCTAVIUS handoff, onboarding, portal discovery, state backup, runbook, edge-case registry).

Ruling

The court adopted all 10 enhancements and delegated implementation to LIL_JEFF (primary) and OCTAVIUS where applicable. Handoff document: courtroom/transcripts/HANDOFF-2026-INFRA-002.md.

Rationale

First round delivered infrastructure; this round prioritizes operator experience and reducing memory load (per Consultant). Structural gaps (SME failure tracking, dissolution) closed; handoff matrix (OCTAVIUS) makes the system coherent.

Risk Accepted

Implementation touches many files; handoff must be clearly scoped. Mitigated by detailed HANDOFF spec.

Implications

  1. Establishes second enhancement cycle; confirms pattern from 2026-INFRA-001-001
  2. Dissolution Protocol (when not to convene) is now binding guidance
  3. docs/ and portal manifest improve discoverability
  4. P5 (Dissolution) removed from honorable mention—adopted as Enhancement #2

2026-ARCH-001-001: Agent Structure (CrewAI-Style Attributes)

Date: 2026-02-15
Feasibility: F3
Vote: 4-0-0 (Unanimous)
Status: BINDING
Tags: #architecture #process #approved
Transcript: courtroom/transcripts/2026-02-15-agent-structure-deliberation.md

Matter

Whether to add CrewAI-inspired optional attributes (role, goal, backstory, allow_delegation, response_format) to Cursor subagent definitions in .cursor/agents/*.md. Runtime-only attributes (max RPM, cache, max iter, etc.) were deemed out of scope.

Ruling

Adopt optional frontmatter: role, goal, optional backstory, allow_delegation, and optional response_format. Add docs/agent-schema.md; extend all three agents; add one-line note in inter-agent protocol. Frontmatter is canonical summary; body elaborates.

Rationale

Improves clarity, discoverability, and future-proofing without breaking Cursor. Consistency rule mitigates drift between frontmatter and body.

Risk Accepted

Minor duplication if maintainers update body but not frontmatter; mitigated by documenting the contract.

Implications

  • New or updated agents should follow the schema when adding optional fields.
  • Template agent and crew_style flag deferred to optional follow-up.

2026-FEAT-001-001: Agentic Production Mutation Controls

Date: 2026-07-25
Feasibility: F5
Vote: 7-0-0 (Unanimous; AI_ML + Security specialists seated)
Status: BINDING
Tags: #agentic-controls #security #devops #approved #deployment
Transcript: courtroom/transcripts/2026-07-25-agentic-production-mutation-controls.md

Matter

Whether autonomous coding agents may mutate production systems without mandatory human-in-the-loop gates, and what kill-switch, audit, and accountability controls are required.

Ruling

Adopt the Agentic Production Mutation Standard (APMS): unsupervised production mutations forbidden by default; human attestation bound to plan hash; dual-control for high blast-radius classes; capped Level-4 self-healing runbooks; out-of-band kill switch; named human accountable officer. Dual-plane Sentinel recommended as hardening, not a ship blocker.

Rationale

Agentic speed belongs in a proposal plane; production remains an authorization plane. Model reliability is heavy-tailed; change-control physics do not change because the actor is an agent.

Risk Accepted

Rubber-stamp approvals and Level-4 runbook loophole sprawl.

Implications

  1. MORNINGSTAR-governed agentic work must default-deny unsupervised prod writes
  2. Cross-cites future security and IR deliberations
  3. First FEAT-category binding precedent

Key Quotes

“Autonomy is not absolution.”
— The Honorable Lucius J. Morningstar

2026-DEL-005-001: Open-Weight Frontier Export Controls

Date: 2026-07-25
Feasibility: F5
Vote: 6-0-1 (Prophet abstain; Compliance + Ethics specialists seated)
Status: BINDING
Tags: #geopolitics #export-controls #ai-ml #compliance #ethics #approved
Transcript: courtroom/transcripts/2026-07-25-open-weight-frontier-export-controls.md

Matter

Whether open-weight frontier-class models should be treated as dual-use export-controlled technology and what institutional redistribution posture to adopt.

Ruling

Adopt Staged Capability Governance (SCG): frontier open weights are dual-use relevant; tiered eval-gated release; compliance review for Tier-3+; distinguish research artifacts from agentic runtime packaging; refuse uncontrolled cyber-offensive fine-tune redistribution. Plurilateral Compact recorded as aspiration, not dependency.

Rationale

Blanket openness and blanket closure both fail against proliferation physics and research norms. Institutional amplification can be restrained even when mirrors leak.

Risk Accepted

Eval gaming, mirror leakage, geopolitical talent flight.

Implications

  1. Sets redistribution checklist for frontier/agentic artifacts
  2. Informs Special Interest findings on civilian entanglement (2026-SEC-003)
  3. Prophet Compact remains diplomatic north star without blocking ops

2026-SEC-003-001: Special Inquiry — Agentic Cyber Attribution

Date: 2026-07-25
Feasibility: F5
Vote: N/A (Special Interest Hearing — findings only)
Status: BINDING (findings)
Tags: #geopolitics #security #law #agentic-controls #process
Transcript: courtroom/transcripts/20260725_190000_special_interest_agentic_cyber_attribution.md

Matter

Investigative inquiry into attribution difficulty, escalation risks, and legal analogues for agentic cyber operations spanning state/proxy and civilian platforms.

Ruling (Findings)

Six findings: (1) capability/tempo shift via tool-use loops; (2) attribution degradation and framing risk; (3) escalation hazard from loosely supervised privileged agents; (4) civilian platform entanglement; (5) stressed LOAC/countermeasures/due-diligence pressure points; (6) institutional recommendations — prohibit offensive cyber tasking, enforce APMS, immutable telemetry, segment research vs actuation, align with SCG.

Rationale

Perfect attribution is unavailable; governance must not depend on it. “Agent exceeded mandate” is a foreseeable excuse pattern requiring architectural preemption.

Risk Accepted

Findings are open-source/constructed-expertise limited; classified realities may exceed the record.

Implications

  1. Cross-binds FEAT-001, DEL-005, DEL-006 into a geopolitics/security stack
  2. Establishes no-offensive-cyber norm for MORNINGSTAR-governed stacks
  3. Leaves plurilateral clearinghouse as unresolved advocacy item

Citation Format

In Deliberation

When citing precedent during arguments:

"The court previously addressed this in [CASE-ID], ruling that [brief ruling].
The rationale was [key reasoning]. I argue this precedent [applies/is distinguishable] 
because [reason]."

In Transcripts

Formal citation in transcript rulings:

**Precedent Cited:**
- [CASE-ID] ([Status]): [How it was applied]

In Documentation

Reference format for other documents:

See [CASE-ID] in `courtroom/precedents.md` for the ruling on [matter].

Shorthand (Transcripts and Rulings)

Use the Case ID alone or with “Case” prefix. Examples:

  • Per 2026-INFRA-001-001
  • See Case 2026-INFRA-001-001
  • 2026-INFRA-001-001 (BINDING)

No need to repeat date or full title in every citation; the precedent index holds the details.

Distinguishing Precedent

When to Distinguish

Precedent may be distinguished (not followed) when:

  • Facts are materially different
  • Context has changed significantly
  • New information was unavailable at prior ruling
  • Technical landscape has evolved

How to Distinguish

During deliberation:

"I acknowledge [CASE-ID] but argue it is distinguishable because:
1. [Material difference 1]
2. [Material difference 2]

Therefore, that precedent should not control this matter."

Recording Distinguished Precedent

In the ruling:

**Precedent Distinguished:**
- [CASE-ID]: Distinguished on grounds that [reason]

Update this database:

  1. Add note to original entry under “Related Precedent”
  2. Create new entry with cross-reference

Overruling Precedent

Requirements to Overrule

Overruling prior precedent requires:

Requirement Details
Feasibility Must be F4+ deliberation
Explicit motion “I move to overrule [CASE-ID]”
Compelling reason Prior ruling was wrong, not just different
Vote threshold Same as original ruling (typically 3+ YES)
Judge approval Judge must endorse overruling rationale

Overruling Procedure

┌─────────────────────────────────────────────────────────────────┐
│ OVERRULING PROCEDURE                                            │
└─────────────────────────────────────────────────────────────────┘

1. Motion: "I move to overrule [CASE-ID] because [reason]."

2. Second required from another personality

3. Deliberation focuses on:
   - Why the prior ruling was wrong (not just different)
   - What changed to justify overruling
   - Implications of reversal

4. Vote on motion to overrule

5. If passed:
   - Original entry status → OVERRULED
   - Add reference to overruling case
   - New ruling becomes binding precedent

Recording Overruled Precedent

Update original entry:

**Status:** ~~BINDING~~ OVERRULED  
**Overruled by:** [NEW-CASE-ID] on [DATE]  
**Reason:** [Why overruled]

Create new entry with:

**Precedent Overruled:**
- [OLD-CASE-ID]: Overruled because [reason]

Maintenance

Adding New Entries

When a certified F3+ transcript is created:

  1. Add index entry to Master Index
  2. Add index entry to appropriate category
  3. Create full entry if the ruling is significant
  4. Tag appropriately
  5. Cross-reference related precedent

Periodic Review

Quarterly, review this database for:

Quick Reference

Searching Precedent

To find… Search by…
Related decisions Tags (#api-design, etc.)
Recent rulings Date column
Specific matter Matter description
Vote patterns Vote column
Active vs. inactive Status column

Precedent Status Quick Guide

Status Follow? Cite? Can Overrule?
BINDING Yes Yes Yes (F4+)
PERSUASIVE Consider Yes N/A
DISTINGUISHED Depends Yes, with caveat N/A
OVERRULED No Historical only N/A
RECONSTRUCTED With caution Yes, with caveat Yes

“Precedent is not a prison. It is a foundation.”
— MORNINGSTAR::ARCHITECT