skip to content
← featured work
Active advanced MVP Product · AI quality engineering v0.9.0 · Phase 9C in progress

Prompt Laboratory

A Git-native, cross-industry quality engineering platform for prompts.

OVERVIEW

What it is

Prompt Laboratory makes prompts reviewable software assets: YAML contracts define the interface, repeatable datasets exercise behaviour, evaluators create evidence, and regression policies support human release decisions.

PROBLEM

Why it exists

Prompts often become production dependencies while remaining unversioned strings with weak test evidence, inconsistent review and provider-specific behaviour.

ARCHITECTURE

System flow

YAML contracts versioned in Git Strict render validated inputs Evaluation deterministic + LLM Comparison quality · cost · latency Regression gate policy evidence Human approval release decision
Figure 1 · Git-controlled prompt lifecycle from contract and dataset to evidence-backed approval.
CAPABILITIES

What is implemented

▸ YAML prompt contracts with versions, owners, variables and output schemas
▸ Strict Jinja2 rendering with Pydantic input validation
▸ Cross-industry synthetic evaluation datasets
▸ Deterministic checks plus optional LLM-as-judge evaluation
▸ OpenAI, Anthropic, Gemini, local-compatible and mock providers
▸ Side-by-side quality, latency, token and estimated-cost comparison
▸ FastAPI, Streamlit and PostgreSQL product surfaces
▸ Authentication, workspaces and encrypted per-user provider credentials
TECHNOLOGY STACK
Python 3.11+FastAPIPydanticJinja2StreamlitPostgreSQLAlembicDocker ComposeGitHub ActionsOpenAIAnthropicGemini
ENGINEERING

Key decisions

ADR-01

Git remains the source of truth

accepted

The workbench executes prompt contracts without silently editing YAML or bypassing code review.

ADR-02

Evidence before release

accepted

Baselines do not update themselves; deterministic and model-based evidence informs human approval.

ADR-03

Credentials remain server-side

accepted

Provider keys are encrypted at rest and never returned to the browser or written into evidence.

TRUST

Security, privacy and quality controls

  • ◆Workspace-scoped membership and experiment history
  • ◆Expiring access tokens and versioned database migrations
  • ◆Encrypted provider credentials with runtime isolation
  • ◆Provider failures are isolated during comparisons
  • ◆LLM-as-judge supplements rather than replaces deterministic checks
EVIDENCE

Verified results

  • ✓Released as v0.9.0 with documented Phase 1–9B capabilities implemented
  • ✓Synthetic demonstrations cover healthcare, finance, retail, HR, legal and education
  • ✓Regression gates produce machine-readable reports and fail configured thresholds
  • ✓Phase 9C collaboration work remains active and is not presented as complete
CURRENT LIMITATIONS

What this does not claim

▲ACCURACY BOUNDARY
  • • Hosted multi-tenant deployment, live A/B testing and billing are not completed features.
  • • Synthetic fixtures are demonstrations, not validated professional systems.
  • • Phase 9C collaboration work is still being completed.
NEXT

Roadmap

  • →Complete and verify Phase 9C collaboration workflows
  • →Strengthen production deployment guidance and operational hardening
  • →Expand traceable evaluation packs while preserving cross-industry scope