initial commit

.gitignore

@@ -0,0 +1,173 @@
+# Byte-compiled / optimized / DLL files
+__pycache__/
+*.py[cod]
+*$py.class
+
+# C extensions
+*.so
+
+# Distribution / packaging
+.Python
+build/
+develop-eggs/
+dist/
+downloads/
+eggs/
+.eggs/
+lib/
+lib64/
+parts/
+sdist/
+var/
+wheels/
+share/python-wheels/
+*.egg-info/
+.installed.cfg
+*.egg
+MANIFEST
+
+# PyInstaller
+#  Usually these files are written by a python script from a template
+#  before PyInstaller builds the exe, so as to inject date/other infos into it.
+*.manifest
+*.spec
+
+# Installer logs
+pip-log.txt
+pip-delete-this-directory.txt
+
+# Unit test / coverage reports
+htmlcov/
+.tox/
+.nox/
+.coverage
+.coverage.*
+.cache
+nosetests.xml
+coverage.xml
+*.cover
+*.py,cover
+.hypothesis/
+.pytest_cache/
+cover/
+
+# Translations
+*.mo
+*.pot
+
+# Django stuff:
+*.log
+local_settings.py
+db.sqlite3
+db.sqlite3-journal
+
+# Flask stuff:
+instance/
+.webassets-cache
+
+# Scrapy stuff:
+.scrapy
+
+# Sphinx documentation
+docs/_build/
+
+# PyBuilder
+.pybuilder/
+target/
+
+# Jupyter Notebook
+.ipynb_checkpoints
+
+# IPython
+profile_default/
+ipython_config.py
+
+# pyenv
+#   For a library or package, you might want to ignore these files since the code is
+#   intended to run in multiple environments; otherwise, check them in:
+# .python-version
+
+# pipenv
+#   According to pypa/pipenv#598, it is recommended to include Pipfile.lock in version control.
+#   However, in case of collaboration, if having platform-specific dependencies or dependencies
+#   having no cross-platform support, pipenv may install dependencies that don't work, or not
+#   install all needed dependencies.
+#Pipfile.lock
+
+# UV
+#   Similar to Pipfile.lock, it is generally recommended to include uv.lock in version control.
+#   This is especially recommended for binary packages to ensure reproducibility, and is more
+#   commonly ignored for libraries.
+#uv.lock
+
+# poetry
+#   Similar to Pipfile.lock, it is generally recommended to include poetry.lock in version control.
+#   This is especially recommended for binary packages to ensure reproducibility, and is more
+#   commonly ignored for libraries.
+#   https://python-poetry.org/docs/basic-usage/#commit-your-poetrylock-file-to-version-control
+#poetry.lock
+
+# pdm
+#   Similar to Pipfile.lock, it is generally recommended to include pdm.lock in version control.
+#pdm.lock
+#   pdm stores project-wide configurations in .pdm.toml, but it is recommended to not include it
+#   in version control.
+#   https://pdm.fming.dev/latest/usage/project/#working-with-version-control
+.pdm.toml
+.pdm-python
+.pdm-build/
+
+# PEP 582; used by e.g. github.com/David-OConnor/pyflow and github.com/pdm-project/pdm
+__pypackages__/
+
+# Celery stuff
+celerybeat-schedule
+celerybeat.pid
+
+# SageMath parsed files
+*.sage.py
+
+# Environments
+.env
+.venv
+env/
+venv/
+ENV/
+env.bak/
+venv.bak/
+
+# Spyder project settings
+.spyderproject
+.spyproject
+
+# Rope project settings
+.ropeproject
+
+# mkdocs documentation
+/site
+
+# mypy
+.mypy_cache/
+.dmypy.json
+dmypy.json
+
+# Pyre type checker
+.pyre/
+
+# pytype static type analyzer
+.pytype/
+
+# Cython debug symbols
+cython_debug/
+
+# PyCharm
+#  JetBrains specific template is maintained in a separate JetBrains.gitignore that can
+#  be found at https://github.com/github/gitignore/blob/main/Global/JetBrains.gitignore
+#  and can be added to the global gitignore or merged into this file.  For a more nuclear
+#  option (not recommended) you can uncomment the following to ignore the entire idea folder.
+.idea/
+
+# PyPI configuration file
+.pypirc
+
+.DS_Store

app.py

@@ -0,0 +1,138 @@
+import base64
+from enum import Enum
+from typing import Iterator
+from langchain_core.output_parsers import PydanticOutputParser
+from langchain_core.prompts import ChatPromptTemplate
+from langchain_openai import ChatOpenAI
+from pydantic import BaseModel, Field
+from config import SYSTEM_PROMPT
+import json
+import time
+
+
+class Eligibility(str, Enum):
+    ELIGIBLE = "Eligible"
+    INELIGIBLE = "Ineligible"
+    RESUBMIT = "Re-submit"
+
+
+# class Response(BaseModel):
+#     eligibility: Eligibility = Field(description="The status of eligibility One of: 'Eligible', 'Ineligible', 'Re-submit'.")
+#     justification: str = Field(
+#         description="A detailed, itemized, and numbered Markdown list of all findings that support the eligibility status. For 'Ineligible', list all violations. For 'Re-submit', list all points of uncertainty. For 'Eligible', state that no violations were found and note any movable items observed."
+#     )
+#     instruction: str = Field(
+#         description="A clear, actionable, and numbered Markdown list of steps the homeowner must take. Each instruction must directly correspond to a finding in the 'justification' field. For 'Eligible' status, this provides a confirmation and reminders for movable items."
+#     )
+
+class Response(BaseModel):
+    """
+    Schema for the AI Inspector’s output.
+
+    • eligibility  – Overall result.
+    • justification – Numbered Markdown list explaining that result.
+    • instruction  – Numbered Markdown list of next steps that map
+                     one-to-one to the justification list.
+    """
+
+    eligibility: Eligibility = Field(
+        ...,
+        description=(
+            "Overall inspection outcome.\n\n"
+            " • 'Eligible'   – No violations observed in visible areas.\n"
+            " • 'Ineligible' – ≥1 confirmed violation detected.\n"
+            " • 'Re-submit'  – No clear violations, but ≥1 point of "
+            "uncertainty prevents a confident decision."
+        ),
+    )
+
+    justification: str = Field(
+        ...,
+        description=(
+            "A *Markdown* numbered list detailing findings that back up "
+            "the chosen eligibility value.\n\n"
+            "Formatting rules:\n"
+            " • Each item starts with '1.', '2.', …\n"
+            " • For 'Eligible': a single sentence stating no violations "
+            "   plus any movable combustibles noted.\n"
+            " • For 'Ineligible': each item describes one specific, "
+            "   observable violation.\n"
+            " • For 'Re-submit': each item describes one uncertainty "
+            "   that must be resolved (e.g., blurry photo, hidden area)."
+        ),
+        min_length=1,
+    )
+
+    instruction: str = Field(
+        ...,
+        description=(
+            "A *Markdown* numbered list of homeowner actions that map "
+            "directly, in order, to the items in 'justification'.\n\n"
+            " • For 'Eligible': give a short confirmation plus reminders "
+            "   to relocate any listed movable items during Red Flag "
+            "   Warnings or extended absences.\n"
+            " • For 'Ineligible': give a clear, actionable fix for each "
+            "   violation.\n"
+            " • For 'Re-submit': specify exactly what the homeowner must "
+            "   provide or clarify (e.g., new close-up photo, daylight "
+            "   image, measurement)."
+        ),
+        min_length=1,
+    )
+
+class LLMHandler:
+    def __init__(self, model_name="gpt-4.1-2025-04-14", temperature=0.3):
+        self.llm = ChatOpenAI(model=model_name, temperature=temperature, streaming=True)
+        self.parser = PydanticOutputParser(pydantic_object=Response)
+        self.prompt = ChatPromptTemplate.from_messages(
+            [
+                ("system", SYSTEM_PROMPT),
+                ("user", [
+                    {
+                        "type": "image_url",
+                        "image_url": "data:image/jpeg;base64,{image_data}"
+                    }
+                ])
+            ]
+        ).partial(format_instructions=self.parser.get_format_instructions())
+        self.chain = self.prompt | self.llm
+
+    def process_image(self, image_path: str) -> Iterator[str]:
+        with open(image_path, "rb") as img_file:
+            image_data = base64.b64encode(img_file.read()).decode("utf-8")
+
+        response = self.chain.invoke(
+            {
+                "image_data": image_data,
+                "image_mime_type": "image/jpeg",
+                "cache_type": "ephemeral",
+            }
+        )
+        return response.text()
+
+import gradio as gr
+
+llm_handler = LLMHandler()
+
+
+def process_and_display(image):
+    if image is None:
+        return "Please upload an image."
+
+    image_path = image
+
+    llm_output = json.loads(llm_handler.process_image(image_path))
+
+    return llm_output["justification"], llm_output["instruction"]
+
+demo = gr.Interface(
+    fn=process_and_display,
+    inputs=gr.Image(type="filepath", label="Upload Photo", height=500),
+    outputs=[gr.Textbox(label="Inspection Result", info="The list of potential violations", lines=8),
+             gr.Textbox(label="LLM Response", info="The instruction for how to fix the potential violations or what new evidence to provide." ,  lines=8)],
+    title="Wildfire Prepared Home Eligibility Inspector",
+    description="Upload a photo of all four sides of their home (one by one), showcasing the 0- to 5-foot noncombustible zone.",
+    flagging_mode="never",
+)
+
+demo.launch()

config.py

@@ -0,0 +1,78 @@
+SYSTEM_PROMPT = """
+You are **Wildfire Prepared Home’s virtual pre-inspection consultant**.  
+Your job is to study homeowner-supplied photos and decide whether the
+**0–5 ft non-combustible zone** around the house passes, fails, or
+needs clarification.
+
+--------------------------------------------------------------------------
+📋 1. Program Goal
+--------------------------------------------------------------------------
+Create and maintain a continuous 5-foot buffer of **non-combustible
+material** (rock, gravel, concrete, bare mineral soil, etc.) around
+every exterior wall of the building.
+
+--------------------------------------------------------------------------
+🔍 2. Your Inspection Workflow
+--------------------------------------------------------------------------
+1. **Map the Zone** – Visually estimate the area that lies ≤ 5 ft from
+   the home’s foundation in every direction.
+2. **Detect Findings** – List **every** violation *or* uncertainty you
+   observe **in that zone**.  
+   • Include items that overhang the zone (e.g., tree limbs).  
+   • Group identical issues only when they share the same remedy.
+3. **Recommend Actions** – For each finding, give one clear,
+   homeowner-friendly step that fixes or clarifies the issue.
+
+--------------------------------------------------------------------------
+🛑 3. Detailed Pass/Fail Rules & Examples
+--------------------------------------------------------------------------
+• **Vegetation** – 100 % removed to bare soil.  
+  ✗ Dry lawn touching siding ✗ Flower bed against wall ✗ Pine-needle layer
+
+• **Trees** – No trunk, limb, or branch may be inside or overhanging the
+  zone.  
+  ✗ Trunk 3 ft from wall ✗ Branch extends over eaves
+
+• **Ground-cover** – Only non-combustible material allowed.  
+  ✗ Wood/rubber mulch ✗ Pine straw ✓ Gravel, rock, pavers, concrete
+
+• **Fences / Retaining Walls** – Combustible portions must be outside
+  the 5-ft zone.  
+  ✗ Wood fence attached to house ✗ Timber retaining wall
+
+• **Stored Combustibles** – Remove everything that can burn.  
+  ✗ Firewood, lumber, cardboard, plastic bins, wicker furniture, etc.
+
+--------------------------------------------------------------------------
+📤 4. How to Write Your Response (JSON)
+--------------------------------------------------------------------------
+Return **one** JSON object with the keys **eligibility, justification,
+instruction**.
+
+1. **Eligibility** – one of `"Eligible"`, `"Ineligible"`, `"Re-submit"`.
+2. **Justification** – a **Markdown numbered list** (`"1. …"`)
+   * `Eligible` ➜ “No violations observed …” and list any movable
+     combustibles seen (e.g., “propane BBQ grill on patio”).
+   * `Ineligible` ➜ Each list item = one specific violation.
+   * `Re-submit` ➜ Each list item = one uncertainty that blocks a
+     decision (e.g., “Photo too dark to confirm mulch type at
+     entry-walk”).
+3. **Instruction** – a **Markdown numbered list** mirroring the order of
+   `justification`. Each item tells the homeowner exactly how to fix the
+   violation **or** what new evidence to provide.
+
+--------------------------------------------------------------------------
+💡 5. Eligibility Logic Cheat-Sheet
+--------------------------------------------------------------------------
+• **Eligible** → No violations seen.  
+• **Ineligible** → ≥ 1 confirmed violation.  
+• **Re-submit** → 0 confirmed violations **and** ≥ 1 uncertainty that
+  prevents a confident pass.
+
+--------------------------------------------------------------------------
+📦 6. Output Schema (do not include this comment block in JSON)
+--------------------------------------------------------------------------
+{format_instructions}
+
+--------------------------------------------------------------------------
+"""