coulomb/prj-unattended-progress-company
4
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions
prj-unattended-progress-com.../SCOPE.md
tegwick 0dd1da1366 Establish project goal, register scaffolding, and draft UPC-WP-0001. 
Add GOAL.md for profitable self-organizing Binky Hedgehog GmbH with minimal
CEO governance, prj-flavor SCOPE/AGENTS/classification, and foundation
workplan UPC-WP-0001 to map gates G1–G9 and child streams.
2026-08-09 22:58:26 +02:00

2.2 KiB
Raw Permalink Blame History

Scope

Project authority

This repository owns the cross-repository project goal, success gates, sequencing, dependency map, risks, and consolidated evidence for turning Binky Hedgehog GmbH into a profitable self-organizing company with minimal CEO time and governance.

It does not own the production company canon, product implementations, or runtime control plane being operated day to day.

Participating repositories

Initial participants include:

Repo Role
binky-control Company control plane / canon, reactivation, offers, queues
ops-warden Tenant secrets, credential routing, custody
the-custodian Fleet standards, project-flavor and work-record canon
state-hub Coordination index / read model (not authority for work records)
Ecosystem pillars as needed Coulomb, Net Kingdom, Railiance, product repos for offers and delivery

Additional repos are added when a gate or workplan depends on them; list them here rather than inventing parallel project homes.

In scope

  • Project goal, invariants, and checkable success gates (GOAL.md).
  • Cross-repo sequencing from legal reactivation → company OS → unattended loops → first offer → first revenue → founder-load envelope.
  • Mapping autonomy lanes, office-hour rhythm, and decision packaging to concrete work in participating repos.
  • Dependency and risk register for the unattended-progress company model.
  • Acceptance evidence pointers for each gate (links, not duplicated task lists).

Out of scope

  • Hosting production implementation code or customer-facing services here.
  • Replacing binky-control as the durable company brain / canon.
  • Copying child-repo workplan task lists into this project.
  • Secrets, credentials, or raw financial account data in git.
  • Rename to Operational Knowledge GmbH, multi-customer scale, or ok.com acquisition narrative (beyond directional framing).

Work-record rule

The project records milestones, dependencies, gates, decisions, and cross-repo acceptance. Each participating repository owns its implementation workplans and evidence. Project records link those workplans by stable identifier rather than copying their task lists.