4.1 KiB
4.1 KiB
Project Portfolio Workflow (2026-02-26)
Purpose
Organize long-horizon projects into one execution system so Whetstone can either:
- finish existing MVPs from other machines/repos, or
- rebuild from scratch with deterministic quality gates.
Current Inputs Found
- Whetstone core planning and sprint execution docs under
CLionProjects/whetstone_DSL/docs/ - A project archive bundle under
drive_projects/drive-download-20260217T155135Z-1-001/(mixed docs, requirements, roadmaps, MVP concepts) - No literal
project_docs/directory found under/home/bill/Documents
Portfolio Lanes
MVP_IMPORT
- Existing codebase exists elsewhere (GitHub/private machine).
- Goal: ingest, normalize, and harden to production thresholds.
GREENFIELD
- No code to import or import is lower value than rebuild.
- Goal: generate from architecture + constraints and iterate with strict validation.
Canonical Project Record (one row per project)
Use one table (or JSONL) with these required fields:
project_idnamelane(MVP_IMPORTorGREENFIELD)source_of_truth(repo URL / machine path / doc path)problem_statementtarget_userscritical_constraints(latency, memory, security, platform)status(intake,specifying,building,hardening,release_ready,paused)next_gateowner(human/agent)last_validated_at
Intake Gate (must pass before any build work)
- Confirm the project has one primary source of truth.
- Convert intent into a compact execution spec:
- target runtime/platform
- must-have features
- no-go constraints
- acceptance tests
- Choose lane (
MVP_IMPORTvsGREENFIELD) explicitly. - Create first 3-7 taskitems with deterministic completion checks.
Lane Workflows
A) MVP_IMPORT Workflow
Snapshot
- Pull/clone code and freeze baseline hash.
- Capture run/build/test state as-is.
Normalize
- Align repo layout, dependency pinning, and CI test entrypoints.
- Add missing schema/contract tests for core behavior.
Gap Audit
- Compare MVP behavior vs current intent docs.
- Tag each gap:
bug,missing feature,quality,security,scalability.
Hardening
- Run strict taskitem pipeline on highest-risk gaps first.
- Require failing test first for each fix.
Promotion
- Promote only after acceptance suite and non-functional checks pass.
B) GREENFIELD Workflow
Architecture Freeze v0
- Generate project skeleton + module contracts + acceptance tests.
Execution Slices
- Build in thin vertical slices with runnable tests every slice.
Constraint Enforcement
- Ensure projection/environment constraints are first-class in taskitems.
Hardening
- Reliability, determinism, performance, and security passes.
Promotion
- Same production gates as import lane.
Readiness Score (0-5 each, promote at >= 20/25)
Spec ClarityDeterministic Test CoverageOperational Readiness(build/release/runbook)Security PosturePerformance Budget Confidence
Weekly Cadence
- Intake/triage (new or updated projects)
- Lane assignment and top-3 portfolio priorities
- Whetstone execution runs (taskitem batches)
- Human review on blockers and lock-level decisions
- Closeout: score update + next gate assignment
Suggested Immediate Backlog
- Create
project_registry.jsonlin Whetstone docs/data. - Import project list from your planning docs (especially the drive archive and any external repos).
- For each project, set lane and next gate.
- Start with 3 projects only:
- one
MVP_IMPORTwith highest near-term value - one
GREENFIELDinfrastructure library - one
GREENFIELDdemonstrator product
- Run strict taskitem generation for those 3 and calibrate thresholds before scaling portfolio width.
Notes From Existing Whetstone State
- You already have mature sprint/taskitem infrastructure and closeout artifacts.
- Active gap logs indicate the main risk now is execution quality drift, not idea scarcity.
- Portfolio organization should therefore optimize for:
- deterministic closeout quality
- clear source-of-truth linkage
- controlled concurrent project count