盤點與就緒判斷
檢查 repo、模組、命令、權限、測試與部署能力;輸出 READY 或 NOT_READY。
本手冊是 Type 3 合作夥伴的統一控制入口:fork 私有參考系統、選擇模組、加入客製、建立 Docker image、安裝到自行選擇的環境,並持續接收 upstream 更新。閱讀本頁不需要登入。
核准的 private repo:github.com/rwanexus/capital-fork。取得權限並 clone/fork 後先執行 ./caas --format json doctor。Repo 尚未具備的能力必須回報 NOT_READY;公開文件不會賦予 repo、雲端或部署權限。
AI Agent Task Menu
每次工作都遵循 DISCOVER → PREFLIGHT → PLAN → AUTHORIZE → EXECUTE → VERIFY → EVIDENCE。唯讀盤點可直接進行;寫入 repo、雲端或資料以前必須確認精確目標。
檢查 repo、模組、命令、權限、測試與部署能力;輸出 READY 或 NOT_READY。
建立 private fork、驗證 origin/upstream、記錄 baseline,使用 feature branch。
驗證 entitlement、dependencies 與 digest,產生精確 composition lock。
優先使用 profile、form/workflow definition 與 private extension。
完成角色、頁面、API、表單與隔離測試,固定 image digest 與證據。
部署到 partner 明確指定的 Linux/GCP/AWS,使用 canary 與 rollback point。
監控服務、建立離機備份,並以隔離還原證明資料與物件可讀。
建立 scoped upgrade PR;保留 partner extension,衝突時停止而不覆寫。
以 synthetic evidence 開 Issue/PR;資安問題使用 private reporting。
驗證 release evidence,或以保留的 image 與 restore point 安全回復。
客製化界線
升級成本取決於合作夥伴程式碼與 upstream 的重疊程度,而不是 Docker。能用設定完成,就不要改共用模組。
partner/profile.json品牌、網域、語系與安全設定。
partner/locks/composition.lock.json由 ./caas compose 產生啟用模組、精確版本、雜湊與相依。
partner/extensions/*依穩定 contract 建立私有流程、報表與整合。
source/modules/*可重用修正送回 upstream,不永久保留 private patch。
AI Agent 前置檢查
Discovery 只能唯讀。任何失敗都要產生 blocker 報告,不能自行創造替代指令或檔案。
合作夥伴自行託管
合作夥伴可選 GCP、AWS、其他雲端或自有 Linux。以下只是起始建議,正式上線須依啟用模組與負載量測。
Linux VM + Docker Compose;例如 GCP Compute Engine 或 AWS EC2。
Linux VM,可選 Cloud SQL/RDS 與 GCS/S3。
只在團隊已有維運能力時使用既有容器平台;Kubernetes 非必要。
最低安全基線:只公開 HTTP/HTTPS;PostgreSQL、Redis 與物件儲存保持私有;使用 IAP、AWS SSM 或核准的 bastion;離機加密備份並驗證還原。
持續開發
在 partner private fork 開發。品牌、導覽、私有流程與整合留在 partner layer。同步 upstream 時使用 upgrade branch,審閱 release notes 與 diff,跑完受影響測試後再經 PR 合併。
Issue → 修正 → 發行
固定目前 image digest,備份資料庫與檔案,並實際驗證還原。
秘密不得進 Git;真正機密的程式碼放在獨立 private extension package。
記錄版本、測試、migration、digest、部署、rollback、未解風險與下一步。
This manual is the Type 3 partner control point for forking the private reference system, composing modules, adding extensions, building a Docker image, installing into a partner-selected environment, and maintaining upstream upgrades. No sign-in is required.
Approved private repo: github.com/rwanexus/capital-fork. After access and clone/fork, run ./caas --format json doctor first. Missing repository capabilities must be reported as NOT_READY; public documentation grants no repository, cloud, or deployment authority.
AI Agent Task Menu
Every task follows DISCOVER → PREFLIGHT → PLAN → AUTHORIZE → EXECUTE → VERIFY → EVIDENCE. Read-only discovery can proceed; repository, cloud, or data writes require an exact authorized target.
Inventory repository, modules, commands, permissions, tests, and delivery capabilities.
Validate origin/upstream, record the baseline, and use a protected feature workflow.
Validate entitlement, dependencies, and digests; emit an exact composition lock.
Prefer profiles, form/workflow definitions, and private extensions.
Run role, page, API, form, and isolation tests; pin image digest and evidence.
Use the partner's named Linux/GCP/AWS target, canary, and rollback point.
Monitor services, keep off-host backups, and prove isolated restoration.
Open a scoped upgrade PR, preserve extensions, and stop on source conflicts.
Use synthetic evidence for issues/PRs and private reporting for security findings.
Verify release evidence or restore from the retained image and restore point.
Customization contract
Upgrade effort follows overlap with upstream, not Docker. Prefer configuration over changing shared modules.
partner/profile.jsonBrand, domain, locale, and safe settings.
partner/locks/composition.lock.json./caas compose records exact enabled versions, hashes, and dependencies.
partner/extensions/*Private workflows, reports, and integrations against stable contracts.
source/modules/*Contribute reusable fixes upstream instead of carrying permanent patches.
AI agent preflight
Discovery is read-only. A failed check produces a blocker report, never an improvised command or look-alike file.
Partner-owned hosting
Choose GCP, AWS, another cloud, or owned Linux. These are starting points, not requirements; size production from measured workloads.
Linux VM + Docker Compose, such as GCP Compute Engine or AWS EC2.
Linux VM, optionally with Cloud SQL/RDS and GCS/S3.
Use an existing container platform only when the team supports it. Kubernetes is optional.
Expose only HTTP/HTTPS; keep PostgreSQL, Redis, and object storage private; prefer IAP, AWS SSM, or an approved bastion; keep encrypted backups off-host and verify restore.
Ongoing development
Develop in the partner private fork. Keep branding, navigation, private workflows, and integrations in the partner layer. Sync upstream into an upgrade branch, review release notes and diffs, run affected tests, then merge through PR.
Issue → fix → release
Pin the current image digest, back up database and files, and verify restore.
Keep secrets outside Git and confidential code in a separate private extension package.
Record versions, tests, migrations, digest, deployment, rollback, risks, and next action.