Explore 41 builds across custom software, cloud engineering and workflow automation. Start with your team’s problem, inspect the product screens, and review the scope and current readiness of each project.
Investigate the incident. Review the action. Keep the record.
Keep incident evidence, runbooks, proposed actions and approvals in one workspace, with a timeline of what happened.
For CloudOps and security leaders
The challenge
Incident investigation needs source evidence, clear action ownership and an independent approval trail.
InputIncident case and operational evidence
ReviewEvidence, policy and independent action approval
OutputRecorded action outcome and incident timeline
Evaluation scope & current status +
The incident workspace is deployed to the AWS evaluation environment with temporary personas and persistent case storage. Jira and CloudWatch are not configured there. This screenshot shows a controlled local incident with a Jira HTTP fixture, not a live integration or customer outcome.
October 2026 local capture. Controlled incident and Jira fixture; not a customer incident.
03 / Infrastructure change reviewPublic demo
TerraGate
Review infrastructure changes before they merge.
Inspect policy findings against the plan evidence, review proposed remediation and record approvals or time-limited risk exceptions.
For platform engineers and infrastructure reviewers
The challenge
Terraform changes can introduce security, cost, reliability or destructive-state risk before merge.
InputTerraform plan JSON and policy rules
ReviewRisk findings, rule provenance and scoped exceptions
OutputReview history and an approval-bound PR comment draft
Evaluation scope & current status +
Public engineering demo with shared review visibility. GitHub writes are mocked and plan artifacts use ephemeral storage. Merge enforcement and deployment authorization are not demonstrated. Use sample plans; private onboarding and durable artifact storage remain unfinished.
October 2026 application capture using a sample Terraform plan.
From source material to useful software.
Two focused applications: album review for photography studios, and cited search across a sermon archive.
Photography studios / Product preview
Album Approve
One place to review an album before it goes to print.
Studios upload exported spreads and share a private proof. Clients pin comments to the page, request changes or approve the version they reviewed.
Preview scope +
The public preview uses sample studio and client data. Production storage, customer onboarding and billing remain unfinished. These captures demonstrate the application workflow; they are not evidence of a paid customer service.
UploadPrepare the spreads for one album version.01 / Upload the spreads
ReviewKeep feedback attached to the exact spread.Actual application capture · sample studio and client data
ApproveRecord the final decision against that version.03 / Record the version's approval
IMPLEMENTED RETRIEVAL ARCHITECTURE
SOURCEKorean–English sermon captionsIngestion and versioned S3 archive snapshots
SEMANTIC SEARCHAmazon S3 VectorsPassage and topic similarity
KEYWORD SEARCHSharded S3 indexSpecific names and terms
APPLICATIONAuthenticated search & cited answersSource cards connect answers to the archive
System diagram · not a product screenshot
Document search / Authenticated application
Pulpit
Make an archive searchable, and keep the source in view.
Pulpit ingests Korean–English sermon captions and combines semantic retrieval with keyword search. Answers include source cards so readers can return to the original material.
Built
Caption ingestion, authenticated search and cited answers.
Updated
S3 Vectors retrieval and versioned archive snapshots, October 2026.
Operated
Infrastructure as code, query logging and index-aware caching.
Application scope +
Access to the archive requires authentication. Retrieval depends on available captions and source coverage. This is an implementation example; no customer savings, search accuracy guarantee or adoption figures are claimed.
The six problems from the homepage, each with the catalog entries that show it. Choose an entry to open its card with the screenshot, audience and scope notes.
01
Infrastructure changes nobody can fully review
Cloud and infrastructure changes checked against policy before they ship.
All 41 entries. Search by product, buyer or problem, or filter by family. Open Scope & readiness on any card for the challenge it addresses and its current status.
41 entries
Browse all 41 entries across six families.
Business & Market Intelligence. Opportunity, market and commercial decision support.
Cloud & Governance. Infrastructure review, governed operations and reusable APIs.
Industry Operations. Inspection, inventory, finance and field workflows.
Knowledge & Media. Turn documents, audio and media into usable evidence.
Creative & Desktop Tools. Focused experiences for creative work and local productivity.
Research & Engineering. Prototypes, migration work and engineering references.
01 / Business & Market IntelligenceWeb / cloud
PursuitDesk
For GovCon consultants and capture advisors
Public demo · sample client profile
Score federal readiness, triage live opportunities, support go/no-go reviews and export client-ready PDF/DOCX work.
Scope & readiness +
The challenge. Intake, readiness, opportunity and proposal work is scattered across portals and documents.
Portfolio note. Working public demo. Tenant JWT enforcement and billing are not active in the shared workspace; validate those controls for a client rollout.
Review Terraform plans against policy evidence, inspect findings and manage approval-bound comments and expiring risk exceptions.
Scope & readiness +
The challenge. Terraform changes can introduce security, cost, reliability or destructive-state risk before merge.
Portfolio note. Public engineering demo with shared review visibility. GitHub writes are mocked in the hosted demo; plan artifacts are ephemeral. Private onboarding and durable artifact storage remain unfinished.
Evaluation workspace · local capture with a controlled incident fixture
Organize incident cases, review evidence and runbooks, request approval for an exact action and inspect its recorded outcome.
Scope & readiness +
The challenge. Incident investigation needs source evidence, clear action ownership and an independent approval trail.
Portfolio note. Hosted AWS evaluation workspace with temporary personas. Incident case storage is deployed; Jira and CloudWatch are unconfigured. The illustrated incident uses a controlled local test and Jira fixture.
The challenge. A sermon archive needs durable, cited search instead of one-off transcript uploads.
Portfolio note. Authenticated archive with an AWS S3 Vectors retrieval backend and versioned archive snapshots. The project story describes implementation, not measured customer outcomes.
Active development · native iPad capture · synthetic test chart
Prepare versioned charts and setlists, keep personal notes available offline and share team markings and rehearsal conversation.
Scope & readiness +
The challenge. PDF arrangements, handwritten notes and weekly setlists need to stay usable as charts and team plans change.
Portfolio note. Active development, not an App Store release. The capture uses a synthetic chart; real multi-iPad rehearsal and release qualification remain open. Later local builds are ahead of the published application source.
Demonstration · sample invoice and extracted fields
Explore invoice field extraction and the proposed human-review workflow in a document-processing demonstration.
Scope & readiness +
The challenge. Copying invoice fields by hand is slow, while OCR alone still needs review.
Portfolio note. Demonstration only. Self-service onboarding, account isolation and export are not complete. Sample output is not evidence of a processed customer document.
The challenge. Album proofing via email and text creates unclear revision requests.
Portfolio note. Public preview with sample studio and client data. Production storage, onboarding and billing remain unfinished; the preview is not a paid studio service.