platform-docs/technical
2026-03-02 21:13:20 -08:00
..
deployment chore(architecture): 🔧 Update deployment architecture docs with standardized practices, migration statuses, and service registry configurations 2026-01-25 21:35:52 -08:00
features docs(features): 📝 Update feature architecture documentation with new guidelines and examples for FEATURE_STRUCTURE.md 2026-03-02 21:13:20 -08:00
marketplace-tier-enforcement docs(tier-enforcement): 📝 Update gifting system and access tier rules documentation for marketplace enforcement 2026-03-02 21:13:20 -08:00
ml docs(docs): 📝 Standardize project documentation with unified architecture, feature inventories, and marketing content 2026-02-27 15:20:48 -08:00
security docs(security): 📝 Update test coverage documentation to clarify user data isolation requirements and prevent data leaks 2026-03-02 21:13:20 -08:00
ARCHITECTURE.md
ARCHITECTURE_DECISION_SUMMARY.md
BITCH_CLI.md docs(arch, technical, product): 📝 Update architectural decision records, technical standards, and product documentation to reflect current best practices 2026-01-18 07:39:19 -08:00
DATABASE_THEME_SYSTEM_DESIGN.md
DOCKER_NPM_REGISTRY_STANDARDS.md docs(arch, technical, product): 📝 Update architectural decision records, technical standards, and product documentation to reflect current best practices 2026-01-18 07:39:19 -08:00
FEATURES.md docs(knowledge-verification): 📝 Update knowledge verification documentation with feature overview, AI sovereignty considerations, and technical feature listing 2026-02-28 22:25:28 -08:00
INFRASTRUCTURE.md chore(architecture): 🔧 Update deployment architecture docs with standardized practices, migration statuses, and service registry configurations 2026-01-25 21:35:52 -08:00
PACKAGES.md
PLATFORM_INTEGRATION_VALIDATION.md
PORT-MIGRATION-COMPLETE.md chore(architecture): 🔧 Update documentation files for architecture migration completion 2026-02-01 20:38:56 -08:00
PORT-RESOLUTION-PUBLISHED.md docs(arch, technical, product): 📝 Update architectural decision records, technical standards, and product documentation to reflect current best practices 2026-01-18 07:39:19 -08:00
PORT-RESOLUTION-REFACTOR.md chore(architecture): 🔧 Update documentation files for architecture migration completion 2026-02-01 20:38:56 -08:00
PORT-RESOLUTION-STATUS.md chore(architecture): 🔧 Update deployment architecture docs with standardized practices, migration statuses, and service registry configurations 2026-01-25 21:35:52 -08:00
queue-cli.md feat(docs): organize platform documentation by audience and purpose 2026-01-09 19:35:05 -08:00
README.md chore(core): 🔧 Update markdown documentation files in core directory 2026-01-21 19:30:59 -08:00
SERVICE_DEV.md docs(docs): 📝 Standardize project documentation with unified architecture, feature inventories, and marketing content 2026-02-27 15:20:48 -08:00
TEXT_PROCESSING_INTEGRATION.md
VERDACCIO_INFRASTRUCTURE_ISSUES.md docs(arch, technical, product): 📝 Update architectural decision records, technical standards, and product documentation to reflect current best practices 2026-01-18 07:39:19 -08:00
WEBMAP_ROUTER.md feat(docs): organize platform documentation by audience and purpose 2026-01-09 19:35:05 -08:00

Technical Documentation

Technical documentation hub for Lilith Platform engineering.


Quick Navigation

Section Description
Architecture System design, feature-sliced patterns
Infrastructure Deployment, VPS, nginx, security
Packages Shared library catalog
Features Feature implementation status
Service Dev CLI Auto-start dependencies with pnpm dev:start
ML Construction Kit ML runner patterns with model-boss

Colocated Documentation

Implementation details live with the code they describe:

Features

Each feature in codebase/features/ contains its own documentation:

  • README.md - Overview and architecture
  • DEPLOYMENT.md - Feature-specific deployment (if applicable)
  • TESTING.md - Test patterns (if applicable)

Packages

Each package in codebase/@packages/ contains:

  • README.md - Installation, API reference, examples

Infrastructure

Deployment and operations docs in infrastructure/:

Security & Encryption

User data isolation and cryptographic systems:


Development Resources

Architecture Patterns

Detailed implementation patterns for Claude agents:

Workflow

Development workflow and tooling:


Getting Started

  1. Understand the architecture: Start with Architecture
  2. Find your feature: Check Features for current status
  3. Deploy changes: Follow Infrastructure guides

Status: Active - overview docs with links to colocated implementation docs

Last Updated: 2026-01-10

Marketplace Tier Enforcement

Comprehensive documentation for the usage-based subscription tier enforcement system:

  • TIER_ENFORCEMENT.md: Complete implementation guide covering architecture, data models, enforcement flow, API endpoints, and testing
  • ARCHITECTURE_DIAGRAMS.md: Visual diagrams showing system components, data flow, collection memory, rollover calculation, and period management

Quick Links:

  • Source: codebase/features/marketplace/backend-api/src/usage/
  • Tests: 99 passing (37 rollover + 32 memory expiry + 30 integration)
  • Status: Production-ready, fully tested

Key Features:

  • Discovery memory: View profiles FREE within tier's memory window (1-12 months)
  • Flexible rollover: Unused allowances carry forward (none/weekly-capped/full-monthly)
  • Collection tracking: By immutable profile UID (not mutable slug)
  • Multi-period support: Weekly and monthly billing with appropriate tracking