This document defines the Official Domain Terminology (Ubiquitous Language) for the Synapse Framework. All code, documentation, and communication should use these medical/biological terms consistently.
Principle: The entire codebase should reflect the body and all that belongs to it. Every term should align with medical/biological terminology.
- NeuralNode: Base class for all processing units. Represents a neuron in the nervous system.
- CorticalNeuron: Stateful processing unit (like neurons in the cerebral cortex). Maintains persistent state.
- ReflexNeuron: Stateless processing unit (like spinal reflex neurons). Fast, stateless responses.
- SensoryNeuron: Input processing unit that receives external stimuli and converts them to signals.
- MotorNeuron: Output processing unit that triggers actions and side effects.
- Connection: Represents a synaptic connection between neurons.
- Synapse: The connection point between neurons where signals are transmitted.
- NeuralCircuit: Organized network of connected neurons.
- Neuroplasticity: System for adaptive rewiring and self-healing of neural connections.
- Dendrite: Input receptor of a neuron (receives signals).
- Soma: Cell body of a neuron (processes signals).
- Axon: Output transmitter of a neuron (sends signals).
- Threshold: Activation threshold for a neuron (0.0-1.0).
- Signal: Neural signal transmitted between neurons.
- Excitatory: Signal type that promotes activation.
- Inhibitory: Signal type that prevents activation.
- Myelinated: Fast, optimized connection (like myelinated nerve fibers).
- Refractory Period: Time period after firing when neuron cannot fire again (debouncing).
- Heart: Central message broker that routes and distributes messages.
- Artery: Outgoing message channel (carries messages away from heart).
- Vein: Incoming message channel (carries messages to heart).
- BloodCell: Message container that carries data through the circulatory system.
- PublishSubscribe: Pub-sub messaging pattern.
- RequestResponse: Request-response messaging pattern.
- EventSourcing: Event sourcing pattern for state reconstruction.
- Saga: Distributed transaction pattern.
- FireAndForget: Fire-and-forget messaging pattern.
- TCell: Authentication system (like T-cells that identify cells).
- BCell: Authorization system (like B-cells that produce antibodies).
- Macrophage: Input sanitization system (like macrophages that engulf pathogens).
- Antibody: Threat detection system (like antibodies that identify threats).
- Session: Active authentication session.
- Token: Authentication token.
- Permission: Authorization permission.
- Role: Authorization role.
- Threat: Security threat detected by antibody.
- Sanitization: Input sanitization performed by macrophage.
- Bone: Immutable data model with schema validation.
- Schema: Structure definition for a bone.
- FieldSchema: Field definition within a schema.
- Validator: Validation function for data integrity.
- ValidationResult: Result of validation operation.
- Joint: Relationship between bones (planned).
- Marrow: Factory for generating bone instances (planned).
- Cartilage: Interface between bones (planned).
- Periosteum: Outer validation layer (planned).
- Calcium: Type constraints that strengthen structure (planned).
- Muscle: Pure function wrapper for business logic operations.
- MuscleGroup: Pipeline of muscles that execute in sequence.
- MuscleMemory: Caching system for muscle results.
- MapMuscle: Transformation muscle (maps over collections).
- FilterMuscle: Filtering muscle (filters collections).
- ReduceMuscle: Reduction muscle (reduces collections).
- SortMuscle: Sorting muscle (sorts collections).
- TransformMuscle: Generic transformation muscle.
- ComputeMuscle: Computation muscle.
- AggregateMuscle: Aggregation muscle.
- Lung: HTTP client with resilience patterns.
- Diaphragm: Resilience system (retry, circuit breaker, throttling, bulkhead).
- Router: HTTP routing system.
- Resource: External resource connection (database, cache, storage).
- ResourcePool: Pool of reusable resource connections.
- RestAdapter: REST API adapter.
- GraphQLAdapter: GraphQL API adapter.
- WebSocketAdapter: WebSocket adapter.
- ProtocolAdapter: Base protocol adapter.
- DatabaseResource: Database connection resource.
- CacheResource: Cache connection resource.
- StorageResource: Storage connection resource.
- Astrocyte: State management and caching (like astrocytes that maintain homeostasis).
- Oligodendrocyte: Performance optimization and connection pooling (like oligodendrocytes that myelinate axons).
- Microglia: Health monitoring and error tracking (like microglia that monitor brain health).
- Ependymal: API gateway and request routing (like ependymal cells that line ventricles).
- Cache: State cache managed by astrocyte.
- Connection Pool: Pool of connections managed by oligodendrocyte.
- Health Check: Health monitoring check performed by microglia.
- Alert: Health alert emitted by microglia.
- SkinCell: Base class for all skin layer UI components (replaces VisualNeuron).
- Receptor: Input component that detects external stimuli (replaces SensoryNeuron).
- Effector: Output component that produces responses (replaces MotorNeuron).
- DermalLayer: Container/layout component (replaces InterneuronUI).
- TouchReceptor: Touch/click input receptor (replaces Button).
- TextReceptor: Text input receptor (replaces Input).
- PressureReceptor: Pressure-sensitive input receptor (planned).
- VibrationReceptor: Haptic feedback receptor (planned).
- Keratinocyte: Visual component cell (planned).
- Melanocyte: Theming/styling cell (planned).
- LangerhansCell: Event detection cell (planned).
- Fibroblast: Layout/structure cell (planned).
- Adipocyte: State storage cell (replaces VisualAstrocyte).
- BloodVessel: Data flow pipe (planned).
- Theater: Main operating theater orchestrator.
- Stage: Surgical stage where components are rendered.
- Amphitheater: Observation gallery for viewing components.
- Specimen: Component variation or state to be examined.
- Observation: Behavioral test or assertion.
- Dissection: Structural analysis of component anatomy.
- Laboratory: Testing environment.
- Experiment: Individual test scenario.
- Hypothesis: Test assertion.
- TestSubject: Component being tested.
- Atlas: Medical reference documentation.
- Protocol: Medical procedure guidelines.
- Instrument: Diagnostic instrument (microscope, profiler, etc.).
- Microscope: Inspection instrument for examining components.
- LabReport: Laboratory test report.
- Microscope: Component inspection instrument.
- StateExplorer: State inspection instrument.
- SignalTracer: Signal flow tracing instrument.
- PerformanceProfiler: Performance profiling instrument.
- HealthMonitor: Health monitoring instrument.
- ComponentCatalogue: Component inventory with dependencies.
- Diagram: Visual documentation (state machines, hierarchies).
- ReportFormat: Format for lab reports (text, json, html, markdown).
- VisualNeuron: Base UI component → Should be SkinCell.
- SensoryNeuron: Input component → Should be Receptor.
- MotorNeuron: Action component → Should be Effector.
- InterneuronUI: Container component → Should be DermalLayer.
- VisualAstrocyte: UI state management → Should be Adipocyte.
- VisualOligodendrocyte: UI rendering optimization → Should be Melanocyte.
- Button: Generic button → Should be TouchReceptor.
- Input: Generic input → Should be TextReceptor.
- Select: Generic select → Needs medical equivalent.
- Form: Generic form → Should be DermalLayer.
- Modal: Generic modal → Needs medical equivalent.
- Card: Generic card → Needs medical equivalent.
- Alert: Generic alert → Needs medical equivalent.
- Text: Generic text → Needs medical equivalent.
- Radio: Generic radio → Needs medical equivalent.
- Checkbox: Generic checkbox → Needs medical equivalent.
- Chart: Generic chart → Needs medical equivalent.
- BarChart: Bar chart → Needs medical equivalent.
- LineChart: Line chart → Needs medical equivalent.
- PieChart: Pie chart → Needs medical equivalent.
- ScatterPlot: Scatter plot → Needs medical equivalent.
- ChartDataPoint: Data point → Needs medical equivalent.
- DataBounds: Data bounds → Needs medical equivalent.
- CanvasPoint: Canvas point → Needs medical equivalent.
- Server: Generic server → Needs medical equivalent.
- Client: Generic client → Needs medical equivalent.
- Bridge: Generic bridge → Needs medical equivalent.
- WebSocketBridge: WebSocket bridge → Needs medical equivalent.
- TheaterServer: Theater server → Needs medical equivalent.
- HotReload: Hot reload → Needs medical equivalent.
- Config: Generic configuration → Needs medical equivalent.
- Options: Generic options → Needs medical equivalent.
- Settings: Generic settings → Needs medical equivalent.
- ComponentProps: Component props → Needs medical equivalent.
- ComponentState: Component state → Needs medical equivalent.
- Props: Generic props → Needs medical equivalent.
- State: Generic state → Needs medical equivalent.
- Test: Generic test → Should use Experiment/Hypothesis.
- Mock: Generic mock → Needs medical equivalent.
- TestSubject: Already medical ✓.
- EventBus: Event bus → Needs medical equivalent.
- Event: Generic event → Needs medical equivalent.
- Signal: Already medical (neural signal) ✓.
- DependencyAuditor: Dependency auditor → Needs medical equivalent.
- AuditReport: Audit report → Needs medical equivalent.
- AuditOptions: Audit options → Needs medical equivalent.
- Classes: PascalCase (e.g.,
NeuralNode,BloodCell) - Interfaces: PascalCase (e.g.,
NeuralNodeConfig,BloodCellOptions) - Types: PascalCase (e.g.,
NeuronType,NodeState) - Enums: PascalCase (e.g.,
ProtocolType,HealthStatus) - Methods: camelCase (e.g.,
activate(),receive()) - Variables: camelCase (e.g.,
signalQueue,activationTime) - Constants: UPPER_SNAKE_CASE (e.g.,
MAX_RETRIES,DEFAULT_TTL)
- ✓ Approved: Term is correct and should be used.
- → Should be: Term should be replaced with medical equivalent.
- Needs medical equivalent: Term needs a medical/biological equivalent to be created.
- Planned: Term is planned but not yet implemented.
- All terms should align with medical/biological terminology.
- Legacy terms (VisualNeuron, etc.) should be migrated to Skin system terms.
- Generic technical terms (Config, Server, Client, etc.) need medical equivalents.
- UI component names (Button, Input, etc.) need medical equivalents.
- Visualization terms (Chart, DataPoint, etc.) need medical equivalents.
- Testing infrastructure terms (Mock, etc.) need medical equivalents.
Last Updated: 2024 Version: 1.0 Status: Official Domain Terminology Glossary