Umbra

The description states that Umbra is a B2B UV-safety planning agent for outdoor crews in construction, agriculture, delivery, and similar field operations. It uses live data including UV index, weather, time of day, surface materials (albedo), and site photos to generate daily sun-safety schedules.

It includes:

• A guided workflow for foremen to create workspaces.
• Crew member profiles with self-reported skin type, sensitivity, PPE/UPF, SPF level, sunscreen application time, shade access, and placement.
• Site photo uploads with object names and locations.
• A Morning Brief that identifies the highest-priority worker, proposes a 20-minute relief rotation, visualizes routes to shade, and requires supervisor approval.

The deterministic exposure engine calculates:

UV Index × sun/time factor × cloud factor × albedo factor

It applies the strongest sun-time factor from 11:00–16:00 and accounts for reflective materials such as glass, concrete, steel, sand, and water.

Inference The product is described as a decision-support tool that integrates environmental data with worker-specific risk profiles to recommend safe break rotations.

The author positions Umbra as:

• A decision support system, not a medical diagnosis or legal guarantee.
• An operational solution for compliance and safety documentation.
• A transparent workflow that shows reasoning behind each recommendation (conditions, worker risk, trade-offs, decision).
• A tool to replace static forecasts, informal reminders, and spreadsheets.

The claim evolution appears to be:

1. Problem: Outdoor crews make safety decisions in changing conditions with limited tools.
2. Solution: Umbra automates scheduling using live data and worker context.
3. Differentiation: It provides explainable decisions, not black-box advice; it requires supervisor approval for actions.

Inference The author frames this as a shift from reactive to proactive safety management in outdoor work environments.

The description states that Umbra targets:

• Outdoor crews in construction, agriculture, delivery, and similar field operations.
• Foremen or supervisors who manage crew scheduling and safety.
• Employers needing to document safety practices and demonstrate hazard consideration.

Inference The target customer is a B2B user (foreman/supervisor) within industries where outdoor exposure is a known risk and compliance matters.

There is no evidence of pricing, revenue model, or monetization strategy in the description. The author only describes the product's functionality and development process.

Not evidenced

The project was built using:

• Codex and GPT-5.6 (Luna and Terra models)
• React, Node.js, JavaScript, Vite, Zustand
• OpenAI Responses API (optional server-side component)
• Open-Meteo for weather data
• Tools: VS Code, Windows 11

The author notes:

• The system was built end-to-end during a hackathon.
• All available Codex credits were used.
• The demo remains runnable without paid API credentials.
• It uses a deterministic fallback while keeping the exposure engine authoritative.

Inference The product is technically feasible and designed for rapid prototyping with AI-assisted development. However, no evidence of scalability or production-grade infrastructure is provided.

There is no evidence of:

• Revenue
• Customers
• Adoption
• Product usage metrics
• Post-hackathon development or iteration

The project was submitted to the OpenAI 2026 hackathon, and the author states it is a demo, not independently verified.

Not evidenced

There is no mention of competitors in the description. The author does not reference existing tools for UV exposure tracking or field safety scheduling.

Not evidenced

• Unverified claims: The product is described as operational decision support, but there's no evidence it has been tested or used outside a hackathon.
• No traction or validation: No customers, revenue, or usage data are provided.
• AI dependency: Heavy reliance on Codex and GPT models may not scale without continued access to these tools.
• Limited scope: The system is described as a demo with deterministic fallbacks — no indication of long-term viability or integration into larger systems.

Inference The project lacks commercial validation, and its current state reflects a prototype rather than a product ready for market.

1. What is the actual use case beyond the hackathon demo?
2. Has the system been tested with real users or in real-world conditions?
3. Are there plans to move beyond the demo and into production-grade infrastructure?
4. How does the product handle edge cases or unexpected inputs (e.g., poor image quality, missing data)?
5. What is the roadmap for monetization or customer acquisition post-hackathon?
6. Is there any intention to integrate with existing safety management platforms or enterprise systems?