🩺 System Status
Live health of the Website, API and MCP server across every environment.
0
✅ Operational
0
⚠️ Degraded
0
⛔ Down
0
🛰️ Total Checks
Operational
Degraded performance
Outage
Maintenance
Demo data — this mockup simulates health checks against each environment’s
/health endpoints.
🔗 Important Links
🏠 Application Home
Open the POD Governance portal (sign-in required).
/
🔐 Sign In
Passwordless magic-link login for every role.
/login
📊 Dashboard
Your role-based landing page after signing in.
/dashboard
📈 Ups & Downs
Account-health review-cycle workflow.
/projects
🎯 Priorities & Achievements
Weekly Priorities & Achievements submission and bilateral review.
/pa
📑 Reports & Analytics
Cycle, participation and export reports.
/reports
📘 API Documentation ↗
Interactive Swagger / OpenAPI explorer.
/api/docs
🧾 OpenAPI Spec (JSON) ↗
Raw OpenAPI 3 definition for integrators.
/api/docs.json
🩺 API Health ↗
Live API + database health probe.
/api/v1/health
🤖 MCP Health ↗
Live Model Context Protocol server probe.
/mcp/health
📖 About POD Governance
POD Governance is an internal platform for structured delivery reporting. Every sprint, Project Leads submit Ups & Downs and Priorities & Achievements for bilateral review through a defined approval chain.
Key requirements
- Project Leads enter Ups (positives) and Downs (risks/issues) independently each cycle; submissions are consolidated per project.
- Project Managers review the consolidated items — edit, add or remove — then forward up the chain.
- Every item flows through a multi-level approval chain; each level can review, comment, modify and Approve or Return.
- A full audit trail of all changes and comments is preserved and visible at every stage.
- Returns require a mandatory comment so the sender knows exactly why an item came back.
- The Cluster Head sees the complete picture and, on final approval, the cycle is closed and locked.
- Priorities & Achievements run weekly (every Monday) through bilateral reporting pairs, independent of the project-based Ups & Downs cycle.
- AI assistants may act on the API on a user’s behalf via scoped Personal Access Tokens through the MCP server.
Roles
| Role | Responsibility |
|---|---|
| Project Lead | Submit U&D + P&A each cycle |
| Project Manager | Review & forward PL submissions |
| Delivery SPOC | Cross-project oversight, bilateral P&A review |
| Sales SPOC | Commercial reviewer; reports directly to the POD Owner |
| POD Owner | POD-level review and forward |
| Cluster Head | Final approval, cluster digest |
| PMO Associate | View-only access to the entire flow (no edit or approval rights) |
| ESO SPOC | Engineering / solutioning SPOC reporting directly to the POD Owner |
| Recruitment SPOC | Talent / recruitment SPOC reporting directly to the POD Owner |
| Administrator | Manages users, projects, PODs, reporting relationships and MCP tokens |
📚 User Manual
🚀 Getting Started
- Sign in with your work email (magic link)
- Select your project from the Projects page
- Your role determines which modules appear
📝 Submitting Ups & Downs
- Go to your workflow screen (Ups & Downs)
- Add items under Ups or Downs
- Submit before the cycle closes
✅ Reviewing & Approving
- Reviewers see submissions in their queue
- Can add items, comment, or return
- Forward to the next approval level
🎯 Priorities & Achievements
- Submit weekly priorities and achievements
- Bilateral review by PM and Delivery SPOC
- Cluster Head sees consolidated digest
📊 Reports & Exports
- Cycle analytics and approval trends
- CSV exports for all major data sets
- Scheduled report delivery via email
🤖 AI / MCP Access
- Generate Personal Access Tokens in Profile
- Connect via MCP server in Claude / AiDE
- Query cycles and P&A via AI assistant