Skip to content

Development Branch Charter

This document defines how the ORS Resource Map repository is organized after the June 2026 project reset.

Branch roles

main — stable production / demo

  • Hosts the public ORS Resource Map MkDocs site.
  • Pulled hourly by a Raspberry Pi for the live demo.
  • Must remain functional at all times.
  • Do not modify directly for experimental work.
  • Merge only after extensive testing on development.

development — active work

  • All future Resource Map improvements happen here.
  • Based on main, not on the v2 prototype experiment.
  • The Resource Map is the product; supporting systems must serve it.
  • Do not merge untested work to main.

archive/resource-map-v2-20260613 — preserved lessons

  • Preserves architecture docs, provenance work, review app, tests, Neo4j lessons, and the full v2 experiment.
  • Tagged archive-v2-lessons-20260613 for easy reference.
  • No active development; treat as read-only reference.
  • The resource-map-v2 branch is retained and not deleted.

Product direction

The Resource Map is the product.

Neo4j, ingestion pipelines, review tooling, provenance layers, and query interfaces are supporting systems. They derive from the map; they are not authoritative sources of truth.

MkDocs remains the current public site. Replacing MkDocs is out of scope unless explicitly decided later.

What we are not building next

  • More graph infrastructure for its own sake
  • Regex-based faculty profile scraping
  • GraphRAG as a primary workflow
  • Autonomous YAML updates without human review

What we are building next

Restore the workflow that produced the original successful Resource Map:

rich source material
  → AI-assisted synthesis
  → reviewable proposed changes
  → human approval
  → updated Resource Map
  → graph / export follows downstream

Future intake should use AI-assisted synthesis from rich source material, not regex scraping.

Review and provenance

  • LLMs may propose changes; humans approve before anything reaches main.
  • Evidence and provenance must be preserved from source through public display and any graph export.
  • Provenance is a first-class concern, but it supports the map rather than replacing it.

Excluded from development (unless explicitly requested)

The following v2 experiment components stay on the archive branch only:

  • Flask review app
  • Regex faculty scraper
  • v2 platform scaffold

Lessons from those experiments remain available on archive/resource-map-v2-20260613.

Merge policy

No work merges to main until it is tested on development and reviewed for impact on the live demo site.