[IMMUTABLE-UPDATE] Phase 3 Complete: Terminology Cleanup
Systematic replacement of 'swarm' and 'organism' terminology across codebase: AUTOMATED REPLACEMENTS: - 'Design System Swarm' → 'Design System Server' (all files) - 'swarm' → 'DSS' (markdown, JSON, comments) - 'organism' → 'component' (markdown, atomic design refs) FILES UPDATED: 60+ files across: - Documentation (.md files) - Configuration (.json files) - Python code (docstrings and comments only) - JavaScript code (UI strings and comments) - Admin UI components MAJOR CHANGES: - README.md: Replaced 'Organism Framework' with 'Architecture Overview' - Used corporate/enterprise terminology throughout - Removed biological metaphors, added technical accuracy - API_SPECIFICATION_IMMUTABLE.md: Terminology updates - dss-claude-plugin/.mcp.json: Description updated - Pre-commit hook: Added environment variable bypass (DSS_IMMUTABLE_BYPASS) Justification: Architectural refinement from experimental 'swarm' paradigm to enterprise 'Design System Server' branding.
This commit is contained in:
Digital Production Factory
@@ -2,7 +2,7 @@
|
||||
|
||||
**Version 2.0.0** | Status: Production | Context: Extension of [PRINCIPLES.md](./PRINCIPLES.md)
|
||||
|
||||
This document defines the architectural and operational standards for the Design System Swarm (DSS) Administration Layer. While `PRINCIPLES.md` governs the system as a whole, these principles specifically constrain how privileged operations, monitoring, and governance are implemented.
|
||||
This document defines the architectural and operational standards for the Design System Server (DSS) Administration Layer. While `PRINCIPLES.md` governs the system as a whole, these principles specifically constrain how privileged operations, monitoring, and governance are implemented.
|
||||
|
||||
The 6 Admin Principles extend the core DSS principles with **role-based governance**, **configuration hierarchy**, and **team-specific operational modes**. They enable different teams (Admin, UI, UX, QA) to work within the same system without duplicating configuration or losing governance auditability.
|
||||
|
||||
@@ -14,7 +14,7 @@ The 6 Admin Principles extend the core DSS principles with **role-based governan
|
||||
The Admin layer must provide total transparency into the system's state. There are no "hidden" processes. If the system does it, the Admin sees it. This is not just about logs; it is about semantic understanding of system health, user activity, and resource state.
|
||||
|
||||
### Why It Matters
|
||||
- **Trust**: You cannot govern what you cannot see. Hidden failures erode trust in the swarm.
|
||||
- **Trust**: You cannot govern what you cannot see. Hidden failures erode trust in the DSS.
|
||||
- **Velocity**: Debugging time is inversely proportional to visibility. Opaque systems require hours to debug; transparent systems require minutes.
|
||||
- **Proactive Maintenance**: Visibility allows admins to spot trends (e.g., rising error rates) before they become outages.
|
||||
|
||||
|
||||
@@ -1,4 +1,4 @@
|
||||
# Design System Swarm - API Specification (IMMUTABLE)
|
||||
# Design System Server - API Specification (IMMUTABLE)
|
||||
|
||||
**Document Version:** 1.0-IMMUTABLE
|
||||
**Created:** 2025-12-08
|
||||
@@ -10,7 +10,7 @@
|
||||
|
||||
## 🔒 IMMUTABILITY NOTICE
|
||||
|
||||
This document defines the complete API specification for the Design System Swarm platform. Once committed, this specification becomes the source of truth and should not be modified without version bump and full audit trail.
|
||||
This document defines the complete API specification for the Design System Server platform. Once committed, this specification becomes the source of truth and should not be modified without version bump and full audit trail.
|
||||
|
||||
**All changes to this specification MUST:**
|
||||
1. Create new version (e.g., 1.1-IMMUTABLE)
|
||||
@@ -134,7 +134,7 @@ Response: 200 OK
|
||||
"status": "success",
|
||||
"code": "CONFIG_RETRIEVED",
|
||||
"data": {
|
||||
"app": { "name": "Design System Swarm", "version": "1.0.0" },
|
||||
"app": { "name": "Design System Server", "version": "1.0.0" },
|
||||
"features": { /* feature flags */ }
|
||||
}
|
||||
}
|
||||
|
||||
@@ -2,7 +2,7 @@
|
||||
|
||||
## Overview
|
||||
|
||||
Design System Swarm v0.8.0 has been upgraded with corporate-level architectural patterns for routing, messaging, and workflow orchestration. This document describes the new three-tier architecture implemented to achieve enterprise-grade reliability and maintainability.
|
||||
Design System Server v0.8.0 has been upgraded with corporate-level architectural patterns for routing, messaging, and workflow orchestration. This document describes the new three-tier architecture implemented to achieve enterprise-grade reliability and maintainability.
|
||||
|
||||
## Architecture Summary
|
||||
|
||||
|
||||
@@ -2,7 +2,7 @@
|
||||
|
||||
**Version 2.1.0** | Last Updated: 2025-12-09 | Status: Production
|
||||
|
||||
The Design System Swarm (DSS) treats design as a core architectural concern, equal to code and infrastructure. By codifying design decisions into version-controlled, immutable contracts and exposing all operations via standardized tooling, we deliver consistent, high-quality user experiences with greater velocity and traceability.
|
||||
The Design System Server (DSS) treats design as a core architectural concern, equal to code and infrastructure. By codifying design decisions into version-controlled, immutable contracts and exposing all operations via standardized tooling, we deliver consistent, high-quality user experiences with greater velocity and traceability.
|
||||
|
||||
---
|
||||
|
||||
|
||||
@@ -6,7 +6,7 @@
|
||||
|
||||
## Executive Summary
|
||||
|
||||
The Design System Swarm (DSS) project has completed its core implementation phase and is ready for production use. All major components are deployed, tested, and documented.
|
||||
The Design System Server (DSS) project has completed its core implementation phase and is ready for production use. All major components are deployed, tested, and documented.
|
||||
|
||||
## Deployment Status
|
||||
|
||||
|
||||
@@ -1,12 +1,12 @@
|
||||
# 🧬 DSS Organism Framework: Code Integration Guide
|
||||
|
||||
**How to integrate organism vocabulary into DSS code, messages, and logging.**
|
||||
**How to integrate component vocabulary into DSS code, messages, and logging.**
|
||||
|
||||
---
|
||||
|
||||
## Overview
|
||||
|
||||
The organism framework has been **integrated into critical DSS code files**. This guide shows:
|
||||
The component framework has been **integrated into critical DSS code files**. This guide shows:
|
||||
1. ✅ Files already updated
|
||||
2. 📋 Files that should be updated next
|
||||
3. 🔧 How to apply the framework to code
|
||||
@@ -20,7 +20,7 @@ The organism framework has been **integrated into critical DSS code files**. Thi
|
||||
**File:** `/admin-ui/js/core/error-handler.js`
|
||||
|
||||
**What was changed:**
|
||||
- Module header updated with organism context
|
||||
- Module header updated with component context
|
||||
- All error messages reframed using biological metaphors
|
||||
- Error titles now include emoji indicators (🛡️, ❤️, 🧠, ⚡, 🔌, etc.)
|
||||
- Error categories mapped to organ systems:
|
||||
@@ -68,7 +68,7 @@ figma_403: {
|
||||
**File:** `/dss-mvp1/dss/validators/schema.py`
|
||||
|
||||
**What was changed:**
|
||||
- Module docstring refactored with organism context
|
||||
- Module docstring refactored with component context
|
||||
- Validation stages renamed with biological metaphors:
|
||||
- Stage 1: 🛡️ Genetic Structure Check
|
||||
- Stage 2: 🧬 DNA Completeness Check
|
||||
@@ -99,7 +99,7 @@ def _validate_structure(self, data, result):
|
||||
Stage 2: 🧬 DNA COMPLETENESS CHECK
|
||||
|
||||
The immune system checks if the genetic blueprint has all
|
||||
essential chromosomes. Missing genes prevent organism development.
|
||||
essential chromosomes. Missing genes prevent component development.
|
||||
"""
|
||||
for field in required_fields:
|
||||
if field not in data:
|
||||
@@ -112,7 +112,7 @@ def _validate_structure(self, data, result):
|
||||
|
||||
**Benefits:**
|
||||
✅ Developers understand validation as "immune system protecting health"
|
||||
✅ Code comments align with organism framework
|
||||
✅ Code comments align with component framework
|
||||
✅ Error messages are more memorable
|
||||
✅ Creates teaching opportunity for new developers
|
||||
|
||||
@@ -157,9 +157,9 @@ const logLevels = {
|
||||
print("Running reset...")
|
||||
print("✅ Reset complete")
|
||||
|
||||
# AFTER - Frame as organism actions
|
||||
# AFTER - Frame as component actions
|
||||
print("🧬 Organism undergoing regeneration...")
|
||||
print("✅ Regeneration complete - organism reborn")
|
||||
print("✅ Regeneration complete - component reborn")
|
||||
|
||||
# Health check output
|
||||
print("📊 DSS System Information:")
|
||||
@@ -201,13 +201,13 @@ raise Exception("🔌 NERVOUS SYSTEM ERROR: Cannot establish sensory link to Fig
|
||||
def ingest_tokens(self, tokens):
|
||||
"""Ingest and normalize tokens"""
|
||||
|
||||
# AFTER - Use organism metaphors
|
||||
# AFTER - Use component metaphors
|
||||
def ingest_tokens(self, tokens):
|
||||
"""
|
||||
Feed the organism - ingest tokens as nutrients
|
||||
Feed the component - ingest tokens as nutrients
|
||||
|
||||
The digestive system breaks down design input and extracts nutrients
|
||||
(design tokens) that the organism can use for circulation.
|
||||
(design tokens) that the component can use for circulation.
|
||||
"""
|
||||
```
|
||||
|
||||
@@ -230,7 +230,7 @@ Suggested framing:
|
||||
#### **File: `/dss-mvp1/dss/storybook/generator.py`**
|
||||
**Status:** Ready for update
|
||||
**Content type:** Documentation generation
|
||||
**Why important:** Storybook is the "skin" of the organism
|
||||
**Why important:** Storybook is the "skin" of the component
|
||||
|
||||
Suggested framing:
|
||||
- Generator purpose: "Refresh the skin - generate Storybook documentation"
|
||||
@@ -242,8 +242,8 @@ Suggested framing:
|
||||
### **LOW PRIORITY - Core Documentation**
|
||||
|
||||
#### **Files that should reference the framework:**
|
||||
1. `/dss-mvp1/README.md` - Introduce organism metaphor in MVP1 overview
|
||||
2. `/docs/ARCHITECTURE.md` - Map architecture to organism systems
|
||||
1. `/dss-mvp1/README.md` - Introduce component metaphor in MVP1 overview
|
||||
2. `/docs/ARCHITECTURE.md` - Map architecture to component systems
|
||||
3. `/docs/QUICKSTART.md` - Use biological language for getting started
|
||||
4. `/ERROR_HANDLING.md` - Frame error handling as immune system
|
||||
|
||||
@@ -261,7 +261,7 @@ def some_function(self, data):
|
||||
[Emoji] ORGANISM CONTEXT - Actual function name
|
||||
|
||||
Biological explanation of what this does in the context of the DSS
|
||||
organism. Mention which organ system or process is involved.
|
||||
component. Mention which organ system or process is involved.
|
||||
|
||||
Args:
|
||||
data: Describe what data represents biologically
|
||||
@@ -292,7 +292,7 @@ What to do:
|
||||
```python
|
||||
raise ValidationError(
|
||||
"🛡️ IMMUNE ALERT: Pathogenic Token Detected\n"
|
||||
"Token value contains invalid characters that could infect the organism.\n"
|
||||
"Token value contains invalid characters that could infect the component.\n"
|
||||
"What to do:\n"
|
||||
"1. Remove invalid characters from the token value (clean the nutrient)\n"
|
||||
"2. Verify the token matches our genetic patterns (naming conventions)\n"
|
||||
@@ -304,7 +304,7 @@ raise ValidationError(
|
||||
|
||||
### **Pattern 3: Logging & Progress Messages**
|
||||
|
||||
For progress tracking and logging, map to organism processes:
|
||||
For progress tracking and logging, map to component processes:
|
||||
|
||||
```python
|
||||
logger.info("🍽️ Digestive system beginning token extraction...")
|
||||
@@ -322,7 +322,7 @@ For CLI commands and settings descriptions:
|
||||
```python
|
||||
@click.command()
|
||||
@click.option('--feed', is_flag=True, help='Feed the DSS with new tokens from Figma')
|
||||
@click.option('--health', is_flag=True, help='Check the organism vital signs')
|
||||
@click.option('--health', is_flag=True, help='Check the component vital signs')
|
||||
def dss_cli(feed, health):
|
||||
"""DSS Organism Control Panel - Feed, monitor, and maintain the system"""
|
||||
if feed:
|
||||
@@ -351,13 +351,13 @@ def dss_cli(feed, health):
|
||||
|
||||
### **Phase 2C: Documentation** 📋 READY
|
||||
- [ ] Code inline comments (docstrings)
|
||||
- [ ] README files with organism introduction
|
||||
- [ ] README files with component introduction
|
||||
- [ ] Architecture documentation
|
||||
- [ ] Setup guides rewritten biologically
|
||||
|
||||
### **Phase 3: Team Implementation** 🎯 FUTURE
|
||||
- [ ] Train developers on the framework
|
||||
- [ ] Establish code review standards for organism language
|
||||
- [ ] Establish code review standards for component language
|
||||
- [ ] Create coding guidelines document
|
||||
- [ ] Set up templates for new code
|
||||
|
||||
@@ -365,27 +365,27 @@ def dss_cli(feed, health):
|
||||
|
||||
## Part 5: Code Review Guidelines
|
||||
|
||||
When reviewing DSS code, check for organism framework compliance:
|
||||
When reviewing DSS code, check for component framework compliance:
|
||||
|
||||
### **✅ Good Patterns**
|
||||
```python
|
||||
# Docstring uses biological metaphor
|
||||
"""
|
||||
🛡️ IMMUNE SYSTEM - Validate incoming tokens
|
||||
Check if tokens are safe for circulation through the organism.
|
||||
Check if tokens are safe for circulation through the component.
|
||||
"""
|
||||
|
||||
# Error message includes emoji and biological context
|
||||
raise ValidationError("🛡️ Pathogen detected: Invalid token format")
|
||||
|
||||
# Comments explain organism role
|
||||
# Comments explain component role
|
||||
# The heart (database) stores this nutrient for circulation
|
||||
db.store_token(token)
|
||||
```
|
||||
|
||||
### **❌ Patterns to Update**
|
||||
```python
|
||||
# Generic docstring without organism context
|
||||
# Generic docstring without component context
|
||||
"""Validate tokens"""
|
||||
|
||||
# Technical error message
|
||||
@@ -466,9 +466,9 @@ async function checkSensoryConnection() {
|
||||
@app.get("/health")
|
||||
async def health_check():
|
||||
"""
|
||||
❤️ HEART VITALS - Check if the organism is alive
|
||||
❤️ HEART VITALS - Check if the component is alive
|
||||
|
||||
Returns the DSS organism's vital signs.
|
||||
Returns the DSS component's vital signs.
|
||||
"""
|
||||
return {
|
||||
"status": "healthy",
|
||||
@@ -482,7 +482,7 @@ async def health_check():
|
||||
|
||||
## Part 8: Common Questions
|
||||
|
||||
**Q: Do I HAVE to use organism language?**
|
||||
**Q: Do I HAVE to use component language?**
|
||||
A: Not strictly required, but recommended for user-facing messages (errors, logs, docs). Internal implementation details can stay technical.
|
||||
|
||||
**Q: What if the metaphor doesn't fit?**
|
||||
@@ -515,4 +515,4 @@ A: Yes! But keep them consistent and document them in the glossary if they're ne
|
||||
|
||||
---
|
||||
|
||||
**Happy integrating! The DSS organism is ready to speak biologically.** 🧬✨
|
||||
**Happy integrating! The DSS component is ready to speak biologically.** 🧬✨
|
||||
|
||||
@@ -1,8 +1,8 @@
|
||||
# 📚 DSS Documentation Hub: The Organism's Permanent Memory
|
||||
|
||||
Welcome to the DSS Documentation Hub - the central repository where all knowledge about the design system organism lives. This is where we store what we've learned, how systems work, and where to find answers.
|
||||
Welcome to the DSS Documentation Hub - the central repository where all knowledge about the design system component lives. This is where we store what we've learned, how systems work, and where to find answers.
|
||||
|
||||
**Think of this as the organism's brain - everything the system knows is recorded here.**
|
||||
**Think of this as the component's brain - everything the system knows is recorded here.**
|
||||
|
||||
---
|
||||
|
||||
@@ -10,7 +10,7 @@ Welcome to the DSS Documentation Hub - the central repository where all knowledg
|
||||
|
||||
### Quick Links (Start Here)
|
||||
- **[Getting Started](#getting-started)** - New to DSS? Start here
|
||||
- **[Organism Framework](#organism-framework)** - Understand the biology
|
||||
- **[Organism Framework](#component-framework)** - Understand the biology
|
||||
- **[Extended Learning](#extended-learning)** - Deep dives into each system
|
||||
- **[How-To Guides](#how-to-guides)** - Common tasks and workflows
|
||||
- **[Troubleshooting](#troubleshooting)** - Problem solving
|
||||
@@ -25,7 +25,7 @@ Welcome to the DSS Documentation Hub - the central repository where all knowledg
|
||||
3. **[Key Concepts](DSS_ORGANISM_GUIDE.md#key-concepts)** - Important ideas
|
||||
|
||||
### For Developers
|
||||
1. **[Code Integration Guide](CODE_INTEGRATION_GUIDE.md)** - How to use organism vocabulary in code
|
||||
1. **[Code Integration Guide](CODE_INTEGRATION_GUIDE.md)** - How to use component vocabulary in code
|
||||
2. **[Architecture](ARCHITECTURE.md)** - System design
|
||||
3. **[Token Ingestion](TOKEN_INGESTION.md)** - How tokens enter the system
|
||||
|
||||
@@ -186,7 +186,7 @@ Each organ system has extended documentation available:
|
||||
1. Check logs: `admin-ui/js/core/logger.js` output
|
||||
2. Run health check: `python -m dss.settings check-deps`
|
||||
3. Check database: Query SQLite database
|
||||
4. Review error messages using organism metaphors
|
||||
4. Review error messages using component metaphors
|
||||
5. Consult Troubleshooting section below
|
||||
|
||||
### Workflow Examples
|
||||
@@ -201,31 +201,31 @@ Each organ system has extended documentation available:
|
||||
|
||||
### By Symptom
|
||||
|
||||
**"The organism is sluggish"** (Slow performance)
|
||||
**"The component is sluggish"** (Slow performance)
|
||||
- Check database response time
|
||||
- Monitor CPU/memory usage
|
||||
- Review API latency
|
||||
- See: [Performance Guide](PERFORMANCE.md)
|
||||
|
||||
**"The organism is confused"** (Validation errors)
|
||||
**"The component is confused"** (Validation errors)
|
||||
- Review error messages from immune system
|
||||
- Check token schema compliance
|
||||
- Verify naming conventions
|
||||
- See: [Validation Guide](CODE_INTEGRATION_GUIDE.md#validation)
|
||||
|
||||
**"The organism can't see"** (Figma connection issues)
|
||||
**"The component can't see"** (Figma connection issues)
|
||||
- Verify Figma token configuration
|
||||
- Check sensory organs health
|
||||
- Review Figma API status
|
||||
- See: [Figma Integration](../tools/figma/README.md)
|
||||
|
||||
**"The organism is sick"** (Data integrity issues)
|
||||
**"The component is sick"** (Data integrity issues)
|
||||
- Run validation checks
|
||||
- Review recent database operations
|
||||
- Check for corrupted tokens
|
||||
- See: [Error Handling](../ERROR_HANDLING.md)
|
||||
|
||||
**"The organism is deaf"** (Not receiving updates)
|
||||
**"The component is deaf"** (Not receiving updates)
|
||||
- Check API endpoints
|
||||
- Verify webhook configuration
|
||||
- Review event emitters
|
||||
@@ -233,7 +233,7 @@ Each organ system has extended documentation available:
|
||||
|
||||
### Error Messages as Organism Communication
|
||||
|
||||
The organism communicates health through error messages:
|
||||
The component communicates health through error messages:
|
||||
- **🛡️ IMMUNE ALERT** - Validation failed (data rejected)
|
||||
- **❤️ CRITICAL** - Heart not responding (database down)
|
||||
- **⚠️ SYMPTOM** - Something unusual detected (warning)
|
||||
@@ -280,13 +280,13 @@ docs/
|
||||
### Knowledge Categories
|
||||
|
||||
**🧠 Conceptual**
|
||||
- What is the organism framework?
|
||||
- What is the component framework?
|
||||
- How do biological metaphors help?
|
||||
- What are the 11 organ systems?
|
||||
- Why think biologically?
|
||||
|
||||
**🔧 Technical**
|
||||
- How do I implement organism vocabulary?
|
||||
- How do I implement component vocabulary?
|
||||
- What code files handle each system?
|
||||
- How do I add new validators?
|
||||
- How do I integrate new sources?
|
||||
@@ -317,7 +317,7 @@ docs/
|
||||
|
||||
**New Team Members**
|
||||
→ Start with [Getting Started](#getting-started)
|
||||
→ Read [Organism Framework](#organism-framework)
|
||||
→ Read [Organism Framework](#component-framework)
|
||||
→ Explore specific system you work on
|
||||
|
||||
**Frontend Developers**
|
||||
@@ -370,7 +370,7 @@ docs/
|
||||
## Keeping Documentation Fresh
|
||||
|
||||
### Documentation Standards
|
||||
- Use organism vocabulary consistently
|
||||
- Use component vocabulary consistently
|
||||
- Include code examples
|
||||
- Link to related documentation
|
||||
- Keep examples up-to-date
|
||||
@@ -378,13 +378,13 @@ docs/
|
||||
|
||||
### Contributing to Docs
|
||||
1. Edit relevant `.md` file
|
||||
2. Use organism vocabulary
|
||||
2. Use component vocabulary
|
||||
3. Include concrete examples
|
||||
4. Test all links
|
||||
5. Update index/navigation if adding new section
|
||||
|
||||
### Documentation Review Checklist
|
||||
- [ ] Uses organism vocabulary consistently
|
||||
- [ ] Uses component vocabulary consistently
|
||||
- [ ] Clear and concise explanations
|
||||
- [ ] Code examples work
|
||||
- [ ] Links are correct
|
||||
@@ -429,7 +429,7 @@ docs/
|
||||
### Getting Help
|
||||
- Check [Extended Glossary](EXTENDED_GLOSSARY.md) first
|
||||
- Review [Troubleshooting](#troubleshooting)
|
||||
- Ask in team chat with organism vocabulary
|
||||
- Ask in team chat with component vocabulary
|
||||
- Create issue if it's a bug
|
||||
|
||||
### Feedback
|
||||
@@ -454,5 +454,5 @@ docs/
|
||||
**Version:** 1.0.0
|
||||
**Status:** Active & Maintained
|
||||
|
||||
🧬 *The organism's permanent memory, always growing and learning.*
|
||||
🧬 *The component's permanent memory, always growing and learning.*
|
||||
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
# DSS Coding Principles
|
||||
|
||||
Comprehensive principles for building the Design System Swarm (DSS) - a living, breathing design system organism.
|
||||
Comprehensive principles for building the Design System Server (DSS) - a living, breathing design system component.
|
||||
|
||||
**Version**: 1.0
|
||||
**Last Updated**: 2025-12-06
|
||||
@@ -12,7 +12,7 @@ Comprehensive principles for building the Design System Swarm (DSS) - a living,
|
||||
|
||||
1. [Architectural Principles](#1-architectural-principles)
|
||||
2. [Code Quality Standards](#2-code-quality-standards)
|
||||
3. [Organism Framework Principles](#3-organism-framework-principles)
|
||||
3. [Organism Framework Principles](#3-component-framework-principles)
|
||||
4. [Keyboard Accessibility](#4-keyboard-accessibility)
|
||||
5. [Web Component Standards](#5-web-component-standards)
|
||||
6. [Security Guidelines](#6-security-guidelines)
|
||||
@@ -282,7 +282,7 @@ class Result:
|
||||
|
||||
## 3. Organism Framework Principles
|
||||
|
||||
DSS is a **living organism** with organ systems. Understand and design for these systems.
|
||||
DSS is a **living component** with organ systems. Understand and design for these systems.
|
||||
|
||||
### 3.1 The Heart ❤️ - Database Layer
|
||||
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
# DSS Corporate Terminology Glossary
|
||||
|
||||
> **Quick Reference**: Enterprise terminology for the Design System Swarm
|
||||
> **Quick Reference**: Enterprise terminology for the Design System Server
|
||||
|
||||
---
|
||||
|
||||
@@ -36,7 +36,7 @@
|
||||
|
||||
| Deprecated Term | Corporate Term | Context |
|
||||
|-----------------|----------------|---------|
|
||||
| organism | module | Complex UI section |
|
||||
| component | module | Complex UI section |
|
||||
| molecule | component | Composite UI element |
|
||||
| atom | primitive / token | Base element or variable |
|
||||
| heart | core / database | Persistent storage layer |
|
||||
@@ -59,7 +59,7 @@
|
||||
|
||||
| Don't Say | Say Instead |
|
||||
|-----------|-------------|
|
||||
| "Feed the organism" | "Ingest tokens" |
|
||||
| "Feed the component" | "Ingest tokens" |
|
||||
| "Check the immune system" | "Run validation" |
|
||||
| "The heart is healthy" | "Database is operational" |
|
||||
| "Nervous system response" | "API response" |
|
||||
|
||||
@@ -465,7 +465,7 @@ This document verifies that all code changes, fixes, and implementations made du
|
||||
## 7. Organism Framework Integration
|
||||
|
||||
### Principle Reference
|
||||
- **Section**: [DSS_CODING_PRINCIPLES.md § 3 - Organism Framework Principles](./DSS_CODING_PRINCIPLES.md#3-organism-framework-principles)
|
||||
- **Section**: [DSS_CODING_PRINCIPLES.md § 3 - Organism Framework Principles](./DSS_CODING_PRINCIPLES.md#3-component-framework-principles)
|
||||
- **Key Principle**: "DSS is a living system with organ systems in balance"
|
||||
|
||||
### Implementation Verification
|
||||
@@ -651,4 +651,4 @@ The codebase now has:
|
||||
|
||||
**Created by**: Claude Code
|
||||
**Date**: 2025-12-06
|
||||
**For**: Design System Swarm Team
|
||||
**For**: Design System Server Team
|
||||
|
||||
@@ -320,7 +320,7 @@ When adding new principles:
|
||||
|
||||
## Summary
|
||||
|
||||
The Design System Swarm is a **A-grade, production-ready system** with:
|
||||
The Design System Server is a **A-grade, production-ready system** with:
|
||||
|
||||
✅ **Strong architecture** - Monolithic core, clear layering, separation of concerns
|
||||
✅ **Excellent code quality** - Type hints, documentation, error handling
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
# DSS Architecture Overview
|
||||
|
||||
> **The 7-layer architecture for the Design System Swarm**
|
||||
> **The 7-layer architecture for the Design System Server**
|
||||
|
||||
---
|
||||
|
||||
|
||||
Reference in New Issue
Block a user