Compare commits

...

2 commits

Author SHA1 Message Date
c1597691e4 BINKY-WP-0001 complete: bootstrap tasks verified and closed
- T01: generated files reviewed — INTENT is ratified canon v1.0; SCOPE
  caveat replaced with review stamp
- T02: local verification commands added to AGENTS.md (fix-consistency,
  agent-harness validate, bridge syntax check, queue YAML parse)
- T03: satisfied long ago — BINKY-WP-0002..0004 exist and are hub-synced

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
2026-07-18 13:48:40 +02:00
0978a0796e rhythm: 2026-07-18 daily brief + DEC-2026-003 cutover go package
Queue hygiene: DecisionQueue gained the missing prepared package for the
now-unblocked BINKY-WP-0004-T06 cutover; OfficeHourQueue and
AutopilotWorkQueue healthy (hub fix-consistency skipped — green lane,
no network).

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
2026-07-18 13:48:24 +02:00
5 changed files with 67 additions and 7 deletions

View file

@ -1,5 +1,24 @@
# binky-control — Agent Instructions
## Local verification (BINKY-WP-0001-T02)
This is a markdown control-plane repo — no build. Before committing, verify
what you touched:
```bash
# Workplan/task frontmatter ↔ hub sync (also registers new workplans)
statehub fix-consistency # or hub MCP check_repo_consistency
# Agent instance manifest (.kaizen/schedule.yml + harness fields)
agent-harness validate --target . --strict
# Rhythm bridge script syntax (if edited)
bash -n scripts/rhythm-session.sh
# Queue docs: YAML blocks must parse — quick check
python3 -c "import yaml,re,sys; t=open(sys.argv[1]).read(); [yaml.safe_load(m) for m in re.findall(r'\`\`\`yaml\n(.*?)\`\`\`', t, re.S)]" DecisionQueue.md
```
## Repo Identity
**Purpose:** binky-control is the company control plane ("company brain") for Binky Hedgehog GmbH's transformation into Operational Knowledge GmbH, holding the canon (intent, policies, plans), work queues, and registries that give agents and the solo founder shared situational awareness with executable next steps.

View file

@ -22,7 +22,26 @@ fallback_if_no_response: ""
## Open decisions
*(none)*
### DEC-2026-003 — Go for executor cutover (retire the cron bridge)
```yaml
id: DEC-2026-003
title: "Execute BINKY-WP-0004-T06: enable harness-scheduled Binky definitions, retire workstation cron bridge"
lane: yellow
status: prepared
created_at: "2026-07-18"
needed_by: "soft — each day of delay keeps the workstation cron dependency alive"
attention_cost: "~5 min: skim runbook gates, say go/no-go"
agent_recommendation: "approve — all three gates cleared as of 2026-07-18
(DEC-2026-002 resolved; Red-lane Lanes 23 provisioned; harness live on
Railiance with tenant #1 onboarded and three definition proof runs)"
evidence:
- integrations/executor-cutover-runbook.md
- integrations/harness-tenant-onboarding.md
options: [approve, reject, revise, defer]
fallback_if_no_response: "cron bridge keeps running; no degradation, but
workstation-independence milestone stalls"
```
## Resolved decisions

View file

@ -1,7 +1,7 @@
# SCOPE
> This file was generated by `statehub register`. Refine it as the repository
> boundaries become clearer.
> Reviewed 2026-07-18 (BINKY-WP-0001-T01): content reflects the ratified
> canon (INTENT v1.0, DEC-2026-001).
## One-liner

View file

@ -0,0 +1,22 @@
# Daily Brief — 2026-07-18
## Decide now
- **DEC-2026-003 — Go for executor cutover** (DecisionQueue.md): all three
gates cleared today; approving lets agents run the cutover runbook and
retire the workstation cron bridge. ~5 min.
## Progress
- **Workstation-independent executor is deployable**: agent-harness deployed
on Railiance (HARNESS-WP-0001-T06), binky-control onboarded as tenant #1
with instance manifest and three clean definition proof runs (T07,
`.kaizen/schedule.yml` + `integrations/harness-tasks/`). BINKY-WP-0004-T06
cutover is unblocked — only the founder go remains (see Decide now).
## Risks
- No register changes. (Cutover, once approved, removes the single-workstation
dependency of the daily rhythm.)
## Best next hour
Approve DEC-2026-003 — one 5-minute go decision unlocks retiring the cron
bridge and completes BINKY-WP-0004. Carry-over: the two suspicious mails
flagged in `mailmeta/mail-log.md` still await a human glance.

View file

@ -4,7 +4,7 @@ type: workplan
title: "Bootstrap State Hub integration"
domain: infotech
repo: binky-control
status: ready
status: done
owner: codex
topic_slug: custodian
created: "2026-07-16"
@ -20,7 +20,7 @@ binky-control is the company control plane ("company brain") for Binky Hedgehog
```task
id: BINKY-WP-0001-T01
status: todo
status: done
priority: high
state_hub_task_id: "f348200e-71dc-4188-bab9-bd3699c8cb07"
```
@ -32,7 +32,7 @@ Replace generated placeholders with repo-specific facts where needed.
```task
id: BINKY-WP-0001-T02
status: todo
status: done
priority: high
state_hub_task_id: "26d0b9ff-a75f-4474-b2e5-990eefaeac3b"
```
@ -45,7 +45,7 @@ changes confidently.
```task
id: BINKY-WP-0001-T03
status: todo
status: done
priority: medium
state_hub_task_id: "30562538-d5e8-4355-a422-6da1df2d35c2"
```