prj-unattended-progress-company/GOAL.md

repo	repo_flavor	project_status	started	reviewed
prj-unattended-progress-company	project	active	2026-08-09	2026-08-09

Project goal

Outcome

Make Binky Hedgehog GmbH a profitable, self-organizing company that advances with minimal founder time and governance from Bernd Worsch as CEO/Geschäftsführer.

"Self-organizing" means the company can detect what needs doing, prepare safe next steps, execute high-autonomy work unattended, and surface only the decisions that must remain human — without stalling when the founder is offline.

"Minimal time and governance" means the default CEO load is roughly 1–3 hours per day outside business hours plus about two office-hour days per month, with attention spent on approve/reject packages, risk acceptance, and strategic direction — not on routine coordination, status chasing, or ad-hoc firefighting.

This project coordinates the cross-repo operating model, company reactivation, offer/revenue path, and autonomy stack. Production implementation, company canon, and durable product code live in participating repositories (especially binky-control and ecosystem pillars), not in this project repo.

Strategic framing

Binky Hedgehog GmbH is the commercial vessel for the operational-knowledge ecosystem (Coulomb / Net Kingdom / Railiance / OK). Long-term identity: Operational Knowledge GmbH. This project's job is not brand mythology; it is to reach profitable unattended progress as a solo-founder company OS.

Invariants

1. Human-on-the-loop, not human-in-the-loop. "Ask Bernd" is never the default. Agents continue with the safest useful next step; uncertainty triggers research, comparison, or a prepared decision package.
2. Autonomy lanes are binding. Green/Blue proceed unattended; Yellow is prepared for review; Orange batches to office hours; Red stays human-only (signing, bank/payment execution, contracts, sensitive legal/HR/security, external company commitments, risk acceptance).
3. Local files remain authoritative. Workplans, decisions, and company records originate in repos; State Hub is a read/index model synced from files — never the reverse.
4. This repo does not host production implementation of company systems or product code. It owns goal, gates, sequencing, dependency map, risks, and consolidated evidence.
5. Founder attention is budgeted. Briefs and decision cards are evidence-backed with approve/reject options; open-ended dumps are out of bounds.
6. Secrets never land in this repo (or chat, workplans, evidence dumps). Route credentials through ops-warden / OpenBao patterns.
7. Profitability is real cash, not ecosystem vanity metrics alone — first paid revenue and a path to repeatable contribution margin matter before rename or category claims.

Success gates

The project goal is achieved only when all of the following are true (with evidence linked from this repo):

Company vessel

• G1 — Administratively clean. Handelsregister, address, tax/StB mandate, bookkeeping workflow, and banking access are current and usable for ordinary operations (binky-control Phase 1 / S1).
• G2 — Company OS active. Canon, autonomy policy, decision queue, office-hour rhythm, and control loops are in force so work does not depend on ad-hoc founder memory (binky-control S2).

Unattended progress

• G3 — Dogfood loop closed. At least one end-to-end internal loop runs unattended under Green/Blue policy and produces auditable progress without founder mid-flight steering (S3).
• G4 — Founder load within budget. Measured over a sustained window (recommended: ≥30 calendar days), CEO time stays within the 1–3 h/day + ~2 office-hour days/month envelope for routine company ops, with Red-lane exceptions logged rather than becoming the default.

Profitability

• G5 — External offer published. At least one concrete offer is public and sellable (S4).
• G6 — First paid revenue. At least one external customer payment is received and booked (S5).
• G7 — Repeatable path. A productized service or software-supported delivery path exists with unit economics that can cover run costs without perpetual founder heroics (S6–S7 directionally; full multi-customer scale is residual to durable product repos).

Governance minimum

• G8 — Decision surface is thin. Outstanding Yellow/Orange items are packaged; Red items are few and explicit; no material company work is blocked solely because "nobody asked Bernd."
• G9 — Residuals owned outside this project. Every unfinished obligation has a live work record in a permanent repo (or cancelled with rationale).

Non-goals (this project)

• Becoming a permanent portfolio database or second company canon (that is binky-control and durable product repos).
• Hosting production services, SaaS deployables, or customer data.
• Renaming to Operational Knowledge GmbH or pursuing ok.com-level brand outcomes (those are later milestones beyond this project's gates).
• Maximizing agent activity for its own sake without revenue or load reduction.

Project retirement

This repository is temporary. It may be completed and archived when:

1. every success gate above has accepted evidence;
2. residuals have live owners and work records outside this repository;
3. durable operating policies, offers, and architecture decisions are promoted into permanent homes (binky-control, product repos, or canon);
4. project workplans are finished, cancelled with rationale, or handed off;
5. a completion record exists under history/ listing evidence, participating repos, promoted artefacts, and remaining operational obligations;
6. project_status is set to completed then archived, and the forge copy is made read-only.

Retirement means archival, not deletion. The repository remains the provenance record for how the unattended-progress company model was established.