Meta Foundation
Meta Foundation helps you select the right brand, connect Zernio, and understand which marketing tasks have enough access and evidence to run. It supplies the shared suite router and Social Media Doctor for Legion Code Inc.'s Meta Marketing Suite.
Start with your task
| Task | Command | Result |
|---|---|---|
| Set up a new brand or reuse an existing connection | set-up-my-meta | Selected profile/accounts, connection checklist and setup checkpoint |
| Diagnose an access or readiness problem | social-media-doctor | Per-feature readiness, evidence gaps and a precise repair handoff |
| Check selected access without changing a connection | check-my-access | Scoped inventory and permission/entitlement/sync findings |
The host adapter supplies its actual command invocation syntax and plugin namespace. Core is a required prerequisite. Source packages, selected installation, loaded roles and a successful invocation are separate evidence states; a companion marketplace does not establish global Wasp Nest dispatch by itself. Zernio MCP setup.
What the doctor checks
The doctor selects exact Zernio profile/account IDs, checks the host capabilities needed by your task, and keeps credential validity, connection health, permissions, entitlement, synchronization and actual feature tests separate. An intentionally disconnected account stays disconnected until you select and approve a reconnection.
The local metadata helper evaluates a saved, redacted record. It does not connect to Zernio, read credentials, call an API, install anything, or prove a fresh provider result. The agent performs authorized MCP reads and supplies their redacted metadata separately. Doctor guide map.
Shared connection, exact destination
All packs reuse the selected Zernio connection. Each task carries an explicit profile and account identity; the router never assumes the default profile or first account matching a platform. A group may contain accounts from multiple profiles, so selecting a group does not replace account-scope checks. Account listing, group scope.
Use the router guide map to find the owner and prerequisites for reports, content, ads, tracking, community or commerce.
External changes need review
Connecting an account, changing OAuth-app or ad-account scope, creating a key, publishing, sending a message, installing a tag, or enabling an automation changes an external system. The doctor can prepare the exact proposal and guide the approved step. A valid credential, healthy account or successful preflight does not approve that change. In particular, the Ads connect GET can persist a selection and remove de-scoped synced records; it is not a health probe. Ads connection contract.
Host templates contain public endpoint settings only. Review the actual configuration diff before applying it. Never add token values to source files, checkpoints, command arguments, screenshots or public reports.