Skip to content

DocCompile

Summary

Status

Working SaaS with an evolving product hypothesis. The implemented foundation is a docs-as-code publisher and AI transformation service. The target direction is a professional artifact compilation platform.

Role

Founder: product owner, system architect, and implementation owner.

Stack

Client-side SPA; AWS CloudFront, private S3, API Gateway, Lambda, DynamoDB, Cognito; Terraform; GitHub Actions with OIDC; replaceable LLM provider; Paddle billing.

Exact service inventory and commercial contour details should be confirmed against the product repository.

Project value

For the target audience (engineers, analysts, architects, and other professionals who already work in Markdown):

  • turn structured Markdown, Mermaid, and architecture icons into a professional PDF without leaving a docs-as-code workflow;
  • keep the document in the browser by default; send content to the server only when an AI compilation is explicitly requested;
  • use bounded, credit-metered AI transformations instead of unbounded chat generation.

For the professional profile:

  • founder-led SaaS from product discovery through AWS serverless architecture, identity, billing, and operations;
  • a documented pivot from proprietary workspace to a processing layer;
  • controlled LLM execution: versioned prompts, transformation jobs, cost bounds, and a target Artifact Contract / Harness model.

What this demonstrates

This project demonstrates the ability to:

  • take a product from a working rendering engine to a commercial AWS SaaS contour;
  • keep architecture, cost, privacy, and AI behavior under explicit control rather than treating the LLM as the system;
  • change the product hypothesis when evidence shows that competing for document storage is the wrong fight;
  • separate what is implemented today from the Compiler / Harness direction being designed next.

Quick reading path

  1. Overview - product summary and stack
  2. Context and Problem - background and problem statement
  3. Architecture and Integrations
  4. Goals, Requirements, and Constraints - key implemented capabilities
  5. All-in-one - full case study in one page

Document assemblies

  • All-in-one - all sections assembled for sequential reading and export
  • Architecture review - goals through decisions for architecture review sessions
  • SRS pack - context through operations for SRS-style review
  • Demo pack - overview, role, architecture, decisions, roadmap, and demonstration

Full structure