coulomb/binky-control
4
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions
binky-control/integrations/harness-tenant-onboarding.md
tegwick 2fbbf9fc76
Some checks failed
Work Records / validate (push) Has been cancelled
Details
BINKY-WP-0006: close with three clean railiance mail cycles 
Host LLM_CONNECT_URL discovery uses ClusterIP when DNS is unreachable;
mail path fails hard if triage fails. Mark T06 done and workplan finished;
update residual docs (OperatingRhythm, cutover runbook, llm-rhythm).
2026-07-22 10:28:11 +02:00

2.5 KiB
Raw Permalink Blame History

agent-harness tenant onboarding — binky-control (HARNESS-WP-0001-T07)

Status: done 2026-07-18; cutover BINKY-WP-0004-T06 completed 2026-07-21; llm-connect continuous intake BINKY-WP-0006 finished 2026-07-22.

Instance manifest

File: .kaizen/schedule.yml (ADR-005 + harness extensions).

Instance activity-core definition Cadence (Europe/Berlin) Lane tool_profile Completion event
coach binky-daily-rhythm weekdays 08:23 green green-commit-only binky_daily_brief
mail-triage binky-weekly-mail-intake Mon 09:37 blue blue-mail-triage binky_mail_intake
review-prep binky-weekly-review-prep Fri 16:43 green green-commit-only binky_weekly_review

Validate:

agent-harness validate --target ~/binky-control --strict

mail-triage and review-prep set blueprint: coach so kaizen-agentic schedule prepare loads the coach persona.

Task files (local / Railiance)

Under integrations/harness-tasks/:

  • daily-rhythm.json
  • mail-intake.json
  • review-prep.json

Run one definition (workstation or railiance01 host install):

source ~/.local/agent-harness/env   # on railiance01
export STATE_HUB_URL="${STATE_HUB_URL:-http://127.0.0.1:18000}"  # remote
# or default http://127.0.0.1:8000 on workstation

agent-harness run --task-file integrations/harness-tasks/daily-rhythm.json

Onboarding proof runs (T07) used a deterministic commit adapter when a full Claude Code session was not required; they still posted the completion events above with detail.repo=binky-control so binky_rhythm_status idempotence can observe them.

Handoff → BINKY-WP-0004-T06

Cleared by T07 + prior work:

  • DEC-2026-002 / agent-harness repo
  • Red-lane Lanes 2–3 (sandbox deploy key + mail AppRole)
  • HARNESS-WP-0001-T06 Railiance deploy + sandbox smoke
  • HARNESS-WP-0001-T07 instance manifest + three definition runs

Still for cutover (founder / Blue with notification):

  1. Attach forgejo write deploy key to coulomb/binky-control (sandbox only today).
  2. activity-core: set enabled: true on the three definitions (governance there).
  3. Wire task intake (HARNESS-WP-0001-T03) or interim pull path.
  4. Three clean scheduled business-day executions, then retire workstation cron bridge.

Rollback: cutover runbook. Do not remove the cron bridge until step 4 passes.