I build operating systems for complex work: portfolio governance, executive cadence, PMO formation, delivery readiness, value realization, controls, partner ecosystems, and practical AI-assisted workflows.

My center of gravity is portfolio, program, project, and operations leadership. The work usually starts when leaders can see activity but cannot yet trust the signal: demand is scattered, ownership is unclear, readiness is inconsistent, tradeoffs are not visible, and decisions are being made from status theater instead of usable evidence.

This GitHub profile is a public-safe portfolio of how I structure that kind of work. It is not a software engineering portfolio and it is not a claim that these modules are deployed production systems. The repositories show governance frameworks, operating models, playbooks, templates, lessons learned, and anonymized examples of AI-assisted leadership work.

• Portfolio site: policani.github.io
• Portfolio artifacts: source pages
• Anonymized governance artifacts: operating-patterns
• LinkedIn: linkedin.com/in/marcpolicani

Because the GitHub Wiki backing repository is not initialized yet, the portfolio artifacts are published directly in this profile repository under wiki/. This keeps the material visible and reviewable without depending on the unused GitHub Wiki feature.

Start with:

• Portfolio Artifact Map
• Governance Frameworks
• Operating Models
• Playbooks and Templates
• Lessons Learned
• AI-Safe Workflow Design
• Public Safety

Evaluate the work as evidence of operating judgment.

The public artifacts are derived from real operating work, then scrubbed and generalized so the useful parts can be reviewed without exposing employer names, client details, internal systems, confidential figures, or proprietary process language. Read them as anonymized portfolio artifacts first and reusable operating patterns second.

Look for how the systems:

• Turn rough demand into structured intake, ownership, risks, dependencies, decisions, and follow-through.
• Clean portfolio signal before leaders are asked to prioritize, sequence, fund, or defend commitments.
• Make readiness, capacity, controls, and value realization visible before problems become late-stage surprises.
• Use AI for structure, synthesis, review, classification, drafting, and repeatability without handing over accountability.
• Separate public examples, runtime instructions, templates, source material, generated outputs, and review guardrails.
• Demonstrate capability through synthetic or generalized examples instead of exposing employer, client, financial, or proprietary details.

The strongest through-line is governed decision support.

I am strongest where organizations need:

• Enterprise PMO, EPMO, PPMO, portfolio governance, or program governance that is useful rather than ceremonial.
• Executive operating rhythm, decision cadence, tradeoff review, sponsor alignment, and follow-through.
• Intake, prioritization, scoring, sequencing, capacity visibility, readiness gates, and portfolio signal quality.
• Revenue technology, finance systems, release readiness, UAT governance, controls, exposure, or value realization discipline.
• Partner ecosystem, provider-network, launch-readiness, GTM, field-readiness, or external delivery governance.
• AI-assisted portfolio operations where business value, human review, evidence, risk, and adoption discipline matter more than tool novelty.

Supported public framing: portfolio governance, executive operating systems, AI-assisted workflow architecture, evidence-bound decision support, PMO operating models, value realization governance, delivery readiness governance, and practical AI operating governance.

Important boundary: I do not present this as software engineering ownership, ML/data-science ownership, autonomous AI decisioning, legal/compliance authority, product-owner authority, or production SaaS deployment experience unless a specific source proves that scope.

Start with:

• PPMO Formation Kit
• Portfolio Signal Quality Auditor
• Portfolio Intake and Readiness Triage System

These modules show how governance structure, taxonomy, intake, owners, sponsors, readiness gaps, and route decisions become visible before work is treated as approved or active.

Start with:

• Executive Portfolio Review Pack Builder
• Portfolio Prioritization Scoring Agent
• Portfolio Capacity and Sequencing Planner

These modules show how portfolio data becomes decision-ready: scoring criteria, constraints, dependencies, capacity pressure, risks, tradeoffs, decision asks, and follow-up registers.

Start with:

• PMO Governance Operations Log
• Release Readiness and UAT Governance Pack
• Controls and Exposure Governance Toolkit
• Value Realization Governance Ledger

These modules show how decisions, blockers, evidence gaps, signoffs, control owners, exposure, value claims, and realization confidence can be tracked without pretending the tool replaces accountable owners.

Start with:

• AI Opportunity Intelligence Review System
• AI Artifact Lifecycle Governance System
• Anonymized Governance Artifacts

These modules and artifacts show how rough AI ideas, vendor claims, prototypes, scripts, dashboards, agents, and informal workflow artifacts can be routed through proof, reliance risk, value signal, ownership, and human review before the business depends on them.

Start with:

• Anonymized Governance Artifacts

Innovation portfolio governance and partner ecosystem governance are supported capability areas. They are currently represented through anonymized governance artifacts and professional evidence themes rather than standalone product modules in this local portfolio set.

Start with:

• Business Case System
• Project Charter Initiation Agent

These modules show how early ideas become business cases, and how approved intent becomes project charters with scope, owners, assumptions, risks, dependencies, governance rhythm, and planning handoff.

The underlying professional evidence supports these themes:

• Rebuilt portfolio visibility across large initiative sets so leaders could separate active work, stalled demand, readiness gaps, and capacity constraints.
• Designed governance rhythms for CTO, CIO, CFO, COO, CMO, and senior-director sponsored environments.
• Built portfolio decision-support models that make prioritization criteria, ownership, risks, dependencies, tradeoffs, and decision rights easier to inspect.
• Built operating models for partner programs, provider networks, launch evidence, pre-release pilots, and customer-facing readiness.
• Used practical AI to improve portfolio hygiene, documentation quality, dependency review, meeting intelligence, content sourcing, scoring consistency, and workflow discipline while keeping accountability with people.
• Turned messy delivery environments into clearer systems of record, ownership, decision cadence, and follow-through.

Each module is designed to stand alone, but the stronger story is how they hand cleaner evidence into the next decision point. These are public-safe examples of PMO, portfolio, readiness, governance, and decision-support design: standalone starting points that can be adapted, extended, or combined for real operating needs.

These are free public tools and proofs of concept, separate from the PMO and portfolio operating-system examples. They are practical utilities for job-search workflow, career documentation, and writing review.

• Start with the operating problem, not the artifact.
• Make ownership, constraints, decisions, risks, dependencies, readiness, value, and tradeoffs visible.
• Separate demand, priority, readiness, and execution so leaders can see what is real.
• Clean signal before asking for portfolio decisions.
• Build only enough process to create trust, decision quality, and follow-through.
• Use AI for structure, synthesis, review, classification, drafting, and repeatability.
• Keep judgment, approvals, funding, risk acceptance, commitments, and accountability with people.
• Produce outputs that leaders can act on, practitioners can use, and sponsors can defend.

The public materials are generalized, synthetic, or scrubbed. They do not include employer names inside examples, client names, internal screenshots, exact dates, confidential financial figures, proprietary process descriptions, private career drafts, credentials, or details that would make a prior organization identifiable.

• Portfolio: https://policani.github.io
• GitHub: https://github.com/policani
• LinkedIn: https://www.linkedin.com/in/marcpolicani