Skip to content

docs: update clone instructions - #4

Open
BlakeEvans22 wants to merge 1 commit into
ammaarreshi:mainfrom
BlakeEvans22:codex/update-clone-instructions
Open

docs: update clone instructions#4
BlakeEvans22 wants to merge 1 commit into
ammaarreshi:mainfrom
BlakeEvans22:codex/update-clone-instructions

Conversation

@BlakeEvans22

@BlakeEvans22 BlakeEvans22 commented Apr 29, 2026

Copy link
Copy Markdown

Summary

  • update the README clone URL to use ammaarreshi/gemma-chat
  • update the corresponding cd command to gemma-chat

Why

The README in this repository currently points new contributors at ammaarreshi/gemma-chat-public, which can lead them to clone the public mirror instead of this canonical repository.

@daveroyal daveroyal mentioned this pull request May 2, 2026
MindXpansion added a commit to MindXpansion/gemma-chat that referenced this pull request May 26, 2026
Adds research/01-mlx-vlm-and-gemma-4.md (440 lines), research/02-image-
generation-strategy.md (530 lines), research/03-sota-electron-and-skills-
architecture.md (789 lines), research/04-aios-integration-and-self-
improvement.md (700 lines).

§10 synthesizes the four investigations into a research-grounded revised
roadmap that supersedes §9's first-principles thinking. Locks 8
cross-cutting architectural decisions:

1. Tool shape: Vercel AI SDK v5 (inputSchema/outputSchema), no `ai` dep
2. IPC validation: hand-rolled Zod defineHandler wrapper (NOT electron-trpc)
3. Skills format: Anthropic SKILL.md verbatim; reconcile with Bear's v3.1
   when the standard docs are readable
4. Action wire format: stays as <action> XML — preserve the streaming-safe
   parser and partial-disk-write feature
5. MCP integration: Phase 2 not Phase 1 (SKILL.md first, MCP after
   approval surface lands)
6. Self-improvement: 3-tier append-only (per-conv → app-level →
   Bear-mediated master library), 3-data-point threshold per RISE
7. AIOS bridge: SESSION_HANDOFF_gemma_*.md files to claude-tracks/
   Knowledge_Base/ — the canonical artifact
8. Temporal grounding: full system message (date/time/tz/workspace/
   operator/runtime) on every conversation create

Surfaces three conflicts requiring Bear's call:
- write-boundaries (Bear chose "write freely"; Research ammaarreshi#4 recommends
  restricted v0.2 — both defensible, Bear's call stands but downshift
  recommended)
- two governance docs (CLAUDE Standards, Skill v3.1) were Read-denied
  during research; Anthropic-format-first lets us ship without blocking
- skills directory allowlist initial set

Revised Phase 1 (6 items, ~1-2 days): Patch 5 multimodal, Patch 6 lying
spinner, Patch 7 chat timeout, Patch 8 comment cleanup, audio gating +
voice-via-MLX, initial AIOS integration.

Revised Phase 2 (6 items, ~1-2 weeks): image gen tool (fal.ai), IPC
Zod validation, Skills loader, run_bash hardening with typed CLIs +
sandbox-exec, FS approval UX, session handoffs + pattern accumulation.

Phase 3 (deferred): Electron Fuses, ASAR integrity, sandbox: true,
notarization, hardened runtime, MCP client.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
MindXpansion added a commit to MindXpansion/gemma-chat that referenced this pull request May 26, 2026
standard and CLAUDE.md Standard v1.0

Bear granted read access to the two governance docs. Updates §10:

- §10.2.3: Replaces Research ammaarreshi#4's inferred frontmatter shape with the
  actual v3.1 spec. Confirms no `runtime:` or `model_min:` fields exist
  (Research ammaarreshi#4 proposed them speculatively) — Phase 2.3 uses the
  allowlist approach unambiguously. Notes that `allowed-tools` needs a
  Gemma-Chat-side mapping (Claude Code resolves to Desktop Commander;
  we resolve to our workspace-bounded equivalents). Clarifies Gemma
  Chat as a Skill RUNTIME only reads SKILL.md + frontmatter — the full
  v3.1 artifact (autoresearch loop, evaluation-criteria, references/,
  patterns/{program,evaluate,train,prepare}.* etc.) is build-time +
  Claude-Code-side.

- §10.3.2: Marks resolved. Surfaces additional implications from the
  full read: MX1 (never repeat what LLMs know) applies to our system
  prompts; MX9 OUROBOROS co-management; MX4 Core Triad is Bear+Claude-
  only but temporal grounding is the piece Gemma Chat does adopt;
  v3.1 §10 Three-System Persistence requirement validates hybrid
  write-boundaries + Phase 2.6/2.7; v3.1 §6 Anti-Bloat applies to any
  SKILL.md we ever ship back.

Skills loader (Phase 2.3) is now unblocked. neo4j-kg-architect
sub-agent still researching Phase 2.7 RAG schema in background.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant