MetaMe Developer Portal
Build sovereign engines. Package them. Verify them.
Publish modules that expand the MetaMe OS — all locally, all cryptographically sealed.
Build Your First Engine
Engines are modular, isolated components that extend the MetaMe OS.
Each engine is a self-contained system with its own manifest, schema, docs, tests, and verification layer.
Every engine begins with the MetaMe folder structure:
src, docs, manifests, legal, dist, tests, samples, build.
The manifest describes your engine’s identity, version, entry point, schema, and verification rules.
Engines expose a deterministic Execute() method.
All side effects remain in the host system.
Use the MetaMe CLI tools to build, package, hash, and verify your engine before publishing.
Engine Templates
Use official MetaMe templates to create engines that match the OS standard —
including manifests, schemas, docs, tests, and build scripts.
Includes engine class, config module, validation module, and execution surface.
README, architecture overview, API reference, and changelog.
engine.json + schema.engine.json with versioning and verification rules.
Build + package scripts for producing commercial ZIP artifacts.
MetaMe CLI Tools
The MetaMe CLI is a local, offline toolchain for building, packaging, hashing, and verifying engines.
Builds and packages every engine into a commercial ZIP artifact.
Generates SHA‑256 hashes for every engine and writes a verification ledger.
Audits every engine for missing files, missing folders, and structural integrity.
Publish Your Engine
Once your engine is built, hashed, and verified, you can publish it to the MetaMe Engine Market.
Ensure your ZIP, manifest, schema, and hash files are complete and verified.
Upload your engine package to the MetaMe Market for review and activation.
Once approved, your engine becomes available for sovereign OS users worldwide.