diff --git a/profile/README.md b/profile/README.md index e6d1103..ebbabe8 100644 --- a/profile/README.md +++ b/profile/README.md @@ -1,44 +1,21 @@ # TerraFirma Robotics -TerraFirma Robotics builds earth science robotics software for sensing, simulation, geospatial context, and autonomy-support workflows. +**Robotics software for the physical world.** -We are developing the digital infrastructure behind field robotics systems: public web properties, geospatial data pipelines, synthetic asset workflows, simulation support, and internal engineering tools. +TerraFirma Robotics builds the software that lets field robotics systems sense, understand, and act in real environments — uniting perception, geospatial intelligence, simulation, and autonomy support into one engineering stack. -## What we work on +## What we do -- **Earth science robotics**: software systems that connect sensing, mapping, and decision support. -- **Geospatial context pipelines**: environmental data workflows for terrain, land cover, hydrology, fire history, soils, and mission context. -- **Simulation and synthetic data**: 3D asset and dataset tooling for perception workflows. -- **Public web and company infrastructure**: websites, dashboards, automation, and internal developer tooling. +- **Earth-science autonomy** — software that turns sensing and mapping into field-ready decisions. +- **Geospatial intelligence** — environmental and terrain data pipelines that give robots mission-grade context. +- **Simulation & synthetic data** — high-fidelity 3D and dataset tooling that trains and validates perception before deployment. +- **Engineering platform** — the web properties, dashboards, and automation that move our systems from lab to field. -## Public links +## Connect - Website: https://www.terrafirma-robotics.com/ - Contact: contact@terrafirma-robotics.com -## For TerraFirma Robotics team members - -Most repositories in this organization are private. If you are joining a project and do not see the repo you need: - -1. Confirm you are signed into the correct GitHub account. -2. Ask Jake or the repo owner for organization access. -3. Use the repo README first. It should explain purpose, setup, run commands, and deployment notes. -4. Keep secrets out of Git. Use approved environment variables, GitHub secrets, Databricks secrets, or the company vault. -5. Do not change production deployment wiring unless Jake has explicitly approved it. - -## Repository standards - -- Private by default. -- Clear README in every repo. -- No secrets, API keys, tokens, `.env` files, generated datasets, model outputs, or large runtime artifacts in Git. -- Small reproducible examples are welcome when they help future team members onboard. -- Public claims should stay grounded in approved TerraFirma Robotics positioning and current technical status. - -## Current engineering areas - -- Public website source recovery and maintenance -- Procedural 3D asset workflows -- TRELLIS.2 image-to-3D batch generation -- Databricks geospatial context packaging -- Internal tools and automation +--- +Most of our work lives in private repositories. Team members: request access from your project lead.