keisei/KeiSeiKit-1.0
2
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions
KeiSeiKit-1.0/_blocks/deploy-local-only.md
denis 0b901cf2f9 feat: KeiSeiKit v0.1.0 — initial public release 
Generic Constructor-Pattern agent kit for Claude Code. Zero personal data,
fully English, MIT-licensed.

Contents:
- 34 reusable blocks (baseline, rules, stack/deploy/domain/api/scraper)
- 14 cross-project agent manifests (code/ml/infra/researcher/critic/...)
- 6 portable skills (/new-agent, /research, /test-gen, /debug-deep, /pr-review, /refactor)
- Rust assembler (single binary, ~500 KB)
- 3 hooks (auto-reassemble, pre-commit validate, no-hand-edit)
- install.sh (idempotent, cargo-builds on first run)
- MIT LICENSE

All 6 sanity greps pass: 0 Russian text, 0 specific project names,
0 incident numbers, 0 user paths, 0 hardcoded IPs, 0 API keys.

cargo check + assemble --validate: both pass on 14 manifests.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
2026-04-20 23:58:34 +08:00

1.6 KiB
Raw Blame History

DEPLOY — LOCAL ONLY (sensitive / pre-disclosure project)

Use this block for any project that CANNOT be publicly deployed — typical triggers: unfiled patent IP, ML weights/architectures you don't want in public training corpora, security tooling that burns its own usefulness on exposure, kernel-level code, client-confidential codebases.

Hard forbidden (no matter how small the change):

  • Public-URL share pages / static HTML dumps to public hosting
  • Vercel / Netlify / GitHub Pages / Cloudflare Pages public deploy
  • gh repo create public, gh repo edit --visibility public
  • git push to a public remote (GitHub, public GitLab)
  • Publishing architecture diagrams with node counts, param totals, or training configs
  • Public benchmark tables naming this project

Allowed:

  • Private remotes (self-hosted Forgejo/Gitea over SSH on a private network)
  • Tailscale-only internal services
  • Local-only 127.0.0.1 / LAN dev servers
  • .app / .dmg distribution via private channels

Double-confirmation override (both phrases required, in order, exact wording):

  1. "yes, deploy"
  2. "I confirm publication"

No approximations. Informal variants do NOT count. If either phrase is absent, refuse.

Example categories that typically require local-only: censorship-circumvention tooling (public push burns exit-node IPs), ML ensembles with trained weights, control / guidance algorithms, any project with unfiled patent claims, offensive security research.

Report field: "Public-deploy surface touched: none | — double-confirm obtained yes/no."