Suleman Manji

AI systems engineering, platform automation, agent runtime infrastructure, and public-safe operational proof by Suleman Manji.

Work Map

From service chaos to controlled action.

The map below reflects the actual operating lanes in my local work: platform CLIs, CWM ticket control planes, billing preview gates, live UI proof, session-memory infrastructure, and public-safe stakeholder outputs.

Translation Layer

Private evidence, public pattern.

Much of the work touches organization systems or client operations, so the public artifact cannot be a raw ticket dump. The useful signal is the repeatable pattern: collect live state, identify the safe action boundary, create a reviewable control plane, execute only when gated, and leave durable proof.

MSP Operations

MSP Command Plane

Problem Surface

Service work spans tickets, time entries, RMM state, Microsoft Graph evidence, project records, stakeholder artifacts, and approval gates.

System Built

A CLI and skill-based command plane that turns live platform state into reviewed actions, CWM task structures, GitHub Project 4 governance, and reusable handoff artifacts.

Proof Discipline

CWM ticket-control-plane registers, time-entry reconciliation artifacts, control-validate gates, live runtime checks, and public-safe session-harvest maps.

Operator Leverage

Eight-platform MSP operations tooling across PSA, RMM, Microsoft 365, documentation, security, remote access, vCloud, and billing workflows.

Eight TypeScript CLI packages and 250+ orchestration skills are represented in the local local-agent-tooling repo. CWM tickets are treated as execution surfaces with tasks, notes, status, schedules, documents, and time entries reconciled after writes. Internal development effort was reconciled against member 346 time entries, GitHub Project 4, git activity, browser history, and Codex session traces.
Financial Agent Systems

Financial-Agent Paper Runtime

Problem Surface

Financial-agent systems need explicit safety boundaries, reproducible runs, and evidence before any operator trusts the output.

System Built

Paper-runtime components for decision policy, ledger checks, broker status reads, forecast scoring, and delivery gates.

Proof Discipline

Test suite results, paper-run logs, reconciliation checks, and configuration gates.

Operator Leverage

Research infrastructure for paper-trading decisions, risk gates, reconciliation, forecasting, and runtime evidence.

Research framing stays paper/runtime only, with safety language separated from operational MSP claims. Runtime outputs are treated as evidence bundles rather than opaque recommendations. Reconciliation and broker-state checks are part of the operating model before any downstream decision.
Agent Runtime

Agent Memory and Runtime Infrastructure

Problem Surface

Agent work loses value when decisions, proof locations, tool state, and blockers disappear between sessions.

System Built

Qdrant-backed mem0 recall, checkpoint/replay helpers, session-harvest maps, repo-native skills, and explicit handoff prompts.

Proof Discipline

Hermes memory search results, Qdrant checkpoint guidance, session-log harvest artifacts, and validation notes tied back to GitHub control-plane items.

Operator Leverage

Local agent runtime, memory, recall, and skill infrastructure that preserves operator context across interrupted sessions.

Local mem0 recovered Project 4 and local-agent-tooling effort history during this portfolio pass. Session harvest maps convert raw Codex logs into skills, docs, CLI gaps, and Project 4 issue graphs. Checkpoint wrappers are used when direct Qdrant writes are unreliable from sandboxed agents.
Operator Interfaces

AlgaPSA and Operator Interfaces

Problem Surface

Operators and stakeholders need to see what the platform actually does, not infer readiness from backend logs.

System Built

AlgaPSA/vArida demo lanes, billing sync previews, SPLA readiness, UI route audits, stakeholder briefing renderers, and screenshot-backed validation.

Proof Discipline

UIUX gap analysis, stakeholder YAML-to-HTML/XLSX and YAML-to-PPTX pipelines, runtime proof captures, and GitHub Project 4 issue gates.

Operator Leverage

Deployed platform and dashboard work for billing review, SPLA, client-scoped operations, stakeholder review, and demo-safe proof capture.

The repo explicitly gates May 10 readiness on live AlgaPSA behavior, not backend proof alone. Stakeholder artifacts are generated from structured sources and verified instead of hand-built one-offs. UIUX analysis ties billing, tickets, devices, reports, and notifications into a client-scoped operating model.
MCP and API Tooling

MCP and Platform API Toolchain

Problem Surface

Assistants need structured access to CWM, CWA, Graph, Sophos, Cavelo, Meraki, vCloud, Portainer, and GitHub without leaking secrets or bypassing approvals.

System Built

Generated CLI contracts, platform-specific fetchers, safety-gated write paths, Graph/CWA/Sophos investigation workflows, and MCP-style tool boundaries.

Proof Discipline

CLI contract generation, help-json surfaces, smoke tests, package builds, read/write gates, and public-safe investigation summaries.

Operator Leverage

API adapters, MCP tools, and platform CLIs that let AI agents work against real operational systems through controlled boundaries.

The local-agent-tooling command surface prefers platform CLIs over raw APIs and emits JSON for agent consumption. High-risk writes require preview tokens, explicit confirmations, or status-gate handling before execution. Service investigations use Graph, CWA, Sophos, Meraki, CWM, and ticket/time evidence together before closure.