2026-07-16 02:34:24 +02:00
|
|
|
|
# INTENT
|
|
|
|
|
|
|
2026-07-16 03:15:11 +02:00
|
|
|
|
> Status: **v1.0 — ratified 2026-07-16** (DEC-2026-001, approved with edits). Owner: Bernd Worsch. To be revised as the company canon grows.
|
2026-07-16 02:34:24 +02:00
|
|
|
|
|
|
|
|
|
|
## Why this company exists
|
|
|
|
|
|
|
|
|
|
|
|
Binky Hedgehog GmbH (founded 2019, until now a dormant legal shell) becomes the
|
|
|
|
|
|
commercial operating company for an ecosystem of **operational knowledge
|
|
|
|
|
|
infrastructure**. Its long-term identity is **Operational Knowledge GmbH — "OK"**.
|
|
|
|
|
|
|
|
|
|
|
|
The thesis:
|
|
|
|
|
|
|
|
|
|
|
|
> Companies increasingly fail not because they lack tools, but because their
|
|
|
|
|
|
> operational knowledge is fragmented, implicit, ungoverned, and not executable.
|
|
|
|
|
|
> This company provides products and services that turn operational knowledge
|
|
|
|
|
|
> into structured, governed, agent-ready company capabilities.
|
|
|
|
|
|
|
|
|
|
|
|
## What the company does
|
|
|
|
|
|
|
|
|
|
|
|
The company is the **economic crystallization point** of the ecosystem — it is
|
|
|
|
|
|
not the ecosystem itself.
|
|
|
|
|
|
|
|
|
|
|
|
- **Package** capabilities from the ecosystem into offers.
|
|
|
|
|
|
- **Sell and deliver** those offers to earn revenue.
|
|
|
|
|
|
- **Operate itself** on the same capabilities (dogfooding), turning every
|
|
|
|
|
|
internal operational pain into product evidence.
|
|
|
|
|
|
- **Feed learning back** into the ecosystem so capabilities mature.
|
|
|
|
|
|
|
|
|
|
|
|
The ecosystem pillars and their roles:
|
|
|
|
|
|
|
|
|
|
|
|
| Pillar | Role |
|
|
|
|
|
|
| --- | --- |
|
|
|
|
|
|
| **Coulomb** | Discover, cluster, mature, and package reusable capabilities |
|
|
|
|
|
|
| **Net Kingdom** | Identity, access, security, governance — make capability governable |
|
2026-07-16 03:15:11 +02:00
|
|
|
|
| **Railiance** | Reliable deployment and operations — turn code into saas ecosystems and products |
|
|
|
|
|
|
| **Operational Knowledge** | Value from experience — drive your business based on what you know |
|
2026-07-16 02:34:24 +02:00
|
|
|
|
|
|
|
|
|
|
## The core loop: the OK Flywheel
|
|
|
|
|
|
|
|
|
|
|
|
1. An internal operational problem appears.
|
|
|
|
|
|
2. The company solves it with an ecosystem capability.
|
|
|
|
|
|
3. The solution is documented and instrumented.
|
|
|
|
|
|
4. The capability becomes reusable.
|
|
|
|
|
|
5. The reusable capability becomes a product or service.
|
|
|
|
|
|
6. Customer usage creates feedback.
|
|
|
|
|
|
7. Feedback improves the ecosystem.
|
|
|
|
|
|
8. The improved ecosystem improves company operations.
|
|
|
|
|
|
|
|
|
|
|
|
## How the company is operated
|
|
|
|
|
|
|
|
|
|
|
|
The company runs as a **human-on-the-loop, unattended-progress stack**: a solo
|
|
|
|
|
|
founder with ~1–3 hours per day outside business hours and roughly two
|
|
|
|
|
|
office-hour days per month.
|
|
|
|
|
|
|
|
|
|
|
|
Operating rules that follow from this:
|
|
|
|
|
|
|
|
|
|
|
|
- **"Ask Bernd" is never the default.** Agents continue with the safest useful
|
|
|
|
|
|
next step; uncertainty triggers research, comparison, or preparation — never
|
|
|
|
|
|
idle waiting.
|
|
|
|
|
|
- Work is classified into **autonomy lanes** (Green/Blue/Yellow/Orange/Red,
|
|
|
|
|
|
defined in `AutonomyPolicy.md`). Green and Blue work proceeds unattended;
|
|
|
|
|
|
Yellow becomes prepared decision packages; Orange batches to office-hour
|
|
|
|
|
|
days; Red stays human-only.
|
|
|
|
|
|
- Founder attention is the scarcest resource and is **budgeted explicitly**:
|
|
|
|
|
|
concise briefs, evidence-backed decision cards, approve/reject options.
|
|
|
|
|
|
- Valid system states are *proceeding*, *prepared for review*, or *deferred by
|
|
|
|
|
|
policy* — never *waiting because unsure*.
|
|
|
|
|
|
|
|
|
|
|
|
## What must remain human
|
|
|
|
|
|
|
|
|
|
|
|
Signing, strategic commitments, bank and payment execution, contracts,
|
|
|
|
|
|
sensitive legal/HR/security decisions, external commitments of the company,
|
|
|
|
|
|
risk acceptance, and final authority on direction. Agents prepare; the founder
|
|
|
|
|
|
decides.
|
|
|
|
|
|
|
|
|
|
|
|
## What counts as success
|
|
|
|
|
|
|
|
|
|
|
|
The success ladder (detail in `SuccessMilestones.md`):
|
|
|
|
|
|
|
|
|
|
|
|
```text
|
|
|
|
|
|
S1 company administratively clean
|
|
|
|
|
|
S3 first internal dogfood loop works
|
|
|
|
|
|
S5 first paid revenue
|
|
|
|
|
|
S6 repeatable productized service
|
|
|
|
|
|
S9 rename to Operational Knowledge GmbH makes sense
|
|
|
|
|
|
S12 acquiring ok.com becomes a rational decision
|
|
|
|
|
|
```
|
|
|
|
|
|
|
|
|
|
|
|
The rename to Operational Knowledge GmbH is a **milestone, not a starting
|
|
|
|
|
|
point** — it happens when the name clarifies the business more than it creates
|
|
|
|
|
|
friction (first repeatable offer, paying customer or serious pilot, coherent
|
|
|
|
|
|
messaging, dogfood evidence).
|
|
|
|
|
|
|
|
|
|
|
|
## Near-term aim
|
|
|
|
|
|
|
|
|
|
|
|
Make Binky Hedgehog GmbH practically operable and strategically aimed at
|
|
|
|
|
|
becoming Operational Knowledge GmbH: reactivate the legal/administrative
|
|
|
|
|
|
shell, map the ecosystem, form first offers (services before software), and
|
|
|
|
|
|
run the company on its own primitive control plane — this repo.
|
|
|
|
|
|
|
|
|
|
|
|
## This repo
|
|
|
|
|
|
|
|
|
|
|
|
`binky-control` is the company brain: the canon (intent, policies, plans),
|
|
|
|
|
|
the queues (decisions, office-hour, autopilot work), and the registries that
|
|
|
|
|
|
let agents and the founder share situational awareness with executable next
|
|
|
|
|
|
steps. Sister repo: `unattended-progress-company`.
|
