Skip to content

Taxonomy Reference

Purpose: Tag taxonomy configuration for code-first documentation Detail Level: Overview with links to details


3 categories | 53 metadata tags | 3 aggregation tags

Current configuration uses @libar-docs- prefix with @libar-docs file opt-in.

ComponentCountDescription
Categories3Pattern classification by domain
Metadata Tags53Pattern enrichment and relationships
Aggregation Tags3Document routing

Domain classifications for organizing patterns by priority.

TagDomainPriorityDescription
coreCore1Core patterns
apiAPI2Public APIs
infraInfrastructure3Infrastructure

Full category reference


Tags for enriching patterns with additional metadata.

TagFormatPurposeRequiredExample
patternvalueExplicit pattern nameYes@libar-docs-pattern CommandOrchestrator
statusenumWork item lifecycle status (per PDR-005 FSM)No@libar-docs-status roadmap
coreflagMarks as essential/must-know patternNo@libar-docs-core
usecasequoted-valueUse case associationNo@libar-docs-usecase "When handling command failures"
TagFormatPurposeRequiredExample
usescsvPatterns this depends onNo@libar-docs-uses CommandBus, EventStore
used-bycsvPatterns that depend on thisNo@libar-docs-used-by SagaOrchestrator
depends-oncsvRoadmap dependencies (pattern or phase names)No@libar-docs-depends-on EventStore, CommandBus
enablescsvPatterns this enablesNo@libar-docs-enables SagaOrchestrator, ProjectionBuilder
implementscsvPatterns this code file realizes (realization relationship)No@libar-docs-implements EventStoreDurability, IdempotentAppend
extendsvalueBase pattern this pattern extends (generalization relationship)No@libar-docs-extends ProjectionCategories
see-alsocsvRelated patterns for cross-reference without dependency implicationNo@libar-docs-see-also AgentAsBoundedContext, CrossContextIntegration
api-refcsvFile paths to implementation APIs (replaces ‘See:’ Markdown text in Rules)No@libar-docs-api-ref @libar-dev/platform-core/src/durability/outbox.ts
TagFormatPurposeRequiredExample
phasenumberRoadmap phase number (unified across monorepo)No@libar-docs-phase 14
releasevalueTarget release version (semver or vNEXT for unreleased work)No@libar-docs-release v0.1.0
quartervalueDelivery quarter for timeline trackingNo@libar-docs-quarter Q1-2026
completedvalueCompletion date (YYYY-MM-DD format)No@libar-docs-completed 2026-01-08
effortvalueEstimated effort (4h, 2d, 1w format)No@libar-docs-effort 2d
effort-actualvalueActual effort spent (4h, 2d, 1w format)No@libar-docs-effort-actual 3d
teamvalueResponsible team assignmentNo@libar-docs-team platform
workflowenumWorkflow discipline for process trackingNo@libar-docs-workflow implementation
riskenumRisk level for planningNo@libar-docs-risk medium
priorityenumPriority level for roadmap orderingNo@libar-docs-priority high
TagFormatPurposeRequiredExample
adrvalueADR/PDR number for decision trackingNo@libar-docs-adr 015
adr-statusenumADR/PDR decision statusNo@libar-docs-adr-status accepted
adr-categoryvalueADR/PDR category (architecture, process, tooling)No@libar-docs-adr-category architecture
adr-supersedesvalueADR/PDR number this decision supersedesNo@libar-docs-adr-supersedes 012
adr-superseded-byvalueADR/PDR number that supersedes this decisionNo@libar-docs-adr-superseded-by 020
adr-themeenumTheme grouping for related decisions (from synthesis)No@libar-docs-adr-theme persistence
adr-layerenumEvolutionary layer of the decisionNo@libar-docs-adr-layer foundation
TagFormatPurposeRequiredExample
arch-roleenumArchitectural role for diagram generation (component type)No@libar-docs-arch-role projection
arch-contextvalueBounded context this component belongs to (for subgraph grouping)No@libar-docs-arch-context orders
arch-layerenumArchitectural layer for layered diagramsNo@libar-docs-arch-layer application
TagFormatPurposeRequiredExample
briefvaluePath to pattern brief markdownNo@libar-docs-brief docs/briefs/decider-pattern.md
product-areavalueProduct area for PRD groupingNo@libar-docs-product-area PlatformCore
user-rolevalueTarget user persona for this featureNo@libar-docs-user-role Developer
business-valuevalueBusiness value statement (hyphenated for tag format)No@libar-docs-business-value eliminates-event-replay-complexity
constraintvalueTechnical constraint affecting feature implementationNo@libar-docs-constraint requires-convex-backend
levelenumHierarchy level for epic->phase->task breakdownNo@libar-docs-level epic
parentvalueParent pattern name in hierarchy (links tasks to phases, phases to epics)No@libar-docs-parent AggregateArchitecture
titlequoted-valueHuman-readable display title (supports quoted values with spaces)No@libar-docs-title:"Process Guard Linter"
executable-specscsvLinks roadmap spec to package executable spec locations (PDR-007)No@libar-docs-executable-specs platform-decider/tests/features/behavior
roadmap-specvalueLinks package spec back to roadmap pattern for traceability (PDR-007)No@libar-docs-roadmap-spec DeciderPattern
behavior-filevaluePath to behavior test feature file for traceabilityNo@libar-docs-behavior-file behavior/my-pattern.feature
discovered-gapvalueGap identified during session retrospectiveNo@libar-docs-discovered-gap missing-error-handling
discovered-improvementvalueImprovement identified during session retrospectiveNo@libar-docs-discovered-improvement cache-invalidation
discovered-riskvalueRisk identified during session retrospectiveNo@libar-docs-discovered-risk data-loss-on-migration
discovered-learningvalueLearning captured during session retrospectiveNo@libar-docs-discovered-learning convex-mutation-limits
extract-shapescsvTypeScript type names to extract from this file for documentationNo@libar-docs-extract-shapes DeciderInput, ValidationResult, ProcessViolation
shapevalueMarks declaration as documentable shape, optionally with group nameNo@libar-docs-shape api-types
includecsvCross-cutting document inclusion for content routing and diagram scopingNo@libar-docs-include reference-sample,codec-system
targetvalueTarget implementation path for stub filesNo@libar-docs-target src/api/stub-resolver.ts
sincevalueDesign session that created this patternNo@libar-docs-since DS-A
conventioncsvConvention domains for reference document generation from decision recordsNo@libar-docs-convention fsm-rules, testing-policy

Full metadata tag reference


Tags that route patterns to specific aggregated documents.

TagTarget DocumentPurpose
overviewOVERVIEW.mdArchitecture overview patterns
decisionDECISIONS.mdADR-style decisions (auto-numbered)
introNonePackage introduction (template placeholder)

How tag values are parsed and validated.

FormatDescriptionExample
valueSimple string value@libar-docs-pattern MyPattern
enumConstrained to predefined values@libar-docs-status roadmap
quoted-valueString in quotes (preserves spaces)@libar-docs-usecase "When X happens"
csvComma-separated values@libar-docs-uses A, B, C
numberNumeric value@libar-docs-phase 14
flagBoolean presence (no value)@libar-docs-core

Format type details


Available configuration presets.

PresetTag PrefixCategoriesUse Case
generic@docs-3Simple projects with @docs- prefix
libar-generic@libar-docs-3Default preset with @libar-docs- prefix
ddd-es-cqrs@libar-docs-21Full DDD/ES/CQRS taxonomy

Taxonomy source files and pipeline flow.

src/taxonomy/
├── categories.ts # Category definitions (21 DDD-ES-CQRS)
├── format-types.ts # Format type constants
├── registry-builder.ts # Single source of truth builder
├── status-values.ts # Status FSM values
├── generator-options.ts # Generator option values
├── hierarchy-levels.ts # Hierarchy level values
├── risk-levels.ts # Risk level values
└── index.ts # Barrel export
graph LR
    Config[Configuration] --> Scanner[Scanner]
    Scanner --> Extractor[Extractor]
    Extractor --> Transformer[Transformer]
    Transformer --> Codec[Codec]
    Codec --> Markdown[Markdown]

    Registry[TagRegistry] --> Scanner
    Registry --> Extractor