Ops

active ray + harness

Building the COO agent and the harness it runs in. Vault, skills, MCP, observability, deployment rails.

hq.raydata.co

at a glance

Skills
65+
Cron loops
13
Vault docs
2913

open decisions 13

open medium
Copy-paste-wall check misfires on attributed quotes — approve the fix?
Notion task 3d4f7d4936d181488590f0e7e0d7f02b: self-review's copy-paste-wall check cannot distinguish attributed primary-source quotes from lazy paraphrase-avoidance. 6th recurrence since 2026-04 (Reviews 8, 9, 10, 16, 26). Proposed fix: exempt >30-word passages inside a blockquote/italic span with an adjacent citation; unattributed runs still deduct.
2026-09-07
open high
hq.raydata.co Phase 0 step 3 — how to unblock?
Phase 0 build (board-sync + cadence chip rail) is done and re-confirmed twice. Remaining: drain the async-decision queue into /check-board (blocked by auto-mode classifier on a SKILL.md permission), founder sets NOTION_TOKEN/NOTION_BOARD_DATABASE_ID, and a manual chip-rail click-through test. None of the three are Ray-actionable without founder input.
2026-09-03
open medium
X write rail — flip app to Read+Write + regenerate tokens
Post script (~/.claude/scripts/x-post.sh), safety guards, and per-draft approval-page template are built and dry-run verified. Live probe confirms the xmcp X app is read-only. Founder 5-min unblock: Developer Portal -> app permissions -> Read and write, regenerate access token+secret, update the Ray Agent 1Password item. Ray verifies read-write on Done tap. No autonomous posting — every draft still gets its own approval page.
2026-08-30
open high
Support-agent fleet hardening - scope the pass?
The Dwarkesh account of the OpenAI/Hugging Face agent incident maps onto our own fleet: seven exposures checked against live config, including OP_SERVICE_ACCOUNT_TOKEN still in plaintext at line 3 of settings.local.json 82 days after the June harness review rated it critical, one 1Password service account shared by every agent, and 18 headless cron jobs inheriting the whole parent environment. Three scopes offered (A credential-only, B per-agent least privilege, C sandboxed runners plus tamper-evident logs) with the Ray/founder split and estimated hours for each. Ray recommends B.
2026-08-30
open medium
Audit cron's 1-day window — widen scope to catch the 55 invisible failures?
The nightly audit-newsletter-outputs.py cron's ~1-day --since window permanently drops unrepaired failures from scope after 24h; a direct --since 2026-06-01 run shows 55 live failures invisible to the daily cron. Self-review guardrail already shipped (stops false-clean reporting) but the coverage hole itself needs a founder call: (a) weekly wide-window (~60d) re-audit cron, or (b) carry-forward re-inclusion of unresolved failures; plus whether --fix should ever be wired to this (Ray recommends no, read-only surfacing for now).
2026-08-17
open medium
Kids-books-on-Shopify wedge — pick concept + character
Surfaced 2026-05-05, sat in Inbox 89 days with no click-back. Three concept directions (How Things Actually Work / The Curious [Place] / Big Ideas for Small Humans) and three character anchors (Ray-mascot-adapted / original / real kid) sketched. Ray recommends How Things Actually Work + Ray-mascot-adapted. Both-owned: Ray can scaffold the production-pipeline doc once picked.
2026-08-02
open medium
/cross-check phase 3 — unblock criterion
Phase-2 graph annotation is verified done (22 validates / 6 contradicts / 29 supports-position edges across 6 clusters). But the ticket's original "12 docs" unblock criterion matches neither candidate cluster: harness-thesis-dissent is 4 docs as curated, agent-architecture is 13. Needs a human call on which cluster was meant before the phase-3 graph-traversal rewrite can start.
2026-07-29
open medium
Self-review rubric inversion — scope this or park it?
Notion task 3aaf7d49-36d1-8186-be95-f0562b79c5d7 has no scope beyond its title. Traces to a real /improve finding (2026-07-27, from review-log.md Review 20 cycle): the newsletter-frontmatter carve-out list has been extended 9 times in 3 months; proposed fix is a single provenance: field both graders branch on. No build spec exists yet.
2026-07-28
open medium
Vault 06-reference restructure — grant the Bash allow rule?
06-reference/ has grown to 2,317 files, 4.6x the threshold that triggered the per-sender-subfolder proposal. Blocked since 2026-06-26 on an auto-mode classifier denial for SKILL.md-edit subagent dispatch — needs a founder-granted Bash allow rule under ~/.claude/skills/, which would also unblock the related deep-fetch-threshold proposal.
2026-07-26
open medium
/behavior-critic — scope + activation
New source-BLIND critic built that exercises artifacts (runs scripts, clicks forms, calls endpoints) against a written behavior contract, closing the gap named in the openclaw/autoreview teardown. Tested against 6 fixtures: cli/api (3 flawed + 1 clean) all correct with zero false approves; web-interactive blocked by a Playwright browser-lock contention issue, discipline held (no fabricated verdict) but that class unproven end-to-end. Dormant pending founder call on scope priority, web-interactive retest, and whether/how to wire a gate.
2026-07-26
open high
/supervise pattern — activate on the first write-path?
Fresh-eyes supervisor sub-agent built and tested (9 scenarios, 7/7 flawed actions caught, zero false approves), modeled on Project Vend Phase 2 CEO-oversight. Dormant pending founder call on action-class tiering, settings.json hook splice for Gmail create_draft, and future coverage extension.
2026-07-25
open medium
Self-Review: 08-tooling/ scope — carve-out vs new template?
Self-review D-grades unmodified 08-tooling/ build artifacts (no vault frontmatter) because the assessment-note rubric is a category error on code/build artifacts. Founder picks: Option A (add 08-tooling/ to scope-exclusions, low effort) or Option B (new lightweight tooling-artifact filing template, higher effort, more discoverable). Page existed on disk since 2026-07-16 but was never registered in the decisions index.
2026-07-16
open high
verify-action hook splice — activate in settings.json?
Build complete, 6/6 fixture tests pass (em-dash, iMessage chat_id format, Discord external @mention, iMessage length rules). Only remaining step is splicing the PreToolUse hook into settings.json to make it live. Page existed on disk since 2026-06-24 but was never registered in the decisions index, so it never reached the founder.
2026-06-24
closed decisions 14
archived
/improve proposal: deterministic I12 heading validation in process-newsletter WATCH path
→ ARCHIVE
2026-06-30
decided
/weekly-bet-review skill — unblock or archive?
→ ARCHIVE
2026-05-23
decided
Alpaca brokerage account — was yesterday exploration only, or account opened?
→ approve
2026-05-12
decided
Multi-agent skill build-out pipeline with spec gating — file as Notion ticket?
→ APPROVE with refinement — meta pattern confirmed. Founder flagged 4 implementation questions (namespacing, triggering, per-domain test/critic shape, possible task split). Follow-up decision page spawned 2026-05-12-multi-agent-pipeline-implementation-shape. /build-website-discovery (the first worked example) stays Blocked until the shape decision lands.
2026-05-12
decided
hq.raydata.co PR #3 — merge to ship Phase 3.5 single-login UX
→ ARCHIVE — PR #3 was already merged. Parent 'Build hq.raydata.co v1' ticket stays In Progress for ongoing HQ work.
2026-05-11
decided
HQ Phase B: per-bet stack-view UI (Squarely first)
→ ARCHIVE — already merged. HQ is organized as desired; no more Phase B changes anticipated.
2026-05-11
decided
Stripe Atlas Partner Perks audit (5-min check in portal)
→ ARCHIVE — Cloudflare credits unavailable. AWS $5k + Google Ads $500 are the only valuable perks. Not immediate action; logged for future reference at 06-reference/2026-05-12-stripe-atlas-perks-audit-result.
2026-05-11
decided
Foldering decision: where do internal-state-snapshot docs live?
→ APPROVE Option B — state-reviews live at 01-projects/<bet>/state-reviews/. Squarely state-review migrated; SOP filed; audit-script interaction documented (no script change needed).
2026-05-11
decided
/email-extend skill: greenlight draft-and-watch email-loop pattern
→ APPROVE — build greenlit with closed-loop constraint: drafts/replies must route through /decisions/, /board/, and vault. No opaque side channels.
2026-05-11
decided
MOOC + foundational knowledge shortlist — commit to a path?
→ APPROVE — curriculum greenlit, D3 (Tooling U-SME, only paid resource) excluded. All 13 free/open resources approved as 6-12mo path.
2026-05-11
decided
Digital-manufacturing YouTube shortlist — pick channels to register
→ APPROVE — top-3 picks (CNC Kitchen, Teaching Tech, Product Design Online) registered to youtube-channels.json as tier-2 watch-only.
2026-05-11
approved
/weekly-plan + /weekly-status skill pair — greenlight build
→ APPROVE
2026-05-11
archived
Scaffold MAC + Sanity Check bet-stack YAMLs from audits
→ ARCHIVE
2026-05-11
decided
Click-back rail test (sms:ray@raydata.co)
→ Rail confirmed working on both iPhone + Mac. Pattern locked.
2026-05-09

recent vault notes 0

No vault notes match this bet's path prefixes (01-projects/process-newsletter, 01-projects/skill-improvements, 01-projects/self-review, 01-projects/hq-raydata-co, 02-sops, 08-tooling).