Geodesic

Geodesic is the product- and project-management substrate. It carries the typed long-form artifacts (ADRs, SPECs, PRDs, runbooks), the work items that materialize them (issues + cycles + projects + initiatives), and the proposal review queue that feeds both.

Designed to be agent-friendly first: every artifact carries provenance edges back to the chat turns, atoms, or external sources it was derived from, so an agent (or human) auditing a decision can trace it all the way back to “why does this exist?”.

Dashboard surfaces

• /geodesic/inbox — proposal review queue (approve / reject / needs revision)
• /geodesic/runs — processor activity (last runs + cursors)
• /geodesic/library — searchable ADR / SPEC / PRD library projected from the repo by the geodesic.docs processor
• /geodesic/board — Kanban over geo_issues; harness-sourced rows (Claude TaskCreate / TaskUpdate captured by scribe) carry a HARNESS chip
• /geodesic/deps — typed dependency edges (blocks, related_to, duplicates, supersedes)

How it fills

Source	Processor	Lands in
Claude TaskCreate / Update	geodesic.harness-tasks	geo_issues, geo_issue_deps
docs/{adr,specs,prd}/*.md	geodesic.docs	geo_documents
Atom clusters (LLM-mined)	feature-requests:*	geo_proposals
Approved proposal → issue	proposal materialization	geo_issues + geo_proposal_resolutions
Repo / scribe sources	source-of-record processors	geo_provenance (the killer feature)

See the Scribe processors page for the full catalogue of what feeds geodesic.

Schema

Migration 025 (geodesic v1) introduced 13 tables; migrations 031 + 032 filled the gaps for ADR-058. Notable tables:

• geo_teams / geo_projects / geo_initiatives / geo_cycles — Linear-style org structure
• geo_issues (+ parent_issue_id hierarchy + external_id for harness mapping + metadata jsonb) — the work unit
• geo_issue_deps — typed graph edges between issues (ADR-058 §1)
• geo_documents — typed long-form artifacts (kind ∈ adr/spec/prd/ runbook/competitive-analysis/market-opportunity/product-opportunity)
• geo_proposals + geo_proposal_resolutions — review queue + materialization edges
• geo_provenance — every derived artifact links back to its scribe source(s)

Related

• ADR-056 — spec-driven substrate (executable specifications)
• ADR-057 — unified property graph (proposed; projects geodesic + scribe + code-symbol nodes into one queryable graph)
• ADR-058 — PM substrate (the gap-fill work that lit up the library / board / deps views)