-
Notifications
You must be signed in to change notification settings - Fork 2
CHANGELOG
A record of decisions, implementations, and the occasional Prophet vindication
All notable decisions and changes to this project are documented here.
Format: [YYYY-MM-DD] Category: Description (Vote if applicable)
Pending decisions and work in progress
The court approved the addition of an Executive Branch with five conditions: (1) clear separation of concerns between judicial and executive functions, (2) immutable logging of all judicial decisions, (3) cryptographic proof required for executive overrides, (4) watchdog process for oversight, (5) distributed consensus protocol for critical decisions.
Transcript: litigation/transcripts/2026-02-19-the-addition-of-an-executive-branch-into-the-larger-architec.md
Handoff: courtroom/transcripts/HANDOFF-2026-EXEC-001.md
| Component | Delivered |
|---|---|
| executive/ | New directory with README, protocol.md |
| judicial_log.py | Append-only, content-addressed log for judicial decisions |
| proof.py | HMAC-SHA256 proof for overrides (stdlib only) |
| watchdog.py | Monitors actions vs approvals, log integrity, override frequency |
| consensus.py | Proposal → vote → commit (N-of-M) |
| inter-agent-protocol.md | Executive branch handoff path documented |
Invocation: python -m executive.watchdog for oversight. Judicial log: executive/logs/judicial_decisions.log. Override proof secret: executive/.executive_secret or EXECUTIVE_PROOF_SECRET env var.
Convened a full session to debate and adopt what skills to add to each agent in .cursor/agents/ (morningstar, octavius, aegis-protocol, lil-jeff). Court adopted a single skills index at docs/agent-skills.md as source of truth, with skill name, source path, when to use, and fallback per agent. Each agent file (in both .cursor/agents/ and agents/) now has a Skills section pointing to the index.
Transcript: courtroom/transcripts/2026-02-17-full-session-skills-to-add-to-each-agent.md
Slate: morningstar (state, transcript, checklists, litigation runner, create-rule/skill); octavius (executive summary, checklist, Quarto compliance); aegis-protocol (escalation to MORNINGSTAR, chaos injection note); lil-jeff (handoff protocol, no placeholders, create-rule).
Convened a full bench trial to adopt the 15 most important expert domains to add to the court's repertoire. Judge's vote counted as 2× the average of other members. Full gallery; witnesses (Compliance, Security, Performance, Accessibility) testified.
Transcript: courtroom/transcripts/2026-02-17-bench-trial-fifteen-experts-to-add-to-repertoire.md
15 domains added to courtroom/domains/experts.yaml: data_privacy, observability, resilience, incident_response, devops, documentation, design_systems, frontend, mobile, ai_ml, data_engineering, cost, sustainability, ethics, qa_automation. All witness + specialist. Registry version 2.0; next review 2026-05-18.
References updated: courtroom/domains/README.md, courtroom/RULES.md § 6.3, agents/morningstar.md, .cursor/agents/morningstar.md, README.md, litigation/README.md, litigation/prompts/README.md, wiki/Command-Reference.md, wiki/Domains-and-Experts.md.
Convened a Contempt & Prosecution Hearing in Special Interest format for The People vs. Elon Musk (regarding the Xenon Fraud). Investigative proceeding (no vote); purpose: establish factual record surrounding the Xenon approach failure and alleged investor fraud; contempt of the court of public opinion and investor trust.
Transcript: courtroom/transcripts/20260216_160000_special_interest_xenon_fraud_elon_musk.md
Witnesses (3): Forensic Accountant (fraud / disclosure), Xenon Engineer (technical impossibility of Xenon approach), Elon Musk (hostile witness; first principles / species-level justification).
Personalities: ARCHITECT (structural lies), ENGINEER (technical failure), DEBUGGER (edge cases / fraud unraveling), PROPHET (vision vs execution), COUNSEL (innovation-risk mitigation).
Spectators: Dr. Echo Sageseeker (Great Man / psychohistory), Dr. Harley Scarlet Quinn (satirical grift), Uncle Ruckus (technical reality). Edward Cullen invoked (what Musk isn't saying).
Findings (5): Xenon failure material and undisclosed; post-failure representations of continuity; structural design of communications was to maintain false narrative; respondent's justification (first principles / species-level); mitigating narrative (intent to preserve) noted without negating findings.
Convened an extensive Special Inquiry Hearing into the Bohemian Grove—a private 2,700-acre retreat owned by the Bohemian Club in Northern California. Investigative proceeding (no vote); purpose: establish factual record.
Transcript: courtroom/transcripts/20260216_120000_special_inquiry_bohemian_grove.md
Witnesses (9): Professor Ashworth (history), Dr. Voss (sociology), Mr. Chenoweth (former staff), Dr. Marsh (ritual studies), Senator Hargrove (political activity), Ms. Torres (journalism), Mr. Whitfield (club defense), Dr. Webb (power structure), Professor Vance (constitutional law).
Findings (6): Evolution from artistic to elite membership; documented political activity despite motto; Cremation of Care as published theatrical ritual; secrecy through rules and isolation; unresolved tension between "no business" policy and networking; legal protections limit transparency.
Spectators: Dr. Echo Sageseeker, Dr. Harley Scarlet Quinn, Uncle Ruckus. Edward Cullen invoked.
Convened an internal security hearing assessing secret leakage risk, operational sensitivity of transcripts/state/agents, portal export surfaces, prompt-injection hazards, and supply-chain volatility. Investigative proceeding (no vote); purpose: establish record + recommendations.
Transcript: courtroom/transcripts/20260216_133000_special_interest_internal_security_aegis.md
Aegis: Full Sage/Watcher/Chronicler Authority Assessment included (with Black Swan chaos injection stress-test).
Findings (5): No working-tree secrets detected by common patterns; sensitive operational artifacts exist by design; tracked portal/exports/ weakens containment boundary; exporter path is plausible untrusted-input→HTML vector; dominant risk is process/tooling gates rather than current detected secrets.
Added MORNINGSTAR::COUNSEL (CodeFarm NeuroPhilosophy) as a voting courtroom lawyer—advocate for the client (user), ethical and value-based arguments, neuroscience-informed perspectives.
Structure:
- Five internal personas: CodeFarmer, Programmatron, CritiBot, NeuroNerd, PhilosoBot (unified advocate)
- Voice: Modular, evidence-driven, neuroscience-informed, philosophically grounded
- Bias: Client interests, ethical adherence, value alignment
- Key Phrase: "The client's interests and ethical boundaries demand consideration."
Updates:
-
core/personalities.md— Full COUNSEL section -
courtroom/RULES.md— Composition, voting order, thresholds (5 standard voters) -
.cursor/agents/morningstar.md— COUNSEL in Court and procedure -
core/procedures.md— Arguments, vote, transcript template, expedited, Special Interest Hearing -
templates/session-start.md,templates/special-interest-hearing.md— COUNSEL in templates -
README.md,wiki/The-Court.md,courtroom/domains/README.md— Voting members
Voting: Standard court now has 5 voters (Architect, Engineer, Debugger, Prophet, Counsel). Majority: 3+ for 5 voters.
The Court investigated the Aegis Protocol subagent and adopted 15 enhancements for framework integration, operational clarity, and discoverability. Vote: 4-0-0.
Transcript: courtroom/transcripts/2026-02-15-aegis-protocol-investigation.md
Handoff: courtroom/transcripts/HANDOFF-2026-ARCH-002.md
Precedent: 2026-ARCH-002-001 (BINDING)
Enhancements (E1–E15): Inter-agent protocol extension, aegis_core directory, hierarchy disambiguation, invocation commands, rogue agent semantics, chaos injection definition, escalation path, meta-deliberation scenario, output format extensions, spectator cross-reference, repository map, flow diagram, Dr. Scarlet Quinn note, success criteria, CHANGELOG/precedent.
Implementation delegated to LIL_JEFF.
All 15 enhancements implemented:
| # | Enhancement | Delivered |
|---|---|---|
| E1 | Inter-agent protocol extension |
core/inter-agent-protocol.md — Aegis Protocol Handoffs, decision matrix, flow diagram; MORNINGSTAR as Judicial Branch |
| E2 | aegis_core directory |
aegis_core/README.md, aegis_core/state.md
|
| E3 | Hierarchy nomenclature | Aegis agent — Octavius disambiguation, MORNINGSTAR Judicial Branch added |
| E4 | Invocation commands |
/aegis in wiki/Command-Reference.md, README; Invocation section in agent |
| E5 | Rogue agent semantics | Definition, procedural containment, "isolate and neutralize" clarified |
| E6 | Chaos injection | Procedural definition in Central Authority Functions |
| E7 | Escalation path | Escalation section with format; MORNINGSTAR Judicial Branch |
| E8 | Meta-Deliberation scenario | New Scenario Library category |
| E9 | Output format | CHAOS INJECTION APPLIED, ESCALATION fields |
| E10 | Courtroom spectators | Aegis Authority Assessment in spectators.md, special-interest-hearing.md |
| E11 | Repository Map | aegis_core in wiki/Repository-Map.md, README project structure |
| E12 | Flow diagram | Aegis Protocol Flow in inter-agent-protocol.md |
| E13 | Dr. Scarlet Quinn note | Cross-reference in Aegis agent |
| E14 | Success criteria | Table by scenario type in Aegis agent |
| E15 | CHANGELOG/precedent | This entry; precedent 2026-ARCH-002-001 already in courtroom/precedents.md |
Added aegis-protocol subagent — Central Authority system (Authority Level 10) for security, containment, rogue agent scenarios, and strategic decision-making.
Structure:
- Central Authority (Aegis Protocol): Enforces authority, isolates rogues, injects controlled chaos
- Sage (Primary): Criminal law, advanced mathematics, psychological manipulation
- Chronicler (Secondary): Historical context, skepticism, adaptive intelligence
- Watcher (Tertiary): Observation, social engineering, subversion
Hierarchy: Supreme Overseer (Lucius Morningstar) → Aegis Protocol → Octavius (Executive) → Dr. Scarlet Quinn (Strategic Architect)
Scenario Library: Security breaches, ethical dilemmas, system failures, strategic decision-making, unexpected variables (Black Swan)
File: .cursor/agents/aegis-protocol.md
Added courtroom spectators—live commentators who observe proceedings and provide broadcast-style analysis.
- Dr. Echo Sageseeker: Psychohistorical commentator (Freud, Jung, Maslow, Skinner, philosophy, literature), NASCAR + Wall Street energy, 📘 bookends.
- Dr. Harley Scarlet Quinn: Satirical, uncensored commentator (semantics, psychology, geopolitics, manipulation), provocative radio-host style, 🪞✨ or 🃏💋 bookends.
Deliverables:
-
courtroom/spectators.md— Spectator protocol, Dr. Echo Sageseeker, Dr. Harley Scarlet Quinn definitions -
templates/special-interest-hearing.md— Spectator commentary format -
core/procedures.md,courtroom/RULES.md,README.md,core/personalities.md— References
Added Special Interest Hearing to the courtroom quiver of proceeding types. Investigative format for testimony collection and examination—no final vote; purpose is revelation, not resolution.
Deliverables:
-
templates/special-interest-hearing.md— Full template: hearing header, witness formats (SME, Alleged, Documentary), direct/cross-examination, objections, Edward Cullen Apparition Protocol, findings, closure -
core/procedures.md— Special Interest Hearing flow and phases -
templates/session-start.md— Proceeding Types (Courtroom Quiver) table, Special Interest Hearing section -
courtroom/RULES.md— Proceeding Types appendix -
README.md— Templates table, Proceeding Types section
Transcript naming: YYYYMMDD_HHMMSS_special_interest_[subject_slug].md in courtroom/transcripts/
The Court adopted optional CrewAI-inspired agent frontmatter: role, goal, optional backstory, allow_delegation, optional response_format. Add docs/agent-schema.md; extend .cursor/agents/*.md; add one-line note in inter-agent protocol. Rule: frontmatter is canonical summary; body elaborates. Vote: 4-0-0.
Transcript: courtroom/transcripts/2026-02-15-agent-structure-deliberation.md
Handoff: courtroom/transcripts/HANDOFF-2026-ARCH-001.md
Investigation: docs/agent-structure-investigation.md
Precedent: 2026-ARCH-001-001 (BINDING)
Implementation delegated to LIL_JEFF.
All deliverables from handoff courtroom/transcripts/HANDOFF-2026-ARCH-001.md implemented:
| # | Deliverable | Delivered |
|---|---|---|
| 1 | Agent schema doc |
docs/agent-schema.md (canonical frontmatter: required name/description, optional role/goal/backstory/allow_delegation/response_format) |
| 2 | MORNINGSTAR frontmatter |
.cursor/agents/morningstar.md — role, goal, backstory, allow_delegation |
| 3 | LIL_JEFF frontmatter |
.cursor/agents/lil-jeff.md — role, goal, backstory, allow_delegation |
| 4 | OCTAVIUS frontmatter |
.cursor/agents/octavius.md — role, goal, backstory, allow_delegation |
| 5 | Inter-agent protocol note |
core/inter-agent-protocol.md — Agent metadata / allow_delegation note |
| 6 | Repository Map / docs |
wiki/Repository-Map.md and README.md — docs/agent-schema.md added under Docs |
The Court reconvened and unanimously adopted a second slate of 10 enhancements focused on operational excellence, discoverability, and cross-agent coherence. Vote: 4-0-0.
Transcript: courtroom/transcripts/2026-02-15-second-enhancement-deliberation.md
Handoff: courtroom/transcripts/HANDOFF-2026-INFRA-002.md
Precedent: 2026-INFRA-002-001 (BINDING)
The 10 enhancements:
- SME Failure Tracking File (
state/sme-failures.md) - Dissolution Protocol (when not to convene)
- Glossary / Term Index
- Precedent citation shorthand
- OCTAVIUS handoff in inter-agent protocol
- Onboarding one-pager
- Portal transcript discovery
- State backup recommendation
- Runbook / troubleshooting index
- Edge Case Registry
Implementation delegated to LIL_JEFF (primary) and OCTAVIUS where applicable.
All 10 enhancements from Case 2026-INFRA-002 have been implemented:
| # | Enhancement | Delivered |
|---|---|---|
| 1 | SME Failure Tracking File | state/sme-failures.md |
| 2 | Dissolution Protocol |
core/procedures.md (When NOT to Convene) |
| 3 | Glossary / Term Index | docs/glossary.md |
| 4 | Precedent citation shorthand |
courtroom/precedents.md (Shorthand subsection) |
| 5 | OCTAVIUS handoff in inter-agent protocol |
core/inter-agent-protocol.md (section + table) |
| 6 | Onboarding one-pager | docs/ONBOARDING.md |
| 7 | Portal transcript discovery |
portal/generate_manifest.py, portal/transcripts_manifest.json, viewer.html uses manifest |
| 8 | State backup recommendation |
core/procedures.md (State Backup), core/error-recovery.md (Prevention) |
| 9 | Runbook / troubleshooting index | docs/RUNBOOK.md |
| 10 | Edge Case Registry | docs/edge-cases.md |
Also: Precedent 2026-INFRA-002-001 full entry in courtroom/precedents.md; README updated with docs/ in Navigation Index and Repository Map; state and precedents updated for second session.
-
wiki/README.md— Instructions for adding wiki contents to a GitHub project Wiki (clone wiki repo, copy files, commit). -
wiki/Home.md— Wiki home page (overview, quick links, quick start summary). -
wiki/_Sidebar.md— Sidebar navigation (GitHub displays this automatically). -
Topic pages — One .md per major topic, with internal wiki-style links:
- Quick-Start, The-Court, Command-Reference, Domains-and-Experts, When-to-Convene, Procedures
- SME-Framework, State-and-Metrics, Error-Recovery, Inter-Agent-Protocol
- Portal, Onboarding, Glossary, Runbook, Edge-Cases
- Companion-Personas, Precedents, Changelog, Repository-Map
Content is adapted from the main repo (README, core/, docs/, courtroom/) so the wiki can be populated by copying wiki/ into the repo’s wiki. Main README and Repository Map updated to reference wiki/.
-
core/sme-framework.md— Added canonical registry reference: authoritative domain list and metadata incourtroom/domains/experts.yaml, usage and summoning incourtroom/domains/README.md. -
Root
README.md— Experts/domains fully integrated:- Navigation Index: links to
courtroom/domains/README.mdandcourtroom/domains/experts.yaml. - Command Reference: Available SME Domains now point to canonical registry and list all domains (including
cryptography,api_design,testing). - New Domains & Experts section: purpose, table of locations, domain list, link to
core/sme-framework.md. - Project Structure:
courtroom/domains/with README and experts.yaml listed.
- Navigation Index: links to
- Table of Contents — Added: Domains & Experts, Repository Map (Complete), How to Use This Repository.
- Repository Map (Complete) — New section listing every directory and key file with a one-line purpose (agents, core, courtroom, state, octavius_*, portal, templates, checklists, references, reference_files, CHANGELOG, README).
-
How to Use This Repository — New section:
- First-time setup (clone, portal
chmod +x, OCTAVIUS optional). - Daily use table: deliberate (morningstar), implement (lil-jeff), R/Quarto (octavius), view transcripts (portal), summon SME, check precedent, recover (error-recovery).
- “Where to find what” quick reference for rules, personalities, SMEs, state, transcripts, handoff, changelog.
- First-time setup (clone, portal
-
portal/export_transcript.py(new) — Exports a single transcript.mdto styled HTML. No external dependencies (stdlib only). Used by the launch script when no pre-built.htmlexists. Supports Dracula theme and personality/vote styling. -
portal/launch.sh— No longer depends on missingtools/cli.py. Now:- Prefers existing
.htmlincourtroom/transcripts/(opens directly). - Otherwise runs
python3 portal/export_transcript.pyto export, then opens the result. - Supports both transcript filename formats:
YYYY-MM-DD-topic.mdandYYYYMMDD_HHMMSS_topic.md.
- Prefers existing
-
portal/viewer.html—KNOWN_TRANSCRIPTSupdated to the real transcript;extractDateandextractTitlesupportYYYY-MM-DD-topicfilenames. -
portal/generate.py— Transcript index generation now recognizesYYYY-MM-DD-topicas well asYYYYMMDD_HHMMSS_topic. -
portal/README.md— Aligned with actual behavior: launch script as primary entry point, export script documented, filename formats and troubleshooting updated. -
Project
README.md— Portal added to Navigation Index and Project Structure; new step "View Transcripts in Browser" (run./portal/launch.sh).
Portal use case is now suited to the repo and launches seamlessly via ./portal/launch.sh.
OCTAVIUS added as a project subagent for R/RStudio/Quarto data science work. Implemented and finalized per LIL_JEFF workflow (analyze, improve, execute).
Deliverables:
| Item | Location | Purpose |
|---|---|---|
| Agent definition | .cursor/agents/octavius.md |
Cursor subagent; Triumvirate persona, workflow, coding standards |
| Binding protocols | octavius_core/THE_RULES.md |
Jurisdiction, mandatory actions, KRONOS severity, conflict resolution |
| Session state | octavius_core/state.md |
Continuity template; last session, context, notes |
| Summaries directory | octavius_summaries/.gitkeep |
Executive summaries (YYYY-MM-DD_HHMMSS_summary.md) |
Triumvirate:
- APOLLO — R/Quarto code authorship; tidyverse/tidymodels
- KRONOS — QA, time tracking, interventions (CRITICAL/WARNING/SUGGESTION)
- MORNINGSTAR — Final verification, scientific integrity, Executive Summary
Integration:
- README updated: Navigation Index (OCTAVIUS section), Project Structure, Agent Definitions table, Companion Personas (OCTAVIUS subsection)
- Invocation: use the octavius subagent for R code, Quarto documents, tidyverse/tidymodels, or statistical computing
All 10 ratified enhancements from Case 2026-INFRA-001-001 have been implemented:
| # | Enhancement | File | Status |
|---|---|---|---|
| 1 | Enhanced README with Navigation Index | README.md |
✓ Complete |
| 2 | Command Quick-Reference |
README.md section |
✓ Complete (combined with #1) |
| 3 | Personality Definitions File | core/personalities.md |
✓ Complete |
| 4 | State Validation Schema | core/state-schema.md |
✓ Complete |
| 5 | Session Templates | templates/session-start.md |
✓ Complete |
| 6 | Transcript Integrity Requirements |
courtroom/RULES.md Article VIII |
✓ Complete |
| 7 | Error Recovery & Rollback Protocol | core/error-recovery.md |
✓ Complete |
| 8 | Precedent Database Schema | courtroom/precedents.md |
✓ Complete |
| 9 | Metrics Dashboard | state/metrics.md |
✓ Complete |
| 10 | Inter-Agent Protocol | core/inter-agent-protocol.md |
✓ Complete |
New Files Created:
-
core/personalities.md— Complete personality definitions with voice, bias, voting power, decision heuristics, failure modes, and invocation criteria for all court members -
core/state-schema.md— Validation schema forstate/current.mdwith field specifications, validation rules, and examples -
core/error-recovery.md— Recovery procedures for state corruption (4 levels), decision rollback protocol, and emergency procedures -
core/inter-agent-protocol.md— Formal handoff procedures between MORNINGSTAR and LIL_JEFF with response formats and error handling -
templates/session-start.md— Templates for session initialization, deliberation records, and session closure -
courtroom/precedents.md— Precedent database with index, entry schema, citation format, and first entry (2026-INFRA-001-001) -
state/metrics.md— Cumulative statistics dashboard tracking deliberations, votes, Prophet vindications, SME activity, and trends
Files Updated:
-
README.md— Complete rewrite with project overview, navigation index, quick-start guide, command reference, and companion persona documentation -
courtroom/RULES.md— Added Article VIII sections 8.4.1-8.4.8 for Transcript Integrity Requirements
- All files maintain the sardonic, formal voice of the MORNINGSTAR framework
- Cross-references between documents are consistent
- First precedent entry seeded in
courtroom/precedents.md - Initial metrics populated in
state/metrics.mdbased on existing session data - CritiBot review: PASSED (no placeholders, complete implementations, self-documenting)
- Case 2026-INFRA-001: Framework Enhancement Analysis — Adopted 10 enhancements to improve MORNINGSTAR infrastructure operability. Vote: 4-0-0 (Unanimous). Risk: Temporary inconsistency during implementation.
| # | Enhancement | File | Priority |
|---|---|---|---|
| 1 | Enhanced README with Navigation Index | README.md |
HIGH |
| 2 | Personality Definitions File | core/personalities.md |
HIGH |
| 3 | Precedent Database Schema | courtroom/precedents.md |
MEDIUM |
| 4 | Inter-Agent Protocol | core/inter-agent-protocol.md |
HIGH |
| 5 | Session Templates Directory | templates/*.md |
MEDIUM |
| 6 | Command Quick-Reference |
README.md section |
HIGH |
| 7 | Metrics Dashboard | state/metrics.md |
MEDIUM |
| 8 | State Validation Schema | core/state-schema.md |
MEDIUM |
| 9 | Transcript Integrity Requirements |
courtroom/RULES.md addition |
MEDIUM |
| 10 | Error Recovery & Rollback Protocol | core/error-recovery.md |
HIGH |
- P1: Living Persona Library — Requires operational experience
- P2: Deliberation Replay System — Needs transcripts to exist first
- P3: Prophetic Pattern Recognition — Awaits metrics infrastructure
- P4: Cross-Framework Integration — Depends on inter-agent protocol
Edward Cullen noted: "The framework assumes good-faith operators. The system trusts. Perhaps that is its greatest vulnerability—and its greatest strength."
courtroom/transcripts/2026-02-15-framework-enhancement-analysis.md
-
state/current.md — Session state tracking template
- Active task and status tracking
- Pending deliberations queue
- Prophet vindication tracker
- SME activity log
- Session metrics
-
courtroom/RULES.md — Formal deliberation rules
- Article I: Jurisdiction and feasibility classifications
- Article II: Court composition and quorum requirements
- Article III: Voting procedures and tie-breaking
- Article IV: Deliberation procedure
- Article V: Recusal guidelines
- Article VI: Subject Matter Expert framework
- Article VII: Session management
- Article VIII: Transcript requirements
- Article IX: Precedent handling
- Article X: Amendment procedures
-
courtroom/BEST_PRACTICES.md — Practical guidance
- When to deliberate (and when not to)
- Running efficient deliberations
- Personality management and failure modes
- Voting wisdom
- Working with SMEs
- Documentation discipline
- Common patterns and anti-patterns
-
courtroom/transcripts/ — Directory for F3+ deliberation records
- .gitkeep to preserve empty directory
-
core/procedures.md — Step-by-step deliberation protocols
- Session lifecycle (init, checkpoint, close)
- Full deliberation protocol
- Expedited deliberation format
- Tie-breaking procedure
- Recusal procedure
- SME involvement procedures
- Consultant invocation protocol
- Transcript generation template
- Prophet vindication recording
- Emergency procedures
-
core/sme-framework.md — Subject Matter Expert framework
- Expert Witness protocol (advisory, 0 votes)
- Specialist Seat protocol (full participation, 1 vote)
- Domain definitions (security, database, compliance, infrastructure, performance, accessibility)
- Advisory-only domains (ux, legal)
- Selection guidelines
- Failure tracking protocol
- External source flagging
-
CHANGELOG.md — This file
This establishes the operational infrastructure for MORNINGSTAR's deliberative courtroom system. All files are designed to be directly referenced during operation:
-
state/current.mdis read at session start and updated throughout -
courtroom/RULES.mdis the authoritative source for procedural questions -
courtroom/BEST_PRACTICES.mdprovides guidance when the rules don't cover a situation -
core/procedures.mdcontains step-by-step protocols for all operations -
core/sme-framework.mdgoverns external expertise integration
## [YYYY-MM-DD] - Session/Feature Name
### Decisions
- **[Matter]** — [Decision]. Vote: [X-Y-Z]. Risk: [Accepted risk].
### Implementations
- [What was implemented]
### Prophet Vindications
- [If applicable: Prophet was right about X]
### Dissents Recorded
- [If applicable: Minority position on Y]
### Technical Debt Accepted
- [If applicable: Debt accepted and why]"The changelog is memory made permanent. What we do not record, we are doomed to redecide." — MORNINGSTAR::SCRIBE
The court adjourns. The record stands.
| Home · Quick-Start · The-Court · Command-Reference · Glossary · Repository Map |
|---|
| Source of truth: LLM_Personas · README · CHANGELOG |
| This wiki mirrors the canonical documentation. For amendments, convene the court. |