Index/ Stage 6 — Connected Architecture
Build In Progress

Stage 6 — Connected Architecture

Stark Industries PMO · 3 tiers linked · status rolls up, work rolls downConnect Boards columns link all three tiers. Intake → Portfolio (request triage). Portfolio → Execution (work assignment). Mirror columns on the Execution Board feed Status and Due Date back up so PMs see progress without clicking through.

01

The Three Tiers

Tier 1Intake Board
↘ Connected Portfolio Item
→ Portfolio Board
Tier 2Portfolio Board
↘ Connected Execution Board
→ Execution Board
Mirrors: Status · Due Date
Tier 3Execution Board
↖ Portfolio Board (mirror)
Sprint 1 · Sprint 2
02

How the Tiers Connect

flowchart TD
  INTAKE[" Intake Board\nForm submissions land here\nAI + Formula triage"]
  PORTFOLIO[" Portfolio Board\nPM strategic view\nStatus pipeline"]
  EXEC[" Execution Board\nTactical work\nSprint 1 & 2"]

  INTAKE -->|"Connect Boards\nlinked on approval"| PORTFOLIO
  PORTFOLIO -->|"Connect Boards\nauto-creates item"| EXEC
  EXEC -.->|"Mirror: Status + Due Date\nrolls up automatically"| PORTFOLIO

  AUTO4["Automation 4\nStatus → Approved\n→ Create Execution item\n+ link + notify PM"]
  PORTFOLIO -.-> AUTO4
        

Architecture complete. A request enters via the intake form, gets AI-summarized, formula-checked for completeness, routed to the Portfolio Board for PM review, approved, and auto-linked to a new Execution Board item. Status rolls up through mirror columns. The executive dashboard shows it all live. Zero manual spreadsheet-to-PowerPoint work for Pepper.

What rolls up vs. what stays local: Status and Due Date roll up (mirror columns). Sprint assignments and daily task details stay local to the Execution Board. This separation is deliberate — executives see trajectory, not micro-detail.