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 · 2026-08-09 22:58:26 +02:00 · 0dd1da1366
commit 0dd1da1366
parent cbbee4e15a
7 changed files with 523 additions and 2 deletions
--- a/.repo-classification.yaml
+++ b/.repo-classification.yaml
@ -0,0 +1,33 @@
 repo_classification:
  standard: Repo Classification Standard
  version: "1.0"
  classified_at: "2026-08-09"
  classified_by: human
  category: project
  domain: infotech
  secondary_domains:
    - agents
    - financials
  capability_tags:
    - governance
    - orchestration
    - automation
    - operations
    - coordination
  business_stake:
    - operations
    - execution
    - automation
    - finance
    - people
  business_mechanics:
    - intention
    - coordination
    - operation
    - control
    - adaptation
  notes: >-
    Temporary prj-flavor repository coordinating Binky Hedgehog GmbH's path to
    a profitable, self-organizing solo-founder company with minimal CEO time
    and governance. Company canon and control plane remain in binky-control;
    archive when GOAL.md retirement gates are met.
--- a/AGENTS.md
+++ b/AGENTS.md
@ -0,0 +1,109 @@
 # prj-unattended-progress-company — Agent Instructions
 ## Repo Identity
 **Purpose:** Temporary cross-repository project to make Binky Hedgehog GmbH a
 profitable, self-organizing company with minimal CEO time and governance.
 **Domain:** infotech  
 **Repo slug:** `prj-unattended-progress-company`  
 **Workplan prefix:** `UPC-WP-`  
 **Primary durable partner:** `binky-control` (company control plane / canon)
 ---
 ## State Hub Integration
 The Custodian State Hub tracks work across domains. Prefer HTTP REST and the
 `statehub` / `custodian` CLI. MCP (`dev-hub`) is optional.
 | Context | URL |
 |---------|-----|
 | Local workstation | `http://127.0.0.1:8000` |
 | Remote via tunnel | `http://127.0.0.1:18000` |
 Canonical health endpoint: `/state/health` (not `/health`).
 ### Orient at session start
 ```bash
 # Offline brief when present
 cat .custodian-brief.md 2>/dev/null || true
 # Project goal (authoritative outcome)
 cat GOAL.md
 # Active workplans for this repo (after registration)
 curl -s "http://127.0.0.1:8000/repos/prj-unattended-progress-company/dispatch" \
  | python3 -m json.tool
 # Inbox
 curl -s "http://127.0.0.1:8000/messages/?to_agent=prj-unattended-progress-company&unread_only=true" \
  | python3 -m json.tool
 ```
 ### Log progress (required at session close)
 ```bash
 curl -s -X POST http://127.0.0.1:8000/progress/ \
  -H "Content-Type: application/json" \
  -d '{
    "summary": "what was done",
    "event_type": "note",
    "author": "agent",
    "workplan_id": "<uuid-or-omit>",
    "task_id": "<uuid-or-omit>"
  }'
 ```
 After workplan file changes:
 ```bash
 statehub fix-consistency
 ```
 ---
 ## Session Protocol
 **Start:**
 1. Read `GOAL.md` — outcome, invariants, success gates, retirement.
 2. Read `SCOPE.md` — authority boundary and participating repos.
 3. Scan `workplans/` for `ready` / `active` / `blocked` items.
 4. Prefer advancing Green/Blue work; package Yellow; batch Orange; never
   invent Red-lane authority.
 **During work:**
 - Implementation lands in participating repos, not here.
 - Link child workplans by stable ID; do not duplicate their task lists.
 - Record binding cross-repo decisions as work records (decision docs /
  hub decisions) with evidence.
 **Close:**
 1. Update workplan task statuses in files.
 2. Hand off residuals as live work records before finishing a workplan.
 3. `POST /progress/` with a concrete summary.
 4. `statehub fix-consistency` when workplan files changed.
 ---
 ## Security
 Before requesting credentials, use `warden route find "<need>" --json` when
 available. Never record secret values in project files, State Hub, workplans,
 evidence, or chat.
 <!-- REPO-AGENTS-EXTENSIONS -->
 ## Project protocol
 This is a temporary **project** repository. It has `GOAL.md`, not `INTENT.md`.
 Read order at session start:
 1. `GOAL.md`
 2. `SCOPE.md`
 3. Active files under `workplans/`
 4. Relevant sections of `binky-control` only when advancing a linked gate
 Complete only when every `GOAL.md` retirement condition is met with evidence.
--- a/GOAL.md
+++ b/GOAL.md
@ -0,0 +1,131 @@
 ---
 repo: prj-unattended-progress-company
 repo_flavor: project
 project_status: active
 started: "2026-08-09"
 reviewed: "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.
--- a/README.md
+++ b/README.md
@ -1,3 +1,23 @@
-# unattended-progress-company
+# prj-unattended-progress-company
-How to set up binky hedgehog as a solo-founder unattended-progress company.
+Temporary **project repository** for making **Binky Hedgehog GmbH** a
 profitable, self-organizing solo-founder company with **minimal CEO time and
 governance**.
 ## Start here
 | Document | Role |
 | --- | --- |
 | [`GOAL.md`](GOAL.md) | Outcome, invariants, success gates, retirement |
 | [`SCOPE.md`](SCOPE.md) | Authority boundary and participating repos |
 | [`AGENTS.md`](AGENTS.md) | Agent session protocol |
 | `workplans/` | Cross-repo coordination workplans (`UPC-WP-`) |
 Durable company canon and day-to-day control plane live in
 [`binky-control`](../binky-control), not here.
 ## State Hub
 - **Repo slug:** `prj-unattended-progress-company`
 - **Domain:** `infotech` (secondary: `agents`, `financials`)
 - **Category:** `project` (`prj-` flavor)
--- a/SCOPE.md
+++ b/SCOPE.md
@ -0,0 +1,52 @@
 # 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.
--- a/history/2026-08-09-genesis.md
+++ b/history/2026-08-09-genesis.md
@ -0,0 +1,21 @@
 # Genesis — 2026-08-09
 ## Why this project exists
 Binky Hedgehog GmbH (founded 2019) has been largely a dormant legal shell.
 `binky-control` already holds the company control plane and reactivation
 canon. What was still missing was an explicit, outcome-bounded **project**
 home for the cross-repo effort to reach:
 > profitable + self-organizing + minimal CEO time/governance
 The README seed for this repository framed the problem as “how to set up
 binky hedgehog as a solo-founder unattended-progress company.” This project
 repo is that coordination surface under the `prj-` flavor standard
 (`GOAL.md` instead of permanent `INTENT.md`).
 ## Initial registration
 - Registered in State Hub as `prj-unattended-progress-company`
 - Classification: `category: project`, domain `infotech`
 - Active hub repo goal established from `GOAL.md`
--- a/workplans/UPC-WP-0001-foundation.md
+++ b/workplans/UPC-WP-0001-foundation.md
@ -0,0 +1,155 @@
 ---
 id: UPC-WP-0001
 type: workplan
 title: "Project foundation and gate map"
 domain: infotech
 repo: prj-unattended-progress-company
 status: active
 owner: bernd
 topic_slug: infotech
 repo_goal_id: "79a2b057-b765-47ad-b5d9-c1bbc49eba43"
 created: "2026-08-09"
 updated: "2026-08-09"
 quality_dor: DoR-Ok
 quality_dor_at: "2026-08-09"
 quality_dor_by: "grok"
 quality_dor_note: "Foundation plan maps GOAL.md gates G1–G9 to evidence and child repos; no production code in this WP."
 ---
 # Project foundation and gate map
 ## Goal
 Stand up this `prj-` repository as the coordination surface for the active
 repo goal: make **Binky Hedgehog GmbH** a profitable, self-organizing company
 with minimal CEO time and governance.
 Deliverables of this workplan:
 1. Project files and State Hub registration are complete and consistent.
 2. A gate map links every `GOAL.md` success gate (G1–G9) to evidence homes and
   participating repos — without duplicating child task lists.
 3. A child-workplan map records existing and missing implementation streams
   (especially in `binky-control`).
 4. The next coordination workplans are scoped so unattended progress can start
   against open gates.
 Implementation remains in participating repositories. This workplan only
 coordinates.
 ## Register project and establish GOAL as hub goal
 ```task
 id: UPC-WP-0001-T01
 status: done
 priority: high
 ```
 Create `GOAL.md` (prj-flavor), `.repo-classification.yaml`, `SCOPE.md`,
 `AGENTS.md`, and genesis history. Register the repo in State Hub and create
 the active repo goal from `GOAL.md`.
 **Result (2026-08-09):**
 - Repo slug `prj-unattended-progress-company` registered
  (`01cc54ec-178d-4547-b17d-24bd97997987`), domain `infotech`, category
  `project`.
 - Active repo goal
  `79a2b057-b765-47ad-b5d9-c1bbc49eba43` —
  *Profitable self-organizing Binky Hedgehog GmbH with minimal CEO time and
  governance*.
 - Progress event recorded for registration + goal create.
 ## Build the gate-to-evidence map
 ```task
 id: UPC-WP-0001-T02
 status: todo
 priority: high
 ```
 Produce `architecture/gate-map.md` (or `inventory/gate-map.yaml` if more
 machine-friendly) covering every success gate G1–G9:
 | Column | Content |
 | --- | --- |
 | Gate | G1…G9 id + short title from `GOAL.md` |
 | Owning repo(s) | Where implementation and evidence live |
 | Known child workplans / loops | Stable IDs only (e.g. BINKY-WP-*) |
 | Evidence path or missing | File/URL or `missing` |
 | Status | `open` / `partial` / `met` |
 | Blockers | Human-only / external / dependency |
 Do not copy task lists from child repos. Link by ID only.
 ## Inventory current company state against G1–G9
 ```task
 id: UPC-WP-0001-T03
 status: todo
 priority: high
 ```
 From `binky-control` (and only other repos when the gate demands it), write a
 baseline snapshot under `inventory/`:
 - Admin / legal / tax / banking posture (G1)
 - Company OS artefacts in force (G2)
 - Autopilot / dogfood / executor evidence (G3)
 - Founder-load measurement approach or gap (G4)
 - Offer and revenue path status (G5–G7)
 - Decision / office-hour queue thinness (G8)
 Prefer pointers into existing `binky-control` docs
 (`CompanyReactivationPlan.md`, `SuccessMilestones.md`, workplans
 BINKY-WP-0001…0007, audits) over rewriting canon here.
 ## Establish the child-workplan map
 ```task
 id: UPC-WP-0001-T04
 status: todo
 priority: high
 ```
 Create `architecture/child-workplan-map.md` listing:
 1. **Existing** child workplans that already advance G1–G9 (status + gate
   tags).
 2. **Gaps** — gates with no live child workplan or residual.
 3. **Recommended next child streams** (one line each; create files only in
   the owning repo, not here).
 Initial known participants: `binky-control`, `ops-warden`, ecosystem pillars
 as referenced by offers/delivery. Update `SCOPE.md` participating table if
 the map adds repos.
 ## Scope the next project coordination workplans
 ```task
 id: UPC-WP-0001-T05
 status: todo
 priority: medium
 ```
 Based on T02–T04, draft (as `proposed` files under `workplans/`, or as a
 single sequencing note if one cluster dominates) the next `UPC-WP-*` plans
 for open gate clusters, for example:
 - Company vessel close-out (G1–G2 residuals)
 - Unattended dogfood + load envelope (G3–G4)
 - First external offer and paid revenue (G5–G6)
 Each draft must name the parent repo goal, linked child IDs, and acceptance
 evidence expected back into this project — still without owning production
 implementation.
 ## Done when
 - T01 remains done and hub/file IDs stay consistent after `statehub
  fix-consistency`.
 - Gate map, baseline inventory, and child-workplan map exist and cover G1–G9.
 - At least one next `UPC-WP-*` (or explicit sequencing decision) is ready for
  review so foundation can finish without leaving an unowned vacuum.
 - Residuals from this workplan are live work records (next WPs or intakes),
  not prose-only leftovers.