feat(ops): non-code workspace with self-refreshing metrics - #15
Merged
Conversation
Growth, funding, partnerships, and content had no home. Finished artifacts existed (logic model, fellowship application, brand handbook) but the ongoing work did not, and the two richest folders were gitignored so no agent could read them. Structure: - ops/METRICS.md — GENERATED from production by scripts/ops-metrics.ts. Every stale doc in this repo went stale because a human had to remember to update a number (VERSION.md sat at v1.1.0-alpha for seven months). These numbers update themselves. - ops/growth/ — the priority. 53 approved reviews, 40 of 91 buildings with none, and only 2 of 27 landlords clearing the three-review display threshold. - ops/funding/ — pipeline plus reusable narrative blocks with no hard-coded figures. - ops/partners/ — organization landscape. Partners are not a nice-to-have channel; they are what makes the depth strategy safe to execute. - ops/content/ — approved language, tied to brand.md voice rules. - ops/AGENTS.md — maintenance rules for agents. Privacy boundary: ops/private/ is gitignored (README excepted). Named individuals and private conversations never enter a tracked file. The repo is currently public, and a committed list of who spoke to you is the exact artifact this project argues against. The rule holds even if the repo goes private, since visibility can change. scripts/ops-metrics.ts invokes wrangler's JS entry via process.execPath rather than the npx/.cmd shims — Node 24 refuses to spawn .cmd without shell:true, and shell:true would force SQL through shell quoting. Read-only against production; every query is a SELECT. Verified: npm run check clean, 510/510 tests, build clean. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Deploying ratemyplace with
|
| Latest commit: |
5b1f0b7
|
| Status: | ✅ Deploy successful! |
| Preview URL: | https://2d25037b.ratemyplace-64y.pages.dev |
| Branch Preview URL: | https://ops-non-code-workspace.ratemyplace-64y.pages.dev |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Growth, funding, partnerships, and content had no home in the repo. Finished artifacts existed (logic model, fellowship application, brand handbook) but the ongoing work did not, and the two richest folders were gitignored so no agent could read them.
Structure
ops/METRICS.mdscripts/ops-metrics.tsops/growth/ops/funding/ops/partners/ops/content/ops/AGENTS.mdops/private/The anti-rot mechanism
npm run ops:metricsqueries production read-only and rewritesops/METRICS.md. Every stale doc found in this repo went stale because a human had to remember to update a number —VERSION.mdsat at v1.1.0-alpha for seven months. These update themselves.It already surfaced a figure nobody had: 40 of 91 buildings have zero reviews.
Privacy boundary
ops/private/is gitignored (README excepted). The repository is currently public, and a committed list of who spoke to you and what they said is the exact artifact this project argues against. The rule holds even if the repo goes private, since visibility can change and a file never committed cannot leak.Note on the script
scripts/ops-metrics.tsinvokes wrangler's JS entry viaprocess.execPathrather than thenpx/.cmdshims — Node 24 refuses to spawn.cmdwithoutshell: true, andshell: truewould force SQL through shell quoting.Read-only against production; every query is a SELECT.
Verified:
npm run checkclean, 510/510 tests, build clean.🤖 Generated with Claude Code