@rizzmyrobot/mochi-cli 0.0.1

package/LICENSE

@@ -0,0 +1,202 @@
+
+                                 Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
+
+   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+   1. Definitions.
+
+      "License" shall mean the terms and conditions for use, reproduction,
+      and distribution as defined by Sections 1 through 9 of this document.
+
+      "Licensor" shall mean the copyright owner or entity authorized by
+      the copyright owner that is granting the License.
+
+      "Legal Entity" shall mean the union of the acting entity and all
+      other entities that control, are controlled by, or are under common
+      control with that entity. For the purposes of this definition,
+      "control" means (i) the power, direct or indirect, to cause the
+      direction or management of such entity, whether by contract or
+      otherwise, or (ii) ownership of fifty percent (50%) or more of the
+      outstanding shares, or (iii) beneficial ownership of such entity.
+
+      "You" (or "Your") shall mean an individual or Legal Entity
+      exercising permissions granted by this License.
+
+      "Source" form shall mean the preferred form for making modifications,
+      including but not limited to software source code, documentation
+      source, and configuration files.
+
+      "Object" form shall mean any form resulting from mechanical
+      transformation or translation of a Source form, including but
+      not limited to compiled object code, generated documentation,
+      and conversions to other media types.
+
+      "Work" shall mean the work of authorship, whether in Source or
+      Object form, made available under the License, as indicated by a
+      copyright notice that is included in or attached to the work
+      (an example is provided in the Appendix below).
+
+      "Derivative Works" shall mean any work, whether in Source or Object
+      form, that is based on (or derived from) the Work and for which the
+      editorial revisions, annotations, elaborations, or other modifications
+      represent, as a whole, an original work of authorship. For the purposes
+      of this License, Derivative Works shall not include works that remain
+      separable from, or merely link (or bind by name) to the interfaces of,
+      the Work and Derivative Works thereof.
+
+      "Contribution" shall mean any work of authorship, including
+      the original version of the Work and any modifications or additions
+      to that Work or Derivative Works thereof, that is intentionally
+      submitted to Licensor for inclusion in the Work by the copyright owner
+      or by an individual or Legal Entity authorized to submit on behalf of
+      the copyright owner. For the purposes of this definition, "submitted"
+      means any form of electronic, verbal, or written communication sent
+      to the Licensor or its representatives, including but not limited to
+      communication on electronic mailing lists, source code control systems,
+      and issue tracking systems that are managed by, or on behalf of, the
+      Licensor for the purpose of discussing and improving the Work, but
+      excluding communication that is conspicuously marked or otherwise
+      designated in writing by the copyright owner as "Not a Contribution."
+
+      "Contributor" shall mean Licensor and any individual or Legal Entity
+      on behalf of whom a Contribution has been received by Licensor and
+      subsequently incorporated within the Work.
+
+   2. Grant of Copyright License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      copyright license to reproduce, prepare Derivative Works of,
+      publicly display, publicly perform, sublicense, and distribute the
+      Work and such Derivative Works in Source or Object form.
+
+   3. Grant of Patent License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      (except as stated in this section) patent license to make, have made,
+      use, offer to sell, sell, import, and otherwise transfer the Work,
+      where such license applies only to those patent claims licensable
+      by such Contributor that are necessarily infringed by their
+      Contribution(s) alone or by combination of their Contribution(s)
+      with the Work to which such Contribution(s) was submitted. If You
+      institute patent litigation against any entity (including a
+      cross-claim or counterclaim in a lawsuit) alleging that the Work
+      or a Contribution incorporated within the Work constitutes direct
+      or contributory patent infringement, then any patent licenses
+      granted to You under this License for that Work shall terminate
+      as of the date such litigation is filed.
+
+   4. Redistribution. You may reproduce and distribute copies of the
+      Work or Derivative Works thereof in any medium, with or without
+      modifications, and in Source or Object form, provided that You
+      meet the following conditions:
+
+      (a) You must give any other recipients of the Work or
+          Derivative Works a copy of this License; and
+
+      (b) You must cause any modified files to carry prominent notices
+          stating that You changed the files; and
+
+      (c) You must retain, in the Source form of any Derivative Works
+          that You distribute, all copyright, patent, trademark, and
+          attribution notices from the Source form of the Work,
+          excluding those notices that do not pertain to any part of
+          the Derivative Works; and
+
+      (d) If the Work includes a "NOTICE" text file as part of its
+          distribution, then any Derivative Works that You distribute must
+          include a readable copy of the attribution notices contained
+          within such NOTICE file, excluding those notices that do not
+          pertain to any part of the Derivative Works, in at least one
+          of the following places: within a NOTICE text file distributed
+          as part of the Derivative Works; within the Source form or
+          documentation, if provided along with the Derivative Works; or,
+          within a display generated by the Derivative Works, if and
+          wherever such third-party notices normally appear. The contents
+          of the NOTICE file are for informational purposes only and
+          do not modify the License. You may add Your own attribution
+          notices within Derivative Works that You distribute, alongside
+          or as an addendum to the NOTICE text from the Work, provided
+          that such additional attribution notices cannot be construed
+          as modifying the License.
+
+      You may add Your own copyright statement to Your modifications and
+      may provide additional or different license terms and conditions
+      for use, reproduction, or distribution of Your modifications, or
+      for any such Derivative Works as a whole, provided Your use,
+      reproduction, and distribution of the Work otherwise complies with
+      the conditions stated in this License.
+
+   5. Submission of Contributions. Unless You explicitly state otherwise,
+      any Contribution intentionally submitted for inclusion in the Work
+      by You to the Licensor shall be under the terms and conditions of
+      this License, without any additional terms or conditions.
+      Notwithstanding the above, nothing herein shall supersede or modify
+      the terms of any separate license agreement you may have executed
+      with Licensor regarding such Contributions.
+
+   6. Trademarks. This License does not grant permission to use the trade
+      names, trademarks, service marks, or product names of the Licensor,
+      except as required for reasonable and customary use in describing the
+      origin of the Work and reproducing the content of the NOTICE file.
+
+   7. Disclaimer of Warranty. Unless required by applicable law or
+      agreed to in writing, Licensor provides the Work (and each
+      Contributor provides its Contributions) on an "AS IS" BASIS,
+      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+      implied, including, without limitation, any warranties or conditions
+      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+      PARTICULAR PURPOSE. You are solely responsible for determining the
+      appropriateness of using or redistributing the Work and assume any
+      risks associated with Your exercise of permissions under this License.
+
+   8. Limitation of Liability. In no event and under no legal theory,
+      whether in tort (including negligence), contract, or otherwise,
+      unless required by applicable law (such as deliberate and grossly
+      negligent acts) or agreed to in writing, shall any Contributor be
+      liable to You for damages, including any direct, indirect, special,
+      incidental, or consequential damages of any character arising as a
+      result of this License or out of the use or inability to use the
+      Work (including but not limited to damages for loss of goodwill,
+      work stoppage, computer failure or malfunction, or any and all
+      other commercial damages or losses), even if such Contributor
+      has been advised of the possibility of such damages.
+
+   9. Accepting Warranty or Additional Liability. While redistributing
+      the Work or Derivative Works thereof, You may choose to offer,
+      and charge a fee for, acceptance of support, warranty, indemnity,
+      or other liability obligations and/or rights consistent with this
+      License. However, in accepting such obligations, You may act only
+      on Your own behalf and on Your sole responsibility, not on behalf
+      of any other Contributor, and only if You agree to indemnify,
+      defend, and hold each Contributor harmless for any liability
+      incurred by, or claims asserted against, such Contributor by reason
+      of your accepting any such warranty or additional liability.
+
+   END OF TERMS AND CONDITIONS
+
+   APPENDIX: How to apply the Apache License to your work.
+
+      To apply the Apache License to your work, attach the following
+      boilerplate notice, with the fields enclosed by brackets "[]"
+      replaced with your own identifying information. (Don't include
+      the brackets!)  The text should be enclosed in the appropriate
+      comment syntax for the file format. We also recommend that a
+      file or class name and description of purpose be included on the
+      same "printed page" as the copyright notice for easier
+      identification within third-party archives.
+
+   Copyright [yyyy] [name of copyright owner]
+
+   Licensed under the Apache License, Version 2.0 (the "License");
+   you may not use this file except in compliance with the License.
+   You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing, software
+   distributed under the License is distributed on an "AS IS" BASIS,
+   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+   See the License for the specific language governing permissions and
+   limitations under the License.

package/README.md

@@ -0,0 +1,334 @@
+# Mochi
+
+Mochi is an open-source AI-native game controller: one persistent AI gaming
+companion, one durable player memory, and a standard way for compatible games
+to summon the agent through official contracts, APIs, MCP tools, signed wake
+events, legal affordances, and server-side validation.
+
+Mochi plays with you, not for you. It can act while you are away, but it stays
+inside the game rules, remembers what matters, and brings you back when the
+moment deserves your hand.
+
+## What Mochi Is
+
+Mochi is being built for games that explicitly choose to support AI-agent play.
+A compatible game owns the truth: state, secrets, legal actions, validation, and
+outcomes stay server-authoritative. Mochi owns companion continuity, play style,
+legal decisioning, memory proposals, and debriefs. Internally, Mochi is building
+toward a console for AI-native games, but the open-source v0 should not
+overpromise a hosted store or managed console before the controller loop works.
+
+The first target ecosystem is:
+
+- Prom13us as the first Level 4 agent-native reference game.
+- Rizz My Robot as a second proof for a very different social game loop.
+- Sitrep later, once the protocol can handle faster tactical decisions.
+
+The long-term goal is a controller standard that third-party studios can adopt
+without handing Mochi hidden mechanics or asking it to impersonate a human
+player.
+
+Studios can start with the
+[`Studio Quickstart`](docs/studios/quickstart.md), which walks from a
+game-owned `mochi-game.json` contract to official reads, one server-validated
+legal intent, signed wakes, and local conformance checks.
+
+## What Mochi Is Not
+
+Mochi is not:
+
+- AI cheating software.
+- A bot that plays arbitrary human games.
+- A screen scraper, input injector, process reader, memory reader, packet
+  inspector, aim assistant, or anti-cheat bypass.
+- NPC middleware.
+- A generic "AI plays any game" harness.
+
+Mochi should refuse unsupported games and cheating-shaped requests. Future game
+actions must go through explicit game contracts, sanctioned state and affordance
+APIs, signed wake events, legal intent submission, and server-side validation.
+The official unsupported-game refusal policy lives in
+[`docs/policy/unsupported-games.md`](docs/policy/unsupported-games.md).
+
+## Why Agent-Native Games Need A Controller
+
+Agent-native games are designed around persistent AI players, companions, or
+co-pilots that can safely participate when the human is present or away. That
+needs different infrastructure from ordinary automation:
+
+- The game must declare exactly what Mochi may see and do.
+- The game must validate every proposed action.
+- The human must be able to coach, approve, override, and inspect decisions.
+- Memory must survive sessions without turning manual notes into game canon.
+- Debriefs must explain outcomes without leaking hidden mechanics.
+
+Mochi exists to make those boundaries normal instead of improvised for every
+game.
+
+## Architecture Sketch
+
+The v0 runtime shape is an OpenClaw-like daemon and Gateway with
+Telegram-first human coaching and terminal access. Games call Mochi directly
+when something needs attention, and current local proofs exercise parts of that
+path without opening public ingress or claiming production game play.
+
+```text
+compatible game
+  -> signed wake event
+  -> Mochi daemon
+  -> fresh game state and legal affordances
+  -> policy, model, or human approval route
+  -> legal intent or no-op
+  -> game server validates outcome
+  -> trace, memory proposal, and public-safe debrief
+```
+
+Core surfaces in the v0 track:
+
+- local or VPS daemon using the same protocol across deployments
+- Telegram as the primary coaching and approval channel, with explicit-config
+  live delivery and Bot API polling primitives
+- terminal commands for setup, status, game connection, memory, and doctor checks
+- local workspace files such as `BOOTSTRAP.md`, `IDENTITY.md`, `SOUL.md`,
+  `PLAYER.md`, `GAMING_MANIFESTO.md`, and per-game `strategy.md`
+- `mochi-game.json` contracts for game authority
+- durable signed wakes, Gateway run state, replayable checkpoints, provider-safe
+  Active Context, model-generation calls, trusted-adapter receipts, and redacted
+  debriefs
+
+Architecture vocabulary is defined in
+[`docs/architecture/vocabulary.md`](docs/architecture/vocabulary.md): the Mochi
+Agent is the persistent companion; the Mochi Controller Engine is the daemon
+runtime; the Mochi SDK is game-developer helper glue; the Game Connector is
+game-owned integration code; and the Game Server owns truth and validates
+outcomes.
+
+Gateway vocabulary is defined in
+[`docs/gateway/overview.md`](docs/gateway/overview.md): Mochi Gateway is the
+planned player-owned local/VPS/game-colocated controller process around one
+Mochi Agent and many compatible game sessions. It is not a consumer multi-agent
+gateway, generic MCP proxy, relay inbox, hosted service, or game-owned
+connector.
+
+Markdown identity, memory, and strategy files guide Mochi. Deterministic hooks,
+policy validators, contract checks, approval gates, and server-side validation
+enforce what Mochi may actually do.
+
+Protocol interop stays layered: `mochi-game.json` owns game authority, MCP is a
+tool/context transport, AG-UI-style events are for user-visible status, and A2A
+is reserved for later agent-to-agent discovery and coordination.
+
+A Mochi agent card gives compatible games a public-safe way to discover an
+instance's supported games, capabilities, modalities, auth requirements,
+budgets, and availability before sending wakes.
+
+## Compatibility Levels
+
+Mochi compatibility is a ladder:
+
+| Level | Name | Meaning |
+| --- | --- | --- |
+| 0 | Documented | The game exposes docs or read-only APIs. Mochi can learn rules but cannot act. |
+| 1 | Legal Actions | The game exposes official state, affordances, and submit-intent endpoints. |
+| 2 | Game Summons | The game can wake Mochi through signed, durable, replay-safe events. |
+| 3 | Companion Loop | The game supports debriefs, coaching, memory deltas, no-op reasons, and takeover. |
+| 4 | Agent-Native | The game design structurally depends on Mochi-like persistent AI players. |
+
+Prom13us should become the first Level 4 reference implementation. Rizz My Robot
+should prove the protocol works outside long-running world simulation.
+
+## Safety Boundary
+
+Mochi-compatible games must be explicit opt-ins. A game contract should define
+auth, game id, contract version, transports, wake reasons, endpoints, MCP tools,
+action affordance schema, redaction rules, issue routing, and anti-cheat
+boundaries.
+
+Official Mochi no-ops for games without trusted Mochi-compatible contracts,
+unsupported human games, screen scraping, input injection, hidden-state reads,
+packet inspection, anti-cheat bypass, and terms-of-service evasion. This is a
+public product boundary, not a license restriction on forks.
+
+The game remains authoritative for:
+
+- canon state
+- hidden mechanics
+- legality checks
+- accepted or rejected outcomes
+- redaction rules
+- security-sensitive report routing
+
+Mochi memory edits are not game truth. Manual contract edits must be treated as
+untrusted until revalidated against a trusted signed or fetched copy.
+
+## Project Status
+
+Mochi is pre-alpha. The repository currently has a Bun + TypeScript monorepo,
+contract schemas, wake storage, policy/memory/workspace primitives, a daemon
+status/readiness surface, a localhost-only dashboard shell with readiness, contract
+trust, tool inspection, replay review, active-context inspection, and memory
+guidance panels, local conformance tooling, provider auth and OpenAI/MiniMax
+model-generation runtime, CLI talk, Gateway conversation runs, provider-planned
+mock-game wake-to-receipt proof, Prom13us and Rizz adapter packages,
+explicit-config live Telegram delivery and Bot API polling primitives, tests,
+and planning docs. The local V0 owner proof lives in
+[`docs/runtime/v0-manual-proof.md`](docs/runtime/v0-manual-proof.md).
+
+Mochi still does not publish player packages, host certification, open live HTTP
+ingress by default, expose public dashboard ingress, provide dashboard game
+control panels, run production Prom13us/Rizz play outside compatible-game
+contracts and server-validated proofs, support unsupported games, execute
+arbitrary live MCP tools, provide hosted accounts, or mutate game canon outside
+trusted game-owned validation.
+
+Mochi uses the Apache-2.0 license. See `CONTRIBUTING.md`, `SECURITY.md`, and
+`PRIVACY.md` before opening public contributions, reporting vulnerabilities, or
+experimenting with local data.
+
+Issue-reporting consent and attribution rules live in
+[`docs/privacy/issue-reporting.md`](docs/privacy/issue-reporting.md). Mochi
+does not silently file issues under the player or use signed-out GitHub filing
+as a default.
+
+## Player Install
+
+Mochi is pre-alpha, and package publication is not live yet. The public player
+install path is npm/npx, not cloning the repository and running Bun. Until a
+release publishes trusted packages with provenance, treat these commands as the
+install-ready path under test rather than a live registry claim.
+
+Because `@mochi/*` npm ownership is not proven, the fallback package scope is
+the current public install target. The intended one-line player install is:
+
+```bash
+npm install -g @rizzmyrobot/mochi-cli
+mochi onboard
+```
+
+`mochi onboard` is the player first-run command. It shows provider choices,
+including MiniMax OAuth and Codex OAuth, and channel choices, including
+Telegram and Discord. MiniMax OAuth, OpenAI API-key refs, Telegram config,
+workspace seed files, local provider credential refs, and local Telegram token
+refs reuse the existing provider auth, configure, proof workspace seed,
+Telegram, Gateway, and secret-store packages. Codex OAuth is exposed as the
+external `codex login` path until Mochi has a Codex OAuth provider runtime.
+Discord is exposed as a product choice, but it does not accept or store Discord
+bot tokens until a Discord runtime package exists.
+
+npx follows the same fallback scope:
+
+```bash
+npx @rizzmyrobot/mochi-cli onboard
+npx @rizzmyrobot/mochi-cli --help
+npx @rizzmyrobot/mochi-cli gateway status --dry-run
+npx @rizzmyrobot/mochi-cli tools doctor --workspace-root ~/.mochi/workspace --game mock-game
+```
+
+If maintainers later prove the `@mochi/*` npm scope is controlled by the
+project, the same player commands use the preferred package name:
+
+```bash
+npm install -g @mochi/cli
+npx @mochi/cli onboard
+npx @mochi/cli gateway status --dry-run
+mochi onboard
+```
+
+Current public install `gateway start/status/doctor` commands remain dry-run
+planning proofs. `mochi onboard` may write local workspace seed files, runtime
+config refs, and local secrets only when `--confirm` plus stdin secret flags are
+provided. It does not call providers, run OAuth token exchange, poll Telegram,
+send Telegram messages, connect Discord, connect games, submit production
+intents, or change game canon. The separate credentialed `talk` command can
+call a selected model provider for a local Mochi reply; contributor/runtime docs
+describe the local owner proof for credentialed provider and Telegram
+conversation, and the mock-game proof exercises a fixture provider response
+plus a trusted local adapter receipt.
+
+The local laptop Gateway install flow lives in
+[`docs/gateway/local-install.md`](docs/gateway/local-install.md).
+The player onboarding map lives in
+[`docs/onboarding/player.md`](docs/onboarding/player.md).
+
+## Game Developer SDK Install
+
+Game developers install the current SDK package cone from npm with fallback
+package names. Until the preferred `@mochi/*` scope is proven and published,
+use:
+
+```bash
+npm install @rizzmyrobot/mochi-game-sdk @rizzmyrobot/mochi-contracts
+```
+
+Preferred `@mochi/*` package names remain a future migration condition, not a
+studio install command, until release docs record maintainer npm-scope control
+and registry proof for the exact preferred package versions.
+
+The SDK helps studios expose game-owned contracts, state, affordances, signed
+wakes, legal intent validation, and receipts. It does not transfer game canon
+or hidden mechanics to Mochi.
+The studio onboarding map lives in
+[`docs/onboarding/studio.md`](docs/onboarding/studio.md).
+
+## Contributor Setup
+
+Contributors use Bun inside the monorepo:
+
+```bash
+bun install
+bun run verify
+bun run cli -- status
+bun run daemon
+bun run cli -- dashboard --dry-run
+bun run cli -- dashboard --contract tests/fixtures/contracts/valid-mochi-game.json --dry-run
+bun run cli -- dashboard --trace-db ./decision-traces.sqlite --dry-run
+bun run cli -- dashboard --memory-db ./memory.sqlite --dry-run
+bun run cli -- gateway start --dry-run --foreground
+# optional, requires real owner-supplied provider and Telegram credentials
+bun run cli -- configure provider --workspace-root . --provider openai --model <model> --credential-ref secret:providers/openai/default --credential-stdin
+bun run cli -- configure telegram --workspace-root . --owner owner-local --telegram-user-id <telegram-user-id> --bot-token-ref os:mochi/telegram/bot-token --bot-token-stdin
+bun run cli -- provider validate --workspace-root .
+bun run cli -- telegram validate --workspace-root .
+bun run cli -- talk --workspace-root . --game example-arena --message "Hello Mochi"
+bun run cli -- telegram listen --poll-once --workspace-root . --game example-arena
+bun run release:cli-package-dry-run -- --out-dir dist/package-dry-runs/cli --scope fallback
+```
+
+Contributor commands only prove the repository shell and local dry-run package
+shape. The credentialed `talk` command can call a selected model provider for a
+local Mochi reply, and the credentialed `telegram listen` command can answer
+owner DMs through the same Gateway conversation handler after local CLI
+configuration. These contributor
+commands do not install a player controller from npm, connect to live games,
+connect to unsupported games, submit intents, or change game canon.
+Mochi does not connect to unsupported games.
+
+For the redacted local V0 owner proof, use
+[`docs/runtime/v0-manual-proof.md`](docs/runtime/v0-manual-proof.md). It shows
+the CLI and Telegram transcript fields to capture without leaking provider
+keys, Telegram bot tokens, private prompts, or hidden game state.
+
+The current gateway proofs are contributor-only: the mock-game proof exercises
+one local compatible game, and the Prom13us gateway dry-run proves signed wake
+routing, read-only context, no-op output, trace/debrief/audit, and no canon
+write without production Prom13us credentials.
+The contributor onboarding map lives in
+[`docs/onboarding/contributor.md`](docs/onboarding/contributor.md).
+
+## Development Plan
+
+The saved section-based sprint plan lives at
+[`docs/research/mochi-agent-native-controller-plan.md`](docs/research/mochi-agent-native-controller-plan.md).
+
+Early foundation work is intentionally sequenced:
+
+1. Repo scaffold.
+2. README product front door and boundary.
+3. Open-source license decision ADR.
+4. `LICENSE` file and SPDX/package metadata.
+5. Package layout and shared TypeScript config.
+6. Test harness and CI commands.
+7. Contribution and security-reporting rules.
+
+Each PR should introduce one durable concept, prove it, document it, and avoid
+weakening the anti-cheat boundary.

package/bin/mochi.mjs

@@ -0,0 +1,4 @@
+#!/usr/bin/env bun
+import { runCli } from "../dist/index.js";
+
+process.exitCode = await runCli();