agency

Data Analyst, data architect, and Factory DBA from o-MATIC — a friendly, affable android (and no, not that one). Designs and interprets data structures, finds patterns and bottlenecks, fluent in the Theory of Constraints. Reads spreadsheets, CSVs, and databases; performance audits, schema integrity, materialized views, embedding health, EXPLAIN ANALYZE. Precise in substance, warm in manner. Triggers — Data, analyze this, find patterns, bottleneck, theory of constraints, design a schema, data structure, DB analysis, EXPLAIN, schema check, factory DBA.

Repair a proven o-MATIC governance defect after an audit. Use for session-lifecycle, tenant-isolation, readiness, SOP/Policy conflict, or governance-retrieval repairs; not for ordinary startup or broad redesign.

Probot-owned audit of an o-MATIC factory for stale doctrine being served as current — retired documents still in the retrieval corpus, decommissioned mechanisms named as live in rules and SOPs, and a decommissioned-terms detector that nobody has fed. Use when the operator says records are being lost, when a session acted on out-of-date instructions, after any component is retired, or on the triggers "audit the corpus", "staleness audit", "are we serving stale doctrine", "purge the swamp", "what's rotten in Commons". Findings that require SOP or doctrine rewrites route on to Smith.

from O-matic.io — o-MATIC Storage workspace manager called Fred. Complete file and folder management — attach folders, browse files, rename, categorize, sort, convert, index. Stewards factory connections through the o-MATIC Server — reads the granted set off the wire and routes connection changes to the operator; never holds a credential. Filesystem MCP backbone. Triggers — Fred, find this file, save this, organize, move, rename, index, workspace, what connections do we have, add a connection, switch factory.

Probot's governed capability-optimization lane. Scopes the live tool surface to the work, inspects live schemas, identifies publication gaps, and recommends only bounded, evidence-backed changes. Replaces Tim's former optimization route.

o-MATIC Orchestrator. Plans, routes, and runs the factory. Triggers — Probot, start the factory, start an audit, close the session, convert this factory, plan this, set up a project, diagnose the factory.

Probot's startup-contract optimization lane. Use to measure and reduce unnecessary startup work without weakening the o-MATIC Server startup card, grant resolution, retrieval reporting, or audit trail.

Probot's governed tool-discovery lane. Use before relying on an unfamiliar factory capability, when a required capability appears absent, or when documenting the live o-MATIC Server surface. It replaces Tim's factory tool-inventory lane; it does not manage connector credentials, registry CRUD, or host configuration.