coulomb/binky-control
4
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions
binky-control/SCOPE.md
tegwick 062947c91a
All checks were successful
Work Records / validate (push) Successful in 23s
Details
docs: residual convention + AWQ-011/012 handoffs for WP-0006 
Align AGENTS, AutonomyPolicy, SCOPE, OperatingRhythm with fleet residual
role (live intakes, not SCOPE prose). Capture BINKY-WP-0006 leftovers as
AWQ-011 (brief-weekly) and AWQ-012 (open-weights retarget).
2026-07-22 18:15:45 +02:00

1.6 KiB
Raw Permalink Blame History

SCOPE

Reviewed 2026-07-18 (BINKY-WP-0001-T01): content reflects the ratified canon (INTENT v1.0, DEC-2026-001).

One-liner

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.

Core Idea

binky-control exists to provide the capability described in INTENT.md.

In Scope

  • Company canon: intent, policies (autonomy lanes), success milestones
  • Queues for decisions, office-hour batches, and autopilot work
  • Registries for founder/agent shared situational awareness
  • Operating the human-on-the-loop, unattended-progress stack
  • Dogfooding ecosystem capabilities on company operations

Out of Scope

  • Building the ecosystem pillars themselves (Coulomb, Net Kingdom, Railiance)
  • Product/service source code and delivery artifacts
  • Human-only actions: signing, contracts, payments, legal/HR/security decisions
  • Sister-repo concerns tracked in unattended-progress-company
  • Residual / follow-up work parking — unfinished leftovers from closed workplans are work records (intake in AutopilotWorkQueue.md, next workplan, decision, engagement), not SCOPE bullets. See fleet canon work-record-types_v0.1.md § Residuals.

Current State

  • Early draft stage: single initial commit, INTENT.md at draft v0.1 (2026-07-16), referenced policy/milestone docs not yet present in the repo.

Getting Oriented

  • Start with: INTENT.md
  • Agent instructions: AGENTS.md
  • Workplans: workplans/