From da6d7b5f1bcfeb0462e6730eae7d844898b902f8 Mon Sep 17 00:00:00 2001 From: itsablabla <236483548+itsablabla@users.noreply.github.com> Date: Sun, 19 Apr 2026 16:33:31 +0000 Subject: [PATCH 1/2] Add Capy repository setup files for agent configuration --- .capy/BUILD.md | 5 +++++ .capy/CAPTAIN.md | 6 ++++++ .capy/REVIEW.md | 6 ++++++ .capy/settings.json | 20 ++++++++++++++++++++ 4 files changed, 37 insertions(+) create mode 100644 .capy/BUILD.md create mode 100644 .capy/CAPTAIN.md create mode 100644 .capy/REVIEW.md create mode 100644 .capy/settings.json diff --git a/.capy/BUILD.md b/.capy/BUILD.md new file mode 100644 index 00000000..efcb3568 --- /dev/null +++ b/.capy/BUILD.md @@ -0,0 +1,5 @@ +- Treat GARZA OS as a monorepo: `mcp-servers/` for MCP implementations, `services/` for app services, `workers/` for Cloudflare Workers, `infra/` for state and manifests, `operations/` for runbooks/templates, `docs/` and `prompts/` for operating guidance. +- Before adding code, check adjacent services plus `templates/` and `docs/stack-first.md`; reuse existing patterns and extend current services before creating a new implementation. +- Keep decisions stack-first: prefer Fly.io, Cloudflare Workers, n8n Cloud, Supabase, and GitHub Actions over new VPSes, ad hoc schedulers, extra databases, or one-off infrastructure. +- Never hardcode secrets or credentials. Follow the repo's existing secret-management paths and deployment conventions. +- When touching infra state, deployment manifests, or automation config, keep related `infra/` state files, lock conventions, and service manifests coherent with the code change. diff --git a/.capy/CAPTAIN.md b/.capy/CAPTAIN.md new file mode 100644 index 00000000..9ab78a94 --- /dev/null +++ b/.capy/CAPTAIN.md @@ -0,0 +1,6 @@ +- GARZA OS is a monorepo for Jaden Garza's personal AI operating system: a unified intelligence layer spanning services, automations, and operational context. +- Major planning areas are `mcp-servers/`, `services/`, `workers/`, `infra/`, `operations/`, plus supporting `docs/`, `prompts/`, `templates/`, and workflow/config directories. +- Craft is the conceptual source of truth for system knowledge; repo docs and prompts provide the operational context agents should follow when planning implementation work. +- Prefer extending an existing service, worker, template, or workflow before proposing a new component. +- New work should generally target Fly.io, Cloudflare Workers, n8n, Supabase, or GitHub Actions. Treat DigitalOcean as legacy/phasing out. +- For infra or operations changes, account for `infra/` state-management conventions, lock files, deployment manifests, and existing runbooks/docs before planning mutations. diff --git a/.capy/REVIEW.md b/.capy/REVIEW.md new file mode 100644 index 00000000..c7d3d2b8 --- /dev/null +++ b/.capy/REVIEW.md @@ -0,0 +1,6 @@ +- Prioritize stack-first violations: flag changes that introduce new infrastructure or bypass Fly.io, Workers, n8n, Supabase, or GitHub Actions without strong justification. +- Check for secret leakage, hardcoded credentials, unsafe `.env` usage, or docs/code that expose operational access details. +- Verify service contracts across routers, MCP tools, workers, dashboards, and infra manifests so interfaces stay aligned. +- When changes affect deployment, operations, or infra, confirm repo docs/state manifests remain consistent with the implementation and audit trail expectations in `infra/`. +- Flag unnecessary churn across unrelated monorepo areas; prefer tightly scoped edits. +- Ignore style-only nits unless they affect clarity, maintainability, or correctness. diff --git a/.capy/settings.json b/.capy/settings.json new file mode 100644 index 00000000..9994953a --- /dev/null +++ b/.capy/settings.json @@ -0,0 +1,20 @@ +{ + "$schema": "https://capy.ai/settings.schema.json", + "hooks": { + "setup": [ + "./scripts/setup.sh" + ], + "terminals": [ + { + "name": "garza-dashboard", + "command": "cd /home/garza-os-github/services/garza-dashboard && npm start" + } + ], + "previews": [ + { + "name": "garza-dashboard", + "port": 8080 + } + ] + } +} From 9b944e381bd93e55db93e7969abecc3a067a84dd Mon Sep 17 00:00:00 2001 From: itsablabla <236483548+itsablabla@users.noreply.github.com> Date: Sun, 19 Apr 2026 16:38:38 +0000 Subject: [PATCH 2/2] chore(capy): fix setup and validation guidance --- .capy/BUILD.md | 1 + .capy/settings.json | 5 +++-- 2 files changed, 4 insertions(+), 2 deletions(-) diff --git a/.capy/BUILD.md b/.capy/BUILD.md index efcb3568..299ff9d1 100644 --- a/.capy/BUILD.md +++ b/.capy/BUILD.md @@ -1,5 +1,6 @@ - Treat GARZA OS as a monorepo: `mcp-servers/` for MCP implementations, `services/` for app services, `workers/` for Cloudflare Workers, `infra/` for state and manifests, `operations/` for runbooks/templates, `docs/` and `prompts/` for operating guidance. - Before adding code, check adjacent services plus `templates/` and `docs/stack-first.md`; reuse existing patterns and extend current services before creating a new implementation. - Keep decisions stack-first: prefer Fly.io, Cloudflare Workers, n8n Cloud, Supabase, and GitHub Actions over new VPSes, ad hoc schedulers, extra databases, or one-off infrastructure. +- Reach for the repo's documented verification entrypoints first: `./scripts/test.sh` for tests, `garza health` for service health, and `garza status` for deployment/status checks. - Never hardcode secrets or credentials. Follow the repo's existing secret-management paths and deployment conventions. - When touching infra state, deployment manifests, or automation config, keep related `infra/` state files, lock conventions, and service manifests coherent with the code change. diff --git a/.capy/settings.json b/.capy/settings.json index 9994953a..204705da 100644 --- a/.capy/settings.json +++ b/.capy/settings.json @@ -2,12 +2,13 @@ "$schema": "https://capy.ai/settings.schema.json", "hooks": { "setup": [ - "./scripts/setup.sh" + "./scripts/setup.sh", + "cd services/garza-dashboard && npm install" ], "terminals": [ { "name": "garza-dashboard", - "command": "cd /home/garza-os-github/services/garza-dashboard && npm start" + "command": "cd services/garza-dashboard && npm start" } ], "previews": [