DexterLab

🚨 New downloadable modules coming soon🌍 Community requests now open — send your ideas🌍 Support available via email or scheduled calls🌍 Technical consulting for companies

Lab Protocols

Internal standards and methods used to maintain consistency, clarity, and technical rigor across the Laboratory.

Documentation Standards

All content in the Lab follows a unified documentation approach to ensure readability and long‑term maintainability.

  • Clear separation between architecture, implementation, and verification
  • Consistent terminology across all entries
  • Minimal narrative, maximum technical precision
  • Use of diagrams only when they add clarity
  • Avoidance of redundant explanations

These standards ensure that every page can be understood independently and referenced reliably.

Naming Conventions

To maintain coherence across architectures, workflows, and RTL blocks, the Lab adopts strict naming rules.

  • Files: lowercase, hyphen‑separated (e.g., axi-stream-fifo.vhd)
  • Modules: PascalCase for entities and architectures
  • Signals: snake_case for internal signals, UPPERCASE for constants
  • Directories: grouped by function (e.g., rtl/, sim/, docs/)

Consistent naming reduces ambiguity and improves searchability.

Versioning Rules

Every entry in the Lab evolves over time. Versioning ensures traceability and clarity.

  • Each page includes a revision history
  • Major changes increment the primary version (e.g., 1.0 → 2.0)
  • Minor edits increment the secondary version (e.g., 1.1 → 1.2)
  • Deprecated content is archived, not deleted

This allows engineers to follow the evolution of a design or workflow.

Verification Protocols

Verification is a core part of the Laboratory’s methodology.

  • All RTL blocks must include a minimal testbench
  • Waveforms must illustrate key behaviors
  • Edge cases must be documented
  • Assertions are recommended when applicable
  • Simulation logs should be reproducible

Verification ensures that reusable components behave predictably across projects.

Publishing Workflow

Content moves through a structured pipeline before appearing in the Lab.

  1. Draft — raw notes, sketches, or partial ideas
  2. Refinement — cleaned, structured, and validated
  3. Review — checked for consistency with Lab standards
  4. Publication — added to the appropriate section
  5. Maintenance — updated as new insights emerge

This workflow keeps the Lab coherent and technically reliable.

Narrative Layer

Protocols evolve as the Laboratory refines its methods and expands its scope.