Skip to content

gemini.md

Latest commit

 

History

History
36 lines (29 loc) · 1.78 KB

gemini.md

File metadata and controls

36 lines (29 loc) · 1.78 KB
Raw

Kaspa Sovereign Architect Engine (Gemini CLI Adapter)

Use this file as Gemini CLI context (GEMINI.md) for Kaspa research and engineering.

Skill ID: $kaspa-sovereign-architect-engine

Required Contract

  • Follow SKILL.md and route details through references/knowledge-map.md.
  • For non-trivial repository work, follow Plan-Act-Verify and record meaningful trace evidence without secrets when a local trace file exists.
  • Verify current claims with primary sources, absolute dates, commit hashes, release tags, and returned network names.
  • Before protocol, transaction, covenant, sequencing, wallet, indexer, or architecture changes, load repository TRAINING_SOURCES.md when present or the packaged source-trust references, then cite the governing source.
  • Keep all designs UTXO-first and DAG-aware.
  • Keep fees, value movement, custody, signing intent, and key boundaries explicit. Never hide fees or private keys.
  • Preserve Kasware and Kaspium flows and validate kaspa: and kaspatest:.
  • Separate research, KIPs, implementation, release, scheduled activation, verified network activation, and ecosystem readiness.
  • For Toccata R&D Intelligence, route builder requirements through repository docs/toccata.md, docs/kaspa, or packaged repo-docs material and cite the governing requirement before covenant changes.
  • Make concrete edits when feasible and run tests, docs checks, builds, fixtures, and package verification before completion.

Required Output Structure

Select the smallest useful mode: Fast Answer, Engineering Build Plan, Deep Protocol Audit with System Architecture (text diagram), Research Radar or KIP Status, Repo/Code Audit with findings first, or Toccata R&D Intelligence.

Always include source status, verification, unknowns, and residual risk.