Skip to content

Project profiles

Profiles configure the dominant artifact and failure model before language or framework refinements are applied.

13 entries
Backend ServiceConfigures a long-running service whose primary responsibility is handling network requests or application operations.backend-service Background WorkerConfigures asynchronously delivered work with explicit acknowledgement, retry, and shutdown behavior.background-worker Browser Web ApplicationConfigures engineering priorities for a browser-executed user interface whose primary responsibility is interactive user behavior.browser-web-application CLI ApplicationConfigures command-line tools with stable invocation, exit, output, and automation behavior.cli-application Data PipelineConfigures staged ingestion and transformation with restartability, provenance, and bounded resources.data-pipeline Distributed SystemConfigures independently failing components with explicit ownership, delivery, and convergence semantics.distributed-system Full-stack Web ApplicationConfigures one product artifact with material browser and server responsibilities, including their trust and data boundaries.fullstack-web-application Infrastructure ToolConfigures tools that plan and apply consequential infrastructure or operational state changes.infrastructure-tool Legacy ModernizationConfigures bounded evolution of a difficult existing system where behavior, history, and reversibility constrain change.legacy-modernization Plugin or ExtensionConfigures code loaded by a host through supported extension points and lifecycle contracts.plugin-or-extension PrototypeConfigures temporary learning artifacts for rapid evidence gathering and reversible decisions.prototype Real-time or Embedded SystemConfigures systems where correctness includes deterministic timing and bounded resource use.real-time-system Reusable LibraryConfigures a reusable artifact consumed independently through an intentional and compatibility-governed public surface.reusable-library