Integration Management

Unifies the moving parts of the project: charter, change control, integrated baselines, knowledge transfer.

Processes in this Knowledge Area

Develop Project Charter

Inputs: business case, agreements, EEFs. Outputs: project charter authorizing project existence and PM authority.

• REQ-BUS-003 — System preserves sponsor approval authority for charter, scope, schedule, budget changes
• REQ-FUN-010 — Store templates with id, kind, version, body, seeded_at_install
• 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)
• REQ-FUN-082 — Charter template sufficient to produce this project's own charter

Develop Project Management Plan

Inputs: charter, outputs of other planning processes. Outputs: the integrated project management plan.

• REQ-FUN-040 — REST API described by an OpenAPI 3.x specification
• REQ-FUN-044 — Error responses conform to documented model with code, message, details, trace_id
• REQ-FUN-051 — MCP tools accept and return JSON schemas matching REST data model
• REQ-FUN-093 — Schema changes crossing MAS boundary coordinated with STK-006 before merge
• REQ-FUN-100 — Configuration loaded as merge of global + per-project overrides; project keys win
• REQ-NFR-021 — Audit rows include actor, ts (UTC ISO 8601), entity kind/id, before/after, change reason

Direct and Manage Project Work

Inputs: PM plan, approved change requests. Outputs: deliverables, work performance data, issue log updates.

• REQ-FUN-013 — Store attachments with id, parent_kind, parent_id, filename, content_hash, storage_uri
• REQ-FUN-097 — In-process lifecycle hooks fire on board-item state transitions and sign-off lifecycle events

Manage Project Knowledge

Inputs: PM plan, deliverables. Outputs: lessons learned register, updates to organizational process assets.

• REQ-FUN-091 — Memory created in MAS appears (or referenceable) in AIPM within 1 minute
• REQ-FUN-092 — Reconciliation report lists drift between AIPM and MAS for requirement, plan, memory
• REQ-FUN-096 — Global read-only mode controlled by AIPM_READ_ONLY environment variable

Monitor and Control Project Work

Inputs: PM plan, work performance information. Outputs: work performance reports, change requests.

• REQ-FUN-007 — Append-only audit log of every create/update/approve/reject/transition
• REQ-FUN-052 — MCP tools produce same audit rows as their REST counterparts
• REQ-FUN-064 — Web UI allows audit log search by entity, actor, date range
• REQ-FUN-070 — Every state-changing operation produces exactly one audit row
• REQ-FUN-071 — Audit log append-only at DB level (no UPDATE or DELETE granted to app role)
• REQ-FUN-072 — Audit log includes tamper-detection (hash chain or equivalent)
• REQ-FUN-074 — Audit log retains rows indefinitely in MVP (no automatic purge)
• REQ-NFR-013 — Audit log append-only at the DB role level
• REQ-NFR-020 — Every mutation produces exactly one audit row regardless of API surface
• REQ-NFR-062 — All scope changes flow through the change control plan

Perform Integrated Change Control

Inputs: PM plan, change requests, work performance reports. Outputs: approved change requests, change log updates.

• REQ-FUN-045 — REST API versioned via URL prefix (/v1/...); breaking changes increment version
• REQ-FUN-081 — Actor can instantiate a template into a working artifact attached to a project

Close Project or Phase

Inputs: PM plan, accepted deliverables. Outputs: final product/service transition, final report, archived project documents.

• REQ-TRN-001 — Migration tooling imports a project from existing flat-file or MAS-only sources into AIPM

General Knowledge Area support

These requirements support the knowledge area broadly rather than fitting one specific process.

• REQ-BUS-001 — System replaces ad-hoc flat-file project state for sponsor-portfolio projects
• REQ-BUS-002 — System allows established_guidelines_conformant project execution end-to-end
• REQ-FUN-001 — Store projects with id, name, description, sponsor, status, timestamps
• REQ-FUN-041 — REST API provides CRUD endpoints for every entity REQ-FUN-001..013 where the operation makes sense
• REQ-FUN-042 — All write endpoints require a bearer token
• REQ-FUN-043 — All POST endpoints accept Idempotency-Key header; same response for retries within 24h
• REQ-FUN-050 — MCP server exposes tools covering 100% of REST surface (parity)
• REQ-FUN-053 — MCP server authenticates via same bearer-token mechanism as REST
• REQ-FUN-090 — Requirement created in AIPM appears (or referenceable) in MAS within 1 minute
• REQ-NFR-050 — AIPM does not introduce parallel canonical store for data already canonical in MAS

Secondary support

Requirements whose primary KA is elsewhere, but which also support Integration Management.

All requirements primarily mapped to Integration Management (44)