prj-unattended-progress-company/workplans/UPC-WP-0001-foundation.md

id	type	title	domain	repo	status	owner	topic_slug	repo_goal_id	created	updated	quality_dor	quality_dor_at	quality_dor_by	quality_dor_note
UPC-WP-0001	workplan	Project foundation and gate map	infotech	prj-unattended-progress-company	active	bernd	infotech	79a2b057-b765-47ad-b5d9-c1bbc49eba43	2026-08-09	2026-08-09	DoR-Ok	2026-08-09	grok	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

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

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

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

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

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.