Functional Requirements
Behavioral capabilities the system must provide.
109 requirements in this category.
| ID | Description | Status | Priority |
|---|---|---|---|
| REQ-FUN-001 | Store projects with id, name, description, sponsor, status, timestamps | approved | P0 |
| REQ-FUN-002 | Store deliverables with id, project_id, name, description, status, accountable_role | approved | P0 |
| REQ-FUN-003 | Store requirements with id, project_id, kind, description, acceptance_criteria, status, source_objective | approved | P0 |
| REQ-FUN-004 | Store risks with id, project_id, description, probability, impact, owner, response, status | approved | P0 |
| REQ-FUN-005 | Store sign-offs with id, subject_kind, subject_id, mode, state, requested_by, created_at | approved | P0 |
| REQ-FUN-006 | Store sign-off events (requested, approved, rejected, delegated) tied to sign-off id | approved | P0 |
| REQ-FUN-007 | Append-only audit log of every create/update/approve/reject/transition | approved | P0 |
| REQ-FUN-008 | Store stakeholders with id, project_id, name, kind, classification, power_interest_quadrant | approved | P0 |
| REQ-FUN-009 | Store work-board items with id, project_id, title, description, state, claimant, posted_by, timestamps | approved | P0 |
| REQ-FUN-010 | Store templates with id, kind, version, body, seeded_at_install | approved | P0 |
| REQ-FUN-011 | Store actors with id, kind (human/agent), display_name, auth_method, status | approved | P0 |
| REQ-FUN-012 | Store delegations linking from_actor to to_actor with scope, expires_at | approved | P0 |
| REQ-FUN-013 | Store attachments with id, parent_kind, parent_id, filename, content_hash, storage_uri | approved | P0 |
| REQ-FUN-020 | Actor (agent or human) can post a work-board item via REST or MCP | approved | P0 |
| REQ-FUN-021 | Actor can claim a posted item; concurrent claims resolved deterministically with exactly one winner | approved | P0 |
| REQ-FUN-022 | Actor can hand off a claimed item to another actor | approved | P0 |
| REQ-FUN-023 | Actor can mark a claimed item completed | approved | P0 |
| REQ-FUN-024 | Board queryable by state, project, claimant, posted-by, and date range | approved | P0 |
| REQ-FUN-025 | Board delivers state changes to subscribers within 5 seconds (SSE or websocket) | approved | P0 |
| REQ-FUN-026 | Claimed item cancellable by original poster or sponsor; cancellation audited | approved | P0 |
| REQ-FUN-030 | Actor can request a sign-off on any sign-off-eligible subject | approved | P0 |
| REQ-FUN-031 | Sign-off any-of mode (one approver suffices) | approved | P0 |
| REQ-FUN-032 | Sign-off all-of mode (every named approver must approve) | approved | P0 |
| REQ-FUN-033 | Approve via REST/MCP/web UI with identical audit rows | approved | P0 |
| REQ-FUN-034 | Approver can reject with required rationale text | approved | P0 |
| REQ-FUN-035 | Approver can delegate to another actor within configured delegation scope | approved | P0 |
| REQ-FUN-036 | Rejected sign-off is not reusable; new sign-off ID required for re-request | approved | P0 |
| REQ-FUN-037 | Notify approvers when a sign-off is requested or delegated to them | approved | P0 |
| REQ-FUN-038 | Agent actor only approves sign-offs whose subject falls within delegated scope | approved | P0 |
| REQ-FUN-040 | REST API described by an OpenAPI 3.x specification | approved | P0 |
| REQ-FUN-041 | REST API provides CRUD endpoints for every entity REQ-FUN-001..013 where the operation makes sense | approved | P0 |
| REQ-FUN-042 | All write endpoints require a bearer token | approved | P0 |
| REQ-FUN-043 | All POST endpoints accept Idempotency-Key header; same response for retries within 24h | approved | P0 |
| REQ-FUN-044 | Error responses conform to documented model with code, message, details, trace_id | approved | P0 |
| REQ-FUN-045 | REST API versioned via URL prefix (/v1/...); breaking changes increment version | approved | P0 |
| REQ-FUN-050 | MCP server exposes tools covering 100% of REST surface (parity) | approved | P0 |
| REQ-FUN-051 | MCP tools accept and return JSON schemas matching REST data model | approved | P0 |
| REQ-FUN-052 | MCP tools produce same audit rows as their REST counterparts | approved | P0 |
| REQ-FUN-053 | MCP server authenticates via same bearer-token mechanism as REST | approved | P0 |
| REQ-FUN-060 | Web UI allows browsing projects, deliverables, requirements, risks, sign-offs, work-board, audit log | approved | P0 |
| REQ-FUN-061 | Web UI allows authoring entities a human user would create | approved | P0 |
| REQ-FUN-062 | Web UI surfaces sign-off requests assigned to logged-in user | approved | P0 |
| REQ-FUN-063 | Web UI allows approval, rejection, and delegation actions | approved | P0 |
| REQ-FUN-064 | Web UI allows audit log search by entity, actor, date range | approved | P0 |
| REQ-FUN-065 | Web UI allows report export (CSV, JSON) of major entities | approved | P0 |
| REQ-FUN-070 | Every state-changing operation produces exactly one audit row | approved | P0 |
| REQ-FUN-071 | Audit log append-only at DB level (no UPDATE or DELETE granted to app role) | approved | P0 |
| REQ-FUN-072 | Audit log includes tamper-detection (hash chain or equivalent) | approved | P0 |
| REQ-FUN-073 | Audit log retrievable via REST and UI | approved | P0 |
| REQ-FUN-074 | Audit log retains rows indefinitely in MVP (no automatic purge) | approved | P0 |
| REQ-FUN-080 | Seed 17 established project management guidelines templates (charter, stakeholder, scope, requirements, WBS, schedule, cost, quality, resource, comms, risk, procurement, stakeholder mgmt, change, lessons, closure) | approved | P0 |
| REQ-FUN-081 | Actor can instantiate a template into a working artifact attached to a project | approved | P0 |
| REQ-FUN-082 | Charter template sufficient to produce this project's own charter | approved | P0 |
| REQ-FUN-090 | Requirement created in AIPM appears (or referenceable) in MAS within 1 minute | approved | P0 |
| REQ-FUN-091 | Memory created in MAS appears (or referenceable) in AIPM within 1 minute | approved | P0 |
| REQ-FUN-092 | Reconciliation report lists drift between AIPM and MAS for requirement, plan, memory | approved | P0 |
| REQ-FUN-093 | Schema changes crossing MAS boundary coordinated with STK-006 before merge | approved | P0 |
| REQ-FUN-094 | Project-level worktree provisioning when project has a code_repo_url | approved | P0 |
| REQ-FUN-095 | Progressive Web App for the sign-off page (manifest.json + service worker) | approved | P0 |
| REQ-FUN-096 | Global read-only mode controlled by AIPM_READ_ONLY environment variable | approved | P0 |
| REQ-FUN-097 | In-process lifecycle hooks fire on board-item state transitions and sign-off lifecycle events | approved | P0 |
| REQ-FUN-098 | Hybrid two-axis capability taxonomy: established project management guidelines knowledge area + action verb | approved | P0 |
| REQ-FUN-099 | Non-MCP fallback control channel via send-text and poll-output endpoints | approved | P0 |
| REQ-FUN-100 | Configuration loaded as merge of global + per-project overrides; project keys win | approved | P0 |
| REQ-FUN-101 | Schedule activity CRUD scoped to project and work package | approved | P0 |
| REQ-FUN-102 | Activity dependency model (FS/SS/FF/SF + lag/lead in days) | approved | P0 |
| REQ-FUN-103 | Critical-path computation triggered on schedule change | approved | P0 |
| REQ-FUN-104 | Schedule baseline (versioned, immutable snapshot) | approved | P0 |
| REQ-FUN-105 | Schedule slippage detection vs approved baseline | approved | P0 |
| REQ-FUN-106 | Read-only Gantt chart view of project schedule | approved | P1 |
| REQ-FUN-107 | Schedule report (variance + SPI by project / WBS branch / time window) | approved | P0 |
| REQ-FUN-108 | Schedule template instantiation seeds activities + dependencies | approved | P1 |
| REQ-FUN-109 | Activity status updates via dedicated activity_status_update rows | approved | P1 |
| REQ-FUN-110 | Auto-create board item when activity deps are satisfied | approved | P1 |
| REQ-FUN-111 | Per-activity forecasted finish date from EV + SPI | approved | P1 |
| REQ-FUN-112 | Resource over-allocation flag (read-only, no auto-leveling) | approved | P2 |
| REQ-FUN-113 | Post-baseline schedule changes require approved Change Request | approved | P0 |
| REQ-FUN-114 | Schedule export in iCalendar (ICS) and CSV formats | approved | P2 |
| REQ-FUN-115 | Budget allocation (project / WBS branch / activity) | approved | P0 |
| REQ-FUN-116 | Cost baseline (versioned, insert-only snapshot) | approved | P0 |
| REQ-FUN-117 | Actual cost capture (cash/non-cash + category taxonomy) | approved | P0 |
| REQ-FUN-118 | EVM rollup (PV, EV, AC, CV, SV, CPI, SPI, EAC, ETC, VAC, TCPI) | approved | P0 |
| REQ-FUN-119 | Cost report (project / WBS branch / time window) | approved | P0 |
| REQ-FUN-120 | EAC forecasting (CPI / CPI*SPI / optimistic methods) | approved | P1 |
| REQ-FUN-121 | Cost categorization taxonomy (default + configurable) | approved | P1 |
| REQ-FUN-122 | Single base currency in MVP (multi-currency future) | approved | P2 |
| REQ-FUN-123 | Per-project Assumption Log entity | approved | P0 |
| REQ-FUN-124 | Issue Log entity (distinct from work-board items) | approved | P0 |
| REQ-FUN-125 | Lessons Learned Register entity | approved | P0 |
| REQ-FUN-126 | Change Request entity with submission/approval workflow | approved | P0 |
| REQ-FUN-127 | Change Log view (distinct from audit log) | approved | P1 |
| REQ-FUN-128 | Project Closure entity with auto-rollup | approved | P0 |
| REQ-FUN-129 | Requirements Traceability Matrix view | approved | P0 |
| REQ-FUN-130 | WBS Dictionary fields on deliverable | approved | P1 |
| REQ-FUN-131 | Milestone flag on activity + Milestone List view | approved | P1 |
| REQ-FUN-132 | Project Schedule Network Diagram (PDM) view | approved | P2 |
| REQ-FUN-133 | Three-point duration estimates on activity (PERT) | approved | P1 |
| REQ-FUN-134 | Estimate basis fields (cross-cutting: duration, cost, resource) | approved | P1 |
| REQ-FUN-135 | Cost estimate basis (per-budget-row) | approved | P1 |
| REQ-FUN-136 | Project Funding Requirements view (stepped tranches) | approved | P1 |
| REQ-FUN-137 | Quality Report view (aggregated quality dashboard) | approved | P1 |
| REQ-FUN-138 | Test Case + Test Run entities per deliverable | approved | P0 |
| REQ-FUN-139 | Team Charter artifact template (18th in seeded set) | approved | P1 |
| REQ-FUN-140 | Per-activity resource_requirement rows | approved | P1 |
| REQ-FUN-141 | Resource Breakdown Structure (RBS) view | approved | P2 |
| REQ-FUN-142 | Actor availability calendar | approved | P1 |
| REQ-FUN-143 | Resource utilization view (planned vs claimed over time) | approved | P1 |
| REQ-FUN-144 | Risk Report view (overall risk dashboard) | approved | P1 |
| REQ-FUN-145 | Stakeholder engagement assessment matrix | approved | P1 |