docs: organization文書を現行契約へ整理

CONTRIBUTING.md

@@ -1,183 +1,24 @@
-# Contributing to Agiletec Inc.
+# Contribution guide
 
-Thank you for your interest in contributing to Agiletec Inc. and our vision.
+agiletec-incの公開projectへのIssue・Pull Requestを歓迎します。変更対象repoのREADME、license、security policy、
+contribution guideを先に確認してください。
 
-## 🎯 Our Mission
+## Issue
 
-**Eliminate the multi-tier subcontracting structure.**
+再現手順、期待結果、実際の結果、version・OSなど必要な環境情報を記載してください。security vulnerabilityは
+public Issueへ書かず[`SECURITY.md`](./SECURITY.md)のprivate reporting channelを使ってください。
 
-We solve structural inefficiencies in Japan's IT industry and realize a future where all companies have in-house development capabilities.
+## Pull Request
 
----
+- 一つの責務へ絞り、関連Issueと変更理由を示す。
+- repoのformat、lint、typecheck、testを実行し、実commandと結果を書く。
+- user-visible behaviorや運用境界を変える場合だけ、正本の文書を同時に更新する。
+- generated file、secret、credential、customer dataをcommitしない。
+- 既存codeの命名、comment密度、architectureへ合わせる。
 
-## 🤝 How to Contribute
+reviewではcorrectness、security、互換性、scope、検証可能性を確認します。変更依頼へ対応後、required checksが
+greenになればmaintainerがmergeします。
 
-### 1. Contributing to Open Source Projects
+## License
 
-#### Our Projects
-
-Open source projects developed and maintained by Agiletec Inc.:
-
-- **[AIRIS MCP Gateway](https://github.com/agiletec-inc/airis-mcp-gateway)** - MCP integrated gateway
-- **[mindbase](https://github.com/agiletec-inc/mindbase)** - AI conversation knowledge management
-- **[superagent](https://github.com/agiletec-inc/superagent)** - Claude Code enhancement framework
-- **[airis-translate](https://github.com/agiletec-inc/airis-translate)** - Native macOS translation tool
-- **[selfhosted-supabase-mcp](https://github.com/agiletec-inc/selfhosted-supabase-mcp)** - Supabase MCP server
-- **[cmd-ime](https://github.com/agiletec-inc/cmd-ime)** - macOS input method switcher
-
-#### Projects We Contribute To
-
-Open source projects we actively contribute to:
-
-- **[SuperClaude Framework](https://github.com/SuperClaude-Org/SuperClaude_Framework)** - AI development framework
-
-Please refer to each project's `CONTRIBUTING.md` for specific guidelines.
-
----
-
-### 2. Issue Reporting
-
-Bug reports and feature requests are accepted through each project's Issues.
-
-**Good Issue Examples**:
-- Clear reproduction steps
-- Description of expected vs actual behavior
-- Environment information (OS, version, etc.)
-
----
-
-### 3. Pull Requests
-
-**Contribution Flow**:
-
-1. **Fork**: Fork the project
-2. **Branch**: Create a `feature/your-feature-name` branch
-3. **Implement**: Implement code changes
-4. **Test**: Add and run tests
-5. **Commit**: Follow [Conventional Commits](https://www.conventionalcommits.org/)
-6. **Push**: Push to your fork
-7. **PR**: Create Pull Request to the original repository
-
-**Commit Message Format**:
-```
-feat: add new API endpoint for user management
-fix: correct authentication token validation
-docs: update README installation section
-chore: update dependencies
-refactor: simplify error handling logic
-```
-
----
-
-### 4. Code Standards
-
-#### General Principles
-- **SOLID**: Single Responsibility, Open/Closed, Liskov Substitution
-- **DRY**: Don't Repeat Yourself
-- **YAGNI**: You Aren't Gonna Need It
-- **KISS**: Keep It Simple, Stupid
-
-#### TypeScript/JavaScript
-- Follow ESLint + Prettier configuration
-- Explicit type definitions
-- Comments explain WHY, not WHAT
-
-#### Python
-- Follow Black + Ruff configuration
-- Type hints required (Python 3.12+)
-- Docstrings (Google Style)
-
----
-
-### 5. Documentation
-
-**Required Documentation**:
-- `README.md`: Project overview, installation instructions
-- `ARCHITECTURE.md`: Technical architecture (complex projects only)
-- `CHANGELOG.md`: Version history
-- Inline Comments: Explain complex logic
-
-**Documentation Principles**:
-- English preferred (technical terms in English)
-- Include examples
-- Keep up to date
-
----
-
-## 💡 Contribution Ideas
-
-### Beginner-Friendly
-- Fix documentation typos
-- Add sample code
-- Translations (English ↔ Japanese)
-- Improve test coverage
-
-### Intermediate
-- Bug fixes
-- New feature implementation
-- Performance improvements
-- Refactoring
-
-### Advanced
-- Architecture improvements
-- Security enhancements
-- Scalability improvements
-- New product proposals
-
----
-
-## 🛡️ Security
-
-If you discover a security vulnerability, **do not create a public issue**. Please contact us directly:
-
-📧 **security@agiletec.net**
-
-See [SECURITY.md](./SECURITY.md) for details.
-
----
-
-## 📋 Code Review Process
-
-1. **Automated Checks**: CI/CD (lint, test, build) must pass
-2. **Code Review**: Maintainers review within 1-3 business days
-3. **Feedback**: Comments if changes are requested
-4. **Approval**: Merge after approval
-
-**Review Criteria**:
-- Code quality
-- Test coverage
-- Documentation clarity
-- Alignment with vision
-
----
-
-## 🌟 Recognition
-
-Contributors are recognized through:
-- Listed in project's `CONTRIBUTORS.md`
-- Acknowledged in release notes
-- Special thanks for significant contributions
-
----
-
-## 🤔 Questions?
-
-If you have questions, feel free to reach out:
-
-- **GitHub Discussions**: Each project's Discussions
-- **Email**: hello@agiletec.net
-- **X (Twitter)**: [@agiletec_inc](https://x.com/agiletec_inc)
-
----
-
-## 📄 License
-
-Contributed code follows each project's license (typically MIT License).
-
----
-
-**Thank you for your cooperation!**
-
-Let's move forward together to realize our vision of "in-house development for every company."
-
-— Agiletec Inc. Team
+contributionには対象repoのlicenseが適用されます。

policies/ci-cd-trigger-strategy.md

@@ -120,27 +120,6 @@ not optional decoration.
   pattern (`.env`, `.env.local`, `.env.*`, `*.pem`, `*credentials*`)
 - Dependabot enabled (free, default for public)
 
-## Implementation status (2026-06-12)
-
-> Per-repo adoption status, gap analysis, and the prioritized remediation
-> checklist live in the companion doc
-> [`ci-cd-standardization-status.md`](./ci-cd-standardization-status.md).
-
-- **airis-studio**: merge=deploy レーン稼働 (deploy-stg.yml、既存 ARC runner
-  + nerdctl direct-bake。ホスト常駐物ゼロ)。bump PR / 耐久マージャは撤去済み。
-  stg=本番の single-environment 運用。
-- **agiletec**: CF Workers (corporate/dashboard) は main push → wrangler deploy
-  (ARC) で stg 自動。k3s レーンは廃止済み (agile-server #400 で manifests 全削除、
-  bump 機械と bumper App credential も 2026-06-12 に全撤去)。prd は
-  Cloudflare (frontend promote = 中井手動) + Supabase (migrations / Edge
-  Functions = main マージで CI 自動 deploy・drift gate 付き、上記 §3 例外)。
-- **Public repos**: release.yml は配布物の公開用として継続 (cmd-ime /
-  airis-mcp-gateway が参照実装)。
-- **旧 release-driven stg deploy 標準 (plan 520) は superseded** (2026-06-12)。
-- **bump PR 機構は org から完全撤去** (2026-06-12): auto-merge-bumps.yml 削除、
-  bump/* ブランチ削除、DEPLOY_BUMPER_* / IMAGE_BUMPER_* org credential 削除、
-  agiletec-image-bumper App はアンインストール。
-
 ## References
 
 - [GitHub Actions: events that trigger workflows](https://docs.github.com/en/actions/writing-workflows/choosing-when-your-workflow-runs/events-that-trigger-workflows)

policies/org-quality-gate.md

@@ -1,10 +1,7 @@
-# Organization quality gate contract
+# Organization quality gate契約
 
-The organization-required workflow runs the same gate for every repository: stack detection picks
-the applicable generic language jobs (Node, Bun, Python, Rust, Swift), and the secret scan,
-feature-flag check, and final aggregator always run.
+organization required workflowは全repoへ同じgateを適用する。stack detectionがNode、Bun、Python、Rust、Swiftの
+該当jobを選び、secret scan、feature flag check、final aggregatorは常に実行する。
 
-There is no per-repository exception mechanism (owner ruling 2026-07-24). A repository with its own
-native CI still runs the generic stack jobs; duplication is accepted in exchange for a single
-uniform gate. Do not reintroduce repository-name conditions or opt-out inputs into
-`org-quality-gate.yml` / `quality-gate.yml`.
+repo別の例外機構は設けない。native CIを持つrepoでもgeneric stack jobを実行し、単一で均一なgateを優先する。
+`org-quality-gate.yml` / `quality-gate.yml`へrepo名条件やopt-out inputを再導入しない。