brushline 0.1.0__tar.gz

brushline-0.1.0/CITATION.cff

@@ -0,0 +1,10 @@
+cff-version: 1.2.0
+message: "If you use this software, please cite the repository."
+title: "Brushline: vegetation management decision support for linear infrastructure corridors"
+abstract: "A decision support system for optimal vegetation management along linear infrastructure corridors in forested landscapes. It couples shrub and young-tree growth, treatment transitions, strategic, tactical, and operational planning, adaptive remote monitoring, a multi-objective metaheuristic search, and an interactive planning studio for asset owners and contractors."
+authors:
+  - name: "UBC FRESH Lab"
+repository-code: "https://github.com/UBC-FRESH/brushline"
+url: "https://github.com/UBC-FRESH/brushline"
+license: "Apache-2.0"
+version: "0.1.0"

brushline-0.1.0/CONTRIBUTING.md

@@ -0,0 +1,63 @@
+# Contributing to Brushline
+
+Read `AGENTS.md` and `ROADMAP.md` before non-trivial work. The domain rules at the end of
+`AGENTS.md` are part of the design, not style advice.
+
+## Setup
+
+```bash
+python -m venv .venv
+. .venv/bin/activate
+python -m pip install -r requirements-dev.txt
+python -m pip install -e .
+pre-commit install
+```
+
+The pre-commit hooks call `python` from `PATH`, so commit from a shell where the environment is
+active. A commit from a shell without it runs the hooks in the system Python, which lacks the dev
+tools, and the hooks fail.
+
+Optional extras are installed only when a task needs them:
+
+```bash
+python -m pip install -e ".[opt]"   # fresh-solutions metaheuristic engine
+python -m pip install -e ".[web]"   # FastAPI, MapLibre assets, vector tiles
+```
+
+## The green dashboard
+
+Run `python scripts/dashboard.py` before each commit. It must be green. Any change from green is
+investigated and fixed immediately, with no exceptions. The pre-commit hooks run the same checks on
+each commit.
+
+## Workflow
+
+- Work on the branch for the active phase, named `feature/p<n>-<slug>`.
+- Start each commit message with the task ID, for example `P0.1 adapt the contract`.
+- Write every function with full type annotations and a numpy-style docstring, and add unit tests for
+  it in the same change set.
+- Keep `ROADMAP.md`, `CHANGE_LOG.md`, `notes/`, and the matching GitHub issues in step with the work.
+- Open pull requests with `Part of #<parent issue>` in the body. CI must be green. A merge happens only
+  as part of an approved phase close-out.
+
+## Domain guardrails
+
+- A segment is the decision unit. Do not compile at a span or treatment-unit level.
+- A vegetation state carries its uncertainty. Do not reduce a plan to a single point estimate without
+  saying so.
+- A treatment is a transition. Do not model it as a reset to zero vegetation.
+- Monitoring is a decision. Do not hard-code a fixed flight calendar.
+- Every reported incumbent must replay exactly from its evidence record.
+- The studio reads artifacts. Do not put model state in the web service.
+- Keep third-party code and documentation out of the repository. Adapters are interfaces, not copies.
+
+## Control characters and public safety
+
+- Write issue and pull request bodies to files, and post them with `--body-file`. Do not build them from
+  escaped strings.
+- Use LF line endings.
+- Run `python scripts/check_workflow.py` before you push. To check one body file, run
+  `python scripts/check_workflow.py --files path/to/body.md`.
+- Keep private data, credentials, raw transcripts, and machine-specific paths out of the repository.
+- Do not commit real asset, contractor, or personal data. Use synthetic fixtures or sanitized extracts
+  with a recorded provenance note.

brushline-0.1.0/LICENSE

@@ -0,0 +1,201 @@
+                                 Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
+
+   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+   1. Definitions.
+
+      "License" shall mean the terms and conditions for use, reproduction,
+      and distribution as defined by Sections 1 through 9 of this document.
+
+      "Licensor" shall mean the copyright owner or entity authorized by
+      the copyright owner that is granting the License.
+
+      "Legal Entity" shall mean the union of the acting entity and all
+      other entities that control, are controlled by, or are under common
+      control with that entity. For the purposes of this definition,
+      "control" means (i) the power, direct or indirect, to cause the
+      direction or management of such entity, whether by contract or
+      otherwise, or (ii) ownership of fifty percent (50%) or more of the
+      outstanding shares, or (iii) beneficial ownership of such entity.
+
+      "You" (or "Your") shall mean an individual or Legal Entity
+      exercising permissions granted by this License.
+
+      "Source" form shall mean the preferred form for making modifications,
+      including but not limited to software source code, documentation
+      source, and configuration files.
+
+      "Object" form shall mean any form resulting from mechanical
+      transformation or translation of a Source form, including but
+      not limited to compiled object code, generated documentation,
+      and conversions to other media types.
+
+      "Work" shall mean the work of authorship, whether in Source or
+      Object form, made available under the License, as indicated by a
+      copyright notice that is included in or attached to the work
+      (an example is provided in the Appendix below).
+
+      "Derivative Works" shall mean any work, whether in Source or Object
+      form, that is based on (or derived from) the Work and for which the
+      editorial revisions, annotations, elaborations, or other modifications
+      represent, as a whole, an original work of authorship. For the purposes
+      of this License, Derivative Works shall not include works that remain
+      separable from, or merely link (or bind by name) to the interfaces of,
+      the Work and Derivative Works thereof.
+
+      "Contribution" shall mean any work of authorship, including
+      the original version of the Work and any modifications or additions
+      to that Work or Derivative Works thereof, that is intentionally
+      submitted to Licensor for inclusion in the Work by the copyright owner
+      or by an individual or Legal Entity authorized to submit on behalf of
+      the copyright owner. For the purposes of this definition, "submitted"
+      means any form of electronic, verbal, or written communication sent
+      to the Licensor or its representatives, including but not limited to
+      communication on electronic mailing lists, source code control systems,
+      and issue tracking systems that are managed by, or on behalf of, the
+      Licensor for the purpose of discussing and improving the Work, but
+      excluding communication that is conspicuously marked or otherwise
+      designated in writing by the copyright owner as "Not a Contribution."
+
+      "Contributor" shall mean Licensor and any individual or Legal Entity
+      on behalf of whom a Contribution has been received by Licensor and
+      subsequently incorporated within the Work.
+
+   2. Grant of Copyright License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      copyright license to reproduce, prepare Derivative Works of,
+      publicly display, publicly perform, sublicense, and distribute the
+      Work and such Derivative Works in Source or Object form.
+
+   3. Grant of Patent License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      (except as stated in this section) patent license to make, have made,
+      use, offer to sell, sell, import, and otherwise transfer the Work,
+      where such license applies only to those patent claims licensable
+      by such Contributor that are necessarily infringed by their
+      Contribution(s) alone or by combination of their Contribution(s)
+      with the Work to which such Contribution(s) was submitted. If You
+      institute patent litigation against any entity (including a
+      cross-claim or counterclaim in a lawsuit) alleging that the Work
+      or a Contribution incorporated within the Work constitutes direct
+      or contributory patent infringement, then any patent licenses
+      granted to You under this License for that Work shall terminate
+      as of the date such litigation is filed.
+
+   4. Redistribution. You may reproduce and distribute copies of the
+      Work or Derivative Works thereof in any medium, with or without
+      modifications, and in Source or Object form, provided that You
+      meet the following conditions:
+
+      (a) You must give any other recipients of the Work or
+          Derivative Works a copy of this License; and
+
+      (b) You must cause any modified files to carry prominent notices
+          stating that You changed the files; and
+
+      (c) You must retain, in the Source form of any Derivative Works
+          that You distribute, all copyright, patent, trademark, and
+          attribution notices from the Source form of the Work,
+          excluding those notices that do not pertain to any part of
+          the Derivative Works; and
+
+      (d) If the Work includes a "NOTICE" text file as part of its
+          distribution, then any Derivative Works that You distribute must
+          include a readable copy of the attribution notices contained
+          within such NOTICE file, excluding those notices that do not
+          pertain to any part of the Derivative Works, in at least one
+          of the following places: within a NOTICE text file distributed
+          as part of the Derivative Works; within the Source form or
+          documentation, if provided along with the Derivative Works; or,
+          within a display generated by the Derivative Works, if and
+          wherever such third-party notices normally appear. The contents
+          of the NOTICE file are for informational purposes only and
+          do not modify the License. You may add Your own attribution
+          notices within Derivative Works that You distribute, alongside
+          or as an addendum to the NOTICE text from the Work, provided
+          that such additional attribution notices cannot be construed
+          as modifying the License.
+
+      You may add Your own copyright statement to Your modifications and
+      may provide additional or different license terms and conditions
+      for use, reproduction, or distribution of Your modifications, or
+      for any such Derivative Works as a whole, provided Your use,
+      reproduction, and distribution of the Work otherwise complies with
+      the conditions stated in this License.
+
+   5. Submission of Contributions. Unless You explicitly state otherwise,
+      any Contribution intentionally submitted for inclusion in the Work
+      by You to the Licensor shall be under the terms and conditions of
+      this License, without any additional terms or conditions.
+      Notwithstanding the above, nothing herein shall supersede or modify
+      the terms of any separate license agreement you may have executed
+      with Licensor regarding such Contributions.
+
+   6. Trademarks. This License does not grant permission to use the trade
+      names, trademarks, service marks, or product names of the Licensor,
+      except as required for reasonable and customary use in describing the
+      origin of the Work and reproducing the content of the NOTICE file.
+
+   7. Disclaimer of Warranty. Unless required by applicable law or
+      agreed to in writing, Licensor provides the Work (and each
+      Contributor provides its Contributions) on an "AS IS" BASIS,
+      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+      implied, including, without limitation, any warranties or conditions
+      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+      PARTICULAR PURPOSE. You are solely responsible for determining the
+      appropriateness of using or redistributing the Work and assume any
+      risks associated with Your exercise of permissions under this License.
+
+   8. Limitation of Liability. In no event and under no legal theory,
+      whether in tort (including negligence), contract, or otherwise,
+      unless required by applicable law (such as deliberate and grossly
+      negligent acts) or agreed to in writing, shall any Contributor be
+      liable to You for damages, including any direct, indirect, special,
+      incidental, or consequential damages of any character arising as a
+      result of this License or out of the use or inability to use the
+      Work (including but not limited to damages for loss of goodwill,
+      work stoppage, computer failure or malfunction, or any and all
+      other commercial damages or losses), even if such Contributor
+      has been advised of the possibility of such damages.
+
+   9. Accepting Warranty or Additional Liability. While redistributing
+      the Work or Derivative Works thereof, You may choose to offer,
+      and charge a fee for, acceptance of support, warranty, indemnity,
+      or other liability obligations and/or rights consistent with this
+      License. However, in accepting such obligations, You may act only
+      on Your own behalf and on Your sole responsibility, not on behalf
+      of any other Contributor, and only if You agree to indemnify,
+      defend, and hold each Contributor harmless for any liability
+      incurred by, or claims asserted against, such Contributor by reason
+      of your accepting any such warranty or additional liability.
+
+   END OF TERMS AND CONDITIONS
+
+   APPENDIX: How to apply the Apache License to your work.
+
+      To apply the Apache License to your work, attach the following
+      boilerplate notice, with the fields enclosed by brackets "[]"
+      replaced with your own identifying information. (Don't include
+      the brackets!)  The text should be enclosed in the appropriate
+      comment syntax for the file format. We also recommend that a
+      file or class name and description of purpose be included on the
+      same "printed page" as the copyright notice for easier
+      identification within third-party archives.
+
+   Copyright 2026 UBC FRESH Lab
+
+   Licensed under the Apache License, Version 2.0 (the "License");
+   you may not use this file except in compliance with the License.
+   You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing, software
+   distributed under the License is distributed on an "AS IS" BASIS,
+   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+   See the License for the specific language governing permissions and
+   limitations under the License.

brushline-0.1.0/MANIFEST.in

@@ -0,0 +1,5 @@
+include RELEASE_NOTES.md
+include README.md
+include LICENSE
+include CONTRIBUTING.md
+include CITATION.cff

brushline-0.1.0/PKG-INFO

@@ -0,0 +1,162 @@
+Metadata-Version: 2.4
+Name: brushline
+Version: 0.1.0
+Summary: Decision support for vegetation management along linear infrastructure corridors
+Author-email: UBC FRESH Lab <noreply@example.org>
+License-Expression: Apache-2.0
+Project-URL: Homepage, https://github.com/UBC-FRESH/brushline
+Project-URL: Documentation, https://ubc-fresh.github.io/brushline/
+Project-URL: Repository, https://github.com/UBC-FRESH/brushline
+Project-URL: Issues, https://github.com/UBC-FRESH/brushline/issues
+Keywords: forestry,vegetation management,rights-of-way,linear infrastructure,optimization,metaheuristics,remote sensing,decision support
+Classifier: Development Status :: 2 - Pre-Alpha
+Classifier: Intended Audience :: Science/Research
+Classifier: Operating System :: POSIX :: Linux
+Classifier: Programming Language :: Python :: 3
+Classifier: Programming Language :: Python :: 3.11
+Classifier: Programming Language :: Python :: 3.12
+Classifier: Topic :: Scientific/Engineering
+Classifier: Typing :: Typed
+Requires-Python: >=3.11
+Description-Content-Type: text/markdown
+License-File: LICENSE
+Requires-Dist: typer>=0.12
+Requires-Dist: rich>=13.7
+Requires-Dist: pydantic>=2.7
+Requires-Dist: pandas>=2.2
+Requires-Dist: numpy>=1.26
+Requires-Dist: pyarrow>=15
+Requires-Dist: pyyaml>=6
+Requires-Dist: packaging>=24
+Provides-Extra: geo
+Requires-Dist: geopandas>=0.14; extra == "geo"
+Requires-Dist: pyogrio>=0.9; extra == "geo"
+Requires-Dist: shapely>=2.0; extra == "geo"
+Provides-Extra: opt
+Requires-Dist: fresh-solutions<0.10,>=0.9.3; extra == "opt"
+Provides-Extra: femic
+Requires-Dist: femic==0.2.0a1; extra == "femic"
+Requires-Dist: freshforge==0.1.0a5; extra == "femic"
+Provides-Extra: freshforge
+Requires-Dist: freshforge==0.1.0a5; extra == "freshforge"
+Provides-Extra: web
+Requires-Dist: fastapi>=0.110; extra == "web"
+Requires-Dist: uvicorn>=0.29; extra == "web"
+Requires-Dist: mapbox-vector-tile>=2.1; extra == "web"
+Requires-Dist: mercantile>=1.2; extra == "web"
+Requires-Dist: shapely>=2.0; extra == "web"
+Requires-Dist: pyproj>=3.6; extra == "web"
+Dynamic: license-file
+
+# Brushline
+
+Brushline is decision support for vegetation management along linear infrastructure corridors in
+forested landscapes: powerlines, pipelines, roads, railways, and the rights-of-way that keep them
+accessible and safe.
+
+The system couples a shrub and young-tree growth model, treatment transitions, strategic, tactical, and
+operational planning, adaptive remote monitoring, and a multi-objective metaheuristic search. One
+versioned plan artifact serves both the asset owner who hires the work and the contractor who bids on
+it, so a budget, a schedule, and a bid can be inspected against the same evidence.
+
+## The problem
+
+A utility or pipeline operator may manage thousands of kilometres of corridor through productive
+forest. Vegetation that is left too long reduces clearance, blocks access, raises fire risk, and
+threatens reliability. Treat it too often and the budget is wasted. The usual answer is a fixed cycle
+and a spreadsheet, with each contractor bidding from a different set of assumptions.
+
+Two things make the problem hard:
+
+- Open growth and yield models for shrubs and young trees are scarce. Brushline must carry its own
+  calibrated state-transition model, and must state its uncertainty.
+- The joint choice of where and when to treat, and where and when to monitor, is an NP-hard
+  combinatorial problem with budget, capacity, access, spatial, temporal, and service constraints.
+  Brushline therefore commits to a metaheuristic search framework and a Pareto archive of trade-offs,
+  not to a claim of optimality.
+
+## What the system will do
+
+- **Build a corridor model.** Segments are the decision unit; spans and treatment units are runtime
+  aggregates. Each segment carries site, vegetation, treatment, access, and observation history.
+- **Grow and treat vegetation.** A state is a distribution over interpretable classes, with
+  continuous summaries. Treatments are transitions with method-specific efficacy, selectivity, and
+  regrowth.
+- **Plan at three scales.** Strategic plans set budget, service levels, risk appetite, and monitoring
+  policy over 10 to 30 years. Tactical plans set multi-year treatment programs, contractor capacity,
+  and access. Operational plans set work-ready treatment units, methods, and schedules.
+- **Decide when to monitor.** Flight frequency, route, sensor, and sampling intensity are decision
+  variables priced by their expected value of information, and observations recalibrate the growth
+  model.
+- **Search the trade-offs.** A `fresh-solutions` problem adapter supplies exact evaluation, moves, and
+  undo; the engine supplies local search, population search, checkpoints, seeds, telemetry, and exact
+  replay. A Pareto archive keeps the cost, risk, service, and uncertainty trade-offs.
+- **Compare owner and contractor views.** A plan carries a line-item cost build-up, assumptions,
+  quantities, rates, and provenance. A bid is an annotated plan, not a separate spreadsheet.
+- **Explore it in a planning studio.** One optional FastAPI service and one static browser shell read
+  the run artifacts. MapLibre carries the 2D corridor map, Three.js carries the 3D operations scene,
+  and checked skins cover owner-strategic, tactical, operations, contractor, monitoring, and reviewer
+  roles. The studio animates deployment and explores the Pareto front without owning model state.
+
+## Status
+
+Phase 0 (bootstrap and scope) and Phase 1 (contracts and prototype) are complete and merged. Phase 2
+(FEMIC-extended instance builder) is active: the repository is pinning the FEMIC provider surface and
+building the map-to-instance workflow on top of it. It does not yet have a usable vegetation model or
+planner. `ROADMAP.md` is the plan of record, and the GitHub issues carry the live status.
+
+Brushline is a working name. It is easy to rename before the first public release.
+
+## Quick start
+
+```bash
+python -m venv .venv
+. .venv/bin/activate
+python -m pip install -r requirements-dev.txt
+python -m pip install -e .
+brushline --help
+python scripts/dashboard.py
+```
+
+The dashboard runs lint, format, strict types, tests with a coverage gate, the workflow validator, the
+docs build, and the docstring audit. Every commit leaves it green.
+
+## How this project works
+
+This project follows the UBC-FRESH dev workflow. Work is planned as phases, tasks, and subtasks in
+`ROADMAP.md`, mirrored in GitHub issues, and recorded in `CHANGE_LOG.md`. The agent operating contract
+is in `AGENTS.md`. Read `AGENTS.md`, then `ROADMAP.md`, before you change anything.
+
+## Repository map
+
+| Path | Purpose |
+| --- | --- |
+| `AGENTS.md` | Operating contract for coding agents |
+| `ROADMAP.md` | Plan of record and issue tracker map |
+| `CHANGE_LOG.md` | Dated narrative of changes |
+| `brushline/` | The Python package and command line |
+| `docs/` | Documentation site, including the design index |
+| `notes/design/` | Scope, architecture, optimization, and UI design records |
+| `notes/adr/` | Architecture decisions |
+| `notes/reports/` | Phase close-out reports |
+| `scripts/check_workflow.py` | Workflow validator |
+| `tests/` | pytest suite, including the planning-surface self-check |
+
+## Relationship to the other FRESH tools
+
+Brushline is a sibling of WS4, FHOPS, the FRESH urban-forest lab, and Fresh Solutions. It borrows
+patterns, not internals:
+
+- **WS4** supplies the pattern for a compiled, inspectable dataset, spatial decisions inside the model,
+  artifact-based runs, and the web shell.
+- **FHOPS** supplies the pattern for tactical and operational planning, machine and crew productivity,
+  and 3D operations visualization.
+- **Fresh Solutions** supplies the metaheuristic engine and the exact replay contract.
+- **The FRESH urban-forest lab** supplies the pattern for a 2D/3D browser studio with vendored,
+  offline-capable map and scene libraries.
+
+The adapters are versioned and optional. Brushline stays installable without the other tools.
+
+## License
+
+Apache-2.0. See [`LICENSE`](LICENSE) and [`CITATION.cff`](CITATION.cff).

brushline-0.1.0/README.md

@@ -0,0 +1,112 @@
+# Brushline
+
+Brushline is decision support for vegetation management along linear infrastructure corridors in
+forested landscapes: powerlines, pipelines, roads, railways, and the rights-of-way that keep them
+accessible and safe.
+
+The system couples a shrub and young-tree growth model, treatment transitions, strategic, tactical, and
+operational planning, adaptive remote monitoring, and a multi-objective metaheuristic search. One
+versioned plan artifact serves both the asset owner who hires the work and the contractor who bids on
+it, so a budget, a schedule, and a bid can be inspected against the same evidence.
+
+## The problem
+
+A utility or pipeline operator may manage thousands of kilometres of corridor through productive
+forest. Vegetation that is left too long reduces clearance, blocks access, raises fire risk, and
+threatens reliability. Treat it too often and the budget is wasted. The usual answer is a fixed cycle
+and a spreadsheet, with each contractor bidding from a different set of assumptions.
+
+Two things make the problem hard:
+
+- Open growth and yield models for shrubs and young trees are scarce. Brushline must carry its own
+  calibrated state-transition model, and must state its uncertainty.
+- The joint choice of where and when to treat, and where and when to monitor, is an NP-hard
+  combinatorial problem with budget, capacity, access, spatial, temporal, and service constraints.
+  Brushline therefore commits to a metaheuristic search framework and a Pareto archive of trade-offs,
+  not to a claim of optimality.
+
+## What the system will do
+
+- **Build a corridor model.** Segments are the decision unit; spans and treatment units are runtime
+  aggregates. Each segment carries site, vegetation, treatment, access, and observation history.
+- **Grow and treat vegetation.** A state is a distribution over interpretable classes, with
+  continuous summaries. Treatments are transitions with method-specific efficacy, selectivity, and
+  regrowth.
+- **Plan at three scales.** Strategic plans set budget, service levels, risk appetite, and monitoring
+  policy over 10 to 30 years. Tactical plans set multi-year treatment programs, contractor capacity,
+  and access. Operational plans set work-ready treatment units, methods, and schedules.
+- **Decide when to monitor.** Flight frequency, route, sensor, and sampling intensity are decision
+  variables priced by their expected value of information, and observations recalibrate the growth
+  model.
+- **Search the trade-offs.** A `fresh-solutions` problem adapter supplies exact evaluation, moves, and
+  undo; the engine supplies local search, population search, checkpoints, seeds, telemetry, and exact
+  replay. A Pareto archive keeps the cost, risk, service, and uncertainty trade-offs.
+- **Compare owner and contractor views.** A plan carries a line-item cost build-up, assumptions,
+  quantities, rates, and provenance. A bid is an annotated plan, not a separate spreadsheet.
+- **Explore it in a planning studio.** One optional FastAPI service and one static browser shell read
+  the run artifacts. MapLibre carries the 2D corridor map, Three.js carries the 3D operations scene,
+  and checked skins cover owner-strategic, tactical, operations, contractor, monitoring, and reviewer
+  roles. The studio animates deployment and explores the Pareto front without owning model state.
+
+## Status
+
+Phase 0 (bootstrap and scope) and Phase 1 (contracts and prototype) are complete and merged. Phase 2
+(FEMIC-extended instance builder) is active: the repository is pinning the FEMIC provider surface and
+building the map-to-instance workflow on top of it. It does not yet have a usable vegetation model or
+planner. `ROADMAP.md` is the plan of record, and the GitHub issues carry the live status.
+
+Brushline is a working name. It is easy to rename before the first public release.
+
+## Quick start
+
+```bash
+python -m venv .venv
+. .venv/bin/activate
+python -m pip install -r requirements-dev.txt
+python -m pip install -e .
+brushline --help
+python scripts/dashboard.py
+```
+
+The dashboard runs lint, format, strict types, tests with a coverage gate, the workflow validator, the
+docs build, and the docstring audit. Every commit leaves it green.
+
+## How this project works
+
+This project follows the UBC-FRESH dev workflow. Work is planned as phases, tasks, and subtasks in
+`ROADMAP.md`, mirrored in GitHub issues, and recorded in `CHANGE_LOG.md`. The agent operating contract
+is in `AGENTS.md`. Read `AGENTS.md`, then `ROADMAP.md`, before you change anything.
+
+## Repository map
+
+| Path | Purpose |
+| --- | --- |
+| `AGENTS.md` | Operating contract for coding agents |
+| `ROADMAP.md` | Plan of record and issue tracker map |
+| `CHANGE_LOG.md` | Dated narrative of changes |
+| `brushline/` | The Python package and command line |
+| `docs/` | Documentation site, including the design index |
+| `notes/design/` | Scope, architecture, optimization, and UI design records |
+| `notes/adr/` | Architecture decisions |
+| `notes/reports/` | Phase close-out reports |
+| `scripts/check_workflow.py` | Workflow validator |
+| `tests/` | pytest suite, including the planning-surface self-check |
+
+## Relationship to the other FRESH tools
+
+Brushline is a sibling of WS4, FHOPS, the FRESH urban-forest lab, and Fresh Solutions. It borrows
+patterns, not internals:
+
+- **WS4** supplies the pattern for a compiled, inspectable dataset, spatial decisions inside the model,
+  artifact-based runs, and the web shell.
+- **FHOPS** supplies the pattern for tactical and operational planning, machine and crew productivity,
+  and 3D operations visualization.
+- **Fresh Solutions** supplies the metaheuristic engine and the exact replay contract.
+- **The FRESH urban-forest lab** supplies the pattern for a 2D/3D browser studio with vendored,
+  offline-capable map and scene libraries.
+
+The adapters are versioned and optional. Brushline stays installable without the other tools.
+
+## License
+
+Apache-2.0. See [`LICENSE`](LICENSE) and [`CITATION.cff`](CITATION.cff).

brushline-0.1.0/RELEASE_NOTES.md

@@ -0,0 +1,65 @@
+# Brushline 0.1.0 release notes
+
+Status: release candidate prepared; tag and GitHub release require maintainer approval.
+
+## What this is
+
+Brushline is an open decision-support prototype for vegetation management along linear infrastructure
+corridors. It provides a shared plan artifact, a strategic/tactical/operational planning stack, a
+Pareto search adapter, a monitoring and replanning loop, a public demo portal, and a local planning
+studio.
+
+## Changes
+
+- P0-P2: identity, contracts, synthetic fixture, FEMIC-extended instance builder, catalogue, fetch
+  planning, capabilities, and model-builder prototype.
+- P3: LiDAR bundle, terrain, canopy, state initialization, coverage, and sibling benchmark.
+- P4: low-vegetation state space, growth, treatment transitions, calibration, hazards, held-out
+  validation, and model card.
+- P5: formulation, exact evaluator, operators, Fresh Solutions adapter, Pareto archive, tiny-instance
+  validation, budget evidence, and studio telemetry.
+- P6: strategic dynamic program, portfolio, monitoring policy, BAU, reports, scenario archive, and
+  synthetic validation.
+- P7: tactical program, contractor resources, access, work orders, FHOPS dry-run boundary, timeline,
+  and validation.
+- P8: observation, mission simulation, value of information, recalibration, replan trigger, and
+  adaptive-versus-calendar validation.
+- P9: shared plan cost build-up, owner/contractor views, bid comparison, approval, and exchange
+  validation.
+- P10: artifact-only planning studio with map, 3D context, forester POV walkthrough, pre/post
+  toggle, skins, Pareto, and timeline.
+- P11: public synthetic demo portfolio, static portal, pilot brief, and validation.
+- P12: 16-criterion verification, BAU case, monitoring value, exchange, performance limit, replay, and
+  release recommendation.
+
+## Known gaps
+
+- No field calibration of shrub/young-tree growth or treatment response.
+- No mature-forest EFI transfer validation.
+- No live FEMIC/FreshForge build, live LiDAR campaign, live FHOPS run, or live road feed.
+- The 10,000-segment/30-year/1,000-evaluation/8-core target is not demonstrated. P12 measures a small
+  case and reports the limit.
+- The public demo is synthetic and static; the lab preview is not a production service.
+- No authentication, production dispatch, safety certification, or engineering clearance claim.
+- The 3D scene and POV walkthrough are context views; they are not survey-grade and invent no
+  positions.
+- Monitoring value of information and budget/performance evidence use approximations and synthetic
+  assumptions.
+
+## Model and use boundaries
+
+Use Brushline to structure evidence and compare transparent scenarios. Do not use it as the sole basis
+for field treatment, contract award, safety clearance, or regulatory approval. Read the model card,
+verification report, caveats, and known-gaps list before citing a result.
+
+## Publishing
+
+- PyPI trusted publisher: project `brushline`, repository `UBC-FRESH/brushline`, workflow `release.yml`, environment `pypi`.
+- TestPyPI trusted publisher: same project/repository/workflow, environment `testpypi`.
+- A published GitHub release publishes the wheel and sdist to PyPI. A manual `Release` run publishes to TestPyPI.
+
+## Verification
+
+- P12 verification report: `notes/reports/p12-verification.md`
+- P12 close-out: `notes/reports/p12-closeout.md`
+- License: Apache-2.0

brushline-0.1.0/brushline/__init__.py

@@ -0,0 +1,7 @@
+"""Brushline: decision support for vegetation management along linear corridors."""
+
+from __future__ import annotations
+
+__version__ = "0.1.0"
+
+__all__ = ["__version__"]

brushline-0.1.0/brushline/build/__init__.py

@@ -0,0 +1,7 @@
+"""Build and compile paths for Brushline."""
+
+from __future__ import annotations
+
+from brushline.build.compiler import CompiledDataset, compile_fixture
+
+__all__ = ["CompiledDataset", "compile_fixture"]