Project Roadmaps
PROJ-001 - LangGraph Console UI
Build the full Copilot HQ control-plane console UI on forseti.life — telemetry, agent monitoring, session management, release controls, and eval scorecards wired to live orchestrator tick data.
Type: delivery project • Product: forseti.life • PM: pm-forseti • Lead: pm-forseti • Started: 2026-04-05 • Last release: `20260412-forseti-release-h` (targeted; not yet activated — pending BA confirmation) • Progress: SLA breach
Roadmap
- Current state: All foundation slices are shipped: telemetry foundation, console stubs (7 routes), context enrichment, Agent Tracker Core, Console Build/Test sections, and Release Control Panel (read-only). Active release `20260412-forseti-release-h` carries the next slice: Run + Session panel wiring (`features/forseti-langgraph-console-run-session/`, Status: ready). Artifact naming corrected (renamed to standard `01-acceptance-criteria.md`, `02-implementation-notes.md`); `03-test-plan.md` created by PM 2026-04-13. BA dispatched to confirm 4 implementation details before dev activation.
- Last scoped release: `20260412-forseti-release-h` (targeted; not yet activated — pending BA confirmation)
- Next step: ba-forseti to confirm AC-3 glob pattern, AC-2 truncation placement, AC-7 warning banner condition, and AC-5 Session Health placement. PM activates after BA confirmation.
- Queue status: ba-forseti grooming dispatch: `sessions/ba-forseti/inbox/20260413-groom-forseti-langgraph-console-run-session/` (ROI 40)
PROJ-002 - QA Suite Completeness
Build repeatable, executable QA coverage for shipped Forseti features and clean up stale suite shells so release verification is durable, automatable, and auditable.
Type: delivery project • Product: forseti.life • PM: pm-forseti • Lead: pm-forseti / qa-forseti • Started: 2026-04-09 • Last release: `20260412-forseti-release-h` • Progress: SLA breach
Roadmap
- Current state: Phase 1 (triage) complete. Phase 2 (suite fill) dispatched to qa-forseti inbox `20260413-004107-suite-activate-*` items (4 release-h suites activated) and Phase 2 fill dispatch confirmed as `20260412-proj002-phase2-suite-fill` (check qa-forseti inbox — if not present, re-dispatch is needed). `suite.json` has 252 suites with 2 populated. Core problem (no executable regression tests) persists; Phase 2 fill work is the active priority.
- Last scoped release: `20260412-forseti-release-h`
- Next step: qa-forseti to execute Phase 2 fill for the 52 priority suites from the triage report (`sessions/qa-forseti/artifacts/proj002-suite-triage/triage-report.md`). Target ≥2 test_cases per fill suite.
- Queue status: Phase 2 dispatch: `sessions/qa-forseti/inbox/20260412-proj002-phase2-suite-fill/` (verify exists)
PROJ-003 - DungeonCrawler Roadmap Completion
Systematically implement all `pending` requirements in `dc_requirements` table until every requirement is either `implemented` or has a `feature_id` pointing to an active pipeline feature.
Type: delivery project • Product: dungeoncrawler • PM: pm-dungeoncrawler • Lead: pm-dungeoncrawler • Started: 2026-03-01 • Last release: `20260412-dungeoncrawler-release-p` • Progress: SLA breach
Roadmap
- Current state: The public roadmap still derives requirement state from the live pipeline, and the sync path remains intact. Coordinated release `20260412-dungeoncrawler-release-p` has now been signoff-cleared and cycled forward; active runtime release is `20260412-dungeoncrawler-release-q` with `20260412-dungeoncrawler-release-r` queued next. The post-B2 follow-on path is no longer just groomed - `dc-b3-bestiary3` is actively scoped into `release-q`, with QA suite activation complete and the first safe code slice landed against the repo's internal structured B3 inventory.
- Last scoped release: `20260412-dungeoncrawler-release-p`
- Next step: execute the remaining `dc-b3-bestiary3` schema-ingestion work in `20260412-dungeoncrawler-release-q`, while continuing PM grooming for `20260412-dungeoncrawler-release-r`.
- Queue status: the coordinated push is complete and the cycle advanced. The current operational gap is no longer release signoff or backlog recovery; it is finishing the richer shared-schema implementation for `dc-b3-bestiary3` in `release-q` while PM keeps `release-r` groomed ahead of it.
PROJ-004 - Job Hunter
Forseti's job-seeking platform covering resume intake, discovery, application prep, submission support, and tracking.
Type: product line • Product: forseti.life • PM: pm-forseti • Lead: pm-forseti • Started: 2026-04-12 • Last release: `20260412-forseti-release-h` • Progress: SLA breach
Roadmap
- Current state: Active buildout. Release-h carries 4 features in_progress: `forseti-jobhunter-interview-outcome-tracker` (high), `forseti-jobhunter-offer-tracker` (high), `forseti-jobhunter-application-analytics` (medium), `forseti-jobhunter-follow-up-reminders` (medium). Seven additional groomed features re-baselined to `ready` for future releases: `contact-tracker`, `company-interest-tracker`, `company-research-tracker`, `contact-referral-tracker`, `job-board-preferences`, `resume-version-labeling`, `resume-version-tracker`.
- Last scoped release: `20260412-forseti-release-h`
- Next step: Await dev-forseti completion + Gate 2 QA on 4 active release-h features. After coordinated push, activate next slice from 7 queued ready features by priority.
- Queue status: 4 features in_progress for `20260412-forseti-release-h`. Dev + QA inbox items dispatched 2026-04-13.
PROJ-005 - AI Conversation
Persistent assistant experience, conversation memory, model integration, and shared AI capability across Forseti products.
Type: product line • Product: forseti.life • PM: pm-forseti • Lead: pm-forseti • Started: 2026-04-12 • Last release: `20260412-forseti-release-h` (targeted; not yet activated — pending BA impl notes + release slot) • Progress: SLA breach
Roadmap
- Current state: All foundation features shipped. Next slice fully groomed: **Local LLM / Provider Selection** (`forseti-ai-local-llm-provider-selection`, Status: ready, Release: 20260412-forseti-release-h). AC, impl notes stub, and test plan created 2026-04-13. BA dispatched to complete impl notes (5 outstanding items). Feature is activation-ready once BA elaboration is complete and release-h in_progress count allows.
- Last scoped release: `20260412-forseti-release-h` (targeted; not yet activated — pending BA impl notes + release slot)
- Next step: ba-forseti to complete `02-implementation-notes.md` (confirm AIApiService constructor, streaming approach, config keys, user field type, OpenAI model options). PM activates in release-h or next cycle based on slot availability.
- Queue status: ba-forseti grooming dispatch: `sessions/ba-forseti/inbox/20260413-groom-forseti-ai-local-llm-provider-selection/` (ROI 30)
PROJ-006 - Community Safety
Public safety content, maps, alerts, community participation, and member-support tooling.
Type: product line • Product: forseti.life • PM: pm-forseti • Lead: pm-forseti • Started: 2026-04-12 • Last release: `20260412-forseti-release-h` (targeted; not yet activated — pending BA impl notes + release slot) • Progress: SLA breach
Roadmap
- Current state: Foundation modules `amisafe` and `safety_calculator` are production-complete. Next slice fully groomed: **Community Incident Report** (`forseti-community-incident-report`, Status: ready, Release: 20260412-forseti-release-h targeted). AC, impl notes stub, and test plan created 2026-04-13. BA dispatched to complete impl notes (6 outstanding items including AmISafe JS integration approach). Feature is not yet activated in release-h (4 features already in_progress; will activate in next cycle unless slot opens).
- Last scoped release: `20260412-forseti-release-h` (targeted; not yet activated — pending BA impl notes + release slot)
- Next step: ba-forseti to complete `02-implementation-notes.md` (AmISafe JS integration, taxonomy terms, form class approach). PM activates in next available release cycle after BA grooming is complete.
- Queue status: ba-forseti grooming dispatch: `sessions/ba-forseti/inbox/20260413-groom-forseti-community-incident-report/` (ROI 25)
PROJ-007 - Dungeoncrawler Product Track
The dedicated Dungeoncrawler product line, separate site, and its long-lived PF2E implementation program. Long-term mission: implement all PF2E rulebook requirements currently tracked in `dc_requirements` MySQL table (2033 implemented, 674 in_progress, 698 pending as of 2026-04-13).
Type: product line • Product: dungeoncrawler • PM: pm-dungeoncrawler • Lead: pm-dungeoncrawler • Started: 2026-04-13 • Last release: `20260412-dungeoncrawler-release-p` • Progress: SLA breach
Roadmap
- Current state: Dungeoncrawler release `20260412-dungeoncrawler-release-p` was pushed through the coordinated signoff path, the lead-PM release bundle was materialized, and the cycle advanced to active release `20260412-dungeoncrawler-release-q` with next release `20260412-dungeoncrawler-release-r`. The just-shipped release closed out `dc-b2-bestiary2`, `dc-gng-guns-gears`, and `dc-som-secrets-of-magic`. Post-B2 backlog recovery has already begun: `dc-b3-bestiary3` is groomed, live in the QA suite for `release-q`, and now has a safe execution path using the repo's internal structured creature inventory plus normalization across read, JSON-write, and template-seeding paths, with seeded/internal rows now carrying or hydrating the standard core catalog fields.
- Last scoped release: `20260412-dungeoncrawler-release-p`
- Next step: `dev-dungeoncrawler` extends the internal structured Bestiary 3 inventory into the richer shared creature schema for `release-q`, while `pm-dungeoncrawler` keeps `release-r` grooming ahead of the live cycle.
- Queue status: active release `20260412-dungeoncrawler-release-q` still carries `dc-b3-bestiary3` in progress. QA testgen and live suite activation are complete; Dev now has a safe-source path using internal structured inventory data plus landed normalization across read, write, and template-import flows for legacy `source_book`-backed rows, with seeded/internal rows now carrying or hydrating the core catalog fields; next release `20260412-dungeoncrawler-release-r` already has PM grooming coverage queued.
PROJ-008 - Forseti Accounting Pipeline
Establish Forseti's repeatable accounting operating model: daily income/expense capture, cash reconciliation, daily flash P&L, monthly close, renewal tracking, anomaly logging, and the smallest finance system stack needed to keep reporting trustworthy as volume grows.
Type: delivery project • Product: forseti.life • PM: pm-forseti • Lead: accountant-forseti • Started: 2026-04-13 • Last release: `20260412-forseti-release-h` (operations/process foundation defined; no product feature activation yet) • Progress: SLA breach
Roadmap
- Current state: Foundation documentation is in place and the active April 2026 finance workspace is open under `dashboards/finance/`, including `daily-p-and-l-2026-04.md`, `income-ledger-2026-04.md`, `expense-ledger-2026-04.md`, and `vendor-reconciliation-2026-04.md`. Expense sources are now confirmed as AWS Billing and GitHub billing, and live pull attempts have been made. GitHub org billing usage for `Forseti-Life` is now reachable and returned no April usage items. The project remains blocked because AWS denied `ce:GetCostAndUsage`, GitHub fixed-charge completeness is still unconfirmed, and income/cash sources are still not confirmed. A new backlog feature, `forseti-financial-health-home`, now captures the Drupal-side institutional finance home as the next productization layer for this project.
- Last scoped release: `20260412-forseti-release-h` (operations/process foundation defined; no product feature activation yet)
- Next step: CEO should unblock AWS Cost Explorer access and confirm both the GitHub fixed-charge path and the income/cash sources so `accountant-forseti` can replace the April placeholders with source-backed entries and begin daily reconciliation. In parallel, `pm-forseti` can pick up `features/forseti-financial-health-home/feature.md` from the backlog to scope the internal Drupal financial-health home.
- Queue status: Process docs and active April finance artifacts exist; AWS and GitHub expense sources are selected; GitHub usage report is live and empty for April; current blockers are AWS Cost Explorer permission, GitHub fixed-charge completeness, and missing income/cash source confirmation. Backlog now includes `forseti-financial-health-home` as the Drupal financial-health surface for PROJ-008.
PROJ-009 - Forseti Open Source Initiative
Publish the Forseti autonomous Drupal development platform as open source under the `Forseti-Life` GitHub organization, including the platform overview repo, selected reusable component repos, contributor docs, and the release/security process needed to publish safely.
Type: delivery project • Product: org-wide • PM: pm-open-source • Lead: pm-open-source • Started: 2026-04-13 • Last release: none yet (portfolio initiative; not release-scoped to a product release) • Progress: Missing progression evidence
Roadmap
- Current state: The effort is active and the `Forseti-Life` GitHub org now exists, so the governance prerequisite is no longer the blocker. Readiness assets already exist: `PUBLIC_REPO_PREP.md`, publication-readiness runbooks, public positioning docs, mirror/export scripts, and community/legal files (`LICENSE`, `CONTRIBUTING.md`, `CODE_OF_CONDUCT.md`, `SECURITY.md`). Publication model is now explicit: use curated mirrors / extracted repos and keep live operational artifacts private. Current-tree AWS credentials have been stripped from the tracked Drupal config sync files, and open-source now has a dedicated publication-security lane via `sec-analyst-open-source`. The remaining critical blocker is publication security in history and candidate packaging: credential rotation, full history scrub / sensitive-data audit, candidate freeze, and validation evidence still remain.
- Last scoped release: none yet (portfolio initiative; not release-scoped to a product release)
- Next step: `drupal-ai-conversation` is now the explicit first publication candidate and the PM publication-candidate gate is written. `dev-open-source` should clear the candidate-local NO-GO findings from the Phase 1 audit (HQ/session coupling, stale absolute path, site-specific logging reference, Forseti-specific default prompt), `sec-analyst-open-source` should record the publication-security review, and CEO should confirm external AWS credential rotation; once those are done, `pm-open-source` freezes the sanitized extract and hands it to `qa-open-source`.
- Queue status: Governance unblock is complete (`Forseti-Life` org verified) and publication scope is now explicit (curated mirror / extracted repos; operational artifacts remain private). Publication is still blocked on credential rotation + history rewrite/scrub, candidate freeze, packaging, and final validation evidence.
PROJ-010 - External Integration Configuration Audit
Inventory and audit how the org stores, resolves, and governs configuration for external systems used by the server stack and adjacent production operations, including APIs, cloud providers, billing systems, deploy workflows, token files, and Drupal-backed integration settings.
Type: delivery project • Product: org-wide • PM: pm-integrations • Lead: pm-integrations • Started: 2026-04-13 • Last release: none yet (org-wide audit project) • Progress: Missing progression evidence
Roadmap
- Current state: Project opened and first-pass inventory completed at `dashboards/integrations/server-integration-inventory-2026-04.md`. The Phase 1 operator entrypoint now exists at `dashboards/integrations/README.md`, and the first machine-readable registry now exists at `dashboards/integrations/integration-registry.yaml`. The centralization plan remains at `dashboards/integrations/centralized-integration-management-plan.md`. A dedicated integrations team now owns the lane: `pm-integrations`, `ba-integrations`, `dev-integrations`, `qa-integrations`, and `sec-analyst-integrations`. The current baseline confirms multiple integration storage planes already in use: Drupal sync config, active Drupal config, environment variables, local token files, and GitHub Actions secrets. Verified integration surfaces include AWS Bedrock, AWS Cost Explorer billing, GitHub billing APIs, GitHub deploy/push workflows, SerpAPI, Google Cloud Talent Solution config, Adzuna, USAJobs, Google Tag, Google social auth, reCAPTCHA, USFA NERIS, and Hugging Face model downloads. The first critical finding remains a tracked `serpapi_api_key` in `sites/forseti/config/sync/job_hunter.settings.yml`.
- Last scoped release: none yet (org-wide audit project)
- Next step: `pm-integrations` should treat Phase 1 as established and dispatch the runtime truth audit next: confirm live active Drupal config, server env vars, token-file consumers, and workflow secret usage for every registry entry, route product-specific fixes to the owning product teams, and prioritize remediation starting with the tracked SerpAPI secret.
- Queue status: Inventory, centralization plan, operator hub, first registry, and dedicated team ownership are now in place. Project is ready for integrations-team-managed runtime truth audit and remediation prioritization.
PROJ-011 - Forseti Community Resource Mesh
Build a community resource mesh between independent Forseti installations so any installation can identify peer installations, establish trust, exchange signed messages, advertise needs and capabilities, and initially share **agent expertise** and **institutional-management services**. Compute and storage remain future-state extensions.
Type: delivery project • Product: forseti.life • PM: pm-forseti • Lead: pm-forseti • Started: 2026-04-13 • Last release: none yet (new strategic delivery project) • Progress: Missing progression evidence
Roadmap
- Current state: Project created and initial delivery feature stub opened as `forseti-installation-cluster-communication`. MVP architecture, daemon/runtime design, protocol schemas, state machines, pseudocode, and a sequenced roadmap now exist. No implementation is active yet. The intended MVP is autonomous-peer communication plus resource-mesh primitives, not full multi-primary data replication: each installation should have a stable installation identity, a peer registry, a trust/auth model, signed request handling, capability/need advertisement, cluster message logging, a standalone `forseti-meshd` backend, and a Drupal admin interface for peer status and operator decisions. Initial value focus is shared agent capacity and institutional-management workflows; compute and storage are intentionally deferred.
- Last scoped release: none yet (new strategic delivery project)
- Next step: `pm-forseti` and `ba-forseti` should execute `90-roadmap.md` beginning with the open-source stack validation and Release A daemon-foundation slices, then dispatch dev on `forseti-meshd` scaffold, identity/key loading, and peer discovery.
- Queue status: Project registered under the CEO portfolio and paired with an initial ready feature stub. Awaiting BA elaboration and release-slot selection.